Before you can use Common Event Infrastructure, you must first
deploy the event service and associated resources in the server runtime
environment.
About this task
The Common Event Infrastructure enterprise
application includes the runtime components of the event service and
the default messaging configuration used for asynchronous event submission.
To
deploy the event service:
Procedure
From the wsadmin tool, run the deployEventService administrative
command in batch or interactive mode. The parameters of
the
deployEventService administrative command are as follows:
- nodeName
- The name of the node where the event service should be deployed.
This parameter is optional; if you do not specify a node name, the
default is the current node. If you specify a node name, then you
must also specify the server name using the serverName parameter.
This parameter is not valid if you are deploying the event service
in a cluster.
- serverName
- The name of the server where the event service should be deployed.
This parameter is required only if you specify a node; it is not valid
if you are deploying the event service in a cluster.
- clusterName
- The name of the cluster where the event service should be deployed.
This parameter is optional and must not be specified if you are deploying
at the node or server scope.
- enable
- Indicates whether the event service should be started automatically
when the server starts. The default value is true.
Results
After the administrative command completes, the
Common Event Infrastructure event service and
default messaging configuration are deployed at the specified scope.
What to do next
If WebSphere® security
is enabled, you must also configure the JMS authentication alias and
password using the setEventServiceJmsAuthAlias administrative
command.
If you are deploying the event service in a cluster,
you must also manually configure the event database.