Oracle ESB Instance Tracking Does Not Show Instances When ESB Runtime and ESB Designtime are in Separate JVM Containers

(Doc ID 1312433.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle ESB - Version: 10.1.3.3 and later   [Release: AS10gR3 and later ]
Information in this document applies to any platform.

Symptoms

Using Oracle ESB 10g, you can run ESB instances without any issues, but when checking the ESB Control Console for instance tracking there is nothing shown. The ESB Control console is configured to show instance tracking and the oraesb.esb_parameter table has TrackingEnabled=Y or the TrackingEnabled column does not exist in the table.

The system is a single node, but has the ESB Runtime (ESBRT) installed into JVM container (e.g. oc4j_soa) and the ESB Designtime (ESBDT) is installed into its own separate container called e.g. oc4j_esbdt.

It is also confirmed by the parameters in oraesb.esb_parameter table that JMS memory/file based ESB topics are being used instead of AQ-JMS based topics as follows:

PROP_NAME_CONTROL_TCF_JNDI      OracleASjms/MyXATCF
PROP_NAME_CONTROL_TOPIC_JNDI    OracleASjms/ESBControlTopic
PROP_NAME_DEFERRED_TCF_JNDI     OracleASjms/MyTCF
PROP_NAME_DEFERRED_XATCF_JNDI   OracleASjms/MyXATCF
PROP_NAME_ERROR_RETRY_JNDI      OracleASjms/ESBErrorRetryTopic
PROP_NAME_ERROR_RETRY_TCF_JNDI  OracleASjms/MyXATCF
PROP_NAME_ERROR_TCF_JNDI        OracleASjms/MyTCF
PROP_NAME_ERROR_TOPIC_JNDI      OracleASjms/ESBErrorTopic
PROP_NAME_ERROR_XATCF_JNDI      OracleASjms/MyXATCF
PROP_NAME_MONITOR_TCF_JNDI      OracleASjms/MyTCF
PROP_NAME_MONITOR_TOPIC_JNDI    OracleASjms/ESBMonitorTopic

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms