The Java Messaging
Service (JMS) replaces the IBM® WebSphere® dynamic cache event
notification mechanism, which was used in previous versions of WebSphere. Perform these steps
after you have installed and registered the Sametime® Gateway Server
or Sametime Gateway
clusters.
About this task
If you are using a single server, set up JMS on the WebSphere Server on which
the Sametime Gateway
Server runs. If you are using a clustered environment, set up JMS
on the deployment manager. You begin by creating the service integration
bus, which is the virtual place where messages are exchanged. Use
these steps to run the script to set JMS provider properties:Procedure
- Restart the server or cluster.
For a single
server deployment, restart the server.
For a clustered deployment,
restart the Sametime Gateway
cluster environment rather than each Gateway Server.
- On the Gateway Server, navigate to the profile_root/bin directory.
For a single server deployment, the directory is was_install_root/profiles/RTCGW_Profile/bin.
For
a clustered deployment, the directory is was_install_root/profiles/DM_Profile/bin.
- Copy the gw_config_jms.py and gw_jms_tuning.properties files
from the Sametime Gateway
Server installation image in the postInstall directory
to the /bin directory.
- Run the wsadmin script.
AIX® and Linux
./wsadmin.sh
-username user -password password -lang
jython -f gw_config_jms.py gw_jms_tuning.properties
Windows
wsadmin.bat
-username user -password password -lang
jython -f gw_config_jms.py gw_jms_tuning.properties
- Restart the server or cluster.
For a single
server deployment, restart the server.
For a clustered deployment,
restart the Sametime Gateway
cluster environment rather than each Gateway Server.