Configuring the Java Message Service (JMS) Server
To pass events to Optimize, Trading Networks uses the JMS server such as Broker or Universal Messaging. By default, Optimize for B2B sends events to the default Integration Server JMS server instance. However, if you want to use a JMS Server other than the default Integration Server JMS provider instance, you must associate that JMS Server as described below. Using a different JMS Server ensures that when Optimize for B2B is processing large amounts of data for monitoring, it does not adversely affect the performance of the JMS Server that might also be processing information for other components.
To use a different JMS Server
Important:
webMethods Broker has been deprecated.
1. From Integration Server Administrator, select Settings > Extended.
2. Click Edit Extended Settings, and then add or update the properties as follows.
For
Broker(deprecated):
watt.server.optimize.jms.server.url=broker://localhost:6849/Broker #1 where Broker #1 is the name of the broker (deprecated) to which events will be passed.
For
Universal Messaging:
watt.server.optimize.jms.server.url=nsp://localhost:90003. Click Save Changes.
4. Restart Integration Server for the changes to take effect.
Optimize for B2B will now pass the events to the JMS server specified in the watt parameters.
For more information about working with extended configuration settings in the Integration Server, see webMethods Integration Server Administrator’s Guide.