Collecting Data: Managed Pages for WebSphere Portal
Collecting data for troubleshooting issues with Managed Pages in IBM® WebSphere® Portal to expedite time to resolution by enabling IBM Support to provide informed problem analysis.
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.
Managed Pages problem information
Managed Pages are Portal pages which have a Web Content Manager (WCM) representation in the Portal Site library. The management of such pages via WCM allows Portal pages to leverage WCM features such as workflow, projects, versioning, etc.
A brief outline of the various problems and other errors related to Managed Pages are given below:
- Pages created in Portal do not appear in the Portal Site library
- Portal pages are out of sync with WCM pages in the Portal Site library
- Project operations failing
- Draft operations failing
- XMLAccess failing
- Portal Scripting failing
- Syndication failing
- Page Title not displayed in WCM
- Access Control
Based on where the problem lies, go to the appropriate section in the table below to collect the necessary troubleshooting data.
Use the following instructions for collecting the necessary troubleshooting data.
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 System event logging topic in the WebSphere Portal Knowledge 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 you increase the Maximum File Size 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 trace string based on the table below.
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. The Enable Tracing portlet appears.
3. Type the required trace string into the field Append these trace settings as per the pertinent problem defined above.
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.
|Pages created in Portal do not appear in the Portal Site library||com.ibm.wps.wcm.access.project.*=all:
Please answer the below questions and provide supporting information wherever needed:
|Portal pages are out of sync with WCM pages in the Portal Site library||Please answer the below questions and provide supporting information wherever needed:
|Project operations failing||com.ibm.wps.wcm.access.project.*=all:
Note: This is especially for the “Publish Project” operation. Make sure all content is published within the project before publishing the project.
|Draft operations failing||com.ibm.wps.wcm.events.extensions.*=all:
Note: Pages in draft mode will not show up in an XMLAccess export.
|Portal Scripting failing||com.ibm.wps.scripting.*=all:
Important Note: Ensure that you first perform a staging to production of the syndicator and subscriber environments. Only after this happens will pages syndicate. Only published pages will be moved via XMLAccess export / import.
Please provide a release export from both the syndicator and subscriber environments
|Page Title not displayed in WCM||com.ibm.wps.wcm.events.extensions.*=all:
|Access Control||Minimum traces:
More detailed traces:
Debugging access control assignment/modification issues:
Check that the access control of the page and wcm node is correctly set and in sync:
Note: Special access control considerations are documented in the InfoCenter under 'Access control for managed pages' refer to the Portal 8.5 Infocenter or Portal 8.0 Infocenter.
II. Collecting and submitting logs and configuration data
1. Reproduce the problem. Collect screenshots, userId, and timestamp information as appropriate.
2. Run the following script from <wp_profile>/PortalServer/bin to collect the data:
- Windows: wpcollector.bat
- Linux/Unix/i: wpcollector.sh
Note: If you wish to use wpcollector to FTP the files to IBM Support, include the -Dpmr=<pmr_number> parameter to indicate the relevant PMR #. For example: wpcollector.bat -Dpmr=11111,222,333
3. If you did not FTP your files via wpcollector, locate the "wp.mustgather.zip" file or the "<pmr #>-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.
Reminder: When sending in logs for review, include any relevant screenshots, timestamps, userIds, etc. in order to expedite analysis of the issue.
More support for:
Software version: 8.0, 8.5
Operating system(s): AIX, IBM i, Linux, Solaris, Windows, z/OS
Software edition: Enable, Express, Extend, Server
Reference #: 1960989
Modified date: 25 November 2015
Translate this page: