Common Event Infrastructure components
are installed as a set of applications, services, and resources on
the server.
When you configure Common Event Infrastructure,
a number of components are created and deployed on your server.
- Common Event Infrastructure service
- A service installed into the server, that enables applications
and clients to use Common Event Infrastructure.
You can view the configuration of the Common Event Infrastructure service in the
administrative console, as follows:
- For a server, select Servers > Application Servers
> server_name > Business Integration > Common Event
Infrastructure > Common Event Infrastructure Service.
- For a cluster, select Servers > Clusters > cluster_name >
Business Integration > Common Event Infrastructure > Common Event
Infrastructure Service.
If the check box labeled "Enable the event infrastructure
server" is selected, then the service is installed and running or
it will start after you restart your server or cluster. If it is cleared,
then the service is not installed or will be uninstalled after you
restart your server or cluster
- Event service settings
- A set of properties used by the event service that enable event
distribution and persistence using the data store. Typically, no configuration
is necessary for this resource, but you might need to create additional
event service settings if you want to set up multiple event services
in the same cell. To view the event service settings, click Service
integration > Event service > Event service settings.
- Event messaging configuration
- The resources that support asynchronous event transmission to
the event service using the Java™ Messaging
Service (JMS). The default messaging configuration uses the server
embedded messaging. You can optionally configure an external JMS provider
for event messaging.
- Event database
- The event database is used to persistently store events received
by the event service. The Derby database is included as part of the
server, but is not recommended for use in production environments.
Instead, you can configure an external event database on the following
products: DB2®, Oracle, SQLServer,
and Informix®.
- Event filter plug-in
- A filter plug-in is used to filter events at the source using
XPath event selectors. To configure the filter properties, click Service
Integration > Common Event Infrastructure > Event Emitter Factories
> Event Filter Settings.
- Emitter factory
- An emitter factory is an object used by event sources to create
emitters; an emitter is used to send events to the event service.
The properties of an emitter factory affect the behavior of any emitter
that is created using that emitter factory. To view the available
emitter factories, click Service Integration > Common Event
Infrastructure > Event Emitter Factories.
- Event service transmission
- An event service transmission is an object defining properties
that determine how emitters access the event service synchronously
using EJB calls; these properties are used by emitter factories when
creating new emitters. You can view or change the available event
service transmissions from the emitter factory settings.
- JMS transmission
- A JMS transmission is an object that defines properties that determine
how emitters access the event service asynchronously using a JMS queue;
these properties are used by emitter factories when creating new emitters.
You can view or change the available JMS transmissions from the emitter
factory settings.
- Event group
An event group is a logical collection of events used to categorize
events according to their content. When querying events from the event
service or subscribing to event distribution, an event consumer can
specify an event group to retrieve only the events in that group.
Event groups can also be used to specify which events should be stored
in the persistent data store. To view the available event groups in
the administrative console, click Service integration >
Common Event Infrastructure > Event service > Event services > event_service >
Event groups.