Perform these steps to switch the Events service on or off, and
specify the JNDI name of the event emitter profile factory that is used to
submit events.
Before you begin
This task assumes you have
- installed the Common Event Infrastructure server
- installed any Common Event Infrastructure Message-Driven
Bean applications
- configured all the Common Event Infrastructure resources
- logged into the WebSphere Process Server administrative
console
Why and when to perform this task
The Events service provides access to the Common Event Infrastructure server
and ensures that information about the WebSphere server, and correlation sphere
information, is automatically included in each event passed to the event infrastructure.
You
configure the Events service by modifying the
Enable service at
server startup property; this specifies whether the service is
started automatically for a specific application server. (You can also change
the JNDI name of the Common Event Infrastructure emitter factory. See Step
5.)
CAUTION:
Disabling the Events service will prevent the Common Event Infrastructure Server from processing
any events. No event information will be persisted in the database, nor will
events be distributed to JMS destinations.
Steps for this task
- In the administrative console navigation pane, click Servers
> Application Servers. A list of the application
servers is displayed in the content pane.
- Click into the Application server you want to configure.
- In the Business Integration table, select Common
Event Infrastructure Destination . The Events service properties
are displayed in the Configuration tab.
- Under General Properties, select or clear the Enable
service at server startup property check box.
- Selected
- [Default] The Events service starts when the application server starts.
This enables applications that generate events to run on the application server.
Important: The Events service is utilized by event monitoring and should
be enabled all the time.
An enabled Events service allows information
about the WebSphere server, and correlation sphere information, to be automatically
included in each event that will be passed to the event infrastructure.
- Cleared
- The Events service does not start when the application server starts.
The Events service is utilized by event monitoring, and a disabled Events
service will not automatically gather and insert information about the WebSphere
server into each event, and also will not create any correlation sphere information.
Any
attempt to start an application that uses the Events service is rejected,
and a message is issued. The server will continue to start without the application.
- Review the Java Naming and Directory Interface (JNDI) name of the
event emitter profile factory that is used to submit events to the event infrastructure.
You can select the JNDI name using one of two methods:
- Drop-down menu
- By default, this method is selected, and will specify a default emitter
factory JNDI from the Common Event Infrastructure Provider, although there
may be other names available on this menu. The default value on this menu
will be com/ibm/events/configuration/emitter/Default, which
is the default emitter factory JNDI from the Common Event Infrastructure Provider
and is part of the WebSphere default profile. Unless you have generated an
alternate profile, accept the default.
- Text entry box
- You can select this and fill in the JNDI name if you do not see the appropriate
name in the pull-down menu.
- To save and apply your configuration, click the OK button.
- Stop and restart the Application server for the changes to take
effect.