Skip Headers
Oracle® Fusion Middleware Administrator's Guide for Oracle Service Bus
11g Release 1 (11.1.1.6.3)

Part Number E15867-08
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

B Debugging Oracle Service Bus

This chapter describes how to enable debugging for different modules in Oracle Service Bus.

This chapter includes the following sections:

B.1 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:

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. Example B-1 provides an example of the contents of the alsbdebug.xml file with debugging disabled for all modules (all entries set to false).

Example B-1 alsbdebug.xml File

<java:sb-debug-logger xmlns:java="java:com.bea.wli.debug">
  <java:alsb-stages-transform-runtime-debug>true</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-proxy-server-manager-debug>true</java:alsb-proxy-server-manager-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>true</java:alsb-throttling-debug> 
  <java:alsb-flow-resource-debug>false</java:alsb-flow-resource-debug> 
  <java:alsb-flow-transport-debug>false</java:alsb-flow-transport-debug> 
  <java:alsb-flow-deployment-debug>false</java:alsb-flow-deployment-debug> 
  <java:alsb-soa-codec-debug>true</java:alsb-soa-codec-debug> 
  <java:alsb-message-tracing-debug>true</java:alsb-message-tracing-debug> 
  <java:alsb-result-caching-debug>true</java:alsb-result-caching-debug> 
  <java:alsb-console-debug>false</java:alsb-console-debug> 
  <java:alsb-bpel-debug>false</java:alsb-bpel-debug> <!-- Split-Join processing details -->
  <java:alsb-jca-framework-adapter-debug>true</java:alsb-jca-framework-adapter-debug> 
</java:sb-debug-logger>

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

Example 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>false</java:config-fwk-debug> 
  <java:config-fwk-transaction-debug>false</java:config-fwk-transaction-debug> 
  <java:config-fwk-deployment-debug>false</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.

Note: For the JCA transport, framework, and adapters, use alsb-jca-framework-adapter-debug.

alsb-jca-framework-adapter-debug

Provides JCA transport, framework, and adapters debug information.

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.

alsb-result-caching-debug

Provides information on business service result caching.


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 DOMAIN_DIRECTORY/servers/servername/logs/servername.log.

B.2 Debugging Proxy Services and Split-Joins in Eclipse

See "Using the Oracle Service Bus Debugger" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus.