Portal User Management Architecture (PUMA)

This technote covers collecting data for Portal User Management Architecture (PUMA) with IBM® WebSphere® Portal 6.1. Gathering this MustGather information before calling IBM Support will help to understand the problem and save time analyzing the data.

The PUMA SPI provides interfaces for accessing the profiles of a portal User or Group. It is used to find, create, modify, and delete users and groups. While it is implemented by administration portlets such as Manage Users and Manage Groups, it can also be used in custom themes and portlets.

Collecting PUMA specific information

1. Provide the following details about the problem:

• Version information for products involved:
  • WebSphere Portal
  • WebSphere Application Server
  • LDAP (if configured)
  • Database
• Code sample if using PUMA SPI
  

Recommendation: If you do not wish to manually collect configuration files and tracing, you can skip the remaining sections of this MustGather by using the IBM Support Assistant Lite for WebSphere Portal Tool (WebSphere Portal->Security and Administration->Puma User Management Architecture Problem option) to gather the requested information and provide it to IBM Support.

2. Enable PUMA trace logging by setting the following trace settings in accordance with the instructions documented in the topic "Trace Logging" in the WebSphere Portal Information Center:

com.ibm.wps.engine.*=all:com.ibm.wps.puma.*=all:
com.ibm.wps.services.puma.*=all:com.ibm.wps.command.puma.*=all:
com.ibm.wps.um.*=all:com.ibm.ws.wim.*=all:com.ibm.websphere.wim.*=all:
com.ibm.wsspi.wim.*=all

Note: Depending on how much traffic is hitting your server during trace collection, you may need to either increase the "Maximum File Size" or "Maximum Number of Historical Files" or both so that your applicable tracing does not get overwritten.

For more information regarding logging and tracing in the portal, refer to the topic "Logging and Tracing" in the WebSphere Portal Information Center.

3. Collect the following files from the server during the time period that the problem occurs:

• /logs/WebSphere_Portal/SystemOut.log
• /logs/WebSphere_Portal/SystemErr.log
• /logs/WebSphere_Portal/trace.log
• /config/cells//security.xml
• /config/cells//nodes//servers/WebSphere_Portal/resources.xml (located in /clusters/ for clustered server)
• /config/cells//wim (including sub-directories)
• /config/cells//fileRegistry.xml

Be certain to indicate the relevant details (date and time, test case, user ID, etc) to IBM Support in your communications, and use specific entries from the log to illustrate the problem reported if possible.