Collecting Data: Problems with modular-based themes in WebSphere Portal



Collecting troubleshooting data for problems with modular-based themes in WebSphere Portal with IBM® WebSphere® Portal expedites 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.

Collecting modular-based theme information

Data Collection

Use the following instructions for manually collecting the necessary information.

1. Does the problem persist after:

-- Clearing the cache?
-- Clearing all cookies?
-- Restarting the browser?
-- Logging out and back in?
-- After changing to the full profile?

-- Delete wstemp and temp directory from <wp_profile_home> and restarting the portal server? (Not recommended on production servers)

2. Answer the following questions:
-- Is the problem specific to a single browser?
-- Is the problem specific to admin or non-admin users?
-- Is the problem specific to a certain portlet/widget/page or user action? If yes, please provide more details.

If the problem still persists, collect the following information.

3. If the problem is with a theme in WebDav, use the following line in a browser to generate a zip of the theme files:


If the problem is with a skin, use the following line:

4. Provide the failing theme/skin dynamic files. This includes the following artifacts:
-- WAR file.
-- Profile used on the failing page.
-- Any required custom modules.
-- Any additional resources (such as JAR files) or special instructions for IBM Product Support to run the theme locally.

5. Enable debug:
When debug is enabled, the modules that contribute to the theme provide their uncompressed Javascript or CSS files if available. Additionally, all the files are retrieved with separate requests. This makes it much easier to find the offending file.

To debug a module or theme, enable portal tracing using the following trace string:

6. Use Fiddler to capture HTTP traffic for the failing scenario. Use the following steps:
a) Download Fiddler at

b) Open your browser and navigate to a website. NOTE: Browsers do not send localhost or traffic through proxies so you must use the machine's IP address or machine name directly.

c) Open Fiddler and watch the HTTP traffic in Fiddler's left panel.

7. Now open your browser and recreate the issue. Document the behavior you see, either through edited screen shots or text and expected behavior.

If there is a javascript error, Product Support must have the complete error details. Please provide a screenshot of the error and any details listed in the browser console.

8. Collect an xmlaccess export of your system using the instructions in Document #1260098, "How to generate a complete XMLAccess export of a Portal configuration." 

9. Collect the resources.xml file that contains the Resource Environment property, "WP DynamicContentSpotMappings" (default location is wp_profile\config\cells\<cell name>\nodes\<node name>\servers\WebSphere_Portal). This file should be at the cell level when clustered.

10. If the issue is with the display of the theme not appearing correctly, please collect a webpage. Complete from the failing browser:

Navigate to the failing page, use the menu's Save As option, and choose webpage.complete as the file type. This generates an HTM file and a corresponding folder. Product Support needs both.

11. For issues creating or deploying a custom module, Product Support must have the following:
-- The WAR file containing the module files.
-- Plugin.xml/json for the module.
-- The profile being used.

Enable the following tracing:*=all
and reinstall the WAR file containing the plugin.xml. Provide the generated trace.log file.

12. Please download the Theme Opimization Analyzer Portlet based on the Portal version from the catalog site:

For Portal 7x --

For Portal 8.0 --

For Portal 8.5 --
Theme Optimization Analyzer is installed with the product.

Note: Theme Optimization Analyzer Portlet version 2.0 or above is required to collect the mustgather information.

Once installed, navigate to the portlets Utilities links. Select the "Click here to export data" to generate the export.

13. Send the following files to Product Support by using the instructions outlined in Exchanging information with IBM Technical Support for problem determination:
a) The answers to the questions in Step 1 and Step 2 above.
b) The zip file from WebDav with your theme (Step 3).
c) The WAR file for your custom theme if created and all required resources (Step 4).
d) Save the Fiddler output of the entire session (File -> Save -> Save all sessions) as in Step 6.
e) Screen shots and console output as in Step 7.
f) The xmlaccess export of your system as in Step 8.
g) The resources.xml file collected in Step 9.
h) If this is a display issue, please provide the webpage.complete as in Step 10.
i) If this is an issue with registering a module, please provided the needed files as in Step 11.
k) Provide the export that was generated from Step 12.

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.

Related Information

Document information

More support for:

WebSphere Portal
Problem Determination

Software version:, 8.0, 8.5

Operating system(s):

AIX, IBM i, Linux, Solaris, Windows, z/OS

Reference #:


Modified date:


Translate my page

Content navigation