The default messaging configuration for asynchronous event transport
uses the WebSphere ESB default messaging feature as the Java Messaging
Service (JMS) provider.
Why and when to perform this task
The
default-event-message.jacl script provides a way to
quickly set up a default messaging configuration, using the WebSphere default
messaging feature as the JMS provider. This script sets up all of the configuration
objects required for asynchronous event transmission:
- It creates a JMS queue and a queue connection factory using the default
messaging feature.
- It creates a service integration bus and adds members to the bus, associating
the bus with queues, topics, and connection factories.
- It creates a JMS transmission profile using the created queue and connection
factory.
- It configures the default emitter factory profile to use 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.
To configure default messaging:
Steps for this task
- Go to the profile_path/event/application directory
for the profile defining the WebSphere ESB runtime environment
where you want to configure default messaging. (Replace profile_path with
the path to the directory containing the WebSphere ESB profile.)
- Run the default-event-message.jacl script using the wsadmin command:
- Windows systems
profile_path\bin\wsadmin [conntype -none] -profile event-profile.jacl
-f default-event-message.jacl -action action -earfile event-message.ear
-node node_name -server server_name
[-cluster cluster_name] [-appname app_name] [-trace]
- Linux and UNIX systems
profile_path/bin/wsadmin.sh [conntype -none] -profile event-profile.jacl
-f default-event-message.jacl -action install -earfile event-message.ear
-node node_name -server server_name
[-cluster cluster_name] [-appname app_name] [-trace]
The parameters are as follows:
- node_name
- The WebSphere ESB 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.
- cluster_name
- The WebSphere cluster into which you want to deploy the messaging application.
Specify this parameter only if you are configuring messaging in a cluster
and you are not specifying a node and server.
Note: The default messaging configuration
uses a Cloudscape event database. The Cloudscape database does not support
clustering in a production environment. You can use the WebSphere Process
Server administrative console to specify a different messaging engine, specifying
a data source that connects to an event database that supports multiple connections.
- app_name
- The name to use for the messaging enterprise application. This parameter
is optional; the default value is EventServerMdb.
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.