User Guide

Debugging Oracle Service Bus

This section provides information about enabling debugging for different modules in Oracle Service Bus.

Debugging Oracle Service Bus

You can enable and disable debugging by modifying the corresponding entries in the following debug XML files, which are located in the root directory of your Oracle Service Bus domain:

alsbdebug.xml—Contains Oracle Service Bus related debug flags
configfwkdebug.xml—Contains configuration related debug flags

If the XML files are not in the root directory or if they have been deleted, they are created again without any contents when the server starts. Listing B-1 provides an example of the contents of the alsbdebug.xml file with debugging disabled for all modules (all entries set to false).

Listing B-1 alsbdebug.xml File

<java:sb-debug-logger xmlns:java='java:com.bea.wli.debug'>

<java:alsb-stages-transform-runtime-debug>false</java:alsb-stages-transform-runtime-debug>
  <java:alsb-alert-manager-debug>false</java:alsb-alert-manager-debug>
  <java:alsb-credential-debug>false</java:alsb-credential-debug>

<java:alsb-jms-reporting-provider-debug>false</java:alsb-jms-reporting-provider-debug>

<java:alsb-management-credential-debug>false</java:alsb-management-credential-debug>

<java:alsb-management-dashboard-debug>false</java:alsb-management-dashboard-debug>
  <java:alsb-management-debug>false</java:alsb-management-debug>

<java:alsb-management-user-mgt-debug>false</java:alsb-management-user-mgt-debug>
  <java:alsb-module-debug>true</java:alsb-module-debug>

<java:alsb-monitoring-aggregator-debug>false</java:alsb-monitoring-aggregator-debug>
  <java:alsb-monitoring-debug>false</java:alsb-monitoring-debug>
  <java:alsb-pipeline-debug>true</java:alsb-pipeline-debug>
  <java:alsb-security-wss-debug>true</java:alsb-security-wss-debug>

<java:alsb-service-account-manager-debug>false</java:alsb-service-account-manager-debug>

<java:alsb-service-provider-manager-debug>false</java:alsb-service-provider-manager-debug>

<java:alsb-service-repository-debug>false</java:alsb-service-repository-debug>

<java:alsb-service-security-manager-debug>false</java:alsb-service-security-manager-debug>

<java:alsb-service-validation-debug>false</java:alsb-service-validation-debug
  <java:alsb-test-console-debug>false</java:alsb-test-console-debug>
  <java:alsb-transports-debug>true</java:alsb-transports-debug>
  <java:alsb-uddi-debug>true</java:alsb-uddi-debug>
  <java:alsb-wsdl-repository-debug>false</java:alsb-wsdl-repository-debug>

<java:alsb-wspolicy-repository-debug>true</java:alsb-wspolicy-repository-debug>

<java:alsb-security-encryption-debug>false</java:alsb-security-encryption-debug>
  <java:alsb-security-module-debug>false</java:alsb-security-module-debug>
  <java:alsb-sources-debug>false</java:alsb-sources-debug>
  <java:alsb-custom-resource-debug>false</java:alsb-custom-resource-debug>
  <java:alsb-mqconnection-debug>false</java:alsb-mqconnection-debug>
  <java:alsb-throttling-debug>false</java:alsb-throttling-debug>
</java:sb-debug-logger>

Listing B-2 provides an example of the contents of the configfwkdebug.xml file.

Listing B-2 configfwkdebug.xml File

<java:config-fwk-debug-logger xmlns:java='java:com.bea.wli.config.debug'>
    <n1:Name
xmlns:n1='java:weblogic.diagnostics.debug'>configfwkdebug</n1:Name>
    <java:config-fwk-debug>true</java:config-fwk-debug>

<java:config-fwk-transaction-debug>false</java:config-fwk-transaction-debug>
    <java:config-fwk-deployment-debug>true</java:config-fwk-deployment-debug>
    <java:config-fwk-component-debug>false</java:config-fwk-component-debug>
    <java:config-fwk-security-debug>false</java:config-fwk-security-debug>

</java:config-fwk-debug-logger>

Although debugging should be disabled during normal Oracle Service Bus operation, you may find it helpful to turn on certain debug flags while you are developing your solution and experimenting with it for the first time. For example, you may want to turn on the alert debugging flag when you are developing alerts and would like to investigate how the alert engine works.

Some of the available Oracle Service Bus debug flags are shown in Table B-1.

Table B-1 Oracle Service Bus Debug Flags
Debug Flag	Action
`alsb-stages-transform-runtime-debug`	Provides information on transformation related actions.
`alsb-alert-manager-debug`	Prints an evaluation of alerts.
`alsb-jms-reporting-provider-debug`	Provides information on the out of the box, JMS-based reporting provider.
`alsb-management-debug`	Provides information on user and group management in the console.
`alsb-monitoring-debug`	Provides information on the statistics system.
`alsb-pipeline-debug`	Provides information on errors that are generated within the pipeline.
`alsb-service-repository-debug`	Provides information on various service related configuration operations.
`alsb-service-security-manager-debug`	Provides information on access control.
`alsb-transports-debug`	Provides transport related debug information, including transport headers, which is printed per-message.
`alsb-wsdl-repository-debug`	Provides information on WSDL related configuration operation.
`alsb-wspolicy-repository-debug`	Provides information on WS policy.
`alsb-custom-resource-debug`	Provides information on custom resources.
`alsb-mqconnection-debug`	Provides information on the MQ connection resource.
`alsb-throttling-debug`	Provides information on the throttling feature.

Table B-2 lists the available configuration framework debug flags.

Table B-2 Configuration Framework Debug Flags
Debug Flag	Action
`config-fwk-debug`	Provides information on general aspects of Oracle Service Bus configuration.
`config-fwk-transaction-debug`	Provides low level debug information about changes made to in-memory data structures and files. This debug flag also generates server startup recovery logs.
`config-fwk-deployment-debug`	Provides debug information on session creation, activation, and distribution of configuration in a cluster.
`config-fwk-component-debug`	Provides low level debug information about create, update, delete, and import operations.
`config-fwk-security-debug`	Provides debug information on encryption and decryption during importing and exporting.

All other debug flags are self explanatory.

For all flags, debug information is logged to the server log at {domaindir}/servers/{servername}/logs/{servername}.log.

Debugging Proxy Services and Split-Joins in Workshop for WebLogic

See Using the Oracle Service Bus Debugger in the Using the Oracle Service Bus Plug-ins for Workshop for WebLogic guide.