Category: portal

On a customer site, all windows machines has a GPO to turn on the IE compatibility mode.

The new WebSphere Portal does not work well with this compatibility mode.

To solve the problem we add the following on the Apache Web Server

Header set X-UA-Compatible “IE=Edge”

The header above tell the IE browser to not use compatibillity mode when accessing the new portal.



From IBM L3 support:

“WebSphere Portal does not explicitly claim support for Oracle Data Guard. It is our understanding that Oracle Data Guard is an extension
of the Oracle Database product. We do support the Oracle Database as isted in our “Supported software” documentation. Unless Oracle Data
Guard limits functionality or impacts the behavior of the Oracle Database product in an intransparent manner or requires changes to the
Portal database object definitions, we do not see a reason why WebSphere Portal would not work in that setup. In other words: If the
database system, that is used by the customer, behaves like a regular Oracle Database, it should work. In case an issue is observed, we may
have to ask the customer to reproduce that issue on a system that is mentioned explicitly in our “Supported software” document.”


Documents for collecting troubleshooting data for IBM WebSphere Portal 8.5 and 9.0 aid in problem determination and save time resolving Problem Management Records (PMRs).

The following data collection documents contain instructions for specific components or scenarios. The wpcollector tool can be leveraged with such instructions to gather and optionally send the data. If one of the product components or scenarios below matches your symptom or the part of the product with which you are experiencing problems, follow the instructions in the associated data collection document.


Component: Link:
General 1962321
Installation 1962645
XML Configuration Interface (XMLAccess) 1451423
ConfigEngine 1968713
Configuration Wizard 1963901
Migration 1963147
Runtime Operations:
OutOfMemoryError 1316563
Crash 1316516
Performance, hang, or high CPU issues 1316528
Configuring Security 1593369
Login (including Impersonation) 1592791
Portal User Management Architecture (PUMA) 1592792
Virtual Portal 1593367
Session Management 1579527
Tivoli Access Manager Integration 1579530
Computer Associates eTrust Siteminder Integration 1243923
Step-up and Remember Me 1377161
People Finder 1458362
Credential Vault 1313734
Portal Access Control (PAC) 1450830
Directory Search / People Picker 1966956
Outbound HTTP Connection 1998965
Content Management:
Web Content Manager 1673017
Managed Pages 1960989
Syndication 1989372
Modular-based Themes 1616359
Web Application Bridge (WAB) 1647465
JavaServer Faces (JSF) 1198110
Mobile Portal Accelerator 1673323
Struts Portlet Framework 1468819
Web Services for Remote Portlets (WSRP) 1468821
Common PIM Portlets (CPP) 1468956
Remote Cache 1468824
Script Portlet 1690618
WebDAV 1497122


portal WebSphere Portal

fix portal

One of the tuning activities is to turn on GZIP compression for HTTP requests.

This tuning can save lots of network traffic and your page will load in a short time.

Just put the lines bellow on the httpd.conf and restart the server

LoadModule deflate_module modules/

LoadModule headers_module modules/

#Only the specified MIME types will be compressed.

AddOutputFilterByType DEFLATE application/atom+xml
AddOutputFilterByType DEFLATE application/atomcat+xml
AddOutputFilterByType DEFLATE application/javascript
AddOutputFilterByType DEFLATE application/json
AddOutputFilterByType DEFLATE application/octet-stream
AddOutputFilterByType DEFLATE application/x-javascript
AddOutputFilterByType DEFLATE application/xhtml+xml
AddOutputFilterByType DEFLATE application/xml
AddOutputFilterByType DEFLATE text/css
AddOutputFilterByType DEFLATE text/html
AddOutputFilterByType DEFLATE text/javascript
AddOutputFilterByType DEFLATE text/plain
AddOutputFilterByType DEFLATE text/xml
AddOutputFilterByType DEFLATE text/xsl
# Ensures that images and executable binaries are not compressed
SetEnvIfNoCase Request_URI \\.(?:gif|jpe?g|png|exe)$ no-gzip dont-vary
# Ensure that proxies do not deliver the wrong content
Header append Vary User-Agent env=!dont-vary
SetEnvIf Request_URI ^/acce(.*) no-gzip dont-vary

