Collecting Data: JMS for IBM Web Content Manager 7.0

Technote (troubleshooting)


Problem

Collecting data for IBM Web Content Manager (WCM) V7.0 JMS issues. Gathering this information before contacting IBM Support will help to understand the problem and save time analyzing the data.

Resolving the problem

Technote (troubleshooting)

If you 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.

Manual collection of troubleshooting data

1) Collecting environment details:
  1. WebSphere version?
  2. LDAP server product and version installed, if any (local or remote and on what platform?)
  3. Database product and version installed, if any other than Cloudscape (local or remote and on what platform?)
  4. Operating System

2) Providing a detailed problem description:

Provide a detailed description of the issue you are reporting. When recreating the issue to collect the traces requested below, document your recreate scenario. Include the approximate time of each action.

  1. Was the create-wcm-jms-resources task run sucessfully?
  2. What topics are being published?
  3. Is there any problem with the message content?
  4. Are the messages not being retrieved properly?

3) Collecting trace file output:

1. Access the WebSphere Application Server Administrative Console by using the URL, http://hostname:port_number/ibm/console.
2. Go to the Server > Application servers section.
3. Select the application server of your portal.
4. Click Troubleshooting > Change Log Detail Levels.
5. Specify the required trace settings as follows:

    com.ibm.workplace.wcm.services.messaging.*=all:
    com.ibm.workplace.wcm.messaging.*=all:
    Messaging=all:JMSApi=all:JMSServer=all

6. Save your updates.
7. Restart the portal.
a) Stop the portal server.
b) Archive and delete the contents of the wp_profile/logs/WebSphere_Portal directory.
c) Start portal.
8. Recreate the reported issue (see Section 2 above).
9. To disable tracing, specify tracestring: *=info, and restart the portal.

4) Collect the required files:

  • Provide the MessagingService.properties file from the wp_profile/PortalServer/wcm/shared/app/config/wcmservices directory.
  • Provide the entire contents of the wp_profile/logs/WebSphere_Portal directory after the traces have been collected.
  • Provide the entire contents of the wp_profile/config/cells/<cell_name>/buses/ directory.
  • Provide resources.xml file from wp_profile/config/cells/<cell_name>/nodes/<node_name>/.
  • Provide the ConfigTrace.log file from wp_profile/configEngine/log/.
    NOTE: When sending in logs for review, include any related screenshots, timestamps, userIds, and so on, in order to expedite analysis of the issue.
Send the diagnostic information to IBM support:
Follow instructions to send diagnostic information to IBM Support and be sure to provide all diagnostic information captured above. This requires that a PMR be opened if not already.

Refer to the detailed instructions in "Exchanging information with IBM Technical Support for problem determination" to make the information available and to update your problem record.
Related information


Rate this page:

(0 users)Average rating

Document information


More support for:

IBM Web Content Manager
General

Software version:

7.0, 7.0.0.0, 7.0.0.1

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Reference #:

1450903

Modified date:

2011-04-12

Translate my page

Machine Translation

Content navigation