|
|
ALSB enables you to trace messages without having to shut down the server. This feature is useful in both a development and production environments. Tracing allows administrators, support engineers, and systems engineers to troubleshoot and diagnose a message flow in one or more proxy services.
For example, if one of your proxy services is failing and you want to find out at which stage the problem exists, you can enable tracing for that proxy service. After tracing is enabled, the system logs various details extracted from the message flow such as stage name, name of the pipeline, and route node name. The entire message context is also printed, including headers and message body. When a fault occurs in the message flow, additional details such as error code and reason are logged. Tracing occurs at the beginning and end of each component in the message flow, which includes stages, pipelines, and nodes. Actions are not traced individually.
You can enable tracing from View a Proxy Service page of the ALSB Console, as shown in Figure 6-1. to configure tracing:
| Note: | To enable tracing for all proxy services, search for all proxy services and click the check box next to Tracing. |
You can view the tracing status for a proxy service in the Operation Settings tab of the View a Proxy Service page, Summary of All Services table, and Summary of Proxy Services table. For more information about Summary of All Services, see Managing Operational Settings for All Services, and for more information about Summary of Proxy Services, see Managing Operational Settings for Proxy Services.
The tracing information is stored in the server directory logs. For example, in the ALSB examples domain, which is created when you install the product, if you enable tracing for the proxy services before they are tested, the tracing information is logged in the following log file.
<BEA_HOME>\weblogic92\samples\domains\servicebus\servers\xbusServer\logs\servicebus.log
where, BEA_HOME is the directory in which you installed your BEA product.
Figure 6-2 shows a sample of the tracing log.
| Note: | The tracing pattern in the server log is identical to the tracing in the test console. For more on tracing in the test console, see Tracing Proxy services—Test Console in Using the AquaLogic Service Bus Console. |
|
