Configuring default event messaging

The default messaging configuration for asynchronous event transport uses the WebSphere Process Server 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:

To configure default messaging:

Steps for this task

  1. Go to the profile_path/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.)
  2. 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 Process Server node in which the messaging application is to be deployed. To determine the node name:
    1. Run the profile_path/bin/setupCmdLine script.
    2. 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.
    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.

Terms of use |

Last updated: Tue Feb 21 17:47:11 2006

(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)