Collecting Data: Portlet Deployment issues for WebSphere Portal 7.0

Content

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

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.

Questions

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?

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 using WPCollector

1. Run the following script from <wp_profile>/PortalServer/bin to collect the data:

• Windows:  wpcollector.bat
• Linux/Unix/i: wpcollector.sh

2. Locate the "wp.mustgather.zip" file or the "<case #>-wp.mustgather-timestamp.zip" file in <wp_profile_root>/filesForAutoPD/. Send the files to IBM Support by using the instructions outlined in Exchanging information with IBM Technical Support for problem determination.

Note: When sending in logs for review, include any relevant screenshots, timestamps, userIds, etc. in order to expedite analysis of the issue.

III. 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
• Cluster only: <dmgr_profile root>/config/cells/cellname/clusters/clusterName/resources.xml
• Standalone only: <wp_profile root>/config/cells/cellname/nodes/nodeName/servers/WebSphere_Portal/resources.xml
• <wp_profile>/config/cells/cellname/security.xml
• <wp_profile>/config/cells/cellname/wim
  

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

Related Information:

• Collecting Data: Read first for WebSphere Portal 7.0