Collecting Data: Managing Users/Groups via Administrative Portlets for WebSphere Portal 6.1

Content

If you already contacted IBM Support and must collect data to determine the nature of a problem in IBM WebSphere Portal, review the information below regarding data collection. Otherwise, review Collecting Data: Read first for WebSphere Portal 7.0.

Collecting Managing Users/Groups via Administrative Portlets specific information

Issues with managing users/groups via the Administrative Portlets can occur when using an administration portlet such as Manage Users/Groups to search for an object in the user registry based on a particular attribute or view membership for a group.

Automated collection of troubleshooting data

Automated log collection is available for this information and is the recommended method for improving accuracy of the data collection.

IBM Support Assistant Lite
Download Tool | View Demo of Trace Collection

After downloading IBM Support Assistant Lite, perform the following steps to collect the data and send to IBM Support:

1. Extract the contents of the downloaded file to the <wp_profile_root>\PortalServer directory which will create the subdirectory, "ISALite" (c:\WebSphere\wp_profile\PortalServer\ISALite).

2. Run the runISALite.bat file (Windows) or runISALite.sh (UNIX or Linux) from the ISALite directory (c:\WebSphere\wp_profile\PortalServer\ISALite\runISALite.bat).

3. Once the tool starts, select the following Problem Type: WebSphere Portal -> Security and Administration -> Portal Manage Users and Groups Problem.

4. Provide the output path and a file name of "<PMR #>.isalite.zip" (such as 22222,111,000.isalite.zip).

5. Click Collect Data and follow the series of dialog boxes to set the tracing, reproduce the issue, and send the files to IBM Support.

Manual collection of troubleshooting data

If you are unable to use IBM Support Assistant Lite for automatic log collection, use the following instructions for manually collecting the necessary information.

I. Enabling trace logging
Enable tracing during problem recreation in order to investigate the specific behavior of the component(s). Choose to enable either static or dynamic tracing and proceed with the steps accordingly. For further information regarding logging and tracing in the portal, refer to the Logging and Tracing topic in the WebSphere Portal 6.1 Information Center.

Option A: Enabling static (extended) tracing
Static tracing is the recommended method of capturing data, as it collects data from server startup until problem recreation.

1. Log into the Integrated Solutions Console as the WebSphere Application Server administrator.

2. Click Troubleshooting -> Logs and Trace -> WebSphere_Portal -> Diagnostic Trace.

3. On the Configuration tab, ensure Enable Log is selected. On this same tab, ensure that you increase the Maximum File Size and and Maximum Number of Historical Files as needed to ensure that the tracing of the problem recreation is not overwritten due to the amount of traffic on the system and output of the tracing itself.

4. Click Change Log Level Details and enter the following trace string:

*=info:com.ibm.wps.portlets.manageprincipals.*=all:
com.ibm.wps.portlets.admin.*=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.wps.ac.impl.AccessControlConfigFederator=all:
com.ibm.wps.ac.impl.AccessControlFederator=all:
com.ibm.ws.wim.*=all:com.ibm.websphere.wim.*=all:
com.ibm.wsspi.wim.*=all:
com.ibm.wps.engine.Servlet=all

5. Click OK and save the changes.

6. Restart the WebSphere_Portal application server.

Option B: Enabling dynamic tracing
Dynamic tracing can be used for situations that do not permit a server restart.

1. Log in as the Portal administrator.

2. Click Administration -> Portal Analysis -> Enable Tracing to display the Enable Tracing portlet.

3. Type the required trace string into the Append these trace settings field:

*=info:com.ibm.wps.portlets.manageprincipals.*=all:
com.ibm.wps.portlets.admin.*=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.wps.ac.impl.AccessControlConfigFederator=all:
com.ibm.wps.ac.impl.AccessControlFederator=all:
com.ibm.ws.wim.*=all:com.ibm.websphere.wim.*=all:
com.ibm.wsspi.wim.*=all:
com.ibm.wps.engine.Servlet=all

4. Click the Add icon. Enable Tracing updates the field Current trace settings.

NOTE: Restarting WebSphere Portal will remove traces that were set by using the Enable Tracing Administration portlet.

II. Collecting and submitting logs and configuration data

1. Reproduce the problem and immediately copy (if possible) the trace logs to prevent rolling over. Confirm that the timestamp for the issue is included in the trace logs and then collect the following information for review:

• Step-by-step details of test case including screenshots, user ID, and approximate timestamps
• <WP_profile_root>/logs/WebSphere_Portal/SystemOut.log
• <WP_profile_root>/logs/WebSphere_Portal/SystemErr.log
• <WP_profile_root>/logs/WebSphere_Portal/trace.log (s)
• <WP_profile_root>/PortalServer/log/VersionInfo.log
• <WP_profile_root>/config/cells/<cellname>/security.xml
• <WP_profile_root>/config/cells/<cellname>/nodes/<nodename>/servers/WebSphere_Portal/resources.xml (located in /clusters/<cluster_name> for clustered server)
• <WP_profile_root>/config/cells/<cellname>/wim (including sub-directories)
• <WP_profile_root>/config/cells/<cellname>/fileRegistry.xml

2. Send the files to IBM Support by using the instructions outlined in Exchanging information with IBM Technical Support for problem determination.

Related Information

• Overview: WebSphere Portal Support
• Steps to getting support for WebSphere Portal
• Collecting Data: Read first for WebSphere Portal