IBM® WebSphere® Portal - Express for Multiplatforms (iSeries) V5.0.2 Cumulative Fix 3 (5.0.2.3)

Release notes

Last updated April 28, 2006

This document contains the Release Notes for WebSphere® (R) Portal. The Release Notes contain information about workarounds for known limitations and supplemental information on topics that might also be covered in the WebSphere® Portal Information Center.

These release notes include the following major topics:

 

Important downloads and interim fixes

The support site and the Portal catalog provide additional information and downloads.

 

Additional documentation

 

WebSphere® Portal Information Center

WebSphere® Portal is shipped with an Information Center that contains information about the following topics:

  • Product prerequisites
  • Planning for installation
  • Installing WebSphere® Portal

  • Administering the portal
  • Developing portals and portlets
  • Troubleshooting

The latest version of the WebSphere® Portal Information Center is available on the Web at: http://www.ibm.com/websphere/portal/library

 

Additional information and downloads on the Web

In addition to shipped documentation, we can find additional information on the Web:

 

Known limitations for WebSphere® Portal

This section describes known limitations for WebSphere® Portal. Some limitations require that we perform workarounds.

 

Installation

 

Related to installing WAS

 

Problem: Receive error messages with incorrect version numbers or incorrect PTF information

While installing WebSphere® Portal on an i5/OS (V5R3) iSeries machine, we might receive error messages that refer to V5R2. For example, if we are missing required PTF groups, we may receive a message indicating that the SF99245 PTF group is required. If we see this message, we are actually missing SF99287 or SF99288.

Solution:Refer to the WebSphere® Portal Express V 5.0.2.2 documentation for a list of all required PTFs. Verify that they are all installed and applied. The error messages will no longer display. 92986

 

Problem: Incompatible Embedded Messaging configurations between Deployment Manager and managed nodes

If we use WAS V.5.0.x, the Deployment Manager system and all nodes must be installed with the same features. If the features installed on the Deployment Manager system are different from the features installed on any of the nodes, WAS behavior can be unpredictable.

Files related to the Embedded Messaging feature might be installed on the Deployment Manager machine even if we did not select this feature when we installed the Deployment Manager. For example, these files might be installed when we install WAS Enterprise or fixes on the Deployment Manager machine.

Solution: To check for files related to the Embedded Messaging feature in our environment:

83180

 

Problem: Upgrading from WAS Version 5.0 to 5.0.2 may fail or hang

The installation process of upgrading from WAS Version 5.0 to 5.0.2 fails or hangs.

Solution: Cancel the installation program, uninstall WAS and WebSphere® Portal, and then proceed using the following steps to install manually:

  1. Install WAS V5.0
  2. Upgrade to WAS V5.0.1
  3. Upgrade to WAS V5.0.2
  4. Apply WAS V5.0.2 cumulative fix 2
  5. Apply WAS VPME 5.0.2 cumulative fix 2
  6. Apply WAS V5.0.2 cumulative fix 6
  7. Proceed with the installation of WebSphere® Portal 5.0.2.2. We may refer to the WebSphere® Portal V5.0.2.2 Readme at http://www.ibm.com/websphere/portal/library.

Refer to the WAS support site for additional help with uninstall and installation procedures: http://www.ibm.com/software/webservers/appserv/was/support/ 98027

 

Related to installing WebSphere® Portal

 

Problem: Server status does not match the installation completion interface

WebSphere® Portal installation program tells us to verify the portal server is installed at http://<hostname>:9081/wps/portal%gt; after installation is finished. However, after WebSphere® Portal V5.0.2.3 installation, the portal server might not start automatically after installation.

Solution: Start WebSphere® Portal manually after installation.122579.RN

 

Problem: UNINSTALL-WP-PTF-5021 task fails on iSeries when attempting to recover from WP-PTF-5021 task failure

