This section discusses the message and trace types that are available through the WebSphere implementation of JRas. Message types are provided by the RASIMessageEvent interface, and trace types are provided by the RASITraceEvent interface.
Message types are provided by the RASIMessageEvent interface. Types include the following:
These types, which are provided by JRas, do not correspond exactly to the
message types supported by the different editions of the WebSphere run
time. The following table shows the mappings between the JRas message
types and their WebSphere equivalents. Note that the Enterprise Edition
types apply to Component Broker on workstations.
Table 1. JRas message types and their WebSphere equivalents
JRas message type | Equivalent WebSphere Standard/Advanced Edition type | Equivalent WebSphere Enterprise Edition (Component Broker for workstations) type |
---|---|---|
TYPE_INFO, TYPE_INFORMATION | Audit | Informational |
TYPE_WARN, TYPE_WARNING | Warning | Warning |
TYPE_ERR, TYPE_ERROR | Error | Error |
Trace types are provided by the RASITraceEvent interface. This interface defines two sets of JRas trace types: a basic set of leveled types for simple trace implementations and a more complex set of nonleveled types that can be logically combined to create precise information about any given trace event. It is recommended that only one of these sets be used in any given application.
The basic set of types consists of the TYPE_LEVEL1, TYPE_LEVEL2, and TYPE_LEVEL3 trace levels. These levels are hierarchical; enabling a higher level of trace automatically enables all levels beneath it (for instance, enabling TYPE_LEVEL2 automatically enables TYPE_LEVEL1).
The complex set of types consists of the following trace values:
TYPE_API
TYPE_CALLBACK
TYPE_ENTRY_EXIT
TYPE_ERROR_EXC
TYPE_MISC_DATA
TYPE_OBJ_CREATE
TYPE_OBJ_DELETE
TYPE_PRIVATE
TYPE_PUBLIC
TYPE_STATIC
TYPE_SVC
These values can be combined logically (that is, by using operators such as AND, OR, and NOR) to provide detailed information about any given trace event.
As with the message types, the JRas trace types do not correspond exactly
to the types used by the WebSphere run time. The following tables show
the mappings between the JRas trace types and their WebSphere
equivalents. Note that the WebSphere equivalents apply to Standard
Edition, Advanced Edition, and, for Enterprise Edition, Component Broker on
workstations.
Table 2. Leveled JRas trace types and their WebSphere equivalents
JRas level event type | WebSphere equivalent |
---|---|
TYPE_LEVEL1 | Event |
TYPE_LEVEL2 | Entry/Exit |
TYPE_LEVEL3 | Debug |
Table 3. Nonleveled JRas trace types and their WebSphere equivalents
JRas nonleveled event types | WebSphere equivalent |
---|---|
TYPE_ERROR_EXC, TYPE_OBJ_CREATE, TYPE_OBJ_DELETE, TYPE_SVC | Event |
TYPE_API, TYPE_CALLBACK, TYPE_ENTRY_EXIT, TYPE_PRIVATE, TYPE_PUBLIC, TYPE_STATIC | Entry/Exit |
TYPE_MISC_DATA | Debug |