Network Deployment (Distributed operating systems), v8.0 > Troubleshoot and support > Work with Diagnostic Providers > Diagnostic Providers


Diagnostic Provider IDs

A Diagnostic Provider ID (DPID) is the unique address of a Diagnostic Provider MBean. Components that have associated Diagnostic Provider MBeans can include the DPID in their log entries.

DPIDs are implemented in WAS as Java Management Extensions (JMX) MBean ObjectNames, and can be used at JMX MBean servers to look up Diagnostic Provider MBeans.

By including the String representation of the DPID in each logged message, the message can be tracked back to the Diagnostic Provider related to the component. A method is provided to associate DPIDs with Loggers (from the java.util.logging logging API).

The diagram above shows how the use of DPIDs in log entries enables callbacks to the component that originally created the log entry.

  1. Component logging with a DPID included in the log entry.
  2. Administrator examines the log entry through the Runtime Messages Utility and notices that the entry has a link to a Diagnostic Provider.
  3. Administrator uses the link to gain access to the relevant MBean in the Diagnostic Provider Utility .
  4. Diagnostic Provider Utility contacts the Diagnostic Provider MBean to ask for more information.
  5. Request for more information is sent back to the source of the original log entry.
  6. Response from the Diagnostic Provider is provided in the administration console.

Associate a Diagnostic Provider ID with a logger
Diagnostic Providers (selection)
Message details

+

Search Tips   |   Advanced Search