Troubleshooting service integration technologies

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

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.
4. For current information from IBM Support on known problems and their resolution, see the WebSphere Application Server support page.
5. Search for WebSphere technotes.
   You can use the following queries to find articles for service integration technologies:

   • All technotes: http://www.ibm.com/support/search.wss?rs=180tc=SSEQTP&tc1=SSCBRCS
   • MustGather technotes, used to debug problems: http://www.ibm.com/support/search.wss?rs=180tc=SSEQTP&tc1=SSCBRCS&q=MustGather
6. Check for error messages.
   Check in the application server SystemOut.log file at profile_root\logs\server_name\SystemOut.log for error messages, where profile_root is the directory in which profile-specific information is stored.

   Note: This topic references one or more of the application server log files. As a recommended alternative, you can configure the server to use the High Performance Extensible Logging (HPEL) log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM® i systems. You can also use HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access all of your log and trace information using the LogViewer command-line tool from your server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.

   Check in the SYSPRINT or SYSOUT log for error messages.

   The following message prefixes relate to specific aspects of service integration technologies:

   Table 1. Prefixes and service integration technologies . The first column of the table lists the message prefixes. The second column contains the specific aspects of service integration technologies related to the message prefixes.

   Message prefix	Aspect of service integration technologies
   CWSIA	API
   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 you 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 IBM MQ error messages or reason codes in WebSphere Application Server messages and logs, refer to the Messages section of the IBM MQ documentation.
8. If the information obtained in the preceding stages is still inconclusive you should explore further, for example by enabling the application server debug trace to provide a detailed exception dump.