Network Deployment (Distributed operating systems), v8.0 > Reference > Log and trace file descriptions
Common Base Event content handler
Content handlers populate data into Common Base Events when the Common Base Event complete method is invoked. We can associate content handlers with Common Base Event templates, which provide default information to transfer into each Common Base Event.
Content handlers might also provide any other information that is relevant to completing the population of the Common Base Event, such as appropriate runtime defaults. The use of content handlers ensures consistency of field use in the Common Base Event within a component or within a set of components that share the same runtime. For example, some content handlers support the specification of a template. If used consistently across a component, this template ensures that all events for that component have the same template information filled in. Similarly, some content handlers can also supply runtime information to their associated Common Base Events. If consistently used throughout the entire runtime, runtime information ensures that all events use runtime data in a similar way.
The event factory home used in the WAS runtime is associated with a content handler that both reads from a template, and supplies runtime data. Have components use Event Factories that are obtained from this event factory home with their own templates, to produce consistency between application events and server events.
More details can be found in Create custom Common Base Event content handlers or the API documentation for org.eclipse.hyades.logging.events.cbe.ContentHandler at www.eclipse.org/hyades.
The Common Base Event in WAS
Create custom Common Base Event content handlers
Log with Common Base Event API and the Java logging API
Log Common Base Events in WAS
Add logging and tracing to the application