Recommended Resources
Abstract
Collecting troubleshooting data for portlet deployment problems with IBM WebSphere Portal 6.1 expedites time to resolution by enabling IBM Support to provide informed problem analysis.
Content
If you already contacted IBM Support and must collect data to determine the nature of a problem in WebSphere Portal, review the information below regarding data collection. Otherwise, review Collecting Data: Read first for WebSphere Portal.
Collecting Portlet Deployment problem specific information
Portlet Deployment problems include any instance where you are unable to install, update, or delete a portlet WAR using either the Manage Web Modules portlet in the Portal Administration pages or using XMLAccess.
1. Are you unable to deploy any portlet application? Or are you only unable to deploy a specific application?
2. Have there been any recent changes to the security configuration?
Automated log collection is available for this information and is the recommended method for improving accuracy of the data collection.
IBM Support Assistant Lite (ISA Lite) for WebSphere Portal
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" (e.g. c:\WebSphere\wp_profile\PortalServer\ISALite).
2. Run the runISALite.bat file (Windows) or runISALite.sh (UNIX or Linux) from the ISALite directory (e.g. c:\WebSphere\wp_profile\PortalServer\ISALite\runISALite.bat).
3. Once the tools starts, select the following Problem Type: WebSphere Portal->Installation and Configuration ->Portlet Deployment Problem
4. Provide the output path and a file name of "<PMR #>.isalite.zip" (e.g. 22222,111,000.isalite.zip).
5. Click Collect Data and follow the series of dialog boxes to set the tracing and reproduce the issue.
6. When asked to proceed to collect data, please select "Enable tracing with restarting the server" and enter the following trace string:
com.ibm.ws.management.*=all:
com.ibm.websphere.management.*=all
com.ibm.wps.pe.mgr.*=all:
com.ibm.wps.services.deployment.*=all:
com.ibm.wps.command.applications.*=all:
com.ibm.wps.command.portlets.*=all
NOTE: If you are in a clustered environment, please manually enable this tracestring against the DMGR and NodeAgent, and restart both of these servers before proceeding:
com.ibm.ws.management.*=all:
com.ibm.websphere.management.*=all
7. When asked to recreate the problem, please try the Portlet Deployment again, and then click "I have recreated the problem" to proceed to the data collection.
8. If you choose not to FTP the files to IBM via ISA Lite, then follow the instructions in Exchanging information with IBM Technical Support for problem determination.
If you are unable to use IBM Support Assistant Lite (ISA Lite) for WebSphere Portal for automatic log collection, use the following instructions for manually collecting the necessary information.
I. Enabling tracing and recreating the problem
1. Enable the following tracestring against the WebSphere_Portal server and restart the server:
com.ibm.ws.management.*=all:
com.ibm.websphere.management.*=all
com.ibm.wps.pe.mgr.*=all:
com.ibm.wps.services.deployment.*=all:
com.ibm.wps.command.applications.*=all:
com.ibm.wps.command.portlets.*=all
2. Cluster only. Enable the following tracestring against the DMGR and NodeAgent and restart the servers:
com.ibm.ws.management.*=all:
com.ibm.websphere.management.*=all
3. Recreate the portlet deployment problem.
II. Collecting and submitting logs and configuration data manually
1. Collect the following log files and directories:
- <wp_profile root>/ConfigEngine/log/ConfigTrace.log
- <wp_profile root>/logs/WebSphere_Portal
- <wp_profile root>/logs/ffdc
- Cluster only: <wp_profile root>/logs/nodeagent
- Cluster only: <dmgr_profile root>/logs/dmgr
- Cluster only: <dmgr_profile root>/logs/ffdc
2. Send the files to IBM Support by using the instructions outlined in Exchanging information with IBM Technical Support for problem determination.
Was this topic helpful?
Document Information
Modified date:
03 December 2021
UID
swg21468572