If you want to use WebSphere® Application Server default
messaging as the JMS provider for the event runtime, and you either
did not select the JMS provider or you selected WebSphere MQ when
you created or augmented the Decision Server Events profile,
you must do some additional configuration of WebSphere Application Server and Decision Server Events.
Before you begin
The event runtime can be configured to work with only one
JMS provider: either the
WebSphere Application Server default
messaging or
WebSphere MQ,
but not both.
The .sh and .bat files
referenced in this topic rely on settings in the setenv file.
Check and confirm your settings before doing the following steps.
For more information, see Editing the setenv files.
Procedure
- If, when you created or augmented the Decision Server Events profile,
you chose to use WebSphere MQ but
now you want to use WebSphere Application Server default
messaging as the JMS provider instead, you must remove the configuration
that was done by the profile:
Table 1. Command
to remove the configuration| Operating system |
Location in which you
must run the command |
Commands |
|---|
| Windows |
<InstallDir>\config\was\ |
configure_MQ_JMS_Messaging.bat
-undo |
| Linux and UNIX |
<InstallDir>/config/was/ |
configure_MQ_JMS_Messaging.sh
-undo |
If, when you created or augmented the Decision Server Events profile,
you did not select the JMS provider, you do not need to do this step.
- To complete configuration of WebSphere Application Server default
messaging as the JMS provider, run the following commands:
Table 2. Command to complete the configuration| Operating system |
Location in which you
must run the command |
Commands |
|---|
| Windows |
<InstallDir>\config\was\ |
configure_bus.bat configure_messaging.bat
|
| Linux and UNIX |
<InstallDir>/config/was/ |
configure_bus.sh configure_messaging.sh
|
The configure_bus.sh script configures
the service integration bus, WbeBus. If application server administrative
security is enabled, the bus is secured. To disable bus security,
supply the optional argument, -disableBusSecurity.
If
the service integration bus is secured, you must specify two arguments
for the
configure_messaging.bat (or
configure_messaging.sh)
script, to supply the user ID and password that the activation specifications
use to connect to the secured bus. For example:
configure_messaging.bat <user_id> <password>
or
configure_messaging.sh <user_id> <password>
If
security is not enabled for the service integration bus, do not specify
a user ID or password. For more information, see
Securing the service integration bus.
- Restart WebSphere Application Server.