Service mapping: Trace and logging

To help you identify and resolve problems, the product has a unified logging component.

WebSphere® Application Server system messages are logged from a variety of sources, including application server components and applications. To help you identify and resolve problems, use the WebSphere Application Server tracing and logging facilities. You can check for system messages in the WebSphere Application Server administrative console, and in the application server SystemOut.log file. You can also enable the application server debug trace to provide a detailed exception dump.

To enable trace for service mapping, set the application server trace string to CWSMW*=all:ServiceMapping=all.

When fine-level tracing is set, CWSMW05** messages write basic information about what is happening in the execution of the mapping service and service map to the trace.log file.

The messages that are in the output contain descriptive information when any of the following events occur:

Here is an example when fine-level tracing is enabled:

CWSMW0500I: Service mapping intercepted a request to http://localhost:9080/Test1/TestService1 [http://test, TestService1Service, TestService1Port].
CWSMW0501I: Local mapping service lmService_testSoapHeaders matches intercepted request to http://localhost:9080/Test1JAXWSProject/TestService1Service.
CWSMW0502I: Service map testSoapHeaders is attached to local mapping service lmServiceSoapHeaders.
CWSMW0550I: Service map testSoapHeaders received a 'Request' message with data:
$Body=<ns2:getGreeting xmlns:ns2="http://test"><arg0>Header1</arg0></ns2:getGreeting>
$SOAPHeaders=<ns2:getGreetingHeader1 xmlns:ns2="http://test">
    <return>request_soap_header1</return></ns2:getGreetingHeader1>
  <ns2:getGreetingHeader2 xmlns:ns2="http://test">
    <return>request_soap_header2</return></ns2:getGreetingHeader2>
$TransportHeaders/HTTP/Headers={ SOAPAction=http://soap.debug.org/TestService1/testSoapActionInWsdl }
$Context={ SourceOperation={http://test}getGreeting, SourcePortType={http://test}TestService1Delegate, TargetOperation={http://test}getGreeting, TargetPortType={http://test}TestService1Delegate }
CWSMW0551I: The message will be routed to selected target service 'TestService5' from service map testSoapHeaders.
CWSMW0553I: Service map testSoapHeaders is transforming the message using data map ../Request.map.
CWSMW0554I: Service map testSoapHeaders transformed the message data to:
$Body=<out:getFarewell xmlns:out="http://testService5"><arg0>Header1</arg0></out:getFarewell>
$SOAPHeaders=<out:getFarewellHeader1 xmlns:out="http://testService5">
    <return>request_soap_header1</return></out:getFarewellHeader1>
  <out:getFarewellHeader2 xmlns:out="http://testService5">
    <return>REQUEST_SOAP_HEADER2</return></out:getFarewellHeader2>
$TransportHeaders/HTTP/Headers={ SOAPAction=http://soap.debug.org/TestService1/testSoapActionInWsdl }
$Context={ SourceOperation={http://test}getGreeting, SourcePortType={http://test}TestService1Delegate, TargetOperation={http://testService5}getFarewell, TargetPortType={http://testService5}TestService5Delegate }
CWSMW0505I: Service map testSoapHeaders is sending the message to service 'TestService5'.
This trace shows the messages that would be seen in a trace.log file for a Service Mapping invocation. You can see:
  • A message is intercepted.
  • The intercepted message is matched with a local mapping service.
  • The local mapping service is attached to a service map.
  • The contents of the intercepted message.
  • The selected target service that the message will be routed to.
  • The message will be transformed by a specific data map.
  • The output from the transformation.
  • The message has been sent to the selected target service.
You would also see similar messages for the return path, whether that is a normal response message or a fault message.
Note: Beginning in WebSphere Application Server Version 8.0, 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. 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 Using HPEL to troubleshoot applications.

For more information about using tracing and logging, see Adding logging and tracing to your application.


Icon that indicates the type of topic Reference topic

Terms and conditions for information centers | Feedback


Timestamp icon Last updated: Tuesday, 22 April 2014
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-base-iseries&topic=rsm_logging
File name: rsm_logging.html