When installing WebSphere® Portal 5.0.2 Cumulative Fix 1 (5.0.2.1) on the iSeries platform, it is possible that the WP-PTF-5021 task could fail, due to incorrect syntax or parameters, for example. In this situation we are instructed to run the UNINSTALL-WP-PTF-5021 task before running the WP-PTF-5021 task again. However, when attempting to run the WP-PTF-5021 task the second time, the following error can display:

 BUILD FAILED                       
 Duplicate target: `WP-PTF-5021'

Solution: To correct the duplicate target error, complete the following steps:

  1. Remove the WP_PTF_5021_TEMP.xml file from the /qibm/userdata/webas5/base/<instance>/portalserver5/config/include directory.
  2. Run the WP-PTF-5021 task again, as described in the WebSphere® Portal 5.0.2.1 readme instructions.
84235

 

Problem: Receive "The Resource was not found in the portal" message

After installing the portal server, we might receive this message logged in the wps*.log: "com.ibm.wps.command.xml.XmlCommandException: XMLC0025E: The Resource was not found in the portal."

2003.12.05 19:55:11.527 E com.ibm.wps.command.xml.Engine XMLEngine
  GNRL0002E: Exception occurred. - StackTrace follows...

2003.12.05 19:55:11.529 E com.ibm.wps.command.xml.Engine XMLEngine
  com.ibm.wps.command.xml.XmlCommandException: XMLC0025E: The Resource was not found in the portal, either because it does not exist or because we have not specified an identifying attribute in the XML input. [content-node uniquename=wps.Portal Settings]
      java/lang/Throwable.<init>()V+4 (Throwable.java:73) 
      java/lang/Exception.<init>()V+1 (Exception.java:24) 
      com/ibm/portal/WpsException.<init>(Lcom/ibm/wps/util/MessageCode;[Ljava/lang/Object;)V+0 (WpsException.java:92) 
      com/ibm/portal/WpsException.<init>(Lcom/ibm/wps/util/MessageCode;[Ljava/lang/Object;Ljava/lang/Throwable;)V+0 (WpsException.java:113) 
      com/ibm/wps/command/xml/XmlCommandException.<init>(Lcom/ibm/wps/util/MessageCode;[Ljava/lang/Object;Lcom/ibm/wps/command/xml/ConfigItem;Ljava/lang/Throwable;)V+0 (XmlCommandException.java:41) 
      com/ibm/wps/command/xml/UpdateEngine.locateItem(Lcom/ibm/wps/command/xml/ConfigItem;)V+0 (UpdateEngine.java:270) 
      com/ibm/wps/command/xml/ExportEngine.exportPortal()V+0 (ExportEngine.java:76) 
      com/ibm/wps/command/xml/Engine.process()V+0 (Engine.java:202) 
      com/ibm/wps/command/xml/XmlCommand.execute()V+0 (XmlCommand.java:122) 
      com/ibm/wps/command/xml/XmlCommandServlet.process(Ljava/io/InputStream;Ljava/io/OutputStream;Ljava/lang/String;)V+0 (XmlCommandServlet.java:157) 
     .
           .
           . 
      com/ibm/ws/http/HttpConnection.readAndHandleRequest(Z)V+0 (HttpConnection.java:562) 
      com/ibm/ws/http/HttpConnection.run()V+0 (HttpConnection.java:373) 
      com/ibm/ws/util/ThreadPool$Worker.run()V+0 (ThreadPool.java:566)

Solution: We can ignore this message. 70764.RN

 

Problem: Installation fails in DBCS environment

In some double-byte character set (DBCS) environments, installation of WebSphere® Portal using the Install and Configure option might fail. Symptoms of this are exceptions in the ConfigTrace.log file that indicate a malformedUrlException.

Solution: To avoid this problem, do one of the following:

71331.RN

 

Problem: Installation log files not created in DBCS environment

When installing WebSphere® Portal in a double-byte character set (DBCS) environment, the installation log files installtraces.txt, installmessages.txt, and portalinstall.lockfile are not created due to an invalid CSSID error.

Solution: We can create the installtraces.txt and installmessages.txt log files before installation, and set their CSSIDs to valid values. To do this:

  1. Create two empty text files named installtraces.txt and installmessages.txt in the directory /tmp/InstallShield.
  2. On an OS/400 command line, run the following commands: 
    CHGATR OBJ('/tmp/InstallShield/installtraces.txt') ATR(*CCSID) VALUE(819)
    
CHGATR OBJ('/tmp/InstallShield/installmessages.txt') ATR(*CCSID) VALUE(819)

This workaround should not be used for portalinstall.lockfile, as it might cause problems with the installation.70944.RN

 

Problem: Additional information to step 3 in Information Center under Installing WebSphere® Portal in a cluster environment

The following information should be included with step 3 of the section "Installing WebSphere® Portal in a cluster environment."

The "Apply fix to external messaging" button should not be checked if the external messaging (MQ series) application is not installed (This application is installed with the base installation of WebSphere® Application Server for WebSphere® Portal). When this button is checked, the installation will try to apply the fix to external messaging (MQ series) application. The application is not there so its absence will cause the Fix Pack installation to fail.

Solution: Do not check the Apply fix to external messaging button in the WAS Network Deployment installation program. 71970

 

Problem: WebSphere® Portal PTF will not install

If the Fix Pack installation fails we will receive the following message, 

 
Fix pack installation has failed. Consult
 /opt/WebSphere/PortalServer/version/log/20040128_214458_WP_PTF_502_selective-install.log for error details.
End of [./updatePortal.sh ]

This log then points us to a component log that has the following error message.

 Error 196 -- Failed to prepare instance data.

The program that updatePortal.bat/sh (the Portal Update Installer) starts is expecting directories and not files in that directory. If there is a file in <WAS_HOME>/config/cells/<cell>/applications, the component log shows up in <WP_HOME>/version/log/.

Solution: Move the file to another directory, preferably outside the WebSphere® Portal directories and then proceed with the installing of the Fix Pack.

If we receive Error 196 and do not have a file in our directory, contact our Customer Support representative.73099.RN

 

Problem: After installation of PTF 5722SS1 SI11277, the portal server configuration fails

The portal server configuration fails with the following message in the these log files.

/qibm/userdata/webas5/base/instanceName/PortalServer5/log/addwpsinst.log
/qibm/userdata/webas5/base/instanceName/PortalServer5/log/WPSWIZARD_timestamp_addwpsinst.log

BUILD FAILED                                                                                                                        
file:/QIBM® /ProdData/PortalServer5/config/actions/inst_cfg.xml:49: 
Execute failed: java.io.IOException: chmod -R 777 
/QIBM® /UserData/WebAS5/Base/WAS5Portal4/PortalServer5: not found

Solution: We must select the 'Install Only' option during the portal server installation, and then modify or replace the inst_cfg.xml file as described below before running the portal server configuration (either manually or using the iSeries Web Administration Portal configuration wizard).

To see if PTF 5722SS1 SI11277 PTF is applied, run the following iSeries CL command:

    DSPPTF LICPGM(5722SS1) SELECT(SI11277)

If the PTF listed above is applied, modify /QIBM® /ProdData/PortalServer5/config/actions/inst_cfg.xml as described below.

Perform the following steps to modify the file /QIBM® /ProdData/PortalServer5/config/actions/inst_cfg.xml after Portal is installed successfully:

  1. Rename the existing file to inst_cfg.xml_old
  2. Modify the file starting at line #49 and save the following changes. 
       
CHANGE:   
  <target name="change-log-file-permissions">
      <exec executable="chmod -R 777 ${WpsInstallLocation}"/>
   </target>
   TO:
   <target name="change-log-file-permissions">
      <exec executable="/usr/bin/chmod">
         <arg line="-R 777 ${WpsInstallLocation}"/>
      </exec>
   </target>
  3. Configure the portal server.
73207/72689.RN

 

Problem: Migrating from WebSphere® Portal 4.2 with WebSphere® Portal content publishing resources

If we are migrating from WebSphere® Portal 4.2 with WebSphere® Portal content publishing resources, we need to manually create tables for DB2/390.

Solution: If we are migrating from WebSphere® Portal 4.2 to WebSphere® Portal 5.02 on DB2/390 and WebSphere® Portal content publishing resources exist, we must manually create the required WebSphere® Portal content publishing tables prior to migration. See Installing > Databases > Creating databases and users for DB2 on z/OS and OS/390 and Installing > Database > Disabling dynamic table creation > Creating tables manually in the WebSphere® Portal Information Center for more information on manual table creation.72802.RN

 

Problem: The remote IBM® HTTP Server times-out when running the cumulative fix configuration task

A HTTP time-out exception occurs during the WPSConfig task when the WebSphere® Portal environment contains a remote IBM® HTTP Server

Solution: Edit the remote IBM® HTTP Server httpd.conf file before running the configuration task.

  1. Recover from a failed configuration. Follow the steps for this procedure as listed in the Installing WebSphere® Portal V5.0.2 Cumulative Fix 1 (5.0.2.1) readme.
  2. Edit the remote httpd.conf file:

    1. Uncomment out #Listen 80
    2. Comment out the lines:

      • AfpaEnable
      • AfpaCache on
      • AfpaPort 80
      • AfpaLogFile "C:/ProgramFiles/IBM® HttpServer/logs/afpalog" V-ECLF
  3. Save and close the file.
  4. Stop and restart the remote HTTP Server.
  5. Continue with the configuration task of the cumulative fix.
78314

 

Problem: Domain not found error after migration

After performing a successful migration, WebSphere® Portal resources show the following error: Domain not found for the xxxx resource, where xxxx is the selected resource. No error messages appear in the log files.

Solution: Additional steps are needed to migrate the authoring component of WebSphere® Portal content publishing.

Before running the migrate-wpcp-author, perform the following steps.

  1. Migrate V4 resources to V5 resource in WebSphere® Studio Application Developer and add the migrated resource classes to the WebSphere® Portal classpath.
  2. If we have automatic table creation turned off, which is the default mode for DB2 on z/OS and 390, create resource tables.
  3. Issue the following command to start WebSphere® Portal: startServer WebSphere_Portal
  4. Perform the following steps to migrate the runtime component for resource collection registration.

    • Edit or update mig-wpcp.properties with our configuration settings.
    • Execute to begin the runtime migration: WPMigrate.sh migrate-wpcp
  5. Perform the following steps to migrate the authoring component:

    • Edit or update mig-wpcp-author.properties with our configuration settings.
    • Continue the migration process by running the following command: WPMigrate.sh migrate-wpcp-author
76626

 

Problem: Unable to access WebSphere® Portal on some nodes after synchronization in a cluster

After applying the WebSphere® Portal V5.0.2 Cumulative Fix 1 (V5.0.2.1) in a clustered environment, and performing a full synchronization, we might be unable to access WebSphere® Portal on some nodes after restarting the cluster.

Solution: Check the the WebSphere® Portal Server logs on the nodes for the following error: 

Host/WebGroup Not Found : The web group default_host/wps has not been defined

If we see this error, stop and restart WAS and the WebSphere® Portal Server on the affected nodes.

 

Related to Installing Various Components

This section includes known restrictions and workarounds for WebSphere® Portal and supported components.

 

Problem: Running Domino Application Server on a machine with an existing mail server

If a mail server is running on the same machine as the Domino Application Server, the Domino Application Server will fail to start its mail server, report that port 25 is in use, and that it cannot start the service.

Solution: There are two ways to fix this problem:

13875

 

Problem: Cancelled jobs remain in Tasks folder

When using the workflow feature, cancelled jobs might remain in the user's Tasks folder. This problem does not affect the Document Manager performance.71592.RN

 

Problem: Using a database index to speed up processing of large portal XML imports

If we want to process an XML request with a high volume of import statements, we might be able to shorten processing time considerably by adding an index to the COMP_INST table on column COMPOS_REF. This can be done manually by the database administrator.

Solution: Use the following SQL statement:

For Microsoft SQL Server:

CREATE INDEX IX320F ON @DbUser@.COMP_INST (COMPOS_REF)

For all other DBMS:

CREATE INDEX @DbUser@.IX320F ON @DbUser@.COMP_INST (COMPOS_REF)

Replace the token @DbUser@ by the database schema used for our portal database objects, that is, by the schema in which COMP_INST is located.

We only have to add the index once. It will then be used for later requests.

If the database uses this index instead of table scans, processing time might decrease considerably. For example when creating 25,000 portal pages, using the index might speed up processing time by a factor of up to 100, depending on our portal installation.71313.RN

 

Problem: Index structure of Portal Search not backward compatible

The index structure of Portal Search is not backward compatible between WebSphere® Portal V5.0 and fix pack 5.0.2. For Portal Search, we need to export and import our data collections when applying fix pack 5.0.2

Solution: If we want to preserve our data collection when applying fix pack 5.0.2, export the data collections before applying the fix pack. After the export, delete the data collections from the portal using the Manage Collections portlet. After applying the fix pack, import our data collections back into the portal.72758

 

Problem: Tivoli® Access Manager SvrSslCfg task fails

The TAM SvrSslCfg task might fail on WebSphere® Portal 5.0.2.1 installations with the following stacktrace in <wp_root>/log/configwizard.log:

Configuration failed.

    Exception in thread "main" com.tivoli.pd.jutil.PDExceptionjava.lang.reflect.InvocationTargetException
        at com.tivoli.pd.jcfg.SvrSslCfg.main(SvrSslCfg.java:43)
    java.lang.reflect.InvocationTargetException: com.tivoli.pd.jutil.PDException[
    0x307a8074
    Cannot contact server.
    2]
            at com.tivoli.pd.jutil.n.a(n.java:8)
            at com.tivoli.pd.jadmin.PDAppSvrConfig.configureAppSvr(PDAppSvrConfig.ja
    va:57)
            at com.tivoli.pd.jcfg.SvrSslCfg.config(SvrSslCfg.java:247)
            at java.lang.reflect.Method.invoke(Native Method)
            at com.tivoli.pd.jcfg.SvrSslCfg.main(SvrSslCfg.java:715

This error occurs because the JRE version shipped in WebSphere® Application Server 5.0.2.3 is incompatible with the SvrSslCfg command.

Solution: Use another version of the JRE to run the SvrSslCfg command. The wizard detects the successful completion of this command, and allows us to continue the integration.79814

 

Problem: Unsupported date and time formats in Excel-SS

The formatting behavior of the spreadsheet depends on the browser's configuration to determine what rules to use when formatting numbers, currencies, dates, and time formats.

The following date and time formats are not supported in Excel-SS:

All unsupported dates revert to m/d/yyyy format.75895

 

Problem: Install IBM® Content Manager before installing WebSphere® Portal

Before we install WebSphere® Portal to work with IBM® Content Manager, we must install IBM® Content Manager and DB2 Information Integrator for Content and their prerequisites. Follow the installation instructions provided with each of these products.

83512.RN

 

Problem: Document Manager does not operate in a WebSphere® Portal clustered environment.

The WebSphere® Content Manager semaphore property value needs to be set.

Solution: In the <WAS_HOME>\wpcp\config\WebSphere_Portal\author\WCM.properties file, set the line to wcm.cluster.enabled=true. This enables special handling of the WebSphere® Content Manager semaphore in a manner that is safe for cluster operation.83611

 

Problem: Additional Sametime fixes are available

To view the latest information about fixes that are available for Sametime, use a Web browser to access the Lotus Sametime Support site: http://www.ibm.com/software/lotus/support/sametime/support.html. Type the search term interim fix to locate information about available fixes.

At the time of this publication, the fixes Interim Fix 2A and Interim Fix 3 were available. We can install these fixes to improve the performance of the people awareness and Buddy list functions. Review the respective readme files provided with the interim fixes for more information.79948

 

Problem removing users on certain Domino LDAP server versions and Novell eDirectory LDAP server versions

When a user is deleted from WebSphere® Portal, this user is not deleted from any user groups on the LDAP server to which it belonged. Therefore, if the same user is added back into WebSphere® Portal, the user is automatically a member of any user groups it previously belonged to, which can lead to security exposure.

Solution: To prevent this problem, ensure that the user is removed from the group as well as from the LDAP server.

 

Related to installing portlets

 

Problem: IBM® NetMeeting portlet not available

If we are using Internet Explorer 5.5 on Windows, and Microsoft NetMeeting is not already installed, the NetMeeting portlet will not be available.

Solution: Upgrade to Internet Explorer 6 or install the Microsoft NetMeeting application (as provided by Microsoft Corporation) on our machine.49224.rn

 

Problem: Administration portlets unavailable after Fix Pack uninstallation

Some administration portlets (For example, Users and Groups or Resource Permissions) are unavailable after Fix Pack uninstallation.

Solution: If we receive an error message stating that the portlets are unavailable, redeploy the missing portlets from the <WPS_HOME>\installableApps directory. 72182.RN

 

installportlets command fails after installing WebSphere® Portal with security enabled

When installing WebSphere® Portal with WAS security enabled, the installation program does not allow us to specify a WebSphere® Portal administrator user ID and password. This will cause the installportlets command to fail when we are configuring WebSphere® Portal to use our LDAP server (this configuration is required when installing with security enabled).

Solution: When configuring WebSphere® Portal to use our LDAP server, do not use the installportlets command to manually deploy portlets, as described in step 15 of the following topics in the Information Center:

Note that all other steps in these topics are not affected.

Instead of using the installportlets command in step 15, complete the following steps

  1. Open a command prompt and change directory to <wp_root>/config/work.
  2. Issue the appropriate command for our operating system, with the entire command on one line:

    • Windows:
      ..\..\bin\xmlaccess -in SetupPortal.xml -user admin_userid -pwd password -url http://your.server.name:port/wps/config
    • UNIX:


      sh../../bin/xmlaccess.sh -in SetupPortal.xml -user admin_userid -pwd password -url http://your.server.name:port/wps/config

    where admin_userid and password are the user ID and password of the portal administrator, and http://your.server.name:port/wps is the fully qualified host name and base URI of the portal machine.

  3. Issue the appropriate command for our operating system, with the entire command on one line:

    • Windows:
      ..\..\bin\xmlaccess -in SetupDazzle.xml -user admin_userid -pwd password -url http://your.server.name:port/wps/config
    • UNIX:


      sh../../bin/xmlaccess.sh -in SetupDazzle.xml -user admin_userid -pwd password -url http://your.server.name:port/wps/config

    where admin_userid and password are the user ID and password of the portal administrator, and http://your.server.name:port/wps is the fully qualified host name and base URI of the portal machine.

  4. Issue the appropriate command for our operating system, with the entire command on one line:

    • Windows:
      ..\..\bin\xmlaccess -in <wp_root>\portletscripts\DeployMailPortlet.xml -user admin_userid -pwd password -url http://your.server.name:port/wps/config
    • UNIX:


      sh../../bin/xmlaccess.sh -in <wp_root>/portletscripts/DeployMailPortlet.xml -user admin_userid -pwd password -url http://your.server.name:port/wps/config

    where admin_userid and password are the user ID and password of the portal administrator, and http://your.server.name:port/wps is the fully qualified host name and base URI of the portal machine.

  5. Issue the appropriate command for our operating system, with the entire command on one line:

    • Windows:
      ..\..\bin\xmlaccess -in <wp_root>\portletscripts\SetupPDM.xml -user admin_userid -pwd password -url http://your.server.name:port/wps/config
    • UNIX:


      sh../../bin/xmlaccess.sh -in <wp_root>/portletscripts/SetupPDM.xml -user admin_userid -pwd password -url http://your.server.name:port/wps/config

    where admin_userid and password are the user ID and password of the portal administrator, and http://your.server.name:port/wps is the fully qualified host name and base URI of the portal machine.

76035

 

Related to uninstalling

 

Problem: Java exceptions appear in uninstallation log file

After uninstalling WebSphere® Portal, Java exceptions appear in the uninstallation log file (wpuninstalllog.txt), indicating that the Java Runtime Environment (JRE) could not be removed.

Solution: This behavior is a limitation of the WebSphere® Portal uninstallation process and does not indicate that the uninstallation failed. The uninstallation program is unable to remove the JRE that is used to run the uninstallation program, which causes the exceptions to be generated. The exceptions that appear in the log file can be ignored.77281

 

Configuration

 

Related to LDAP

 

Problem: (SSL only) Cannot log in to WebSphere® Application Server or WebSphere® Portal using normal login ID

We cannot log in to WAS or WebSphere® Portal using a normal login ID. Enabling the security for the LDAP does not set the correct userFilter, groupFilter, and userIDMap in the security.xml. When we have enabled the security for the LDAP and configured WAS to enable SSL, we need to provide a fully distinguished name such as uid=wpsadmin,cn=users,dc=ibm,dc=com to log in to WebSphere® Application Server and WebSphere® Portal.

Solution:

  1. Log in to WAS using full name, such as uid=wpsadmin,cn=users,dc=ibm,dc=com.
  2. Go to the WAS administrative console by clicking: Security > User Registries > LDAP.
  3. Click Advanced LDAP Settings and verify these properties: 
    User Filter:         (&(uid=%v)(objectclass=inetOrgPerson))
Group Filter:        (&&(cn=%v)(|(objectclass=groupOfNames)(objectclass=groupOfUniqueNames)))
User ID Map:         inetOrgPerson:uid
Group ID Map:        *:cn
Group Member ID Map: groupOfNames:member;groupOfUniqueNames:uniqueMember
  4. Restart WAS and WebSphere® Portal.
50194.rn

 

Problem: Not all results are returned when searching using the Manage Users and Groups portlet

When LDAP is used as the user repository, searches in the Manage Users and Groups portlet and in other portlets, a SizeLimitException is thrown instead of returning the items. If the results of a search exceed the maximum defined in wmm.xml, only the maximum number of objects is returned.

Solution: Refine our search to return fewer results or change the Member Manager maximum setting.49697f_3.RN

 

Problem: Cannot share or assign workflows to individual users or groups

When LDAP is used as the user repository, search for users or groups in the Share/Assign workflow dialogs fails and a SizeLimitException is thrown instead of returning the items. This happens if the results of the search exceeds the maximum defined by the maximumSearchResults attribute in the <wp_root>/shared/app/wmm/wmm.xml file. The default value for maximumSearchResults attribute is 200.

Solution: Change the value of attribute maximumSearchResults in wmm.xml.71407.RN

 

Problem: Error occurs when trying to edit a profile.

This problem might occur if WebSphere® Portal is using LDAP as the user repository. After we successfully create an account, if we click Edit My Profile before updating the PumaService.properties file, we will receive an error message similar to "An error has occurred. User subsystem failed. Please contact system administrator." This error occurs when our LdapUserPrefix is set to cn within the wpconfig.properties file.

Solution: Update the PumaService.properties file before using "Edit My Profile" in WebSphere® Portal.

Manually update the following line in the PumaService.properties file:
#user.sync.remove.attributes=

And replace the line with:
user.sync.remove.attributes=cn,CN

We only do this once, not each time we create a new account.

56254

 

Problem: Problem returning special characters within Domino (R5) distinguished names

There are some problems returning special characters within Domino(R5) distinguished names (DN). With users or groups with special characters in the DN existing, none of the users or groups within the LDAP were returned when searching through the Portal > Administration > Access portlets.

Solution: Do not use special characters in the DNs of users or groups within Domino R5.57243

 

Problem: Create two accounts for users with the same first name and last name on WebSphere® Portal using Domino LDAP

WebSphere® Portal can be configured to create the distinguished name (DN) for a user account created through WebSphere® Portal interfaces (self-regulated or the user management portlet "create new user" functions) by using the common name (cn) as the first Relative Distinguished Name (RDN) component. In particular, this will be the default configuration for WebSphere® Portal with a Domino LDAP server.

WebSphere® Portal builds the cn from the first name concatenated with the last name (where first name and last name are entered by the user or administrator). This means that WebSphere® Portal cannot create two users with the same first name and last name, because that would cause two DNs to be created with the same value, and this is not allowed (the definition of a DN is that it is unique).

Solution: To create two accounts for users with the same first name and last name, we must use the Domino administrative client or other mechanism, to specify the accounts with DNs that are unique. 9195, 13853

 

Problem: Self-registered user does not show in names.nsf file

After a user self-registers through the portal, they are created successfully although the newly created user is not listed in the names.nsf file. Even though, the user is hidden, there is no adverse impact on the user.

Solution: In PortalServer/shared/app/wmm, edit the file wmm.xml with the information below. 

               <supportedLdapEntryType name="Person"
                   rdnAttrTypes="cn" 
                   objectClassesForRead="inetOrgPerson"
                   objectClassesForWrite="dominoPerson"
                    searchBases="o=kmportal7"/>
               <supportedLdapEntryType name="Group"
                   rdnAttrTypes="cn" 
                    objectClassesForRead="groupOfNames"
                    objectClassesForWrite="dominoGroup"
                    searchBases=""/>

Domino 6.x only shows users with the dominoPerson objectclass within its views. Nothing is lost as dominoPerson inherits inetOrgPerson.70984.RN

 

Problem: Exceptions in the JVM log files during Server startup after LDAP Security enabled

The following Exceptions are seen in the JVM log files during Server startup after LDAP Security is enabled.

[12/5/03 15:29:00:201 UTC] bf5ea326 WebGroup      I SRVE0180I: [processportal.war] [/bpe] [Servlet.LOG]: init: init
[12/5/03 15:29:00:223 UTC] bf5ea326 WebGroup      I SRVE0180I: [processportal.war] [/bpe] [Servlet.LOG]: com_ibm_wps_AdminServlet: init
[12/5/03 15:29:00:232 UTC] bf5ea326 ApplicationMg A WSVR0221I: Application started: BPEWebClient
[12/5/03 15:29:00:253 UTC] bf5ea326 ApplicationMg A WSVR0200I: Starting application: wmmApp
[12/5/03 15:29:00:336 UTC] bf5ea326 LdapRegistryI E SECJ0350E: Could not get the uniqueId of the user "".
[12/5/03 15:29:00:363 UTC] bf5ea326 LdapRegistryI E SECJ0351E: Could not get the uniqueId of the user "" due to the following exception com.ibm.websphere.security.CustomRegistryException: Cannot find uniqueID for the user ""
      java/lang/Throwable.<init>(Ljava/lang/String;)V+4 (Throwable.java:85) 
      java/lang/Exception.<init>(Ljava/lang/String;)V+1 (Exception.java:33) 
      java/security/GeneralSecurityException.<init>(Ljava/lang/String;)V+1 (GeneralSecurityException.java:39) 
.
.
.
      com/ibm/ws/runtime/WsServer.start([Ljava/lang/String;)Z+480 (WsServer.java:153) 
      com/ibm/ws/runtime/WsServer.main([Ljava/lang/String;)V+10 (WsServer.java:260) 
      com/ibm/ws/bootstrap/WSLauncher.main([Ljava/lang/String;)V+0 (WSLauncher.java:23) 
.
[12/5/03 15:29:00:539 UTC] bf5ea326 EJBContainerI I WSVR0207I: Preparing to start EJB jar: wmm.ejb.jar
[12/5/03 15:29:01:010 UTC] bf5ea326 EJBContainerI I WSVR0037I: Starting EJB jar: wmm.ejb.jar
[12/5/03 15:29:01:242 UTC] bf5ea326 EJBContainerI I WSVR0207I: Preparing to start EJB jar: wmm.internal.ejb.jar
[12/5/03 15:29:01:637 UTC] bf5ea326 EJBContainerI I WSVR0037I: Starting EJB jar: wmm.internal.ejb.jar
[12/5/03 15:29:01:855 UTC] bf5ea326 ApplicationMg A WSVR0221I: Application started: wmmApp

Solution: We can ignore these exceptions. 70732.RN

 

Problem: Document Manager cannot communicate with WebSphere® Portal content publishing when LDAP enabled

This is caused by a mismatch in LDAP user id attribute used in WebSphere® Application Server and the WebSphere® Portal user attribute.

Solution: Change the User Id Map in the LDAP settings within the WAS administration console:

  1. Log on to WAS Administrative console
  2. Go to Security < User Registries < LDAP User Registries page.
  3. Go to the Advanced LDAP Settings page (Link at right-hand bottom of page).
  4. Change the User Id Map to match the Default User Filter(user.fbadefault.filter) defined in <WPS_ROOT>\shared\app\config\services\PumaService.properties.
62446.rn

 

Workaround for Novell Directory Server LDAP

Problem: WebSphere® Portal configuration assumes that Novell eDirectory is configured using cn as distinguished name identifier. As a result, the user ID is mapped to cn.

Solution: Disable mapping of user ID to cn within <wp_root>/config/templates/wmm/wmmLDAPAttributes_NDS.xml This process looks like the following example:

<attributeMap   wmmAttributeName="uid"
                        pluginAttributeName="uid"
                        applicableMemberTypes="Person"
                        requiredMemberTypes="Person"                    
                        dataType="String"
                        valueLength="256"
                        multiValued="false" />
81416.RN

 

Problem: (Linux only) IBM® Directory Server 5.1 process stops

During the prepopulation step of configuring WebSphere® Portal V5.0, the IBM® Directory Server 5.1 process stops. This happens when WebSphere® Portal and DB2 8.1 are running on a Linux for zSeries machine and IBM® Directory Server 5.1 is running on an Intel Linux machine with the operating system as RedHat Linux 7.3.54330.RN

 

Related to database

 

Problem: Experiencing deadlocks with the WebSphere® Portal database

We might experience deadlocks when users concurrently modify or create pages.

Solution:: To reduce deadlocks with the WebSphere® Portal databases:

  1. DB2 V8.1 FP4 or higher users only (skip this step if we use DB2 on OS/390): Enter the following commands on the DB2 server with DB2 instance owner privileges (for Windows, please use the DB2 Command Window): 
       db2set DB2_EVALUNCOMMITTED=YES
   db2set DB2_INLIST_TO_NLJN=YES
   db2 update db cfg for <wpcp_db> using locklist 1024

    In order to apply all of these settings we need at least DB2 Fixpak 4 applied.

  2. All database users: Connect to the WebSphere® Portal database and enter the following commands on the database server: 
       CREATE INDEX DbUser.IX2110D ON DbUser.PROT_RES (PARENT_OID, OID);
   CREATE INDEX DbUser.IX2140B ON DbUser.LNK_USER_ROLE (ROLE_INST_OID);
    where DbUser is the WebSphere® Portal database administrator

    If we use WebSphere® Portal's document management features with DB2 V7.2 or SQL Server databases, we might continue to experience deadlocks. Deadlocks can occur when multiple users update or create documents in high load environments. These issues will be addressed in a future WebSphere® Portal release.

82777

 

Problem: Experiencing deadlocks with the WebSphere® Portal database

We might experience deadlocks when multiple users concurrently modify or create pages.

Solution: Follow these steps:

  1. From the the Qshell Interpreter, type: 
         strsql
  2. Connect to the Portal database and do the following: 
         CREATE INDEX <QWPS50>/IX2110D ON <QWPS50>/PROT_RES (PARENT_OID, OID)
     CREATE INDEX <QWPS50>/IX2140B ON <QWPS50>/LNK_USER_ROLE (ROLE_INST_OID)
    where <QWPS50> is the default name for the WebSphere® Portal database.

82777

 

Problem: basic-config task fails

The task basic-config can fail if one of the database schema names set in wpconfig.properties matches the user profile name that is signed on to run the configuration.

A sample failure message, using WPS1TEAM user as signed on and attempting to configure with a database schema called WPS1TEAM, is below.

[java] CREATE TABLE ID_TABLE (                                                                       
[java]     RES_TYPE INTEGER NOT NULL,                                                                
[java]     LAST_ID BIGINT NOT NULL,                                                                  
[java]     CONSTRAINT PK10 PRIMARY KEY (RES_TYPE)                                                    
[java] )                                                                                             
                                                                                                           
[java] com.ibm.db2.jdbc.app.DB2DBException: Not authorized to object WPS1TEAM in QSYS type *USRPRF.  
                                                                                                           
BUILD FAILED                                                                                              
file:../config/actions/db_cfg.xml:218: Java returned: 4                                                   
                                                                                                           
Total time: 4 minutes 42 seconds

Solution: Avoid using the user profile name as a database schema name when configuring for iSeries.65563.RN

 

Problem:Cannot connect with DB2 database on WebSphere® Portal

Problem: We cannot establish a connection with DB2 database on WebSphere® Portal.

The following prerequisites must exist separately from the prod_wp_short installation.

Do NOT use prod_db2_short Connect V8 to connect to a prod_db2z_short V7 database server. This configuration will result in major problems caused by BLOB and CLOB data.

Solution: Ensure that all prerequisites are met.81225

 

Problem: Errors in Creating databases and users topic in Information Center

The Information Center topic, Creating databases and users for DB2, contains errors in describing the DB2 commands that are used in step 4 of the "Creating remote databases" section. In particular, the following command examples are in error: 

    $ db2 connect to wpcp50;
    $ db2 create bufferpool wpcpBP8K size 8192 pagesize 8K;
    $ db2 connect reset;

Solution: When entering these commands, do not include the semi-colon (;) at the end of each line. Instead, enter the commands using the following syntax: 

    $ db2 connect to wpcp50
    $ db2 create bufferpool wpcpBP8K size 8192 pagesize 8K
    $ db2 connect reset
82655

 

Problem: DB2 7.1 FP11 users connecting to DB2 z/OS databases only: Errors while enabling portal security or using other configuration tasks

If we use DB2 UDB 7.1 Enterprise to connect to a z/OS database, we might see see error messages similar to the one below in the WebSphere® Application Server administrative console when enabling portal security or running other configuration tasks: 

 XAException occurred.  Error code is: XAER_OUTSIDE.  Exception is: <null>
4c9bfb XATransaction E J2CA0027E: An exception occurred while invoking start on an XA Resource Adapter from dataSource 
jdbc/wps50DS, within transaction ID {XID: formatId(57415344), gtrid_length(26), bqual_length(25), data(00000001 5E14C1C7 
00A52AB0 6E71A27E FDDE80B3 E148EBAE 66D901C1 C700A52A B06E71A2 7EFDDE80 B3E148EB AE66D989 336200)}: javax.transaction.xa.XAException

Solution:We must perform these additional steps before running any configuration tasks for WebSphere® Portal 5.0.2.1:

  1. Go to the WebSphere® Portal support site at http://www-306.ibm.com/software/genservers/portal/support/ and download the appropriate fix for DB2 UDB 7.1 FP11.
  2. Follow the instructions in the extracted readme file to apply the fix. The fix must be applied on the DB2 7.1 client as well as the DB2 7.1 server systems.

If we encountered this error while enabling portal security because we had not already applied the DB2 fixes, follow these steps:

  1. Run disable-security configuration task to undo the changes made to the portal configuration by the enable-security-ldap task. The disable-security task will fail at approximately the same point where enable-security-ldap task failed.
  2. Stop WebSphere® Portal.
  3. Apply the DB2 fixes as documented above.
  4. Run the enable-security-ldap task again. If we get the following warning from the XML configuration interface, ignore it: 
    It is not possible to modify credential-segment resources. Existing settings are left unchanged.

    This warning does not impact portal functionality.
81157.RN

 

Problem: Additional PTF needed for DB2 Universal Database for OS/390

If the PTF is not installed, error code 00C20206 occurs when more than one user accesses Document Manager. If this error occurs, follow the recovery instructions from DB2 Universal Database for OS/390 and z/OS Messages and Codes and the recovery instructions in the PTF.

Solution: Install DB2 Universal Database for OS/390 PTF UQ83393 on the DB2 system. After installation, the system must be IPLed.83848

 

Problem: Oracle Enterprise Edition 9i Release 2 supports 32-bit only

Oracle Enterprise Edition 9i Release 2 (9.2.0.1) has 32-bit support only. 98523

 

Problem: "DuplicateKey" exceptions after turning on session persistence to database

We might see "DuplicateKey" exceptions after turning on session persistence to database.

Solution: After turning on session persistence to database, we might see DuplicateKey exceptions logged. These messages appear not to cause a functional problem.92336.RN

 

Problem: "mIBM® SessionListenerImplemented field not found" exceptions might appear

"mIBM® SessionListenerImplemented field not found" exceptions might appear

Solution: In a clustered deployment of WebSphere® Portal, when using database session persistence, we may see exceptions logged on the Node Manager machine indicating that a NoSuchFieldError exception has been thrown where the field name is "mIBM® SessionListenerImplemented". This message appears not to cause a functional problem.89781.RN

 

Problem: Update to WebSphere® Portal V5.0.2 Information Center in section Creating databases and users for DB2 for z/OS and OS/390

The Portal 5.0.2 Information Center is not consistent with its recommendations for DB2 for z/OS and OS/390 database names. On the page entitled Creating databases and users for DB2 for z/OS and OS/390, the section Creating a connection to the host database, step 2, instructs us to use wpcp5zos, wps5zos, and fdbk5zos as the local cataloged database alias names.

After the database connections have been made, in the section of the Information Center entitled Configuring WebSphere® Portal for DB2 for z/OS and OS/390, the table in step 4 recommends different default values for the WpsDbName, WpcpDbName, WmmDbName, and FeedbackDbName fields. These values are the default AIX® DB2 database names, not the DB2 for z/OS and OS/390 names from the other section.

Solution: If we use all of the recommended values, the database import will work properly but when the portal server is launched it will not have created the WebSphere® JDBC Datasources properly. The values for WpsDbName, WpcpDbName, WmmDbName, and FeedbackDbName must reflect the names used to create the databases in the first Information Center page.94643

 

Related to authorization and permission

 

Problem: Receive error message Page Cannot Be Found when logging in to Portal

If we receive an error message "Page Cannot Be Found" when trying to log in to the portal, it might be that the Web server is running on a non-80 Port (For example, the Web server is running on port 8080). In this case, the login link breaks and points to port 80.

Solution: To correct this issue, perform the following steps:

  1. Update the wpconfig.properties file for WpsHostName and WpsHostPort.
  2. Run the task httpserver-config task to configure to the External Web server.
  3. Restart the WebServer and Portal Server.
  4. Launch the Portal Page in the Browser as http:/<hostname>:8080/wps/portal.
  5. Click on the login link.

 

Problem: Receiving "Not Authorized" message when using Edit Page Layout portlet

XML configuration interface import allows content nodes of the page type without any layout definitions so that these pages are created in the portal without an initial container layout. Because the current user interface design says that the process of page creation is not complete without the definition of an initial container layout, when a portal user with Privileged User access rights on such a shared page logs in and tries to use the Edit Page Layout portlet to create an implicit derivation (a private view) of this page they get a "not authorized" error message even though this should be allowed according to the PAC policies.

Solution: The resource owner (or someone with at least Editor access) needs to define an initial container layout, using either XML configuration interface or the Edit Page Layout portlet. The page can then be customized with Edit Page Layout by anyone with Privileged User access on that page.55953

 

Problem: Display and Modify Ownership of a Resource incorrect

After creating a Page and navigating to Access > Resource permissions if we click on Pages and search for the Page title just created by clicking on the Access icon next to the page and clicking on Display/Modify Owner, we see that the current owner for the page is blank.

Solution: Search on cn and search for *. We are then able to select the User or User Group that the ownership should be transferred to.55198f_1.rn

 

Problem: WAS LDAP settings reset

If a blank LDAP port is used within the WAS administrative console, the port numbers for Security, User Registries, LDAP, and Port within WAS 5.0.2, are reset to '0' upon saving. This creates a conflict within pre-existing LTPA configuration.

Solution: We must have all WAS LDAP port numbers explicitly defined and identically. (The default is 389; for LDAP over SSL, 636 is the default).

  1. After we update the port number, save the change.
  2. Regenerate the LTPA keys.
  3. Save again.
  4. Export the LTPA keys.
  5. Reimport and redeploy the new LTPA keys across the LTPA domain.

Non-WASs, such as Domino Application Server, that are participating in the LTPA domain will also need to reimport the new LTPA keys. Follow application server product specific documentation for importing new LTPA keys.67681RN

 

Problem: Receiving session timeout screen

When a user from another application server instance within the single signon domain has WebSphere® Portal with a Session cookie that has the name JSESSIONID and a cookie path that matches the portal URL (for example, the default value /) accesses the WebSphere® Portal protected area (for example, myportal), the user will see the session timeout screen. This is because WebSphere® Portal cannot distinguish if the cookie sent by the browser was created by itself or by another application server instance.

Solution: To prevent this problem, the cookie path has to be adjusted accordingly (so that it does not match the WebSphere® Portal URL) in the other Application Server instances that share the same single signon domain.68609.rn

 

Problem: Cookie path for the WebSphere® Portal application is not set

If the cookie path is not set,the cookies (JSESSIONID, LtpaToken) that are created or issued by WebSphere® Portal to be sent by the browser are sent to every other accessed URL as well. This problem only occurs if we do not log out before accessing another URL.

Solution: To correct this problem, perform one of the following steps.

Both settings require restarting WebSphere® Portal.68740.RN

 

Problem: Cannot use XMLAccess function

If the XML configuration interface virtual resource is externalized, we are no longer able to use the XML configuration interface function provided by WebSphere® Portal.

Solution: If the access rights of WebSphere® Portal are externalized to Tivoli® Access Manager, verify that the XML configuration interface virtual resource is not externalized.68774.RN

 

Problem: Correction to comment for wpconfig.properties file for security custom user registry

Solution: The comment for setting PortalAdminID for Security custom user registry is incorrect in wpconfig.properties file. The correct setting is documented in the Information Center.70195.RN

 

Problem: Setting up SSL for WebSphere® Portal

Use this information in step 4 of the Setting up SSL for WebSphere® Portal topic. If we have errors logging off when SSL is enabled, perform the step below.

Solution: If we have enabled SSL, set the values for the redirect.login.ssl and redirect.logout.ssl parameters in the <wp_root>/shared/app/config/services/ConfigService.properties file to true. Do not leave the redirect.logout.ssl value set to false.71637.RN

 

Problem: Information about initial access control settings

The following table supersedes the Initial Access Control Settings section of the Access Control Administration topic in the Information Center.

Solution:The following table describes the initial access control settings.
User or Group Role
The administrative user identified during the installation Administrator@Portal
<wpsadmins> Administrator@Portal
All Authenticated Users User@ the following portlet applications:

  • Edit page content and layout
  • Concrete Properties Web Application
  • Appearance Web Application
  • Set Permissions Portlets
  • Page Properties
  • Organize Favorites
  • Page Customizer

Privileged User@ the following pages:

  • My Portal
  • Welcome
  • Information Portlet Application


79596

 

Problem: Receive SSLHandshakeException

If we have global security enabled and our application uses Java Secure Socket Extension (JSSE) to implement Secure Sockets Layer (SSL) when connecting to an HTTPS server, javax.net.ssl.SSLHandshakeException: unknown certificate might be thrown and logged in the SystemOut.log for our application after installing WebSphere® Portal V5.0.2.

Solution: Configure the same Java trust store for applications running on the server and for the CSIv2 outbound transport for the server. In other words, add the signer certificates required by applications running on the application server to the Java trust store configured for the CSIv2 outbound transport.

Refer to the following link if we need more information:

http://www-912.ibm.com/s_dir/slkbase.NSF/0/7c09836525c4c5c186256db8007547c9?OpenDocument76322

 

Problem: Moving a resource from external security manager control back to portal control results in leftover dangling ACL

Moving a resource from external security manager control back to portal control might result in leftover dangling ACL.

Solution: When a portal resource has been externalized to external security manager control (For example, moved to Tivoli® Access Manager control) under previous WebSphere® Portal 5.0.x versions (For example, 5.0.2.1) and then is moved back internally under portal access control after WebSphere® Portal 5.0.2.2 has been applied, the Access Control List (ACL) for the roles on that resource may be left in the external security manager instead of being correctly cleaned up. The ACLs can be manually deleted, and should be if the resource will later be re-externalized. PQ86200.RN

 

Problem: Receiving error messages after running wpsconfig.sh enable-security-cur

After running the task wpsconfig.sh enable-security-cur, we will receive error messages.

Solution: We can ignore these error messages. 69779.RN

 

Problem: Configuring security with a Member Manager database-only configuration topic

Addition to the Installing < Security < Configuring security with a Member Manager database-only configuration topic in the Information Center.

Solution: The note about the Cloudscape database should read as follows:

WebSphere® Portal does not support a Member Manager database-only configuration using Cloudscape as the database. In the database-only configuration, the Member Manager database is the primary user store, and WebSphere® Portal uses Member Manager to access that user store directly. WebSphere® Portal provides a Custom User Registry that iWebSphere® Application Server uses to access the Member Manager database. Before setting up a Member Manager database-only configuration, WebSphere® Portal and Member Manager must be migrated from Cloudscape to another database. This procedure involves installing separate database software and running the appropriate WebSphere® Portal configuration task. See Installing - Database for more information.71772

 

Related to Locale

 

Problem: Unable to specify Double Byte Character Set directory for Themes and Skins

No preview image is displayed if we are creating new Themes and Skins when using the double byte character set (DBCS) directory.

Solution: To avoid this problem, do not use the Double Byte Character Set name as a directory for new Themes and Skins.13764.RN

 

Problem: Enabling Ichitaro format in full-text search

In a Japanese system environment, either while the Sametime Server is installed or after we start the Domino server, we might see the following error.

Unable to load FT alternate filter config file: C:\Domino\ FTAF.ncf

Solution: Ignore the error when we install the Sametime Server. To enable the Ichitaro attachment document full-text search after we install it, set the following NOTES.INI variable: ft_use_altfltr=1.

The ftaf.ncf file is automatically installed in our Notes program directory. We should also set two values in the ftaf.ncf file:

Copy the ftaf.ncf file to our Domino program directory.

An example of the ftaf.ncf file follows: 
************BEGINNING OF DATA************** 
aftaro6 
aftaro9 
************END OF DATA********************
23931

 

Problem: Show portlet titles correctly

Some portlets, such as Themes and Skins or Manage Portlets, might show various portlet titles in different languages in one single panel. If the user languages is one that uses a Double Byte Character Set, some languages might not be displayed correctly (other DBCS languages and languages using special characters).

For example, if Chinese is the selected language, the Chinese title will be displayed correctly, but not the other languages with special characters. If Japanese is the selected language, the Japanese title will be displayed correctly, but not the other languages with special characters. However, if English (or any language using UTF-8) is the selected language, all titles will be displayed correctly.

Solution: To have all portlet titles display correctly, set UTF-8 as the encoding for the desired languages.25480

 

Problem: (Windows only) Russian characters appear corrupt

Solution: The default Russian encoding for WebSphere® Application Server is ISO-8859-5 but should be Windows-1251 for Windows. The encoding can be changed in the <was>/properties/encoding.properties file. 56345

 

Problem: Help files incorrectly aligned in bidirectional environment

In a bidirectional environment, help files can appear left to right instead of right to left.

Solution: The portlet title must be updated to a title in the bidirectional language. Use the following steps to update the portlet title.

  1. Click on Administration.
  2. Expand Portlets in the menu, and click Manage Portlets.
  3. Select the portlet from the list of portlets, and click Modify parameters.
  4. Select the bidirectional language from Edit Locale Specific Titles, and click Set title for selected locale.
  5. Enter the new title in the Title field, and click OK. We must enter the new title in the bidirectional language, or the help continues to render with the incorrect alignment.
67738

 

Problem: (Windows only) Czech characters appear corrupt

The default Czech encoding for WAS is ISO-8859-2 but should be Windows-1250 for Windows.

Solution: The encoding can be changed in the <was>/properties/encoding.properties file. In Internet Explorer, right-click on the help window and select Windows codepage.68137.rn

 

Problem: Incorrect characters shown in WebSphere® Portal SystemOut.log file

If we see incorrect characters, especially question marks, in the WebSphere® Portal SystemOut.log, we need to set the proper encoding in the Java run-time arguments for WebSphere® Portal in the WAS Administrative Console.

Solution: To set the proper encoding, perform the following steps.

  1. Change to the WAS bin directory (for example, for AIX, /usr/WebSphere/AppServer/bin).
  2. Edit the setupCmdLine.sh script. At the bottom, we see a setting for the LANG environment variable. It is probably set to a different locale value than what we require (for example, en_US for US English is specified instead of Japanese (ja_JP) which is required).
  3. Change the locale value to the desired value and save the file.
  4. Stop and restart the WebSphere® Portal application server and the native language characters in the WebSphere® Portal SystemOut.log should be correct.

This might only be a problem with double byte or multibyte character set encodings like Japanese and Chinese.54489f_2

 

Related to portlet configuration

 

Problem: Collaborative Portlets will not work through Webservices for remote portals (WSRP)

Some collaborative portlets cannot be exported from a WSRP producer and imported to a WSRP consumer. Portlets that are known to be affected are:

Solution: This limitation will be corrected in a future release of WebSphere® Portal.96412.RN

 

Problem: Update to Information Center, under Administering our portal, Portal Configuration, Portal Service configuration, Deployment Service

This is an update to the Information Center, under Administering our portal, Portal Configuration, Portal Service configuration, Deployment Service. This section mentions the following property:

update.portlet.preserves.config.settings = (true)
This controls the update of portlet configuration settings during updates of portlet application WAR files. This parameter determines whether the portlet configuration parameters from the file portlet.xml should replace the existing ones, or whether the existing parameters should be preserved, and only new ones be added.

The following addition has been made to the description of this property:

If we set this property to true, this prevents modifications made by an administrative user from being overwritten with default values that the portlet developer put into the portlet.xml in the new WAR file. The following fields are preserved from modification by an updated portlet.xml file:
Portal resource JSR 168 portlet application Version 4.x portlet application
Portlet Application Default locale N/A
Title Title
User attributes Context parameter
Portlet Name Name
Title Title
Short title Short title
Keywords Keywords
Description Description
Default locale and description Default locale
Initialization parameter Initialization parameter
Preferences N/A
Remote cache settings Cache settings
Expiration date settings N/A
Servlet N/A Mappings
90033.RN

 

Problem: Portlets not rendered completely on session failover

In certain circumstances, a portlet might be incompletely rendered after session failover. When this happens, the log file might contain error messages similar to the one below:

Response is already committed to client. Session cookie cannot be set.

Solution: Refresh the browser and log in to WebSphere® Portal again.79315f_2.RN

 

Problem: Supported version of Opera browser

In the portal help, it states that the following browsers are supported: Opera 6.0, Opera 6.1, and Opera 7.0. This is incorrect.

Solution: The only level of Opera that is supported is Opera 7.11.pcr374

 

Problem: Portlet parameters might be lost if doing a Portlet Update or a migration

If we have made changes to existing portlet parameters through the Portal 'Manage Portlet' utility, these changes will be lost after a Portlet Update is done through the 'Portlet Application' utility or through a migration to another version of WebSphere® Portal that does a silent update of the portlet.

Solution: Make note of any modifications that we made through the 'Manage Portlet' utility and reapply the changes after the portlet update is complete. For example, we can change the Notes View portlet parameters to point to a particular Notes Server/Database/View/Credential Vault Slot. After the portlet is updated, these changes will be lost and reset to the default placeholder values. For future additions of this portlet to a page, the portlet would not be configured. If we have made many copies of the portlet, each configured separately, we would lose those changes. Therefore, it is important to note any modifications that are made to portlet parameters.

Comments: For more information on migrating portlets, refer to the product documentation site for the latest migration information: http://www.ibm.com/websphere/developer/zones/portal/proddoc.html25337_RN

 

Problem: Attachments in Exchange Mail cannot be sent correctly

Attachments in Exchange Mail cannot be sent correctly when the file names contain characters that must be URL encoded. These characters include any nonalphanumeric characters except for asterisk, underscore, period, and hyphen.

Comments: If a user tries to send a message with an attachment with one of these file names, an appropriate error message is displayed and the message is not submitted.50610.rn

 

Problem: Link to launch Edit Mode of a portlet disappears

While using the Edit Layout portlet to edit a page, the link to launch the edit mode of a portlet on that page will disappear after the page is deactivated. A page is deactivated right after the user performs an action in edit content and layout portlet, such as "Add Portlets" or "Move Portlets/container."

Solution: After the page is deactivated and after the user performs an action, the user needs to click Done to leave the page. This action will activate the page. The Edit Portlet link will be displayed when user clicks the Edit Page link. 55558.rn

 

Problem: How to create a bookmark to a user-created page

When we create a new page in the portal, that page does not appear in the list of internal bookmarks in the edit mode of the bookmarks portlet.

Solution: After we create a new page, the page needs to have a custom unique name specified in Administration. We should go to Administration > Portal Settings > Custom Unique Names, then navigate to the newly created page and select the Edit icon to provide a Unique Name for the page. After this is completed, the page will appear in the list of internal bookmarks in the edit mode of the bookmarks portlet. 52407f_1.rn

 

Problem: Change does not occur after editing Supported Clients portlet

When editing a client within WebSphere® Portal Supported Clients Portlet, the change is not dynamically picked up by the corresponding property file within Transcoding Technology.

Solution: Manually update the property file with the change.

  1. Navigate to <WPS_root>/IBM® Trans/etc/preferences/device
  2. Locate the property file and make the appropriate changes.
56721

 

Problem: Portlet menus do not render completely in portal navigation

In certain circumstances, portlet menus might render incorrectly in the portal navigation.

Solution: If we use the standard portal navigation, portlets that provide portlet menus must be placed only on pages that are on the third level of the page hierarchy or lower. In the following example this would be all pages placed under Page 1, that is Page 1.1, Page 1.1.1, and so on. 

Navigation level    Portlet menu items
         Level 1          MyPortal 
         Level 2             Page 1
         Level 3                Page 1.1
         Level 4                   Page 1.1.1
         Level 5                      .....

Navigation level    Portlet menu items            Display status
         Level 1          MyPortal 
         Level 2             Page 1               Portlet is displayed on this page.
         Level 3                Page 1.1          Portlet primary menu entries are displayed here.
         Level 4                   Page 1.1.1     Portlet secondary menu entries are not displayed.
56446

 

Problem: Cannot see any pages after deleting a page with scrolling

If we create a page that introduces scrolling and then delete that page, we will not be able to see any other pages in the portal including any default pages.

Solution: There are two fixes for this. We can log out and log back in to the portal or we can re-create a page that introduces scrolling.57098

 

Problem: Editing the predefined taxonomy requires installing and deploying the Taxonomy Editor portlet

Solution: In order to manipulate the predefined taxonomy, we must install the TaxonomyEditor.war file that is located in the <wps_home>;\installableApps directory. After this file is installed, the Taxonomy Editor portlet can be deployed. For example, the file can be deployed on the Manage Search Index page. 57596

 

Problem: Only portlet title translated when using WebSphere® Translation Server

In EnableViewerInitiatedTranslation the portlet title is translated in the drop-down menu but not the body of the portlet.

Solution: Stop and start WebSphere® Portal after we start WebSphere® Translation Server. 57711.rn

 

Problem: Unable to move a page

The Access Rights topics states that moving a page to a new parent page is supported in WebSphere® Portal V5.0. This is incorrect.

Solution: It is not possible to move a page to a different parent page in WebSphere® portal V5.0. We can instead manually create a new page with identical content and delete the old one. However, the new page does not contain the customizations on derived pages.57811

 

Problem: Install embedded search component

The Taxonomy Editor portlet is not automatically installed but must be installed and deployed manually.

Solution: The embedded search component can be installed and used in two ways, either accessing a locally installed search service or using a remote search service through the SOAP (Web services) interface.

After we configure either the Document search portlet or the Manage Search Index portlet to access one of those services, if we want to switch to the other type of service (for example, from local to remote), we will need to do so manually. Simply updating the respective portlet configuration parameters will have no effect. We must reconfigure the access to service. We can reconfigure by creating a copy of the portlet and configuring these to use the desired service type. To reconfigure to local access, leave the SOAP URL parameter empty and to reconfigure to remote access, specify a SOAP URL.24901

 

Problem: PreferredLanguage parameter does not work

The optional PreferredLanguage parameter is not supported for Machine Translation of portlets with WebSphere® Portal. Do not use that parameter.24901

 

Problem: Search fails when using an asterisk (*) in the search string

Solution: Retry the search string without the asterisk (*). The asterisk (*) is already a substring of the search parameter.63449.rn

 

Problem: After changing IDs in the My Notes portlet, cannot log in

After changing IDs in the My Notes portlet and logging in using single signon, we are sent back to the portal login screen but we cannot log in.

Solution: Shut down the browser and the portal will reset itself.64630.RN

 

Problem: Request Viewer cannot reconnect to portal

When trying to reconnect to the portal server using the Request Viewer, we might receive an error message saying we are already connected.

Solution: Restart the portal server. 69033.RN

 

Problem: Configuring the MovieSite sample

Solution: In addition to properties mentioned in the Information Center, set the following database properties in the wpcpconfig.properties file.
Database properties
>Property >Value
DbType

Description: The type of database used to store information for WebSphere® Portal.

Value type:

  • DB2: db2
  • Oracle: oracle
  • MS SQL Server: sqlserver
  • Cloudscape: cloudscape
  • DB2 for iSeries: db2_iseries
  • DB2 for z/OS and OS/390: db2_zos

Default Value: cloudscape

DbDriver

Description: The Java class name for the JDBC provider that WebSphere® Portal uses to communicate with its databases.

Value type: Alphanumeric text string, conforming to the Java namespace syntax for specifying classes. For example, COM.ibm.db2.jdbc.app.DB2Driver. The following values can be specified:

  • Cloudscape: com.ibm.db2j.jdbc.DB2jDriver
  • DB2: COM.ibm.db2.jdbc.app.DB2Driver
  • Oracle: oracle.jdbc.driver.OracleDriver
  • SQL Server: com.microsoft.jdbc.sqlserver.SQLServerDriver

Default Value: com.ibm.db2j.jdbc.DB2jDriver (Cloudscape)

DbLibrary

Description: The directory path where the classes for the JDBC provider are located.

Value type: Directory path with elements delimited by forward slashes (/).

In UNIX environments, we must use a colon (:) instead of a semi-colon (;) to separate multiple paths.

Example:

  • Cloudscape: <PortalServer>shared/app/cloudscape/db2j.jar
  • DB2: <SQLLIB>/java12/db2java.zip
  • DB2_iSeries: /QIBM® /ProdData/Java400/ext/db2_classes.jar
  • DB2 iSeries (remote): /QIBM® /ProdData/PortalServer5/IBM® Trans/lib/jt400.jar
  • DB2_zos: <SQLLIB>/java12/db2java.zip
  • Oracle: <Oracle>/jdbc/lib/classes12.zip
  • SQL Server: <SQLServerJDBC>/lib/mssqlserver.jar; <SQLServerJDBC>/lib/msbase.jar;<SQLServerJDBC>/lib/msutil.jar

Default Value: d:/websphere/portalserver/shared/app/cloudscape/db2j.jar

79283.RN

 

Problem: Additional browser support for some collaboration portlets

Solution: The Information Center provides specific information about Web browser support for the following portlets: Lotus QuickPlace, Inline QuickPlace, Lotus Sametime Connect, and Web Page. In addition to the Web browsers listed in the Information Center, the following Web browsers have also been tested for use with these portlets:

80130

 

Problem: Problems with double-byte character set files in mail portlet

We might experience problems when working with double-byte character set files in the mail portlet. We might not be able to browse or detach the file, or after creating a file, there is no file name or folder displayed in the document tree.70283.RN, 70405.RN, 70449.RN

 

Problem: Cannot create role mappings in the external system using Portal Server user interface

In the User and Group Permissions Portlet for externalized resources the links to create or delete the role mappings are displayed. It is not possible to create role mappings in the external system using the portal server user interface. Exceptions occur if we try to modify the role mappings and the Inherited column shows the wrong results.

Solution: Do not use the User and Group Permissions Portlet for externalized resources. 70802.RN

 

Problem: UpdatePortletApplicationCommand fails

If a portlet application WAR file is updated with fewer resources than the original WAR file, UpdatePortletApplicationCommand fails (preserve=false).

Solution: Delete the obsolete resources manually through the management portlets. 64494.RN

 

Problem: Manage Portlets portlet unavailable

If we use the Manage Portlets portlet to browse portlets, selects one portlet (for example, Appearance), and uses Manage Applications to delete the web module containing this selected portlet (for example, Appearance.war) and then try to open the Manage Portlets portlet again, we will see the message "This portlet is unavailable. If the problem persists, Please contact the portal administration.".

Solution: Log out of WebSphere® Portal and then back in again. The Manage Portlets portlet will then work. 71454.RN

 

Problem: Some log files in iSeries are illegible

After executing installportlets batch job, the output file portletinstall.txt is illegible because it is written in EBCDIC.

Solution: Use the iSeries utility EDTF from a 5250 session to read the file. 70591.RN

 

Problem: addwpsinst.log is illegible

We cannot read addwpsinst.log from a mapped drive.

Solution: Use the iSeries utility EDTF from a 5250 session to read the file. 70576.RN

 

Problem: Receive error FileNotFoundException: No such path or directory when using Pinnacor portlets

Pinnacor portlets log to their own files that they create rather than logging into stdout. They set the location for this logfile based on what they assume is the default location for WebSphere® Portal.

Solution: Download the latest Pinnacor war from the portlet catalog. 70477.RN

 

Problem: Exception in SystemErr.log file

After starting WebSphere® Portal, we receive the following exception in the SystemErr.log file:

[1/9/04 13:13:13:380 EST]  d89289f SystemErr     R log4j:ERROR setFile(null,true) call failed.
[1/9/04 13:13:13:380 EST]  d89289f SystemErr     R java.io.FileNotFoundException:../PortalServer/log/pcor2.log (The system cannot find the path specified)
[1/9/04 13:13:13:380 EST]  d89289f SystemErr     R     at java.io.FileOutputStream.openAppend(Native Method)
.
.
.
[1/9/04 13:13:13:390 EST]  d89289f SystemErr     R     at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
[1/9/04 13:13:13:400 EST]  d89289f SystemErr     R     at java.lang.reflect.Method.invoke(Native Method)
[1/9/04 13:13:13:400 EST]  d89289f SystemErr     R     at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)

Solution: Download the latest version of the Pinnacor portlet package from the portlet catalog.72590.RN

 

Problem: The My Lists portlet does not function properly after installing the WebSphere® Portal 5.0.2 fix pack

Solution: Manually update the My Lists portlet by completing the following steps:

  1. Ensure that WebSphere® Portal is running.
  2. In a Web browser, open the following URL: http://<host>:<port>/wps/portal:, where host is the fully qualified host name of the machine that is running WebSphere® Portal and port is the port number. For example, http://www.ibm.com:9081/wps/portal.
  3. Click Log in.
  4. Type our User ID and Password. This user must have appropriate access rights.
  5. Click Administration in the banner.
  6. Click Portlets in the navigation tree.
  7. Click Manage Applications in the Portlets section of the navigation tree.
  8. Select mylist.war from the list of Web modules.
  9. Click Update.
  10. Browse for the <wp_root>\installableApps\mylist.war file.
  11. Click Next.
  12. Click Install. After the installation has completed, a message should appear at the top of the screen indicating a successful installation.
68565f_1

 

Problem: In the Manage Document Libraries administrative portlet, special views not copied to the new document library.

When copying an existing document library, special views are not copied to the new document library. The copy document library process can create a new document library with the same settings, documents, and folders. However, views will not be copied to the new document library.

Solution: Recreate the views for the new document library, as we would for a new document library.82822.RN

 

Problem: IBM® Internet Mail Box portlet might not run on WebSphere® Portal 5.0.2.2 on WebSphere® Business Integration Server Foundation 5.1

IBM® Internet Mail Box portlet might not run on WebSphere® Portal 5.0.2.2 on WebSphere® Business Integration Server Foundation 5.1

Solution: If WebSphere® Portal is deployed on WebSphere® Business Integration Server Foundation 5.1, the IBM® Internet Mail Box portlet might experience problems, including references to a nested javax.management.MBeanException. 91913.RN

 

Problem: The Sametime portlet generates the error "Sorry, Sametime is either not enabled in the portal, or the Sametime Server is unavailable."

This error message from the "My Contacts" portlet typically indicates that a configuration is incomplete or incorrect.

Solution: Follow the steps below to correct the problem.

  1. Verify that the WebSphere® Portal server has been configured to use Sametime.

    The values, shown in italics below, need to be modified to our specific environment. To confirm that the settings have been applied and are correct, review the Sametime section in the CSEnvironment.properties file, in the <wp_root>\shared\app\config directory. Reference the WebSphere® Portal 5.0.2 Information Center at http://www.ibm.com/websphere/portal/library for more information about the CSEnvironment.properties file by selecting Installing -> Lotus Collaborative Components -> Configuring -> Reference: Additional configuration.
    Section of properties file
    Property
    Value
    Collaborative Components Properties LCC.Sametime.Enabled Description: The property that determines whether Lotus Sametime is enabled.

    Setting LCC.Sametime.Enabled to true enables this component. Setting the value to false disables it.
    Recommended Value: true
    Default Value: false

    LCC.Sametime.Server Description: The name of the Lotus Sametime server.
    Recommended Value: my.server.com
    Default Value: my.server.com
    LCC.Sametime.Protocol Description: The protocol used to connect to the Lotus Sametime server.
    Recommended Value: http
    Default Value: http
    LCC.Sametime.Port Description: The port number for the Lotus Sametime server.
    Recommended Value: 80
    Default Value: 80

  2. Verify that the security setting have been set properly on the Sametime Server by referencing "Configuring Lotus Sametime and WebSphere® Portal to work together" in the WebSphere® Portal 5.0.2 Information Center at http://www.ibm.com/websphere/portal/library and selecting Installing -> Lotus Collaborative Components -> Configuring -> Sametime in the Contents menu.
93856.RN

 

Problem: Only two groups display when we initially click the Users and Groups portlet

When we initially click the Users and Groups portlet (Administration>Access>Users and Groups), only the following two groups display:

Solution: Do a search to find more users and groups or click All portal user groups to see further groups in the registry.104084

 

Problem: WebSphere® Portal continues to install after giving an installation failure message

We see an installation failure message but WebSphere® Portal continues to install.

Solution: There is no installation support for locale zh_CN.gb18030, use zh_CN.gbk instead.128382.RN

 

Related to small devices

 

Problem: Support for Handheld and Cell Phone Device Simulators

Solution: If we need to test a portlet with a device simulator, we might need to add the user agent string of the device simulator to the WebSphere® Portal client list. To do this, go to Administration > Portal Settings > Supported Clients > New Client.

Comments: Consult the documentation that is included with the device simulator to determine the user agent strings that the simulator supports and add these using the Manage Clients administration portlet.23240.RN

 

Problem: Remove default WML pages for i-mode phone users

There are several WML default pages that users might have to scroll through to get to the page they want.

Solution: The administrator can remove these default pages in the portal.48756f_1.RN

 

Problem: Cannot see drop-down menu for portlets on small devices

Comments: Small devices do not support the type of WML that is needed to see drop-down menus.57505.rn

 

Problem: Overriding the default HTML client

The Manage clients portlet in Portal Administration is used to define user agent strings that could be found in the accept header of a client request to help the portal server identify the client. By default, when the client cannot be determined, the Default HTML client is used, which is assigned the user agent pattern of a period followed by an asterisk (.*). As a result, WML clients that are not recognized receive HTML markup.

Solution: If our portal supports WML, cHTML, or other markup, use the Manage clients portlet to remove the default HTML client and user agent string.

The portal sends the following message to unrecognized clients:

  Error 202: Our client could not be determined.
24144

 

Related to Document Manager

 

Problem: Receive deadlocks or numerous timeout errors when using Document Manager

When using Document Manager under stress, two error conditions can occur: one involved deadlocks, the other involves numerous timeout errors.

Solution: The deadlocks can be resolved by following the steps in the release note in this document to alleviate WebSphere® Portal deadlocks. The timeout errors can be fixed by updating the DB2 locklist parameter. We can update this parameter using the following command.

 
db2 update db cfg for <wpcp_db> using locklist 1024

where <wpcp_db> is the name of our WebSphere® Portal content publishing/Document Manager database.

For more information, refer to the WebSphere® Portal V5.0 Tuning Guide available at http://www-1.ibm.com/support/docview.wss?rs=688&context=SSHRKX&q1=tuning&uid=swg27004492&loc=en_US&cs=utf-8&lang=en+en 83448

 

Problem: Cannot save or load an attachment to Document Manager

If we try to add an attachment from Document Manager while using Internet Mail Box, we will receive a blank portlet.

Solution: There is no known workaround at this time.83353

 

Problem: (UNIX only) Cannot view files using Document Manager portlet viewer

If we attempt to view a file, such as a.PRZ or.ppt file, using Document Manager portlet viewer and receive a window with no viable content, we might need to set a DISPLAY variable in our UNIX environment.

Solution: Check the following:

  1. Verify Motif2.0 or LessTif2.0 (lesst if 0.93.x releases/builds) is installed.
  2. Verify the account which starts portal server (likely the root) has DISPLAY=ip:0.0 (where ip is the ip address of the machine) set in their profile.
  3. Verify that xhost+ is enabled.
  4. Start the portal server from the console or XServer enabled client.
80467.RN

 

Problem: Unable to import files into Document Manager that contain multiple periods (.) in the file name.

Only Productivity Component documents can have multiple periods (.) in a file name. This is because documents that are created using Productivity Components use the odc extension, which requires multiple periods. For example, a Microsoft Word document named "My.Word.doc" is not supported. However, a Rich text Editor document named "My.odc-text.zip" is supported. Further, file names with more periods than are required by the odc extension are also not supported, so a document named "My.Test.odc-text.zip" is not supported.

Solution: When using Document Manager, only import files with the supported use of periods (.) in the file name, such as those that are necessary for naming Productivity Component files.80290

 

Problem: Document Manager option to set search index frequency is not supported.

In WebSphere® Portal version 5.0.2.3, the option to set search index frequency through the Document Manager configuration page has been removed.

Solution:The search index is updated every 60 minutes. This interval can not be changed.124642.RN

 

Related to various component configurations

 

Problem: Single signon between WebSphere® Portal and other applications does not work

Under certain circumstances there is a known problem with single signon between WebSphere® Portal and other applications on the same WebSphere® Application Server installation. In these cases it is not possible to log into an application on an application server, such as the application server Administrative console, and then log in to a portal that is running on the same application server without renewed authentication (In other words, single signon fails). The portal displays a misleading error message saying that the user's portal session has timed out. The portal then prompts the user to log in again. This problem occurs only with single signon between applications that run on the same WAS installation.

Solution: To resolve this problem, make sure that the session cookie of the other application is scoped to that application only. To do this, perform the following steps:

  1. Log in to the WAS Administrative console.
  2. Navigate to Applications > Enterprise Applications > respective application > Session Management, where respective application is the application with which single signon does not work.
  3. Click on Enable Cookies link (not the check box).
  4. Set the cookie path value to the complete application base path. For example, for the Administrative console of the application server this would be /admin.
  5. Apply the changes and restart the application so that the changes take effect.

Single signon will now work when logging into the portal.

Comments: The reason for this error is that the session cookie of the other application is not specified properly, that is the cookie path has a too general value, and is therefore also sent to the portal. In most of these cases the cookie is specified as a simple slash ( / ). The portal application mistakes this as an old, invalid portal session cookie.57193.RN

 

Problem: (Solaris only) WebSphere® Portal configuration fails on GB18030 locale

We might receive the following error message during portal configuration tasks on Solaris with a GB18030 locale, 

BUILD FAILED
file:../config/actions/process.xml:101: Failed to copy /opt/WebSphere/PortalServer/config/templates/SetupDazzle_hr.properties to /opt/WebSphere/PortalServer/config/work/SetupDazzle_hr.properties due to null

Solution: Remove <Portal>/config/templates/SetupDazzle_hr.properties, and then rerun the task manually, if possible. If we cannot rerun this task manually, change the locale to GBK or C, and then reinstall the portal server. 81106

 

Problem: "Duplicate target: 'WP-PTF-5021' " error when attempting to run WPSconfig

This problem occurs in a WebSphere® environment where a removal of the WebSphere® Portal V5.0.2 Cumulative Fix 1 (5.0.2.1) was not successful. When uninstalling the cumulative fix, the process creates a temporary XML file. The temporary file remains if a failure to perform the configuration task to restore portal content and web applications to WebSphere® Portal V5.0.2 occurs.

Solution: Remove the duplicate XML file.

From the <wp_root>/config/includes/ directory, delete the file WP_PTF_5021_TEMP.xml before reinstalling the cumulative fix.80017.1

 

Problem: Changing the WebSphere® Portal URI

The Information Center topic, Changing the WebSphere® Portal URI, does not provide complete information for modifying the URI. The modify-servlet-path task does not update the context root of the portlets. An additional step is required to configure all applications of WebSphere® Portal to use the new context root.

Solution: After running the modify-servlet-path task as described in step 7, perform the following steps before starting WebSphere® Portal, depending on whether we are using an internal or external Web server:

Internal Web server

  1. Enter the following commands to configure the WebSphere® Portal URI:

    • UNIX:

      ./WPSconfig.sh action-update-portlets

    • Windows: WPSconfig.bat action-update-portlets

    Check the output for any error messages before proceeding with the next task. If any of the configuration tasks fail, verify the values in the wpconfig.properties file.

External Web server (such as IBM® HTTP Server)

  1. Regenerate the HTTP plug-in in WAS. If we are using a remote Web server, copy the generated plugin-cfg.xml file to the remote server.
  2. Restart the Web server.
  3. Update the portlets with the new context root information. Enter the following commands to configure the WebSphere® Portal URI:

    • UNIX:

      ./WPSconfig.sh action-update-portlets

    • Windows: WPSconfig.bat action-update-portlets
  4. Regenerate the HTTP plug-in in WAS. If we are using a remote Web server, copy the generated plugin-cfg.xml file to the remote server.
  5. Restart the Web server.
79608f_1

 

Problem: DisableTranslation parameter cannot be changed through GUI

There is a note in the Information Center stating that all the Machine Translation parameters can be modified through the GUI. However, DisableTranslation cannot be changed through the GUI.

Solution: Change the DisableTranslation parameter through the web.xml file for our portlet.

57246.rn

 

Problem: Ignore exception traces in WebSphere® Portal configuration log

When examining the WebSphere® Portal configuration log or watching the output of a database transfer, we might see one or both of the following exception traces.

Solution: These exceptions are benign and can be ignored. For the first exception trace shown here, the line at the bottom (JDBCProvider wpcp50JDBC successfully created.), indicates the desired action was successfully accomplished.57433.RN, 78967

 

Problem: In a clustered environment, Search does not work correctly in Document Manager

When using Document Manager in a clustered environment, the search does not work because the search index location is not available to all the machines in the cluster.

Solution: To enable Search for a clustered environment, complete the following steps on each machine in the cluster:

  1. Edit the WCM.properties file in the <was_root>/wpcp/config/WebSphere_Portal/author directory. Change the value of the wcm.indexedsearch.path property to a cluster-safe directory (for example, wcm.indexsearch.path=C:/idx/). Note that we must use a forward slash (/) instead of a backward slash (\) when typing the directory path, regardless of the operating system used.
  2. Edit the WCM.properties file in the <wp_root>/wpcp/v5.0/author directory. Change the value of the wcm.indexedsearch.path property to be the same directory path we specified in the previous step.

    The value of wcm.indexedsearch.path in both copies of the WCM.properties file must match.

  3. Go to the directory we specified in the wcm.indexedsearch.path property, and delete the existing search index file on the machine, if the file already exists.
  4. Update the search index. We can either wait until the next scheduled update occurs, or we can change the interval to the shortest possible time to cause the update to occur sooner. Refer to the "Managing documents > Document Manager > Search" topic in the WebSphere® Portal Information Center for details on setting the update interval.
  5. Verify that the update process is complete by going to the directory where the search index file is located and monitoring the disk space used by the file. When the size of the file stabilizes, the update is complete.
71995

 

Problem: Restart the portal server after removing style sheet

Page aggregation is not dynamic in that if a stylesheet is removed, the portal server will not use the next stylesheet in the directory structure. The portal server must be restarted in order to use the next stylesheet.

Solution:

Here is the order that the portal server looks for the stylesheet.

 /wps/themes/html/Science/ie/en/Styles.css              
 /wps/themes/html/Science/ie/Styles.css                 
 /wps/themes/html/Science/en/Styles.css                 
 /wps/themes/html/Science/Styles.css                    
 /wps/themes/html/ie/en/Styles.css                      
 /wps/themes/html/ie/Styles.css                         
 /wps/themes/html/en/Styles.css                         
 /wps/themes/html/Styles.css

If the portal server is started using the stylesheet /wps/themes/html/Science/ie/en/Styles.css and then we remove that stylesheet we will need to restart the portal server before it will use the new stylesheet, /wps/themes/html/Science/ie/Styles.css. 88277.RN

 

Problem: XML Access tasks may result in errors during install and uninstall if the direct port is not used

Solution: When running any XML Access, we must use the direct port, for example, 9081, instead of going through the HTTP server on port 80.81925

 

Problem: Search index appears corrupt

The search index appears corrupt and is not built the next time WebSphere® Portal starts.

Solution: Delete the corrupted index and allow it to be rebuilt. Check the systemerr log in wp_root/log/SystemErr.log for the following error:

R DocStorage add failure! _38_0G0ALFJJOD0CH91C_20Q - Thread-30
R java.lang.ArrayIndexOutOfBoundsException: 24 >= 1
R     at java.util.Vector.elementAt(Vector.java(Inlined Compiled Code))
R     at com.ibm.hrl.juru.storage.DocStorage.add(DocStorage.java(Compiled Code))
R     at com.ibm.hrl.juru.storage.Storage.invertIndex(Storage.java:803)
R     at com.ibm.hrl.juru.Index.doBuildAndKeepAndSwapFwdIndex(Index.java:1006)
R     at com.ibm.hrl.juru.Index.buildAndKeepAndSwapFwdIndex(Index.java:961)
R     at com.ibm.hrl.juru.DoubleIndex.doMaintenance(DoubleIndex.java:1600)
R     at com.ibm.hrl.juru.DoubleIndex.build(DoubleIndex.java:1553)
R     at com.ibm.wcm.utils.SearchIndexUtility.updateSearchIndex SearchIndexUtility.java:303)
R     at com.ibm.wcm.commands.JuruIndexCommand.execute JuruIndexCommand.java:116)

The following error occurs in systemout log at wp_root/log/SystemOut.log:

TraceNLS      u No message text associated with key java.lang.ArrayIndexOutOfBoundsException:.24.>=.1 in bundle com.ibm.wcm.CMStrings
WCPLogger     E com.ibm.wcm.commands.response.JuruIndexJobResponse updateSearchIndex java.lang.ArrayIndexOutOfBoundsException: 24 >= 1

There may also be related exceptions from the com.ibm..hrl.juru package, which will be resolved by allowing the index for that project to be rebuilt.

To remove a corrupt index, delete the contents of that project's directory within the search index directory structure. For example, if the project number is 101, delete the /101 directory in /was_root/wpcp/config/WebSphere_Portal/author/Indexes/. This path may be different if we specified an alternate location in wcm.properties.

The next change to the content of that project triggers the thread which rebuilds the index.104422_doc

 

Problem: WebSphere® Portal V5.0.2 Cumulative Fix 1 (5.0.2.1) for iSeries does not work without applying the appropriate patch

Solution: Go to the iSeries support Web site at http://www-912.ibm.com/supporthome.nsf/document/10000069 to obtain PTF SI12761 and apply the patch.78108

 

Problem: Errors related to credential-segment resources when enabling security

We might see an errors similar to the one below when enabling security for the portal: 

com.ibm.wps.command.xml.XmlCommandException: XMLC0090W: It is not possible to modify credential-segment resources. 
Existing settings are left unchanged.

This indicates that the credential segment entry already exists and has not been modified.

Solution: No action is necessary. WebSphere® Portal will continue to work normally even after this warning.82918

 

Problem: Cannot clean <wp_root>/config/work directory after moving to a cluster environment

When upgrading WebSphere® Portal V5.0.2 or 5.0.2.1 to 5022 in a cluster environment, the <wp_root>/config/work directory cannot be cleaned up after the 5.0.2.2 configuration is finished.

Solution:

This workaround should be done only if the WP-PTF-5022 task has not yet been run.

Delete the directory manually by 

 
    Windows:   rmdir /s /q <wp_root>/config/work
    Unix:      rm -rf <wp_root>/config/work

The work directory can be deleted manually if there are no other errors. If there are errors, the work directory should have logs that are useful or necessary for debugging.

If we have already experienced this failure, manually execute the last task in the subtask list ( action-create-history-event-WP-PTF-5022-INCREMENTAL and manually delete the work directory using the tasks above. 98506.RN

 

Related to Remote Web server

 

Problem: Configuring our Web server

The Information Center topic, Configuring our Web server, contains misleading information about the value for the WPSHostName property in the Configuring for a remote Web server section.

Solution: The value for this property should be the fully qualified host name of the Web server that WAS is configured to use, which in this case, is the remote Web server.71965

 

Problem: Exception occurs while starting WebSphere® Portal in the portal server log files

We might receive the following exception while starting WebSphere® Portal in the portal server log files: 

--8<----- wps_<timestamp>.log - snippet start --------
<date> <time> E com.ibm.wps.services.cache.CacheFactoryImpl createNewCache
  javax.naming.NameNotFoundException: Name comp/websphere not found in context "java:".
 <stack trace>
<date> <time> E com.ibm.wps.services.cache.CacheFactoryImpl createNewCache
  Could not create transaction-aware cache wrapper, running without it! - StackTrace follows...
--8<------ wps_<timestamp>.log - snippet end ---------

As a result of this exception, caches cannot be wrapped in a transaction-aware interface. However, portal can work without the transaction-aware cache wrapper. The portal might not perform as well if administrative tasks are performed in a multiuser environment. Portal users and administrators might not experience any differences as a result of this problem.79959.rn

 

Problem: Additional step needed to configure external Web server

The information in Step 13 of the Installing WebSphere® Portal on a separate WAS instance not managed by Deployment Manager > Installing WP01 in the WebSphere® Portal V5.02 Information Center is incomplete. Step 13 currently reads as follows:

If WP01 was installed using the default HTTP port values, then the port
 configured to access WebSphere® Portal might not be recognized as a
 Virtual Host in the Deployment Manager and must be added. For example, 
if we access WebSphere® Portal using the URL http://wp01:9081/wps/portal,
 then we must ensure Deployment Manager has a Virtual Host definition
 for port 9081 as well. In the Administration Console, open the 
Environment  Virtual Hosts view, click on the default_host entry or 
the entry for the virtual host that is being used to access the 
WebSphere® Portal application. Select the Host Aliases link. 
On the resulting page, ensure there is a host name and port entry to 
match the values used to access WebSphere® Portal (for example, "*:9081").

Solution: We must confirm that Deployment Manager has a Virtual Host definition for port 9081. If we do not complete this step, the cluster will not start.81292

 

Related to custom themes and skins

 

Problem: Administrative portlets fail on pages that use customized themes

When one of the administrative portlets is placed on a page with a customized theme, or a customized theme has been applied to Portal Administration, the portlet could fail with a null pointer exception written to the log file. This is because the administrative portlet requires certain request parameters for processing.

Solution: If we need to use an administrative portlet with a customized theme, make sure we add the <wps:adminNavHelper/> tag in the Default.jsp and the Plain.jsp for the theme. This tag should be placed towards the top, just after the taglib directive for the portal tag library (engine.tld). For an example of this tag, examine the Default.jsp for the Admin theme. 82284

 

Development

 

Problem: Cannot create a version of a document in Document Manager in WebSphere® Portal V5.0.2.3 V5R4 on iSeries DB2

If try to create a version of a document in Document Manager in WebSphere® Portal V5.0.2.3 V5R4 on iSeries DB2, we will receive the error message 

  Error updating document properties!

Solution: Apply APAR PK23937. This fix is available on the IBM® Support site.

157737.RN

 

Problem: Cooperative portlets cannot implement doTitle() method

Cooperative portlets cannot implement the doTitle() method of the IBM® portlet API. This is because the standard wrapper portlet for cooperative portlets does not implement PortletTitleListener to prevent the container from always calling each cooperative portlet's doTitle() method, regardless of whether the portlet implements PortletTitleListener.

Solution: If the portlet needs to implement doTitle(), it must extend the base PortletWrapper class, implement PortletTitleListener in the extension, and use this as the wrapper class in web.xml.

Example

package com.myco.mywrapper;

import org.apache.jetspeed.portlet.*;

public class MyPortletWrapper extends com.ibm.wps.pb.wrapper.PortletWrapper implements PortletTitleListener
{
  Portlet appPortlet_ = null;

  public void doTitle(PortletRequest request, PortletResponse response) throws PortletException, IOException
  {
    Portlet appPortlet_ = getApplicationPortlet();
    try
      {
      ((PortletTitleListener)appPortlet_).doTitle(request, response);
      }
    catch (ClassCastException e)// should not happen, 
                                // as this class should be provided only if the app portlet implements PortletTitleListener
    {
      response.getWriter().print(request.getPortletSettings().getTitle(request.getLocale(), request.getClient()));
    }
  }                      
}

To specify the new wrapper portlet in the web.xml, change the standard wrapper for cooperative portlets:

   <servlet-class>com.ibm.wps.pb.wrapper.PortletWrapper</servlet-class>

to the new wrapper class:

   <servlet-class>com.myco.mywrapper.MyPortletWrapper</servlet-class>
82613

 

Problem: Cooperative portlets displaying incorrect strings for Click-to-Action

A user invoking the click-to-action menu of a cooperative portlet might be presented with the name of the action instead of the caption that is intended to be displayed. Action names are used internally by the property broker and are not intended to be displayed. The caption for the action is more informative and can be displayed in the user's click-to-action menu in any locale supported by the portlet.

This problem can occur if the user's browser or portal locale is set to a language that is not supported by the portlet (the portlet does not provide a compatible resource bundle for the locale).

Solution:

If the user needs to keep the locale settings, then the solution is for the portlet developer to provide the appropriate resource bundle for that language.82700.RN

 

Mixing JSR 168 and IBM® Portlet APIs in WebSphere® Portal

We can place any combination of IBM® and JSR 168 compliant portlets on a page. However, portlets can only import packages from one of these APIs - not both. 93672#endif

 

Administration

 

Problem: Browser back button can show secured page after logout

With some browsers we might be able to view the information from a previous portal session by using the back button after logout. When we log out and click the back button, we can see the page that was last viewed. The problem only concerns the display and view of data. The portal or the displayed data cannot be modified as clicking the back button does not undo the logout. The reason for this is that when we click the back button, the browser returns to the data cached by the browser.

Example scenario: We view an e-mail and click Log out. The portal returns to the Login panel. If we then click the back button, we might be able to view the e-mail again, depending on our browser.

Solution: Users can prevent the display of secured pages by either closing the browser after logout or clearing the browser cache. 83991

 

Problem: Creating and ordering new clients does not always work on iSeries V5R3

The Manage Clients portlet, which is used to add, edit, or remove clients that are supported by the portal server, does not always allow us to add a new client at the last position and arrange the position of clients when the portal server is installed on iSeries V5R3.

Solution: To set the position of new clients in the clients list.

91850.RN

 

Known limitations for Productivity Components

 

Problem: Spell Checker component does not work

Spell Checker component does not work on SuSE SLES 9(x86) platform with the WAS V5.1.1.3.

Solution:This is a limitation of the present release.129498.RN

 

Problem: After changing the context root using the modify-servlet-path task the inline Productivity Components no longer works

Solution: There are four applications which must be updated with the new context root: 

RichTextEditor (/wps/richText/*)
SpreadsheetBlox (/wps/spreadSheet/*)
Presentation (/wps/presentation/*)
WPCP_Email (/wps/PersEmail/*)

  1. Update <context-root>/wps/PersEmail</context-root> with our context root (replace /wps) for the following files: 
    <was_home>\config\cells\yourcell\applications\RichTextEditor.ear\deployments\RichTextEditor.war\META-INF\application.xml
<was_home>\config\cells\yourcell\applications\SpreadsheetBlox.ear\deployments\SpreadsheetBlox.war\META-INF\application.xml
<was_home>\config\cells\yourcell\applications\Presentation.ear\deployments\Presentation.war\META-INF\application.xml
<was_home>\config\cells\yourcell\applications\WPCP_Email.ear\deployments\WPCP_Email\META-INF\application.xml
  2. Restart WebSphere_Portal.
67222.RN

 

Problem: Error message "error occurred while converting the document" occurs when viewing a password-protected file

We can receive this error message while using Rich Text Component, Spreadsheet Component, Internet Mail Box, or Document Manager. Document conversion for viewing or editing documents is not supported with documents that are password-protected from within their native applications.

Solution: Use the access control mechanisms of WebSphere® Portal and Document Manager.71186

 

Problem: (Mozilla only) Closing the window using the button in the upper right corner

In Mozilla, if we use the close button in the upper right corner of the window, we might receive numerous prompts to save.

Solution: Click OK to continue until the prompts no longer appear. 79964

 

Problem: In Spreadsheet Component, using keyboard sequences for copy and paste when using Mozilla causes application failure

If we use Ctrl + C to copy data and Ctrl + V to paste data multiple times, we might see all the rows of data moved to one cell. In Mozilla, this causes the application to crash.

Solution: Use the drop-down menu to copy and paste instead of the keyboard sequences.69425

 

Problem: Logical functions such as isstring() and isvalue() do not convert correctly when exporting to Excel

In Spreadsheet Component, logical functions such as isstring() and isvalue() do not convert correctly when exporting to Excel.

Solution: Rewrite the formula to avoid these functions.67022.RN

 

Problem: Editing Excel files with formula =Cell("ROW,A30) fails and gives #PARSE error

In Spreadsheet Component, if we edit Excel files with the formula =Cell("ROW,A30), the operation fails and gives a #PARSE error. The =Cell() function does not exist in the Spreadsheet Component, so it cannot be converted when the Excel file is imported.

Solution: Rewrite the formula for that cell.68389.RN

 

Problem: small() and large() functions do not export correctly to Excel

If a Spreadsheet Component document is created with these functions using the syntax =small(num1, num2, num3,..., n), and then exported to an Excel file, the exported file will have the wrong value in that cell.

Solution: The syntax for the large() and small() functions is not valid in Excel. The correct syntax is large(Range, n), such as =large(A1:B5,2). If we use this syntax in the original document,the conversion will work correctly.67343.RN

 

Problem: Problems displaying currency in spreadsheet

An Excel spreadsheet document that uses certain national currency formats will not display with the correct currency symbol when loaded in the Spreadsheet Component.

Solution: Apply the desired currency format from within the Spreadsheet Component.61386f_1.RN

 

Problem: User error message when creating a document

When using the Document Manager workflow feature, a user might receive the message "Document Manager cannot communicate with WPCP" when creating a document. Users receive this message if their user name is longer than 13 characters.

Solution: Modify the username to contain 13 or less characters.70835.RN

 

Problem: Receive error message when converting document using Rich Text

Attempts to convert documents result in the message "Error occurred converting document!"

Solution: To convert documents successfully, perform the following steps:

  1. Export PATH=$PATH:/opt/WebSphere/PortalServer/shared/app/oiexport
  2. Export SHLIB_PATH=/opt/WebSphere/PortalServer/shared/app/oiexport
  3. Restart WebSphere® Portal.
76219

 

Problem: Attachments cannot be viewed using IBM® Internet Mail Box

Email attachments cannot be opened and viewed.

Solution: To view attachments, perform the following steps:

  1. Export PATH=$PATH:/opt/WebSphere/PortalServer/shared/app/oiexport
  2. Export SHLIB_PATH=/opt/WebSphere/PortalServer/shared/app/oiexport
  3. Restart WebSphere® Portal.
76575

 

Known limitations for Portal Toolkit

 

Known problems and limitations

 

Hardware requirements

See the Portal Toolkit Installation Guide for the hardware requirements regarding installing of Portal Toolkit.

 

Supported software

 

Operating systems:

 

WebSphere® Studio:

 

WebSphere® Portal:

For the WebSphere® Portal Test Environment (Local debugging)

For the WebSphere® Portal Server Attach (Remote debugging)

 

Databases supported in WebSphere® Portal 5.0 Test Environment:

 

Where to find more information

 

Search Frequently Asked Questions

 

Search products updates and fixes

 

Search products news

 

At a glance

Portal Toolkit for WebSphere® Studio is a comprehensive toolkit for developing portlet applications. Portal Toolkit V5.0.2.2 is provided in the form of plug-ins to the following products of the WebSphere® Studio family.

Portal Toolkit provides the following:

What's new in Portal Toolkit V5.0.2.2

 

Known problems and limitations

This section describes known problems we may encounter while using Portal Toolkit. Some problems may require workarounds.

 

Installation

 

Problem: CREATE DATABASE fails during installation

When we install WebSphere® Portal V4.2 Test Environment, the installation will fail to create databases if the DB2 Database user ID or password is invalid.

Solution: Specify the correct DB2 Database user ID and password.

 

Problem: Failure of installation of the WebSphere® Portal Test Environment

The portal toolkit installation fails to install the WebSphere® Portal Test Environment for some reason.

Solution:

If the problem can not be determined by the log files, then try performing one of the following:

 

Problem: Portal Toolkit does not work properly on Linux

When the Linux (Red Hat 8.0) operating system is used, Portal Toolkit does not work properly in Korean, Simplified Chinese, Japanese, and Traditional Chinese languages.

Solution: If we want to use the double-byte character set on Red Hat 8.0, we will need to upgrade GTK 2.0 to GTK 2.2.2 or later. However, support for Korean, Simplified Chinese, Japanese, and Traditional Chinese languages is not fully functional. To avoid these limitations, we must use the product in English. To upgrade GTK, refer to "(Optional) Upgrading to GTK 2.2.2 or later" in the Installation Guide of WebSphere® Studio V5.1.2.

Comments: This is a limitation of the national language capability of the GIMP Tool Kit (GTK) that is currently available to Red Hat developers.

 

Creating portlets

 

Problem: Cannot find the Portlet project wizard after installing Portal Toolkit

Solution: Typically, we will be informed about pending updates with a prompt upon the first startup of WebSphere® Studio after installing Portal Toolkit. When this prompt appeared, we should have proceeded accordingly to install these updates. We may have missed or dismissed the prompt.

  1. Start WebSphere® Studio.
  2. Go to Help > Software Updates > Pending Changes. (We should see a Pending Configuration Changes screen. )
  3. Select the updates and click on the finish button.
  4. Restart WebSphere® Studio.

Comments: For more information, refer to the WebSphere® Portal InfoCenter > Portal Toolkit.

 

Problem: Compilation errors with the latest WebSphere® Portal

We can build portlets for WebSphere® Portal V5.0 and WebSphere® Portal V4.2 using Portal Toolkit V5.0.2.2. If we apply a WebSphere® Portal service to our portal server, we may get compilation errors while building the portlets. In this case we need to manually update the files required by the compilation.

Solution: To compile portlets correctly, carry out the following steps.

Comments: We will have to restore these files to the original before we can uninstall the Portal Toolkit.

 

Problem: URL encoding function does not work properly in Portlet JSP files

The URL encoding function does not work properly if the appropriate tag library directive and initialization tag do not exist in the portlet JSP file. Resource URLs in portlet JSP files must be encoded in order to work correctly. The encoding function in Portal Toolkit requires portlet JSP files to include a tag library directive for the appropriate portlet TLD, along with the corresponding initialization tag for that tag library. If these are missing, the encoding function will not work properly and resources may not be found at run time. This problem will appear most commonly when importing existing portlet JSP files created with something other than Portal Toolkit.

Solution: To insert resources that must be encoded into a portlet JSP file correctly, first insert the following appropriate tag library directive and initialization tag into the portlet JSP file.

IBM® Portlets:

<%@taglib uri="/WEB-INF/tld/portlet.tld" prefix="portletAPI"%>
<portletAPI:init />

JSR 168 Portlets:

<%@ taglib uri="http://java.sun.com/portlet" prefix="portlet" %>
<portlet:defineObjects />

 

Problem: Unexpected portlet icon is displayed when enabling Click-to-Action

The Portlet Deployment Descriptor editor and the Project Navigator view show the portlet icons and their name. The icons indicate the state of the portlets. The portlet states are normal, source enabled, target enabled, and source and target both enabled. When we convert a portlet to a Click-to-Action source portlet, only the converted portlet icon should be changed. However, there are cases when more than one portlet icon is changed, such as when multiple portlets are associated with a single servlet. In these cases, icons for portlets other than the intended Click-to-Action portlet icon are incorrectly displayed. The same situation exists when we convert a portlet to a Click-to-Action target portlet.

Solution: More than one portlet icon is changed, however, only one portlet changes, the conversion is successful, and the portlet project is not corrupted.

 

Problem: "Failed to add WPCP nature to project" error during the New Portlet Project wizard

The "Failed to add WPCP nature to project" error occurs during the New Portlet Project wizard if we enable the server targeting support and select any servers.

Solution: Verify that we leave the Disable server targeting support checked in the J2EE Preferences page. When developing portlets, server targeting support should be disabled.

 

Debugging and testing portlets

 

Problem: Cannot set a break point correctly

Solution: Verify that we do not have duplicate JSP files (files with the same filename) in our workspace.

 

Problem: Help mode does not work correctly

Help mode does not work correctly in WebSphere® Portal V5.0 Test Environment or WebSphere® Portal V4.2 Test Environment (WebSphere® Portal V4.2.1) if the portlet application is running on an internal browser. When an external browser is opened in order to display help, the session will not be able to maintain both the internal ActiveX browser and the external browser resulting in the external browser being closed.

Solution: Use a device emulator or an external browser to run the portlet application. For how to use these, see the Portal Toolkit online help.

Comments: If we work with WebSphere® Portal V4.2.0, we will also need to apply WebSphere® Portal V4.2.1. Otherwise doHelp() will not be called.

 

Problem: Cannot create a user in WebSphere® Portal

A user cannot be created in WebSphere® Portal if it is running in the debug mode.

Solution: We need to restart WebSphere® Portal in the normal mode.

For a local debug configuration:

Stop the WebSphere® Portal Test Environment server. Execute "Run on Server" and create a user. Stop this server and execute "Debug on Server".

For a remote debug configuration:

Stop the WebSphere® Portal which is running on the remote machine. Deselect the "Debug Mode" checkbox in the "Administrative Console" of WebSphere® Application Server by referring to "Preparing WebSphere® Portal for Server Attach" in the Portal Toolkit online-help. Start WebSphere® Portal and create a user. Stop WebSphere® Portal, select the "Debug Mode" checkbox, and start WebSphere® Portal.

 

Problem: Click-to-Action does not work with pager function

Click-to-Action portlets does not work with the pager function for WebSphere® Portal or the WebSphere® Portal Test Environment, when included in a Faces JSP page that includes the <c2a:encodeProperty> tag along with the <hx:pagerDelux> tag or the <hx:pagerWeb> tag.

Solution: To use Click-to-Action and the pager function of the data table together in a Faces JSP page, use the <hx:pagerSimple> tag or the <hx:pagerGoto> tag instead of the <hx:pagerDelux> tag or the <hx:pagerWeb> tag.

 

Problem: Faces Portlet cannot be installed on WebSphere® Portal v5.0.2

When creating a Faces portlet using the Portal Toolkit, the JS Resource Servlet in the web.xml file is not assigned an ID. Installation of this portlet on WebSphere® Portal v5.0.2 or earlier will fail. This problem does not occur when installing onto a v5.0.2.1 WebSphere® Portal.

Solution: The workaround for this is to add a unique ID to the JS Resource Servlet in the web.xml file, as in the following example: 

 <servlet id="Servlet_12345">
     <servlet-name>JS Resource Servlet</servlet-name>
     <servlet-class>com.ibm.faces.webapp.JSResourceServlet</servlet-class>
     <load-on-startup>-1<load-on-startup>
 </servlet>

 

Problem: Can not start the WebSphere® Portal Test Environment

The WebSphere® Portal Test Environment fails to start.

Solution:

Verify successful installation:

This problem may occur because the installation had failed. Check Failure of installation of the WebSphere® Portal Test Environment and remedy as required.

Rectify the situation regarding excessively long filenames:

This problem may have also occurred because the portlet project has files with an excessively long filename. To solve this problem, either shorten the project name, the package prefix, and/or the class prefix so that the generated filename length will be acceptable. Alternatively, the individual filenames themselves may be shortened to an acceptable length. Furthermore, if the default directory is used as the workspace, it would also be effective to use a different workspace with a shorter directory length. We can specify the workspace directory by launching WebSphere® Studio. If the dialog box to specify it does not appear, go to the command prompt and type "-setworkspace" after typing the WebSphere® Studio execution command.

Change the server configuration:

This solution only applies when WebSphere® Portal V5.0 Test Environment cannot start in the debug mode. In the server configuration, make sure that the Enable hot method replace in debug mode checkbox in the Server page is selected. To do this, carry out the following steps:

  1. In the Servers view, double-click the WebSphere® Portal V5.0 Test Environment which fails to start in the debug mode in order to open its server configuration.
  2. Select the Server page.
  3. Select the Enable hot method replace in debug mode checkbox.
  4. Press Ctrl+S to save the updated server configuration.

(Linux only) Change the access permission for the WebSphere® Portal database:

Because of a limitation of WebSphere® Portal, the WebSphere® Portal Test Environment is available for only one user to use. We can allow other users to use the server by turning on read, write, and execute permissions for the WebSphere® Portal database.To change the access permission, carry out the following:

  1. cd <wsad>/runtimes/portal_v50/cloudscape
  2. chmod -R 777 wps50
Alternatively, we can change the user who is able to use the server by uninstalling and reinstalling the WebSphere® Portal Test Environment.

(Windows only) Verify that the Windows user is an Administrator:

We must be logged in as an Administrator. If not, login to Windows as an Administrator and run the WebSphere® Portal V5.0 Test Environment.

 

Problem: Single-sign-on using LDAP does not work

Single-sign-on using LDAP does not work on the WebSphere® Portal Test Environment. This problem occurs because LDAP is not installed on the WebSphere® Test Environment.

Solution: This is a limitation of the Test Environment as LDAP cannot be installed on the WebSphere® Test Environment. However, it will work when debugging using the Server Attach debug configuration.

 

Problem: Updated resources are not refreshed

Updated resources are not refreshed during local debugging with WebSphere® Portal V5.0 if the Enable universal test client is selected in the server configuration.

Solution: Restart the server in order to confirm the resource changes of the portlet projects.

 

Problem: Cannot install portlets using the administration portlet in the test environment

In the WebSphere® Portal V5.0 Test Environment server, installing portlets using the administration portlet will fail.

Solution: In the WebSphere® Portal Test Environment server, installing portlets using the administration portlet is not supported. To deploy portlets in the WebSphere® Portal Test Environment, we must use the "Publish" function of WebSphere® Studio. To use the "Publish" function, right-click the portlet application project and select Run on Server, or right-click the server in the servers view and select Publish.

 

Problem: ClassCastException or NamingException errors

The problem occurs if the portlet project refers to other projects.

Solution: To run or debug portlet projects which refer to other projects in our workspace, carry out the following: This solution works only for WebSphere® Portal V5.0 Test Environment.

  1. Add required projects to Java Build Path and Project References.
    1. In the Project Navigator view, right-click the portlet project and select Properties.
    2. Select Java Build Path > Projects.
    3. Select all required projects.
    4. In the left, select the Project References page.
    5. Select required projects.
    6. Click OK.

    Continue the following steps only if the required projects are EJB projects:

  2. Add all required projects to the EAR project for the portlet project.
    1. In the Project Navigator view, expand the EAR project.
    2. Double-click the EAR Deployment Descriptor to open its editor.
    3. Select Module page.
    4. In Module section, click Add to add projects to use and then click Finish. Repeat this for all other required projects.
    5. Press Ctrl + S to save the data.
    6. Click OK if Repair Server Configuration dialog appears.
  3. Add Java JAR Dependencies.
    1. In the Project Navigator view, right-click the portlet project and select Properties.
    2. Select Java JAR Dependencies page.
    3. Select jar files and click OK.
  4. Add all required projects to the server.
    1. In the Servers view, right-click the server and select Add and remove projects.
    2. Select an unused project in the Configured projects list box and click Remove. Repeat this for all other unused projects.
    3. Select a required project in the Available projects listbox and click Add. Repeat this for all other required projects.
    4. Click Finish.

In this case, we do not have to copy library files to the /WEB-INF/lib folder or define shared library files in the Portal server configuration.

 

Problem: Error occurs if portlet application uses a database

An error may occur if our portlet application uses database other than Cloudscape.

Solution: We need to add the JDBC driver to the WebSphere-specific class paths of the WebSphere® Portal Test environment. Carry out the following.

  1. In the Servers view, double-click the WebSphere® Portal Test Environment server. The server editor opens.
  2. Click the Environment tab at the bottom of the editor.
  3. In the ws.ext.dirs section, add the JDBC driver. For example, add SQLLIB\java12\db2java.zip file for DB2, where SQLLIB is the directory that we installed DB2.
  4. Press Ctrl+S.

 

Problem: PortletSession data is not correct

PortletSession data is not correct during local debugging on WebSphere® Portal V4.2 Test Environment.

Solution: If we want to debug a portlet that uses portlet session data, we will need to add the following statement in the following portal server configuration file.

<WS_installdir>\runtimes\aes_v4\config\WebSphere® Portal-cfg.xml
<jvmSettings xmi:id="JavaVirtualMachine_1" classpath="" bootClasspath="" verboseModeClass="false" verboseModeGarbageCollection="false" verboseModeJNI="false" initialHeapSize="0" maximumHeapSize="256" runHProf="false" hprofArguments="" debugMode="false" debugArgs="" genericCommandLineArgs="com.ibm.ws.runtime.StandardServer" disableJIT="false">
<systemProperties xmi:id="SystemProperty_1" name="HttpSession.RecurseThroughProxy" value="true"/>
</jvmSettings>

 

Problem: "No contents available" error after Run-on-Server

A "No contents available" error occurs in the WebSphere® Portal V4.2 Test Environment with WebSphere® Portal V4.2.0 when we execute "Run/Debug/Profile on Server" or "Run/Debug/Profile with Device Emulator".

Solution: Reload the content by clicking the browser refresh button or apply WebSphere® Portal 4.2 Fix Pack 1 or APAR PQ72388 (APAR PQ72209).

Comments: Fixed in WebSphere® Portal 4.2.1.

 

Problem: Occurrence of PCO java exceptions

Our debug session may be interrupted due to the following java exception if we debug or test with WebSphere® Portal 4.2.0.

java.lang.reflect.InvocationTargetException: java.lang.NoSuchMethodError: com.ibm.websphere.personalization.resources.SqlMultiTableUtils: method <init>([[Ljava/lang/Object;ILjava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/util/Properties;Ljavax/sql/DataSource;)V not found

at com.ibm.wcm.resources.WorkingSetManager.<init>(WorkingSetManager.java:267)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java(Compiled Code))
at com.ibm.wps.pco.PCOContentFormat.createResourceManagerClassInstance(PCOContentFormat.java:332)
at com.ibm.wps.pco.PCOContentFormat.init(PCOContentFormat.java:225)
at com.ibm.wps.pco.PCOContentFormat.<init>(PCOContentFormat.java:102)
at com.ibm.wps.pco.PCOContentFormat.convertFindAll(PCOContentFormat.java:52)
at com.ibm.wps.pco.PCOContentFormat.findAll(PCOContentFormat.java:92)

Solution: Apply WebSphere® Portal V4.2 Fix Pack 1 or APAR PQ72200.

 

Portlet Preview

 

Problem: An error; "JSPG0113E JSP file (Filename too long) not found" occurs

An error; "JSPG0113E JSP file (Filename too long) not found" occurs in WebSphere® Portal V4.2 when executing the portlet preview if the project name, the filename, the file directory structure or the preview user name is excessively long.

Solution: Shorten the length of the filename, the file directory structure or the preview user name.

 

Problem: An error occurs during configuration of the server (Xml Exception)

An XML Exception occurs and the portlet preview fails to deploy the portlet application in WebSphere® Portal V5.0 if the project name, the filename, the file directory structure or the preview user name is excessively long.

Solution: Shorten the length of the filename, the file directory structure or the preview user name.

 

Problem: An error occurs during configuration of the server (SaxParseException)

A SaxParseException occurs and the portlet preview fails in WebSphere® Portal V4.2 if the specified place name includes a space character.

Solution: Change the place name in the portlet preview preference (Windows > Preferences > Portlet Preview) so that it does not contain a space character.

Comments: This problem does not occur in WebSphere® Portal 5.0.

 

Problem: Portlet modification is not previewed correctly

Portlet modifications are not previewed correctly when the portlet previewed before the modifications are cached by the browser.

Solution: Log out and log back in to the portal server.

 

Migrating portlets

 

Problem: Failure of migrating Portal V4.2 portlets to V5.0

Changing the Portlet API level fails if the length of the class path is long.

Solution: We need to correct the Java Build Path of the migrated portlet projects. For the required Java Build Path, we can refer to a basic portlet project which is generated by the portlet application wizard. Add the missing required JAR files to the Java Build Path of our migrated portlet project.

 

Problem: Java Build Path is not updated if the Apply button is clicked

Java Build Path is not updated when the user changes the Portlet API level and clicks the Apply button on the properties dialog.

Solution: This is an Eclipse problem. Do not click the Apply button after changing the Portal API level. Instead, only click the OK button and Java Build Path will be correctly updated.

 

Known limitations for Collaborative Component features

The following sections describe known issues and workarounds for Collaborative Portlets and Collaborative Components in WebSphere® Portal 5.0.2:

 

Installation and setup of collaborative portals

This section identifies known problems and workarounds related to installing and setting up collaborative portals with WebSphere® Portal 5.0.2.

 

Problem: Uninstalling Lotus Collaborative Components introduces instability in collaboration features of the portal and in collaborative portlets

Although WebSphere® Portal 5.0.2 supports incremental installation of portal components, if you, as the portal administrator, uninstall Lotus Collaborative Components, collaborative features that use Collaborative Components will no longer work in the portal and in Lotus collaborative portlets.

Solution: Reinstall Lotus Collaborative Components.

 

Problem: LDAP methods in Lotus Collaborative Components fail with authentication error if bind user password for WebSphere® Application Server is entered improperly

When WebSphere® Portal is configured with the IBM® Directory Server set up for LDAP authentication, so that the IBM® Directory contains the bind user name and password, and both the IBM® Directory and the Domino server are configured not to allow anonymous LDAP access, entering the bind user password without quotes causes an authentication error for all LDAP methods in the Lotus Collaborative Components.

Solution: Enclose the bind user password for the WebSphere® Application Server in quotation marks (").

(SPR #SMUY5NSFJQ)

 

Problem: Some actions in Notes and Domino portlet might fail on Windows with newer version of WebSEAL configured for portal

If our portal is configured with WebSEAL version 4.1 Fix Pack 5, users of the Notes and Domino portlet on Windows might experience problems with some portlet actions such as Launch New Document. This occurs because the URL launched by the action might be blocked at the WebSEAL junction due to errors in the locations of certain files.

Solution: When installing WebSEAL version 4.1 Fix Pack 5, carefully follow all included documentation describing how to update binary files.

(SPR #MSHN5QZRPW)

 

Lotus Domino with WebSphere® Portal

This section identifies issues pertaining to configuring Lotus Domino with WebSphere® Portal 5.0.2.

 

Problem: Additional instructions are required for configuring the Lotus Domino server for use with the portal server

After following all other instructions for installing and configuring Lotus Domino, follow these additional steps:

  1. Open Domino Administrator (Notes administrative client).
  2. Log in when prompted for the password.
  3. Open the Domino Directory database (names.nsf) for the server.
  4. Accept the default settings for Directory Profile and click Save and Close.
  5. Open the Server document.
  6. Click the Basics tab and complete the following fields:

    • Domain name. The Domino domain name should be automatically entered here when the server is registered; if not, enter the Domino domain name.
    • Fully qualified Internet host name, for example, Srv1.Acme.com.
    • Administrator. Fill in the name(s) of any administrators, such as wpsadmin, who should have access to this server.

      Depending on our deployment model, we might want to specify additional administrators in this field.

  7. Click the Security tab and specify the following settings:

    Server Access. Use the Access Server field to give users access to the server. (We usually do this through a group.)

If we leave this field empty, all users who can connect to the server will have access to Domino; this creates a potential security risk.

Be sure to give all users whom we want to use Domino access to the server. If we don't, any users without access to the server will not be able to run Domino.

Leave Create new databases empty

Leave Create replica databases empty.

  1. On the Internet Protocols tab, click the HTTP tab, and ensure that the following settings are specified:

    • Host Name

      The fully qualified host name of the server, for example, Srv1.Acme.com

    • Basics

      Set Allow HTTP clients to browse databases to Yes.

      This setting enables the database view selection list that appears when users edit the properties of the Notes and Domino portlet and other collaborative portlets.

  2. On the Ports tab, ensure that the following settings are specified:

    • Port field: A valid network port (for example, TCPIP)
    • Notes Network field: TCPIP Network
    • The server's network address is specified by either the server's numeric IP address or the server's fully qualified host name. The fully qualified host name is preferred; for example, Srv1.Acme.com.
    • Enabled field: Enabled (for the valid network port specified in the Port field)

      Verify that the remaining Enabled fields are set to Disabled to prevent unnecessary error messages from displaying on the server console.

  3. Save and close the Server document.
  4. If necessary, push the server configuration to the secondary servers that host Lotus Collaborative Components and collaborative portlets for the portal.
  5. Restart the server.

(DEFECT 57452)

 

Problem: The Domino Directory used as the LDAP source for the portal cannot contain user or group distinguished names that have special characters if the Domino server is release 5.x

When the Domino server is release 5.x, special characters in distinguished names of either users or groups prevent the names from being recognized by portal administration.

Solution: Change any distinguished names that contain special characters, or use a 6.x release of the Domino server.

(SPR #MSHN5QDLZ9)

 

Problem: Database lists in some portlets fail to populate with database names

In the Notes and Domino, Domino Web Access, and QuickPlace portlets, drop-down lists of database names appear empty if all Domino servers used with the portal do not have SSL certificates signed by the same certificate authority. Solution: Perform the following steps:

  1. Ensure that the Domino server configured for use with the portal has SSL set up properly.
  2. Do one of the following:

    • If the Domino server uses HTTP, set HTTP to run on the default port of 80.
    • If the Domino server uses HTTPS, set HTTPS run on the default port of 443, and enable DIIOP over SSL.
  3. Restart the Domino server.
  4. Examine the SSL certificates for each of the Domino servers that contain source databases for portlets in the portal, and make sure they are all signed by a single certificate authority (CA).
  5. From any of the Domino servers that has a properly signed SSL certificate, copy and paste the TrustedCerts.class file from within the <domino_root>\data\domino\java directory to the portal server machine's class directory <wp_root>\shared\app\.
  6. Restart the portal server.

(SPR #MSHN5RQL3D)

 

Browser issues

This section identifies known problems and workarounds related to browsers used for collaborative portals with WebSphere® Portal 5.0.2. Also refer to People awareness for additional Netscape issues.

 

Problem: Using Netscape or Mozilla, Notes and Domino portlets placed side-by-side on pages with double and triple columns will overlap

When users add Notes and Domino portlets that have many rows of information side-by-side on a portal page that is formatted in double- or triple-column layout, the information in the portlets will overlap if viewed with the Netscape or Mozilla browser.

Solution: Advise users to format portal pages that include Notes and Domino portlets without multiple columns if the Netscape or Mozilla browser is a requirement, or switch to Microsoft Internet Explorer 5.5 or later.

(SPR #SCII5C6HQF, SPR #RPAS5B4LBL, SPR #LMAN5SJNK2)

 

Problem: In the Notes and Domino portlet, using Netscape, users might experience difficulty collapsing and expanding views

When users click the plus or minus icons to collapse or expand views in Netscape 6.02, the icons might not work. In Netscape 7.01, the icons might collapse and expand but not change to display the appropriate plus or minus symbol.

Solution: Close and re-open the portlet to return to the default expanded state. Users might also consider switching to Internet Explorer.

(SPR #VMAA5N4L8W)

 

Problem: In the Notes and Domino portlet, using Netscape, Actions drop-down list might display incorrectly

When users click the Actions (down arrow) icon, its drop-down list with Open, Edit, and Delete options might display incorrectly in some other part of the portlet.

Solution: Users can still select options from the drop-down list. Users might also consider switching to Internet Explorer.

(SPR #VMAA5NKRTY)

 

Problem: In the Notes and Domino portlet, using Netscape, the Show Profile option on the people awareness menu might not work

Solution: Users might consider switching to Internet Explorer.

(SPR #VMAA5NKTRG)

 

Problem: In the Notes and Domino portlet, using Netscape, users cannot create documents that require the rich text applet

The Domino server does not support the rich text applet in the Netscape browser. As a result, if Netscape users click a button in the Notes and Domino portlet that creates a rich text document -- for example, the New Memo button in a mail view -- they might experience a system crash.

Solution: Advise users to switch to Microsoft Internet Explorer 5.5 or later.

(SPR #JHEY5PALM3)

 

Problem: Using Netscape 6.2 or 7.0 with the Notes and Domino portlet, users might experience a system freeze when closing an additional browser window

The problem might occur if a user takes an action in the Notes and Domino portlet that opens a separate window (for example, creating a new document in a view ), and then closes the separate browser window.

Solution: Upgrade to Netscape 7.1, or switch to Internet Explorer.

(SPR #JHEY5P3E8Q)

 

Problem: In the Notes and Domino portlet, using Netscape or Mozilla, options for opening documents in the Lotus Notes client software do not work

If users edit the properties of the portlet when it is configured with a portlet type (such as NOTESVIEW) that allows them to specify how to view documents, and on the Style | Columns page, they specify Lotus Notes, if available for the View documents in option, the portlet opens browser windows instead of Notes when users click the Launch Application icon.

In addition, when the portlet is configured as either MYCALENDAR or NOTESMAIL, and Lotus Notes, if available is specified for viewing documents, clicking either New Calendar Entry or Launch Application does not work.

Solution: Advise users to switch to Microsoft Internet Explorer 5.5 or later to open documents in the Lotus Notes client.

(SPR #VMAA5M6NZ3, SPR #DMAS5PCP5B, SPR #LMAN5SJQ38)

 

Problem: Incorrect hourglass cursor while editing properties of Notes and Domino portlet in Netscape 6.2

Users who edit properties of the Notes and Domino portlet using Netscape 6.2 might notice that the cursor remains an hourglass even after they click Done or Cancel in the Work with Notes Views pages and return to view mode.

Solution: Advise users to switch to Microsoft Internet Explorer 5.5 or later.

(SPR #JHEY5P9AU5)

 

Problem: Using Netscape 6.2, deleting a document from a Notes portlet can cause a browser crash

Solution: Advise users to upgrade to Netscape 7.x, or to Mozilla.

(SPR #VMAA5SVRJY)

 

Problem: People awareness does not work with Netscape 6.2 or 7.0 and Mozilla 1.x.

Solution: Advise users to use Microsoft Internet Explorer.

(SPR #SMUY5T9LFB, #DGAO5D43TD, #BJKE5J3JUR)

 

People awareness

This section identifies known problems and workarounds related to the people awareness functionality in collaborative portals with WebSphere® Portal 5.0.2.

 

Problem: The column specified for people awareness in the Notes and Domino portlet must contain user names

When the Notes and Domino portletType parameter is configured as NOTESMAIL, NOTESDISCUSSION, NOTESTEAMROOM, or NOTESVIEW, in order to enable people awareness, assist portal users to identify and specify a column containing user names in the source database.

Solution: For example, when the portlet is configured as NOTESMAIL, and a user edits the portlet properties to specify the Column for showing people awareness, if the view is $Inbox, advise users to select the Who column from the drop-down list of column names. When the portlet is configured as NOTESDISCUSSION, if the view is the AuthorView, advise users to select Column 0.

(DEFECT 23945)

 

Problem: The Domino Directory used for people awareness might cause delays or lack of awareness if it contains replication conflicts or identical common user names

Solution: Resolve all replication conflicts in the Domino Directory on the Domino server set up for use with the portal by identifying the Person document with the latest updates and deleting any earlier ones. Also, modify names of any users who share a common name so that names become unique (for example, by including an initial).

(SPR #MSHN5NGHCQ)

 

Problem: Sametime status does not update when portal is left inactive

If the portal is configured with people awareness, and a user leaves the portal inactive, the user's online status does not automatically update to Away.

Solution: Apply the Sametime fix for SPR# YSAI-5T6BFD to the Sametime server configured for the portal. Contact Lotus Support for this fix.

The fix is intended for Sametime 3.0 with interim fix 3, and Sametime 3.1 with interim fix 1.

 

Problem: Selecting a name and selecting Add to Contact List does not work

Solution: Users must launch and log in to their Lotus Sametime Client software separately before using this menu item on portlets in the portal.

(SPR #MSHN5SUJ5Y)

 

Problem: Extraneous text appears at top of portal page if people awareness is on and any portlet displays any name of a person who is offline

The extraneous text is

%s is offline

The problem is cosmetic. It does not interfere with functionality of the portal or collaborative portlets. A minor edit to a portal file corrects the problem.

Solution: Follow these steps:

  1. Using a text editor, edit the person.js file located in the following directory: 
    <AppServer>\installedApp\<servername>\wps.ear\wps.war\peopleawareness\person.js.
  2. Locate the following line of text: 
    var s = "<DIV id='personTagTipOffline' type='hidden'></DIV>";
  3. Change type='hidden' to style='display:none', as follows: 
    var s = "<DIV id='personTagTipOffline' style='display:none'></DIV>";
  4. Save the file.
  5. Restart our browser and look at the portlet again. The extraneous text should not appear.

(SPR #MSHY5U5JGV)

 

Problem: People awareness does not work, or a user cannot log in to the Sametime server with the Sametime Connect portlet, if WebSphere® Portal and Sametime 3.1 use different LDAP servers

An example of when one of these problems might occur is if WebSphere® Portal uses iPlanet or IBM® Directory Server and Sametime 3.1 uses a native Domino Directory.

Solution: Perform the following configuration:

   Configuration steps:

  1. Ensure that our Sametime server is set to allow both sttoken and ltpa token for authentication. This setting can be found in our sametime administration page under Configuration - Community Services.
  2. Select Allow users to authenticate using either LTPA or Sametime Token.
  3. Modify the CSEnvironment.properties file to use these settings:

    • CS_SERVER_SAMETIME_1.useLTPAToken=false
    • CS_SERVER_SAMETIME_1.dnNameSeparator=loginName
    • CS_SERVER_SAMETIME_1.nameFormatForResolve=/

    The CSEnvironment.properties file is installed in the wp_root\shared\app\config directory.

79944

 

Collaborative portlets

The following sections describe known issues and workarounds for Collaborative Portlets and Collaborative Components in WebSphere® Portal 5.0.2:

 

Installation and setup of collaborative portals

This section identifies known problems and workarounds related to installing and setting up collaborative portals with WebSphere® Portal 5.0.2.

 

Problem: Uninstalling Lotus Collaborative Components introduces instability in collaboration features of the portal and in collaborative portlets

Although WebSphere® Portal 5.0.2 supports incremental installation of portal components, if you, as the portal administrator, uninstall Lotus Collaborative Components, collaborative features that use Collaborative Components will no longer work in the portal and in Lotus collaborative portlets.

Solution: Reinstall Lotus Collaborative Components.

 

Problem: LDAP methods in Lotus Collaborative Components fail with authentication error if bind user password for WebSphere® Application Server is entered improperly

When WebSphere® Portal is configured with the IBM® Directory Server set up for LDAP authentication, so that the IBM® Directory contains the bind user name and password, and both the IBM® Directory and the Domino server are configured not to allow anonymous LDAP access, entering the bind user password without quotes causes an authentication error for all LDAP methods in the Lotus Collaborative Components.

Solution: Enclose the bind user password for the WebSphere® Application Server in quotation marks (").

(SPR #SMUY5NSFJQ)

 

Problem: Some actions in Notes and Domino portlet might fail on Windows with newer version of WebSEAL configured for portal

If our portal is configured with WebSEAL version 4.1 Fix Pack 5, users of the Notes and Domino portlet on Windows might experience problems with some portlet actions such as Launch New Document. This occurs because the URL launched by the action might be blocked at the WebSEAL junction due to errors in the locations of certain files.

Solution: When installing WebSEAL version 4.1 Fix Pack 5, carefully follow all included documentation describing how to update binary files.

(SPR #MSHN5QZRPW)

 

Lotus Domino with WebSphere® Portal

This section identifies issues pertaining to configuring Lotus Domino with WebSphere® Portal 5.0.2.

 

Problem: Additional instructions are required for configuring the Lotus Domino server for use with the portal server

After following all other instructions for installing and configuring Lotus Domino, follow these additional steps:

  1. Open Domino Administrator (Notes administrative client).
  2. Log in when prompted for the password.
  3. Open the Domino Directory database (names.nsf) for the server.
  4. Accept the default settings for Directory Profile and click Save and Close.
  5. Open the Server document.
  6. Click the Basics tab and complete the following fields:

    • Domain name. The Domino domain name should be automatically entered here when the server is registered; if not, enter the Domino domain name.
    • Fully qualified Internet host name, for example, Srv1.Acme.com.
    • Administrator. Fill in the name(s) of any administrators, such as wpsadmin, who should have access to this server.

      Depending on our deployment model, we might want to specify additional administrators in this field.

  7. Click the Security tab and specify the following settings:

    Server Access. Use the Access Server field to give users access to the server. (We usually do this through a group.)

If we leave this field empty, all users who can connect to the server will have access to Domino; this creates a potential security risk.

Be sure to give all users whom we want to use Domino access to the server. If we don't, any users without access to the server will not be able to run Domino.

Leave Create new databases empty

Leave Create replica databases empty.

  1. On the Internet Protocols tab, click the HTTP tab, and ensure that the following settings are specified:

    • Host Name

      The fully qualified host name of the server, for example, Srv1.Acme.com

    • Basics

      Set Allow HTTP clients to browse databases to Yes.

      This setting enables the database view selection list that appears when users edit the properties of the Notes and Domino portlet and other collaborative portlets.

  2. On the Ports tab, ensure that the following settings are specified:

    • Port field: A valid network port (for example, TCPIP)
    • Notes Network field: TCPIP Network
    • The server's network address is specified by either the server's numeric IP address or the server's fully qualified host name. The fully qualified host name is preferred; for example, Srv1.Acme.com.
    • Enabled field: Enabled (for the valid network port specified in the Port field)

      Verify that the remaining Enabled fields are set to Disabled to prevent unnecessary error messages from displaying on the server console.

  3. Save and close the Server document.
  4. If necessary, push the server configuration to the secondary servers that host Lotus Collaborative Components and collaborative portlets for the portal.
  5. Restart the server.

(DEFECT 57452)

 

Problem: The Domino Directory used as the LDAP source for the portal cannot contain user or group distinguished names that have special characters if the Domino server is release 5.x

When the Domino server is release 5.x, special characters in distinguished names of either users or groups prevent the names from being recognized by portal administration.

Solution: Change any distinguished names that contain special characters, or use a 6.x release of the Domino server.

(SPR #MSHN5QDLZ9)

 

Problem: Database lists in some portlets fail to populate with database names

In the Notes and Domino, Domino Web Access, and QuickPlace portlets, drop-down lists of database names appear empty if all Domino servers used with the portal do not have SSL certificates signed by the same certificate authority. Solution: Perform the following steps:

  1. Ensure that the Domino server configured for use with the portal has SSL set up properly.
  2. Do one of the following:

    • If the Domino server uses HTTP, set HTTP to run on the default port of 80.
    • If the Domino server uses HTTPS, set HTTPS run on the default port of 443, and enable DIIOP over SSL.
  3. Restart the Domino server.
  4. Examine the SSL certificates for each of the Domino servers that contain source databases for portlets in the portal, and make sure they are all signed by a single certificate authority (CA).
  5. From any of the Domino servers that has a properly signed SSL certificate, copy and paste the TrustedCerts.class file from within the <domino_root>\data\domino\java directory to the portal server machine's class directory <wp_root>\shared\app\.
  6. Restart the portal server.

(SPR #MSHN5RQL3D)

 

Browser issues

This section identifies known problems and workarounds related to browsers used for collaborative portals with WebSphere® Portal 5.0.2. Also refer to People awareness for additional Netscape issues.

 

Problem: Using Netscape or Mozilla, Notes and Domino portlets placed side-by-side on pages with double and triple columns will overlap

When users add Notes and Domino portlets that have many rows of information side-by-side on a portal page that is formatted in double- or triple-column layout, the information in the portlets will overlap if viewed with the Netscape or Mozilla browser.

Solution: Advise users to format portal pages that include Notes and Domino portlets without multiple columns if the Netscape or Mozilla browser is a requirement, or switch to Microsoft Internet Explorer 5.5 or later.

(SPR #SCII5C6HQF, SPR #RPAS5B4LBL, SPR #LMAN5SJNK2)

 

Problem: In the Notes and Domino portlet, using Netscape, users might experience difficulty collapsing and expanding views

When users click the plus or minus icons to collapse or expand views in Netscape 6.02, the icons might not work. In Netscape 7.01, the icons might collapse and expand but not change to display the appropriate plus or minus symbol.

Solution: Close and re-open the portlet to return to the default expanded state. Users might also consider switching to Internet Explorer.

(SPR #VMAA5N4L8W)

 

Problem: In the Notes and Domino portlet, using Netscape, Actions drop-down list might display incorrectly

When users click the Actions (down arrow) icon, its drop-down list with Open, Edit, and Delete options might display incorrectly in some other part of the portlet.

Solution: Users can still select options from the drop-down list. Users might also consider switching to Internet Explorer.

(SPR #VMAA5NKRTY)

 

Problem: In the Notes and Domino portlet, using Netscape, the Show Profile option on the people awareness menu might not work

Solution: Users might consider switching to Internet Explorer.

(SPR #VMAA5NKTRG)

 

Problem: In the Notes and Domino portlet, using Netscape, users cannot create documents that require the rich text applet

The Domino server does not support the rich text applet in the Netscape browser. As a result, if Netscape users click a button in the Notes and Domino portlet that creates a rich text document -- for example, the New Memo button in a mail view -- they might experience a system crash.

Solution: Advise users to switch to Microsoft Internet Explorer 5.5 or later.

(SPR #JHEY5PALM3)

 

Problem: Using Netscape 6.2 or 7.0 with the Notes and Domino portlet, users might experience a system freeze when closing an additional browser window

The problem might occur if a user takes an action in the Notes and Domino portlet that opens a separate window (for example, creating a new document in a view ), and then closes the separate browser window.

Solution: Upgrade to Netscape 7.1, or switch to Internet Explorer.

(SPR #JHEY5P3E8Q)

 

Problem: In the Notes and Domino portlet, using Netscape or Mozilla, options for opening documents in the Lotus Notes client software do not work

If users edit the properties of the portlet when it is configured with a portlet type (such as NOTESVIEW) that allows them to specify how to view documents, and on the Style | Columns page, they specify Lotus Notes, if available for the View documents in option, the portlet opens browser windows instead of Notes when users click the Launch Application icon.

In addition, when the portlet is configured as either MYCALENDAR or NOTESMAIL, and Lotus Notes, if available is specified for viewing documents, clicking either New Calendar Entry or Launch Application does not work.

Solution: Advise users to switch to Microsoft Internet Explorer 5.5 or later to open documents in the Lotus Notes client.

(SPR #VMAA5M6NZ3, SPR #DMAS5PCP5B, SPR #LMAN5SJQ38)

 

Problem: Incorrect hourglass cursor while editing properties of Notes and Domino portlet in Netscape 6.2

Users who edit properties of the Notes and Domino portlet using Netscape 6.2 might notice that the cursor remains an hourglass even after they click Done or Cancel in the Work with Notes Views pages and return to view mode.

Solution: Advise users to switch to Microsoft Internet Explorer 5.5 or later.

(SPR #JHEY5P9AU5)

 

Problem: Using Netscape 6.2, deleting a document from a Notes portlet can cause a browser crash

Solution: Advise users to upgrade to Netscape 7.x, or to Mozilla.

(SPR #VMAA5SVRJY)

 

Problem: People awareness does not work with Netscape 7.0

Solution: Advise users to use Microsoft Internet Explorer.

(SPR #SMUY5T9LFB)

 

Page not found errors in the administrative console of WebSphere® Portal application server

Problem: Page not found errors occur in the administrative console of WebSphere® Portal application server.

Solution: To resolve Page not found errors complete the following steps.

  1. Open the administrative console, and click Enterprise Applications.
  2. Open the wpsadminconsole.ear application, and select Map virtual hosts for Web Modules.
  3. Select the adminconsole check box, and select admin host in the combo box.
  4. Save our changes.
  5. Click Environment and Virtual Hosts.
  6. Click the admin host link and the Host Aliases link.
  7. Add two new ports with host name * for both 9091 and 9044.
  8. Save our changes.
  9. Restart WebSphere® Portal.
  10. Connect to the administrative console using port 9091 instead of 9081.

    The SSL port will be 9044.

80968

 

People awareness

This section identifies known problems and workarounds related to the people awareness functionality in collaborative portals with WebSphere® Portal 5.0.2.

 

Problem: The column specified for people awareness in the Notes and Domino portlet must contain user names

When the Notes and Domino portletType parameter is configured as NOTESMAIL, NOTESDISCUSSION, NOTESTEAMROOM, or NOTESVIEW, in order to enable people awareness, assist portal users to identify and specify a column containing user names in the source database.

Solution: For example, when the portlet is configured as NOTESMAIL, and a user edits the portlet properties to specify the Column for showing people awareness, if the view is $Inbox, advise users to select the Who column from the drop-down list of column names. When the portlet is configured as NOTESDISCUSSION, if the view is the AuthorView, advise users to select Column 0.

(DEFECT 23945)

 

Problem: The Domino Directory used for people awareness might cause delays or lack of awareness if it contains replication conflicts or identical common user names

Solution: Resolve all replication conflicts in the Domino Directory on the Domino server set up for use with the portal by identifying the Person document with the latest updates and deleting any earlier ones. Also, modify names of any users who share a common name so that names become unique (for example, by including an initial).

(SPR #MSHN5NGHCQ)

 

Problem: Sametime status does not update when portal is left inactive

If the portal is configured with people awareness, and a user leaves the portal inactive, the user's online status does not automatically update to Away.

Solution: Apply the Sametime fix #YSAI-5T6BFD to the Sametime server configured for the portal. This fix is available at the Lotus Support Web site at:

http:www.lotus.com\support

The fix is intended for Sametime 3.0 with interim fix 3, and Sametime 3.1 with interim fix 1.

 

Problem: Selecting a name and selecting Add to Contact List does not work

Solution: Users must launch and log in to their Lotus Sametime Client software separately before using this menu item on portlets in the portal.

(SPR #MSHN5SUJ5Y)

 

Problem: Extraneous text appears at top of portal page if people awareness is on and any portlet displays any name of a person who is offline

The extraneous text is

%s is offline

The problem is cosmetic. It does not interfere with functionality of the portal or collaborative portlets. A minor edit to a portal file corrects the problem.

Solution: Follow these steps:

  1. Using a text editor, edit the person.js file located in the following directory: 
    <AppServer>\installedApp\<servername>\wps.ear\wps.war\peopleawareness\person.js.
  2. Locate the following line of text: 
    var s = "<DIV id='personTagTipOffline' type='hidden'></DIV>";
  3. Change type='hidden' to style='display:none', as follows: 
    var s = "<DIV id='personTagTipOffline' style='display:none'></DIV>";
  4. Save the file.
  5. Restart our browser and look at the portlet again. The extraneous text should not appear.

(SPR #MSHY5U5JGV)

 

Collaborative portlets

This section identifies known problems and workarounds related to Lotus Software portlets for collaborative applications with WebSphere® Portal 5.0.2.

 

Problem: Adding a name to an empty contact list might require two attempts

In any collaborative portlet, if a user selects Add to Contact List for a group that does not currently have any names, the name might not immediately display in the group list.

Solution: Advise the user to select the command again.

(SPR #DGAO5FDQHG)

 

Problem: Cursor focus can be incorrect when entering user name for some portlets

In portlets that use the iFrame feature (Domino Web Access, Domino.Doc, Web Page, and Inline QuickPlace) when users type in a text input field using Microsoft Internet Explorer, cursor focus can unexpectedly shift to areas of the portlet outside the field. This happens when the iFrame points to a Web site that automatically moves focus to a text input field, and users move in or out of edit mode, or maximize or minimize the portlet.

Solution: Advise users to click inside any input field before typing.

(SPR #SBED5NDMER)

 

Problem: Notes portlets of certain types do not resolve the Domino mail server and database for authenticated portal users when the corporate LDAP service is not Domino LDAP

When Domino LDAP is not configured as the Domino Directory for the Lotus Collaborative Components service for WebSphere® Portal, the Notes and Domino portlet, when configured with a portlet type of either MYINBOX, MYCALENDAR, or MYTODO, might fail to resolve the mail file and mail server information. Consequently, the portlet displays an ERROR MAILINFO link. Clicking the error link results in another error message indicating that portlet content cannot be displayed because the Notes server does not recognize the user name and password used to log in to the portal.

Solution: Advise portal users that they must edit the properties of any Notes and Domino portlet they use to access their mail, and manually specify the server and database names for their source mail database.

(SPR #MSHN5A7LC7)

 

Problem: In the Notes and Domino portlet configured with a portletType of MYINBOX, hiding either the File size or Attachment icon column might cause XML error

If users edit the portlet properties and, under Show:, deselect either or both the File size or Attachment icon column, the portlet might display an XML error.

Solution: Advise users to leave both of these columns selected (showing) in the properties.

(SPR #SJCN5TLUGV)

 

Problem: Deleting a document in one instance of the Notes and Domino portlet does not refresh other instances of the portlet that are above it on the portal page

This problem can occur when multiple instances of the Notes and Domino portlet, deployed on the same portal page, display the same document in the same source Notes database. If a user deletes a document from a portlet that is below another portlet displaying the same document, any portlets above do not refresh to show the deletion.

Solution: Advise users to delete the document from the first portlet deployed on the page, and the portlets below it will refresh.

In some situations users, or we as portal administrator if we populate portal pages, should always place certain portlet types above others on a portal page. For example, if the first instance of Notes and Domino is configured with a portlet type of MYCALENDAR and the second is configured with a portlet type of MYTODO, showing the same source database, deleting documents from the My ToDo portlet will not refresh the My Calendar portlet because it is above the My ToDo portlet. Users also cannot delete documents directly from the My Calendar portlet, so this arrangement is not useful. The My Calendar portlet should always be placed below a My ToDo portlet displaying the same source database.

(SPR #SJCN5SULSG)

 

Problem: In the Notes and Domino portlet, specifying view or server names by typing might not work

If users edit the Notes and Domino portlet and attempt to add a view by typing a visible view title such as "All Documents," the view might not be saved in the portlet. In addition, typing a view or server name that contains a double quote (") character does not work.

Solution: Advise users to select view and server names from the drop-down lists provided instead of typing names. Also, if users are familiar with Notes database design and know view alias names (for example, ($All) instead of All Documents), typing an alias name works to specify a view.

(SPR #VMAA5NPL47, SPR #VMAA5NURWD, SPR #VMAA5NVQPT)

 

Problem: In the Notes and Domino portlet, no error message appears when users attempt to add views to which they have no access in the source database

Solution: If a user cannot add views to this portlet from a specific database, examine the ACL of the source database and correct it if it is set to No Access for the user.

(SPR #VMAA5P2USE)

 

Problem: In the Notes and Domino portlet, options that open new windows in the Lotus Notes client software might function improperly if Notes is not already launched

If users edit the properties of the portlet and specify Lotus Notes, if available for the View documents in option, but do not launch the Note client software ahead of time, login errors might occur, or view focus might be incorrect, when users take actions, such as creating a mail message, that require Lotus Notes to open a new window.

Solution: Advise users to launch the Lotus Notes client software, and enter their Notes password, before using the Notes and Domino portlet when the Lotus Notes, if available option is specified.

(SPR #SJCN5TGU5C)

 

Problem: Difficulty editing repeating tasks or calendar documents in the Notes and Domino portlet

If the Notes and Domino portlet displays a To Do view or Meetings view, editing repeating tasks or calendar documents (for example, meetings) requires specific steps. For example, when a user selects a repeating item and then selects Edit from the drop-down list under the Actions (down arrow) icon, a dialog box might display dates incorrectly so that a single instance of the task cannot be selected. In addition, editing the parent document of a set of repeating items causes problems in the way Notes manages the documents.

Solution: To edit any repeating item, users must select one of the instances of the item (not the parent item) and select Open, instead of Edit, from the Actions drop-down list. Selecting Open displays a dialog box where users can specify which repeating item they want to edit. In some cases the dialog box does not appear; if this happens, users can edit only the first repeating item.

(SPR #DMAS5P3QNK, SPR #LMAN5N7L59, SPR #LMAN5N7Q6U, SPR #LMAN5N7M8W)

 

Problem: Cannot always save changes to sorting preference when editing properties of Notes and Domino portlet

Changes to the sorting preference in the edit properties might not be saved, or if saved, might not affect behavior in the view mode of the portlet. For example, if a user edits a Notes and Domino portlet configured with a portlet type of MYINBOX, selects Ascending for sorting, and clicks Save, the change is lost and the preference is set back to Descending.

Solution: In view mode, users can click the header of any column that sorts, for example a Date or Due column, to sort the column.

(SPR #DMAS5NUJZ9)

 

Problem: Edits to title of Notes and Domino portlet might persist even when user clicks Cancel

Solution: If the Notes and Domino portlet is configured with a portlet type of MYCALENDAR or MYINBOX, and users edit the portlet title, advise them to make sure the title is correct before saving changes to the portlet properties.

(SPR #DMAS5NUMAB)

 

Problem: In Notes and Domino portlet configured with MYCALENDAR portlet type, the New Calendar Entry button might create incorrect document

If the Domino server hosting the mail database is running R5, the New Calendar Entry button always creates an Appointment, not a calendar entry, even if the user selects a different calendar document, such as Meeting, from the Entry type drop-down list.

Solution: Advise users who want to create calendar documents other than Appointments to click the Launch Application button and use the New button at the top of the window to specify the type of calendar document.

(SPR #DMAS5N9PU8)

 

Problem: In some portal configurations, drop-down lists for selecting server and database for the Notes and Domino portlet display incorrectly

If the portal configuration runs SSL, does not support DIIOP, or restricts access to Java, JavaScript, or COM run by portal users, editing properties for the Notes and Domino portlet might not work correctly. Users might notice drop-down lists for selecting a source Notes server and database painting incorrectly with check mark icons out of place, obscuring buttons at the bottom of the screen.

Solution: Users can still make entries in the drop-down lists, and click buttons such as Done at the top of the screen.

(SPR #MSHN5PPK37)

 

Problem: In the Notes and Domino portlet, deleting calendar documents directly does not allow proper workflow

When the Notes and Domino portlet is configured to display a calendar or meetings view, selecting Delete from the Actions drop-down list for a document deletes the document, but does not properly manage the deletion. For example, deleting a meeting does not inform invitees that the meeting has been canceled.

Solution: Advise users to select Open instead of Delete from the Actions drop-down list, and then click the Delete action in the separate browser window that appears.

(SPR #LMAN5N7QM7)

 

Problem: In the Notes and Domino portlet, the icon for creating new documents does not work if specified form has a space character in its name

This problem occurs when users set up a view in a Notes and Domino portlet, specify an icon for creating documents, specify a form that has a space in its name, and also set the View documents in option to Lotus Notes, if available.

Solution: Advise users to specify only forms that have no space characters in their names in the source Notes database. If necessary, ask the database designer to adjust form names.

(SPR #VMAA5NGPQC)

 

Problem: Cannot use an HTTP/HTTPS port setting other than the default for the Domino server that is the data source for the Notes and Domino and the QuickPlace portlets

If the administrator of the Domino server that contains Notes databases that are data sources for the portal changes the http or SSL (https) port number of the Domino server, the Notes and Domino and the QuickPlace portlets display errors and fail to load properly.

Solution: The administrator of the Domino server must make certain that the http/https port number matches the default for the portlet types MYINBOX, MYTODO, and MYCALENDAR; there is no way to specify a non-default port number for these types of portlets. For the other types of the Notes and Domino portlet, and for the QuickPlace portlets, the port number can be appended to the server name. But making the port number match the default for the portlets is less error-prone.

(SPR #MSHN5P8JHG)

 

Problem: Lotus QuickPlace portlet does not support SSL protocol

The Lotus QuickPlace portlet that was released originally as part of the WebSphere® Portal 4.2 Enable offering (deployed from the quickplace.war file) does not support the SSL security portal protocol.

Solution: If our organization must use SSL, remove the Lotus QuickPlace portlet from the portal and deploy the Inline QuickPlace portlet (from the quickplace2.war file) instead.

(SPR #DGAO5PNNY7)

 

Problem: Logging out of the Domino Web Access (iNotes) portlet or a QuickPlace portlet also logs out of WebSphere® Portal

Solution: If users work with the Domino Web Access portlet or either QuickPlace portlet (Inline QuickPlace or Lotus QuickPlace), and they see a Logout or Sign Out button in the portlet (the Logout button appears in the Domino Web Access portlet when the functional area is All or Welcome), advise them not to click the button -- doing so logs out of the WebSphere® Portal session.

(SPR #MKIM5GKMTP)

 

Problem: Some parameters for Domino Web Access portlet might disappear when saving portlet configuration

If a portal administrator edits and saves the Domino Web Access (iNotes) portlet configuration in Manage Portlets, three parameters that are blank by default -- PortNumber, UseReverseProxyString, and reverseProxyPortNumber -- disappear from the list of parameters for the portlet.

Solution: To specify values for any of these parameters, type the parameter's name in the blank left field at the bottom of the list, type the desired value in the right field, and click the Add button.

(SPR #SBED5PCTN8)

 

Problem: Cannot create calendar entries in Domino Web Access portlet when source database design is UseiNotesTemplate

If users' source mail databases have the UseiNotesTemplate design, and the Domino server is earlier or later than Domino 6.01, users of the Domino Web Access portlet cannot create calendar entries directly in the portlet. Solution: Advise users to click Launch Application and create calendar entries in the new window that opens.

(SPR #LMAN5SYPTD)

 

Problem: Domino Web Access portlet fails with combination of IBM® Edge server and Domino R5 mail server

The IBM® Edge Server is not compatible with the version of SSO used on a Domino R5 server, and SSO is required for the Domino Web Access portlet.

Solution: If we deploy the Domino Web Access portlet in our portal, make sure that the Domino server where all users' mail databases are stored is running R6, and that the database design inherited by the databases is R6.

 

Problem: Quick Appointment portlet requires additional entry after login if IBM® Directory Server is set up for use with the portal

If an IBM® Directory Server, instead of a Domino LDAP server, is configured to work with the portal, and a user makes an entry to Who, What, or When in the Quick Appointment portlet, a login dialog box appears, and the user's entry is lost.

Solution: Advise users to repeat their appointment entries after logging into the portlet.

(SPR #DGAO5PKLK6)

 

Problem: Invalid login in Quick Appointment portlet does not allow additional attempts

If a user enters an incorrect name or password in the Quick Appointment portlet, a message appears telling the user to make a correction, but no new entry is allowed.

Solution: Advise users to log out of the portal, log back in, and re-enter the name and password for Quick Appointment.

(SPR #SBED5PPJYY)

 

Problem: Lotus Sametime Connect portlet fails to load when the port number for the Sametime server has been changed from default

Solution: As portal administrator, make sure that the http or https port number for the Lotus Sametime server that is set up for use with the portal is the default number of 80 for http and 443 for https. If the number must be changed for some reason, then the server port field in all instances of the Lotus Sametime Connect portlet (which specifies 1533 by default) must be edited to match the non-default number for the Sametime server for http or https, whichever is used.

(SPR #MSHN5P8PMK)

 

Problem: Protocol setting for Lotus Sametime Connect portlet requires user specification if Sametime server protocol setting does not match the portal server protocol setting

If the administrator of the Sametime server set up for use with the portal changes the Sametime server's protocol so that it no longer matches the protocol used by the portal server (for example, to https from http), the Lotus Sametime Connect portlet can no longer launch Sametime.

Solution: Advise users of the Lotus Sametime Connect portlet that they must edit the portlet and specify the protocol as well as the server URL in the Server name field, and let them know which protocol the Sametime server is using. For example, if the portal is using http and the Sametime server sametime.acme.com is using https, the user must enter https://sametime.acme.com in the field.

(SPR #MSHN5P8NFF)

 

Problem: When the Who Is Here portlet is on the same page as Inline QuickPlace, and the Sametime server is release 3.1, names might appear twice in the Who Is Here contact list

Solution: Advise users not to add the Sametime Who Is Here portlet to the same portal page as Inline QuickPlace.

(SPR #RPAS5T6KSZ)

 

Problem: In Notes and Domino portlet, selecting Switch ID causes unexpected behavior

There are several problems.

Solution: Take one of these actions:

(SPR #DMAS5SMLS4, SPR #DMAS5U5KYZ, SPR #DMAS5U5L8X)

 

Problem: Notes and Domino portlet set with new parameter can cause loss of access to iNotes mail design

The UseiNotesTemplate parameter, when enabled in the Notes and Domino portlet, allows iNotes users to access their iNotes mail through the Notes and Domino portlet and take advantage of people awareness in the portlet.

However, if a user adds an instance of the Notes and Domino portlet that is not enhanced with this parameter, and the Domino Web Access (iNotes) portlet to the same portal page, and then uses the Notes and Domino portlet to access mail that uses the iNotes design, both the Notes and Domino portlet and the Domino Web Access portlet fail to load the iNotes mail design, and provide only the Notes mail design.

Solution: If our collaborative portal is new and we have not yet set up user access for creation of portlets, the simple solution is to prevent users of the Domino Web Access (iNotes) portlet from adding instances of the Notes and Domino portlet to their pages, so that these two portlets will never coexist.

If we have an existing portal where users already have access to add portlets, and have added instances of the Notes and Domino portlet that are not configured with the new UseiNotesTemplate parameter, any users whose source mail has the iNotes design and who attempt to access their mail using the Notes and Domino portlet will encounter the error. Take the following steps:

(SPR #DMAS5TLNAD)

 

Problem: The Domino Web Access (iNotes) portlet does not support the use of Netegrity SiteMinder single sign-on

When the portal is configured to use SiteMinder, the Domino Web Access portlet cannot access its source database and displays an error message.

Solution: Do not use the Domino Web Access portlet in a portal configured with SiteMinder.

(SPR #JGRP5U3SSE)

 

Accessibility issues

This section describes issues with accessing the collaborative portlets using the keyboard, or using screen reader software.

 

Problem: Sametime Contact List portlet is not completely accessible with JAWS screen reader

Users of the JAWS screen reader software might have difficulty selecting radio buttons in the Sametime Contact List portlet.

Solution: Use screen reader software other than JAWS.

(SPR #MKIM5NVQZY)

 

Problem: Incorrect behavior of TAB key in Domino Web Access portlet

When users edit properties of the Domino Web Access portlet using the keyboard, pressing TAB when the focus is on the Fit to column radio button should move to the Height field, but instead the focus moves to the pixels text entry field for the other radio button under Width.

Solution: Press TAB again to move the focus to the Height field. SHIFT-TAB is also useful for moving back through the buttons and fields.

(SPR #MKIM5MGKMH)

 

Migration issues

This section describes issues with collaborative portlets deployed in releases of WebSphere® Portal earlier than 5.0.

 

Problem: If the portal has had iNotes portlets deployed since release 4.1.2, 404 error occurs

If our organization is migrating from a previous release of the portal server that used iNotes portlets (inotes.war), the Domino Web Access portlets used in WebSphere® Portal 5.0.2 will yield a 404 Not Found error in all browsers, because the mail database name is not resolved the way it was previously.

Solution: Edit the properties for any instance of this portlet, and in the Database field, pre-pend the following to the database (.nsf) file name:

/mail

(SPR #DMDD5PWTYG)

 

iSeries issues

This section describes issues with collaborative portlets deployed on the iSeries platform.

 

Problem: On iSeries, People Finder portlet initially displays configuration error message

This problem occurs because the ibm - PersonalTitle field is missing its value until initialized.

Solution: Click the wrench icon in the portlet title bar to change to Configuration mode. Click Apply Changes Now. The portlet will return to the initial view and redisplay correctly.

(SPR #BJKE5T7H7D)

 

Problem: Notes and Domino portlet column settings for people awareness and document launch might intermittently behave incorrectly

If the portal is running on iSeries, a Notes and Domino portlet configured with a portletType of MYINBOX, MYTODO, or NOTESMAIL and with columns set for people awareness and document launch might, after an undetermined time of operation, start displaying the incorrect columns for these features.

Solution: Restart the portal server.

(SPR #DMAS5UAQS8)

 

Lotus Collaborative Components

This section describes issues related to the Lotus Collaborative Components API and samples.

 

Problem: Lotus Collaborative Components API methods and samples will not run on default WAS 5 server1 over SSL without additional configuration

This problem refers to an environment in which you, as a portlet developer, are using the Lotus Collaborative Components samples on a WebSphere® Application Server without a WebSphere® Portal installation, but with a Domino server.

With the default WAS5 configuration, a conflict on server1 might cause the IOR file to be read incorrectly, causing an error 4457 from the Domino server.

Solution: To install the Lotus Collaborative Components sample enterprise application to a new WebSphere® Application Server instance:

  1. Create a new WAS instance (server2) and enable SSL on the server. To enable SSL, follow instructions in the red book at this location: 
    http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/sg246976.html?Open
  2. Do one of the following to locate and copy the cs.ear file:

    • If we have WebSphere® Portal installed, copy the file from this location: 
          \WebSphere\PortalServer\installableApps\cs.ear
    • If we do not have WebSphere® Portal installed, copy the file from the appropriate CD in the WebSphere® Portal software.
  3. Paste the file to the following location on our WebSphere® Application server: 
        \WebSphere\AppServer\installableApps
  4. In the WebSphere® Administration Console, deploy the Collaborative Components sample enterprise application on server2 as described in Deploying Collaborative Components Samples in the WebSphere® Portal Information Center.
  5. From the Domino SSL server, copy the TrustedCerts.class file, and paste it into the following location on our WAS: 
        \WebSphere\AppServer\installedApps\yourserver\cs.ear\cs.war\WEB-INF\lib
  6. While in that location on the WAS, copy both the TrustedCerts.class file and the ssl.jar file.
  7. Paste both files to the following location: 
        \WebSphere\AppServer\lib
  8. Restart our new WAS.
  9. Start the Collaborative Components sample enterprise application.

(SPR #SMUY5RVJHN, SPR #MSHN5TGKLZ)

 

Help and documentation updates

This section describes corrections to the online Help for collaborative portlets, and to topics in the WebSphere® Portal Information Center file provided with the portal server software.

The online version of the WebSphere® Portal Information Center contains more current information than does the version of the Information Center that was shipped on disc with our portal software. We can find the online version at this IBM® Web site location:

http://www.ibm.com/websphere/portal/library

 

Problem: Help for the Domino.Doc portlet contains inaccurate field name

Solution: Advise users of the Domino.Doc portlet that the field described as "Application title" in the online Help is actually called "Title."

 

Known limitations for Collaboration Center

This document contains the release notes for Collaboration Center features of WebSphere® Portal 5.0.2. The release notes describe workarounds for known defects and provide supplemental information on topics that might also be covered in the WebSphere® Portal Information Center and Collaboration Center portlet Help.

 

Supported hardware and software

The Collaboration Center requires an existing installation of a collaborative portal.

For information on the server and operating systems supported by the Collaboration Center in this release, refer to the WebSphere® Portal Information Center topics, Planning, Supported hardware and software, Software requirements, Supported software for Collaboration Center.

The online version of the WebSphere® Portal Information Center contains the most current information. We can find it at this IBM® Web site location:

http://www.ibm.com/websphere/portal/library

For information on browser releases supported for each of the Collaboration Center portlets, see their documentation under Installed portlets, Collaborative portlets.

 

WebSphere® Portal offerings

The Collaboration Center is available to licensed users of WebSphere® Portal Express Plus only.

 

Companion products for collaboration

One or more of the following IBM® Lotus products will be required depending on which companion products we have chosen to enable in our collaborative portal and which Collaboration Center portlets we have chosen to deploy:

For each of the companion products for collaboration listed here, see the terms and conditions of the applicable WebSphere® Portal license for specific details.

For current release information on companion products, see the WebSphere® Portal Information Center topics, Planning, Supported hardware and software, Lotus companion products.

 

Directory servers

Refer to the WebSphere® Portal Information Center topics, Planning, Supported hardware and software, Software requirements, Supported software for Lotus Collaboration Center for the list of directory servers that are supported in this release of Collaboration Center.

Exclusions The following directory server is not supported in this release of Collaboration Center:

NDS eDirectory

 

Hotfixes for IBM® Lotus Instant Messaging (Sametime) 3.0 required

Our installation of Sametime 3.0 must include Service Pack 1 (SP1) and might also require the hotfixes related to Lotus Software Problem Reports (SPR) #STTE5F797Y and #MPAS5KAMNB. The hotfixes for Sametime 3.0 correct defects for meetings containing attachments. If the meetings we are working with in the Collaboration Center Web Conferencing portlet do not contain attachments, we will probably not need to apply the hotfixes. Contact IBM® Technical Support for Lotus Software to determine whether we need to apply hotfixes for Sametime 3.0.

 

Installation issues

The following notes identify known problems for installation of Collaboration Center components.

 

Problem: Installation of Collaboration Center portlets fails when the portal is configured to use a reverse proxy server

Solution: For the duration of the installation, allow direct http access to the portal server. After installation is complete, we can reconfigure the portal environment to use a reverse proxy server.

(SPR #MSHN5R3PTX)

 

Problem: Uninstalling the Collaboration Center after installing WebSphere® Portal 5.0.2 does not remove all necessary files and does not update DB2 configuration

Solution: If we uninstall the Collaboration Center after we have installed it as part of WebSphere® Portal 5.0.2, errors will occur when we attempt to reinstall and deploy the Collaboration Center.

Take the following steps:

  1. Under Administration --> Manage Pages, delete the page lotus.workplace.hiddenpage.PeopleFinder.
  2. If our portal is configured to use remote DB2, use the following command in the DB2 Command Center to delete a DB2 table entry: 
    delete from db2admin.unique_name where UNIQUE_NAME =

    'lotus.workplace.hiddenpage.control.PeopleFinder'
  3. Run wpsconfig cc-deploy-page again.

(SPR #CBOD5XDJQU, SPR #CBOD5XFT4R)

 

Problem: Installation of Collaboration Center portlets fails when the portal is configured to use a reverse proxy server

Solution: For the duration of the installation, allow direct http access to the portal server. After installation is complete, we can reconfigure the portal environment to use a reverse proxy server.

(SPR #MSHN5R3PTX)

 

Problem: Information on and portlets for Lotus Collaboration Center are out of date

The WebSphere® Portal 5.0.2 Information Center topics describing the Lotus Collaboration Center list only the five portlets that were included as of WebSphere® Portal Release 5.0.2, and installation and configuration procedures are specific to those five portlets and underlying technology.

Solution: An upgrade is available to the Collaboration Center, to include the IBM® Lotus Notes/Domino and Extended Product Portlets (DEPP) package. Refer to the following information.

As of WebSphere® Portal Release 5.0.2.2 and 5.0.2.3, the Lotus Collaboration Center can be upgraded to the IBM® Lotus Notes/Domino and Extended Product Portlets (DEPP) V6.5.1.1. The Collaboration Center now includes nine portlets, and has different installation and configuration requirements than those described in the Information center. The Collaboration Center still includes the following five portlets: People Finder, Sametime Contact List, Lotus Web Conferencing, Lotus My Team Workplaces, and Sametime Who Is Here. The four additional portlets now included in the Collaboration Center are:

When we install and configure the DEPP upgrade to the Collaboration Center, all portlets except Sametime Who Is Here will be replaced with new versions. The upgraded Collaboration Center uses the Sametime Who Is Here portlet that is installed with WebSphere® Portal 5.0.2.3.

Changes to installation of the Collaboration Center with DEPP

If we currently use or plan to use collaborative features, install the collaborative update provided with WebSphere® Portal 5.0.2.3. The Collaboration Center and other collaborative portlets are provided as a single package called the IBM® Lotus Notes/Domino and Extended Product Portlets. The only exception is the Sametime Who Is Here portlet provided by the SametimeWhoIsHere portlet application, which was part of earlier versions of Collaboration Center and is not included in this package. It is supplied separately with WebSphere® Portal 5.0.2.3.

We will find the IBM® Lotus Notes/Domino and Extended Product Portlets Version 6.5.1.1 in the /depp directory on CD12. Review CD12/depp/readme.html for additional information on the content of this package. The SametimeWhoIsHere portlet application and an update to Collaborative Services code are also supplied on CD12 in the /collabupdate directory.Follow these instructions to install the collaborative updates supplied with WebSphere® Portal 5.0.2.3:

  1. Complete the installation and configuration of WebSphere® Portal 5.0.2.3.
  2. Stop WebSphere® Portal 5.0.2.3.
  3. Copy /collabcenter/cs.jar from CD12 to wp_root/shared/app/cs.jar. Overwrite the existing cs.jar file if present.
  4. Start WebSphere® Portal 5.0.2.3.
  5. Ensure that WebSphere® Portal 5.0.2.3 is running and verify, using a browser, that we are able to log in using the administrative credentials.
  6. Install the new SametimeWhoIsHere portlet application if we plan to use this application with WebSphere® Portal 5.0.2.3. If a previous version of the Collaboration Center is...

    • ...installed: The Sametime Who Is Here portlet has already been deployed on our system. In this case, we need to update it instead of installing the newer version. Go to the WebSphere® Portal server, and select Administration --> Portlets --> Manage Applications. Select the SametimeWhoIsHere.war from the list of Web modules, click Update, and select the portlet application from CD12 to use for the update.
    • ...not installed: We will need to install the version of the portlet application supplied with WebSphere® Portal 5.0.2.3. First copy the /collabcenter/SametimeWhoIsHere.war from CD12 to the wp_root/installableApps directory. Then, on the WebSphere® Portal server, select Administration --> Portlets --> Install to install the portlet application.
  7. Follow the instructions provided in the /depp/readme.html on CD12 to install IBM® Lotus Notes/Domino and Extended Product Portlets V 6.5.1.1. Any previously installed collaborative portlets will be updated to the newer version.

    It is recommended to use the -portlets option when installing the "IBM® Lotus Notes/Domino and Extended Product Portlets" package. Installing the "IBM® Lotus Notes/Domino and Extended Product Portlets" package without the -portlets option will also deploy sample pages to host instances of portlets supplied by the package. However, the script to deploy the sample pages changes all localized titles of "My Portal" page to "My Workplace" and also changes its default theme. This will affect the look and feel of all our existing pages under the "My Portal" page.
    If we need to deploy the sample pages and want to preserve existing titles and theme settings, first use xmlaccess to export the "My Portal" page. After completing the install of "IBM® Lotus Notes/Domino and Extended Product Portlets," use xmlaccess to import the exported "My Portal" page that we exported. See the WebSphere® Portal 5.0.2 Information Center for information on how to use xmlaccess to export and import specific pages. For example, use uniquename="wps.My Portal" as the attribute for exporting the existing "My Portal" page.

Changes to configuration of the Collaboration Center after DEPP is installed

If we were not using collaborative portlets earlier, we will need to configure them first before using them. Perform the following steps:

  1. Follow the instructions to configure the collaborative servers and portlets provided in the WebSphere® Portal 5.0.2 Information Center in the topics under Installing --> Lotus Collaborative Components --> Configuring.

    Tip: We can configure the Domino and Extended Products servers (Domino, Sametime, and QuickPlace) either individually as described in the topics above or all together using the lcc-configure-all command. For more information, see the information about this command in the WebSphere® Portal 5.0.2 Information Center under Installing --> Component configuration --> Configuration task reference.

  2. Verify that all collaborative features are working as expected.

The WebSphere® Portal 5.0.2 Information Center topics Installing --> Lotus Collaborative Components --> Collaboration Center --> Configuration overview and Installing --> Lotus Collaborative Components --> Collaboration Center --> Configuring WebSphere® Portal to use Collaboration Center portlets are obsolete for the new version of the Collaboration Center provided in the IBM® Lotus Notes/Domino and Extended Product Portlets package.

Changes to portlet deployment in the Collaboration Center after DEPP is installed

The WebSphere® Portal 5.0.2 Information Center topic Installing --> Lotus Collaborative Components --> Deploying portlets --> Deploying Lotus collaborative portlets includes two tasks that are out of date for the Collaboration Center:

Changes to content of the Collaboration Center pages after DEPP install
The WebSphere® Portal 5.0.2 Information Center topic Installing--> Collaboration Center --> Features describes an outdated list of the contents of the Collaboration Center sample page.

The following table lists the pages in the Collaboration Center, the portlet instances users see on each page, and the name of portlet from which each instance is derived. The Collaboration Center appears on the My Workplace page of WebSphere® Portal.

Page Named portlet instances
Welcome
Domino Extended Products Welcome
Mail
Mail (instance of Domino Web Access portlet)
People Finder
My Contacts (instance of Sametime Contact List portlet)
Calendar
Calendar (instance of Domino Web Access portlet)
People Finder
My Contacts (instance of Sametime Contact List portlet)
Address Book
Address Book (instance of Domino Web Access portlet)
People Finder
My Contacts (instance of Sametime Contact List portlet)
Web Conferences
Web Conferences (instance of Lotus Web Conferencing portlet)
People Finder
My Contacts (instance of Sametime Contact List portlet)
Team Spaces
My Lotus Team Workplaces (instance of Lotus My Team Workplaces)
People Finder
My Contacts (instance of Sametime Contact List portlet)
Documents
Documents (instance of Domino.Doc portlet)
Domino Application Portlet
Domino Application Portlet
Domino Databases
Domino Databases (instance of Notes and Domino portlet)
Domino Document Manager
People Finder
My Contacts (instance of Sametime Contact List portlet)
Administration
Bookmarks

(defect 128963)

 

Issues affecting all Collaboration Center portlets

The following note identifies a known problem that affects all Collaboration Center portlets.

 

Problem: Portlet configuration parameters that have no values disappear from parameter list.

If we modify the configuration parameters of any portlet in WebSphere® Portal 5.0.2, parameter fields left blank when we save our changes will not appear in the list of parameters the next time we open the Modify parameters task (Portal Administration - Manage portlets - Modify parameters).

(SPR #WHOR5KXM2D, #SPUL5KZNFW)

 

People Finder portlet

The following notes identify known problems and limitations of the People Finder portlet.

 

Problem: Configuration mode for the People Finder provides no locking to prevent concurrent updates by multiple users.

The People Finder portlet Configuration mode has no locking mechanism to prevent update conflicts and overrides by multiple users.

Solution: Until this problem is corrected in a future release, consider implementing a plan whereby only one administrator or designer is configuring the People Finder at a given time. Scheduling and communicating single-user sessions for configuring the People Finder will alleviate the potential for lost work.

(SPR #HGRR5L9JZT)

 

Problem: E-Mail address links might have different behavior in People Finder than in other portlets such as Notes Mail

The default specification for the attribute E-mail address (ibm-primaryEmail) in the People Finder portlet causes the Send E-Mail action on the Person menu (available on people links in People Finder) to open a new mail message in the HTML-based mail application specified in the user's browser. This might not match behavior of the same action on the Person menu in portlets such as Notes Mail.

Solution: Click the wrench icon to enter Configuration mode in the People Finder portlet, and specify the display format "People link" for the E-mail address attribute.

(SPR #MZER5S3QY9_LWP, SPR #CSPA5S3RAM_LWP)

 

Problem: Names in People Finder might not match names in other portlets

The People Finder portlet Name field is specified by default with a Common Name ("cn") attribute, because that attribute is frequently used in corporate directories. However, the Lotus Collaborative Components Person tag, which displays people awareness links in Lotus portlets, has a default of the "displayName" attribute. The Person tag uses displayName wherever it can find a value for that attribute, and defaults to the common name when it cannot.

Solution: Set the People Finder portlet to use the same format as the Person tag. Click the wrench icon to enter Configuration mode in the portlet, and change the "cn" attribute used by the Name field in all views where it is specified to "displayName."

(SPR #MZER5RQNHN_LWP)

 

Lotus Web Conferencing (Sametime) portlet

The following notes identify known problems and limitations of the Lotus Web Conferencing portlet.

 

Problem: Meeting attachments sometimes do not appear in the portlet.

Solution: If our meeting contains attachments and these attachments do not appear when we open the meeting using the Web Conferencing portlet, verify that the Sametime server has both the Sametime 3.0 Service Pack 1 (SP1) and any necessary hotfixes that correct this problem.

(SPR #LHUG5K3BY3)

 

My Lotus Team Workplaces (QuickPlace) portlet

The following notes identify known problems and limitations of the My Lotus Team Workplaces portlet.

 

Problem: What's New and My Tasks views do not display the pages of inner rooms.

If we have created a team workplace (QuickPlace) that has inner rooms, the My Team Workplaces portlet does not show pages from inner rooms in the views What's New and My Tasks.

(SPR #BJKE5KYJPS)

 

Problem: A limitation with the QuickPlace API causes page content to display incorrectly.

If we search or open the My Pages view of a team workplace, we will notice that the columns of Page, Workplace, and Author have additional, unexpected content. In addition, sometimes pages in a workplace display no links. Links are suppressed in workplace pages rendered by the portlet when invalid URLs are returned from the QuickPlace server.

(SPR #LSWN5LWPPL, SPR #TDEY5M2FBJ)

 

Problem: Tasks in My Team Workplaces portlet must be assigned to individuals, not to groups.

Verify that we always assign tasks in My Team Workplaces to a specific person. If we assign a Team Workplace task to a group, members of the group will not see the task in the My Tasks view of the My Team Workplaces portlet.

(SPR #TDEY5LEDLB)

 

Problem: Searches using wildcard characters return no results.

IBM® Lotus QuickPlace 3.0.x does not support wildcard searches using the asterisk (*) or question mark (?).

(SPR #TDEY5L8LEA)

 

Problem: Searching for My Team Workplaces before and after a certain date includes the specified date.

The My Lotus Team Workplaces portlet returns results for searches before and including the specified date, while IBM® Lotus Team Workplace (QuickPlace) returns results before and excluding the specified date. Similarly, the portlet returns results for searches after and including the specified date, while IBM® Lotus Team Workplace (QuickPlace) returns results after and excluding the specified date.

(SPR #TDEY5M2HNN)

 

Problem: Searching for the title of a Team Workplace always returns no matches.

IBM® Lotus QuickPlace 3.0.x domain search does not include the titles of team workplaces in the search index. Therefore, when we try to search for a team workplace by its title, the portlet will always display the No Matches Found message.

Solution: We can, however, search for and find content in pages of our team workplaces.

(SPR #LHUG5LEAP3, #LSWN5L3LK2)

 

Problem: My Lotus Team Workplaces does not work if secure sockets layer (SSL) protocol is enabled.

If we have configured the Team Workplaces portlet to run on a server configured to run secure sockets layer protocol (HTTPS), workplaces will not appear in the portlet nor will they be available for search.

Solution: Avoid configuring our Team Workplaces (QuickPlace) server with SSL.

(SPR #MSHN5PNR58)

 

National language support

The following notes identify known problems and limitations with national language support in Collaboration Center.

 

Problem: People Finder portlet displays names containing non-ASCII characters improperly.

If the Domino Directory that is the LDAP source for the People Finder portlet contains person names with non-ASCII characters, these names will not appear properly in the People Finder portlet. IBM® Lotus Domino requires that InternetAddress values be provided in the Domino Directory for each person entry where the person name contains non-ASCII characters.

Solution: To ensure that names containing accented and other international characters display properly in the People Finder portlets, we must supply a value in the InternetAddress field for each person entry in the Domino Directory that contains non-ASCII characters.

(SPR #ACLL5LLJV4, SPR #ACLL5LFKZ4)

 

Problem: People Finder sorts names in unexpected order when names contain international characters.

If we search for people with names that contain accented and international characters, we might notice that the names listed in the People Finder are sorted in an unexpected order. The sorting order of names containing international characters is controlled by the Java Virtual Machine (JVM) used by the browser. This JVM effect might also be seen in the sort order of My Workplaces listed in the My Lotus Team Workplaces portlet.

(SPR #BJKE5JALR2)

 

Problem: People Awareness (people links) is not supported in all languages that portal supports

IBM® Lotus Instant Messaging (Sametime) 3.0 with people awareness features does not support all languages that WebSphere® Portal supports. When our browser is set to a preferred language that Sametime 3.0 does not support, people awareness features (for example, people links in Collaboration Center portlets) should default to English.

(SPR #ACLL5LWJSB, SPR #ACLL5L9EK6, SPR #ACLL5L9N95)

 

Problem: My Lotus Team Workplaces shows content in the language of the QuickPlace regardless of browser language setting.

A limitation with IBM® Lotus QuickPlace 3.0 causes some text (for example, task priorities and workplace type description) to display in the language in which the Team Workplace (QuickPlace) was created. If we set our browser to display text in a language that is different from the one used to create the Team Workplace (QuickPlace), some text in the Team Workplace (QuickPlace) might appear in the language of the QuickPlace and not the language specified in our browser. For example, a QuickPlace created in French and opened in a browser set to English will display task priorities and workplace type description in French.

(SPR #TDEY5LMH6T)

 

Problem: My Lotus Team Workplaces sorts My Workplaces list in unexpected order when names contain international characters.

If we work with My Team Workplaces that contain accented and international characters, we might notice that the names listed in My Workplaces are sorted in an unexpected order. The sorting order of names containing international characters is controlled by the Java Virtual Machine (JVM) used by the browser. This JVM effect might also be seen in the sort order of people names in the People Finder portlet.

(SPR #ACLL5LQBJ7)

 

Help and documentation updates

This section describes corrections to the online Help for Collaboration Center portlets, and to topics in the WebSphere® Portal Information Center file provided with the portal server software.

The online version of the WebSphere® Portal Information Center contains more current information than does the version of the Information Center that was shipped on disc with our portal software. We can find the online version at this IBM® Web site location:

http://www.ibm.com/websphere/portal/library

 

Problem: Information Center topic on Installing Collaboration Center components contains misleading statements

The prerequisite section in the Information Center topic, Installing Collaboration Center components, states that we must configure portal to use LDAP and the Lotus companion products before we can install Collaboration Center components. This statement is misleading because we can install Collaboration Center successfully without having first completed this configuration, but we cannot use the Collaboration Center functionality until after this configuration is complete.

In addition, the section on removing existing Collaboration Center components instructs us to remove all Collaboration Center portlets before starting the WebSphere® Portal 5.0.2 installation. Instead, the only portlet that must be removed, if it was installed before V5.0.2, is the People Finder portlet.

Solution: Read the following clarification:

To install Collaboration Center, we must install on a system that has an existing portal installation, but we do not have to configure portal to use LDAP and the Lotus companion products before we install Collaboration Center.

To use Collaboration Center components, we must configure portal to use LDAP and the Lotus companion products. Thus, to use Collaboration Center functionality, we can configure the portal to use LDAP and the Lotus companion products before or after the Collaboration Center installation.

If our portal includes a previous version of the People Finder portlet, follow this procedure instead of the procedure in the Information Center section that is entitled, "Removing Collaboration Center portlets."

Removing the People Finder portlet

Follow these steps:

  1. Log in to the portal as an administrator and click Administration.
  2. Click Portlets - Manage Applications to display the Manage Portlet Applications task.
  3. In the list of Web Modules, select the People Finder portlet from WebSphere® Portal 5.0 (PeopleFinder.war).
  4. Click Uninstall and then click OK.

 

Problem: Help topics on People Finder contain incorrect names for some page labels and display formats

Solution: Refer to these corrected names in the Help for the People Finder configuration mode.

 

Trademarks

AIX, DB2, IBM, RS/6000, SecureWay, Tivoli® and WebSphere® are trademarks of the IBM® Corporation in the United States, other countries, or both.

Lotus and Domino are trademarks or registered trademarks of Lotus Development Corporation and/or IBM® Corporation in the United States, other countries, or both.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

JDBC is a trademark of Sun Microsystems, Inc. in the United States, other countries, or both.

Linux is a registered trademark of Linus Torvalds.

Microsoft, Active Directory, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Verdana is a trademark of Microsoft Corporation in the United States, other countries, or both.

This product includes software developed by the ExoLab Project (http://www.exolab.org/).

This product includes software developed by the Java Apache Project (http://java.apache.org/).

Other company, product, and service names might be trademarks or service marks of others.

 

Third party components

WebSphere® Portal contains, and future updates and Fix Packs to WebSphere® Portal might contain, certain third party components. For terms and conditions related to third party components, see the related file third_party.txt on the SETUP disc.

 

Copyright

(c) Copyright International Business Machines Corporation 2000, 2004. All rights reserved.
U.S. Government Users Restricted Rights - Use, Corp.

 

audio = true; //$MTC->notify = 'michael.pareene@gmail.com'; $MTC->init('my page'); ?>

There are currently comment_count();?> comments

comments(); ?>

 

Add your comment...

comment_form(); ?>

 

 

® WebSphere is a trademark of the IBM® Corporation in the United States, other countries, or both.

 

® IBM is a trademark of the IBM Corporation in the United States, other countries, or both.

 

® Tivoli is a trademark of the IBM Corporation in the United States, other countries, or both.

 

® AIX is a trademark of the IBM Corporation in the United States, other countries, or both.