performance portal

IBM Digital Experience V9.0 offerings provide integration with IBM Cognitive Engagement solutions
and enable hybrid cloud capability to deliver engaging multichannel experiences.
Starting with CF13, combined cumulative fixes apply to both WebSphere Portal version 8.5 and 9.0. The IBM Knowledge Center for Version 9.0 contains installation documentation and documentation on how to migrate your IBM WebSphere Application Server. After you install Version 9, return to the Version 8.5 IBM Knowledge Center for information on how to configure and use WebSphere Portal.

You can purchase an extra license (WebSphere Portal Version 9.0) to integrate WebSphere Portal with Watson Content Hub. The license gives you access to the Asset Picker portlet. Use the portlet to select assets (files, videos, and images) that are stored in the content hub and publish them on your site.
See the announcement letter here


Today i receive a disk full alarm from my portal server. As usual i delete some logs and files left behind, but for this time this does not solve the issue.

Search for big files or what folder is bigger on linux is hard using du. Googling i found a nice toll and what i found was a big surprise.

I setup NCDU (NCurses Disk Usage) is a curses-based version of the well-known “du”, and provides a fast way to see what directories are using your disk space.

The setup is easy:

1 - yum install ncurses-devel ncurses

2 – download ncdu

3 – untar the file

4- ./configure –prefix=/usr

5 – make && make install

To run just type ncdu at / and the tool will scan your entire server.

Navigating on the toll i found a big folder inside of the connections portlets called “logs” full of files 5GB. The path on my server is :


I check my server and no tarces are on.

Why these logs are there? I don’t know yet.  I just clean my server.

NCDU did the trick !  Thanks.

Linux portal

If you are not sure what your port number is, use the list-server-ports command to determine the port number. Change to the wp_profile_root/ConfigEngine/log. Run the list-server-ports task to generate the WebSphere_Portal_PortMatrix.txt file. For example: ./ list-server-ports -DWasPassword=password.

Change to the /opt/IBM/WebSphere/AppServer/profiles/cw_profile/ConfigEngine. Run the list-server-ports task to generate the server1_PortMatrix.txt file. For example: ./ list-server-ports -DWasPassword=password.

Bellow the content of PortalMatrix.txt file

Ports for WebSphere_Portal :

During the configuration process, you might need to following URLs to access different administration user interfaces.

Use the following default URLs to access IBM® WebSphere Portal V8.5,  the WebSphere Integrated Solutions Console, and the Configuration Wizard:

IBM WebSphere Portal V8.5



WebSphere Integrated Solutions Console



Configuration Wizard




There is a vulnerability in IBM WebSphere Application Server that could allow an HTTP response splitting attack in Channel.

More information on this link

portal segurança WebSphere WebSphere Portal

Quando habilitamos a segurança LDAP de um portal stand alone o nome do usuário administrador pode conter espaços, por exemplo cn=wpsadmin,dc=Contas Admin,dc=Acme mas em uma configuração do portal em cluster e com suporte a realm (wmmur) o nome não pode conter espaço em lugar algum seja no CN ou nas unidades organizacionais.

Esta dica foi enviada pelo Paulo que está instalando um ambiente em cluster nesta semana.


A IBM ainda não homologou o IE 8 para ser utilizado como “cliente” do WebSphere Portal. De acordo com o TN 1389292 o IE 8 somente será compatível com versões e com a versão ou seja em breve estaremos aplicando fixes nos ambientes para mais uma mudança de browser, claro que ainda tem de ver o suporte para o FireFox 3.5.
A falta de padronização dos browsers causa muita dor de cabeça…


Um log que pode ser muito útil para rastrear as “tarefas” administrativas pode ser configurado no Portal. O seriço é o Auditing Service que gera um log de vários eventos tais como criação de portlets entre outras. Para ver mais detalhes veja neste link.
O serviço tem de ser habilitado alterando-se o arquivo e reiniciar o portal