WebSphere Today

You delete then create the same users or groups in your LDAP directory. After that, access to Portal pages and Web Content Management content does not work for them. What steps are needed to complete this task?

[Read more →]

This list provides information regarding all known “Unsupported Products” as discussed in the WebSphere® Portal Support Statement in the version 5.1 or 6.0 Information Center. This list is not intended to be exhaustive. In the absence of an explicit listing of a product and unless told otherwise by the Portal Support team, customers should assume that the status of the product is unknown and that the product may be incompatible with WebSphere Portal.

[Read more →]

This list provides information regarding all known “Unsupported Products” as discussed in the IBM® WebSphere® Portal Support Statement in the version 6.1 Information Center. This list is not intended to be exhaustive. In the absence of an explicit listing of a product and unless told otherwise by the Portal Support team, customers should assume that the status of the product is unknown and that the product may be incompatible with WebSphere Portal.

[Read more →]

A comprehensive list of recommended, generally available (GA) fixes for current IBM® WebSphere® Portal and Lotus/Workplace Web Content Management™ server releases. Tables are organized by version in the order they were released.

[Read more →]

Before migrating an existing IBM® WebSphere® Portal installation to WebSphere Portal V6.1, you must apply the required interim fixes to ensure that the earlier version is at the required level.

[Read more →]

The virtual user and group principals such as the “anonymous” user, the “[All Users]” group and the “[All Authenticated Portal

[Read more →]

defect 218439

[Read more →]

Defect 215284

[Read more →]

PZN updated JCR team recommends the use of QUERYOPTION_LEAFTREE_TRAVERSALDEPTH=1 setting for rule

[Read more →]

Rules to return web content also return web components. The reverse is also true - rules returning web components also

[Read more →]

for defect 201620

[Read more →]

Unique identifier can not be selected in PZN 1. Navigate to Personalization > Business Rules

[Read more →]

Information in the infocenter is incorrect at the information for the favorites loop this section of code

[Read more →]

The <portletExt:portalRenderURL> tag provided by WebSphere Portal applies to JSR standard portlets. When employed to generate URLs within standard portlets to point to IBM portlets, there are limitations with regards to how parameters are passed on to the target portlet, that is, not all supplied query parameters might be accessable in the addressed portlet.

[Read more →]

Where can you find documentation on WebSphere® Portal performance testing and analysis?

[Read more →]

This document describes the limits of IBM remote technical support available to you when implementing custom interface artifacts or applications in your IBM® WebSphere® Portal environment.

[Read more →]

As a consequence of the database domain split federated database domain home objects were introduced. DatabackendExceptions are

[Read more →]

Subsequent updates on attributes of the current user does not immediately take effect (e.g. for preferredLanguage attribute)

[Read more →]

The migration of database domain ‘JCR’ on DB2 for z/OS from releases V6.0.x to V6.1 might fail if a high number of roles are defined. In that case error SQL -904 is reported on update of table ROLE_INST.

[Read more →]

You notice slow WebSphere® Portal initialization with messages WTRN0006W and WSVR0605W.

[Read more →]

The migration engine when importing draft documents does not mark the associated published items as checked out. The failure

[Read more →]

The migration engine will automatically create a site (called ‘Orphaned content site’) and a site area (called ‘Orphaned

[Read more →]

When running the portal-post-upgrade task where your 6.1 server is not pointing to the same physical ldap as your previous

[Read more →]

Objects that were needed temporarily during XMLAccess requests remain in memory. The number of objects depends on the

[Read more →]

In the WAS fixpacks 6.0.2.29 and 6.1.0.17 the value of the WASReqURL cookie was changed from relative URL to:

[Read more →]