If you do not want to use the WebSphere Process Server default
messaging feature for event transmission, you can configure asynchronous message
transport to use a different 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.
Why and when to perform this task
The
event-message.jacl script sets up the configuration
objects required for asynchronous event transmission using an external JMS
provider such as WebSphere MQ:
- If a scope is specified, then it creates a JMS transmission profile using
the JMS queue and connection factory you specify.
- It creates an emitter factory profile using the created JMS transmission
profile for asynchronous event transmission.
- It deploys the message-driven bean used by the Common Event Infrastructure
to receive events sent asynchronously to the event server, using either a
listener port or a JMS activation specification.
If you want to set up more than one JMS queue to the event server,
you can run this script 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.
To configure event messaging to use an external JMS provider:
Steps for this task
- Go to the $WAS_HOME/event/application directory for the profile
defining the WebSphere Process Server runtime
environment where you want to configure default messaging. (Replace profile_path with
the path to the directory containing the WebSphere Process Server profile.)
- Run the event-message.jacl script using the wsadmin command:
- Windows systems
%WAS_HOME%\bin\wsadmin -profile event-profile.jacl -f event-message.jacl
-action install -earfile event-message.ear -node node_name
[-server server_name] [cluster cluster_name]
-appname app_name -qjndi queue -qcfjndi connection_factory
[-listenerport listener_port] [-activationspecjndi spec_name]
[-eventprofilescope scope] [-trace]
- Linux and UNIX systems
$WAS_HOME/bin/wsadmin -profile event-profile.jacl -f event-message.jacl
-action install -earfile event-message.ear -node node_name
[-server server_name] [cluster cluster_name]
-appname app_name -qjndi queue -qcfjndi connection_factory
[-listenerport listener_port] [-activationspecjndi spec_name]
[-eventprofilescope scope] [-trace]
$WAS_HOME/bin/wsadmin -profile event-profile.jacl -f event-message.jacl
-action install -earfile event-message.ear -node node_name
[-server server_name] [cluster cluster_name]
-appname app_name -qjndi queue -qcfjndi connection_factory
[-listenerport listener_port] [-activationspecjndi spec_name]
[-eventprofilescope scope] [-trace]
The parameters of the
event-message.jacl script are
as follows:
- node_name
- The WebSphere Process Server node
in which the messaging application is to be deployed. To determine the node
name:
- Run the profile_path/bin/setupCmdLine script.
- Run the command echo $WAS_NODE (Linux/UNIX systems) or echo
%WAS_NODE% (Windows systems).
This value is case-sensitive. If you are deploying the application in
a cluster, omit this parameter.
- server_name
- The WebSphere server into which the messaging application is to be deployed.
This value is case-sensitive. If you are deploying the application in a cluster,
omit this parameter.
The optional -trace parameter
causes additional debugging information to be displayed on the standard output.
Note: - If you specify a fully qualified path for the location
of the event-message.ear file, make sure you use forward slashes (/) in the
path, even on Windows systems.
- If you are deploying the messaging application on a stand-alone node,
specify the optional -conntype none parameter to run wsadmin in
local mode
After you start the script, you are prompted
for your JMS user ID and password.