If you do not want to use the default embedded messaging
configuration for event transmission, you can configure asynchronous
message transport to use an external Java™ Messaging
Service (JMS) provider.
Before you begin
Before you can configure event messaging using an external
JMS provider, you must first create a JMS queue and connection factory
using the appropriate interfaces for your JMS provider. You must also
create a listener port or activation specification.
About this task
To configure event messaging using an external JMS provider:
Procedure
From the wsadmin tool, run the deployEventServiceMdb administrative
command in batch or interactive mode. The parameters of
the
deployEventServiceMdb command are as follows:
- applicationName
- The application name of the event service message-driven bean
to be deployed. This parameter is required.
- nodeName
- The name of the node where the event service message-driven bean
should be deployed. If you specify a node name, you must also specify
a server name. This is an optional parameter; the default value is
the current node. Do not specify this parameter if you are deploying
the application in a cluster.
- serverName
- The name of the server where the event service message-driven
bean should be deployed. This parameter is required if you are deploying
the application at server scope; otherwise it is optional. Do not
specify a server name if you are deploying the application in a cluster.
- clusterName
- The name of the cluster where the event service message-driven
bean should be deployed. Specify this parameter only if you are deploying
the application in a cluster.
- listenerPort
- The name of the listener port that should be used by the event
service message-driven bean to publish events. The specified listener
port must already exist. You must specify either a listener port or
an activation specification, but not both.
- activationSpec
- The JNDI name of the activation specification that should be used
by the event service message-driven bean to publish events. The specified
activation specification must already exist. You must specify either
a listener port or an activation specification, but not both.
- qcfJndiName
- The JNDI name of the JMS queue connection factory to be used by
the event service message-driven bean. This parameter is required
if you specify an activation specification; otherwise it is optional.
If you specify a queue connection factory and a listener port, the
queue connection factory must match the one configured for the listener
port.
Results
The
deployEventServiceMdb administrative command deploys
the message-driven bean for the event service, configured for the
specified listener port or activation specification. It also creates
an emitter factory and JMS transmission using the external JMS configuration.
Applications can use either the default emitter factory (which is
configured to use the default messaging configuration) or the new
emitter factory (which uses the external JMS provider).
What to do next
If you want to set up more than one JMS queue to the event
service, you can run this command multiple times, specifying different
enterprise application names and JMS queues. Each time you run the
script, it deploys an additional message-driven bean and configures
new resources to use the specified JMS queue.