The event server enterprise application must be deployed in each
WebSphere runtime environment where the profile has been augmented to use
the Common Event Infrastructure.
Why and when to perform this task
The event server enterprise application is packaged in the event-application.ear
EAR file. The event-application.jacl script installs this application
in the WebSphere ESB.
Steps for this task
- Go to the profile_path/event/application directory
for the profile defining the WebSphere Application Server runtime environment
where you want to deploy the application. (Replace profile_path with
the path to the directory containing the WebSphere Application Server profile.)
- Run the event-application.jacl script using the wsadmin command:
- Windows systems
profile_path\bin\wsadmin [-conntype none] -profile event-profile.jacl
-f event-application.jacl -action action -earfile event-application.ear
-backendid backend_id -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 event-application.jacl -action action -earfile event-application.ear
-backendid backend_id -node node_name -server server_name
[-cluster cluster_name] [-appname app_name] [-trace]
The parameters are as follows:
- action
- The action to perform. To install the enterprise application, specify install.
To update an existing event server application that is already installed,
specify update. During an update, the script makes a backup
copy of the existing application EAR file in the current directory; if necessary,
you can later use this backup copy to restore the previous version of the
application.
- backend_id
- The type of database back end to be used by the enterprise application.
This must be one of the following values:
- CLOUDSCAPE_V51_1
- DB2UDBNT_V82_1
- DB2UDBNT_V8_1
- ORACLE_V10_1
- ORACLE_V9_1
- DB2UDBOS390_V8_1
- DB2UDBOS390_V7_1
- node_name
- The WebSphere ESB node
in which the event server is to be deployed. To find out the node name, follow
these steps:
- 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 enterprise application
in a cluster, omit this parameter.
- server_name
- TheWebSphere server into which the event server enterprise application
is to be deployed. This value is case-sensitive. If you are deploying the
enterprise application in a cluster, omit this parameter.
- cluster_name
- The WebSphere cluster into which the event server enterprise application
is to be deployed. Specify this parameter only if you are deploying the application
in a cluster and you are not specifying a node and server.
- app_name
- The name to use for the Common Event Infrastructure enterprise
application. This parameter is optional; the default value is CommonEventInfrastructureServer.
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-application.ear
file, make sure you use forward slashes (/) in the path, even on Windows systems.
- If you are deploying the application on a stand-alone node, specify the
optional -conntype none parameter to run wsadmin in
local mode.
For more information about the wsadmin utility, refer
to the WebSphere Application Server documentation.
Result
After the
event-application.jacl script completes, the Common
Event Infrastructure enterprise application is deployed in the specified server
or cluster. In a
WebSphere ESB Network
Deployment environment, if the application is already installed, the script
only adds the deployment information for the specified node and server.