Configuring SOAP-JMS Messaging
Before you create a virtual service that uses JMS as its entry protocol or routing protocol, you must configure SOAP-JMS messaging on your system, as follows:
1. Configure and provide access to an external JMS service provider. You can use webMethods Broker to act as a JMS provider. Alternatively, you can use a third-party JMS provider or an open source JMS provider.
2. Use the JMS service provider to create request and response queues. For more information, see the documentation for your JMS service provider.
3. Specify the JMS client libraries in the Integration Server classpath so that Mediator is able to communicate with the JMS service provider.
4. Create one or more JNDI provider aliases to specify where Integration Server can look up administered objects when it needs create a connection to JMS provider or specify a destination for sending or receiving messages. For more information, see webMethods Integration Server Administrator’s Guide.
5. Create one or more connection aliases that encapsulate the properties that Integration Server needs to create a connection with the JMS provider. For more information, see webMethods Integration Server Administrator’s Guide
For this step, it is helpful to modify the default alias provided with Integration Server, DEFAULT_IS_JMS_CONNECTION, to work with your JMS service provider.