Express (Distributed operating systems), v8.0 > Secure applications and their environment > Authenticate users > Select a registry or repository > Manage realms in a federated repository > Virtual member manager > Troubleshoot and Support


Logs and trace

The logging function for virtual member manager is enabled through the console.

Virtual member manager uses the JSR-47 APIs to incorporate message logging and supports these levels of logging:

Severe

Severe messages indicate that the problem requires user action to enable the program to continue.

Warning

Warning messages inform the user or caller that potentially undesirable conditions have occurred or might occur. The condition does not require any action to enable the program to continue.

Info

Informational messages provide users with information or feedback about normal events that have occurred or are occurring. These events do not require any action.

Config

Configuration messages record and changes made to the configuration.

See the WAS Information Center for information about how to enable the logging function, to set the log levels and to designate the location of the log files.

Set the following trace string:

com.ibm.websphere.wim.*=all:
com.ibm.wsspi.wim.*=all:
com.ibm.ws.wim.*=all

To enable tracing for custom EMF classes and the associated Util class, set the following system properties in the JVM:

-Dcom.ibm.config.eclipse.epackage.debug=true
-Dcom.ibm.config.eclipse.epackage.debug.dir=
<logs_dest_location> 
EMF has its own logging mechanism, and is initialized before the RAS (Reliability, Availability, and Serviceability) trace component. Hence tracing for EMF must be enabled by setting these system properties. The EMF trace logs are collected at the location specified as <logs_dest_location>.

For more information read about Federated Repositories Specific MustGather information on the WAS support web site.

Parent topic: Troubleshoot and Support



+

Search Tips   |   Advanced Search