CBE Function Component

These event objects can be written to CBE logs (which can be then viewed / managed using the Autonomic Computing Toolkit's Log and Trace Analyzer) or issued to an IBM® Common Event Infrastructure (CEI) server; alternatively, send it to an external application that is listening for CBE events.

Using the FC in IBM Security Directory Integrator, you must map your work entry attributes to the standard CBE attributes exposed in the Output Map of the CBE FC, so that when the AssemblyLine is run, the CBE FC creates a CBE Event object (and a CBE Event XML) and puts it back into the AssemblyLine's work entry.

You can also map a CBE object to the event attribute or XML representing a CBE object to the eventXml attribute of the OutputMap, so when the AL is run, the CBE FC retrieves all the standard CBE attributes and puts them back to the work entry.

An event encapsulates message data sent as the result of an occurrence of a situation. Events exchanged between and among applications in complex information technology systems allow these various facets of the system to interoperate, communicate and coordinate their activities. Fundamental aspects of enterprise management and e-business communications, such as performance monitoring, security and reliability, as well as fundamental portions of e-business communications, such as order tracking, are grounded in the viability and fidelity of these events.

The Common Base Event is defined as a new standard for enterprise management and business applications events. The Common Base Event definition ensures completeness of the data by providing properties to publish general information whenever a situation occurs. This general information provided by the Common Base Event is called the 3-tuple.