Network Deployment (Distributed operating systems), v8.0 > Troubleshoot and support > Work with Diagnostic Providers > Diagnostic Providers
Diagnostic Service MBean interfaces
Diagnostic Provider services are available through a JMX interface. An example of such an interface is wsadmin.sh.
Formatted output is localized to the client Locale.
The Diagnostic Service interface provides four signatures...
- configDump
- stateDump
- selfDiagnostic
The four Diagnostic Service methods that map to configDump on a Diagnostic Provider are:
public DiagnosticEvent [] configDump(String aDPName, String aAttributeIdSpec, boolean aRegisteredOnly)
public DiagnosticEvent [] configDumpById(String aDPid, String aAttributeIdSpec, boolean aRegisteredOnly)
public String [] configDumpFormatted(String aDPName, String aAttributeIdSpec, boolean aRegisteredOnly, Locale aLocale)
public String [] configDumpFormattedById(String aDPid, String aAttributeIdSpec, boolean aRegisteredOnly, Locale aLocale)
The first two return exactly what the DP does. The second two methods act as a pass-through to the actual DP, but they take the array of Diagnostic Events that the DP returns, and convert it into a more easily consumable String array. In addition, these methods handle localizing the output to the appropriate locale. It is important to note that the same method can be driven using the DP ID or the DP Name. Work with Diagnostic Providers