Troubleshooting service integration technologies

Use this overview task to help resolve a problem that you think is related to service integration technologies.

For general information about fixing problems, see Diagnose problems (using diagnosis tools). To help you identify and resolve problems, use the WAS tracing and logging facilities.

See about using tracing and logging, see Add logging and tracing to the application.

If you encounter a problem that you think might be related to service integration technologies, complete the following stages.


  1. Check the "Tips for troubleshooting" related links for specific problems related to service integration technologies.

  2. Use Troubleshooting service integration message problems to investigate problems with messages, such as messages not arriving or being consumed. If the tips and the investigations do not help you fix the problem, complete the following general stages.

  3. Check the Release Notes for known problems and their resolution. The Release Notes are available from the WAS library website.

  4. For current information from IBM Support on known problems and their resolution, see the WAS support page.

  5. Search the WebSphere Technotes database. Use the following queries to find articles for service integration technologies:

  6. Check for error messages.

    Check in the appserver SystemOut log at profile_root\logs\server_name\SystemOut.log for error messages, where $PROFILE_ROOT is the directory in which profile-specific information is stored. The following message prefixes relate to specific aspects of service integration technologies:

    Table 1. Prefixes and service integration technologies
    Message prefix Aspect of service integration technologies
    CWSIB Message formatting and parsing core
    CWSIC Communications
    CWSID Administration and system management
    CWSIE Message formatting and parsing SPI
    CWSIF Message formatting and parsing
    CWSIG Example
    CWSIH Match space
    CWSII Security
    CWSIJ Communications formats and protocol
    CWSIK Common messages
    CWSIL Publish and subscribe bridge
    CWSIM Mediations
    CWSIN Mediation services
    CWSIO Administration migration
    CWSIP Message processor
    CWSIQ MQ formats and protocol
    CWSIR Core programming interface
    CWSIS Message store
    CWSIT Topology routing and management
    CWSIU Utilities
    CWSIV Resource adapter
    CWSIX Core beans
    CWSIY Mediation handler framework
    CWSIZ Mediation framework
    CWSJA Administration commands
    CWSJB Inter-bus link
    CWSJC Core selector
    CWSJD Administration security
    CWSJO Service Data Objects configuration
    CWSJQ Message formatting and parsing MQ interoperability
    CWSJR Resource adapter (JMS)
    CWSJU Message tracing
    CWSJW WLM classifier for z/OS

    The Troubleshooter reference: Messages contains information about the messages, indexed by message prefix. For each message there is an explanation of the problem, and details of any action that we can take to resolve the problem.

  7. Check for more information and error messages that might provide a clue to a related problem. For example, if you see WebSphere MQ error messages or reason codes in WAS messages and logs, refer to the WebSphere MQ Messages document at

  8. If the information obtained in the preceding stages is still inconclusive you should explore further, for example by enabling the appserver debug trace to provide a detailed exception dump.

Last updated Nov 10, 2010 8:23:07 PM CST