Using JMS from stand-alone clients to interoperate
with service integration resources
The Thin Client for JMS with WebSphere® Application Server allows
third party applications to interoperate with default messaging provider
messaging engines on WebSphere Application Server.
Securing JMS client and JMS resource adapter connections
There are two approaches to configuring Secure Sockets
Layer (SSL) for the Thin Client for JMS with WebSphere Application Server and
the Resource Adapter for JMS with WebSphere Application Server. The global configuration
approach affects all stand-alone outbound connections from the process,
and the private approach applies only to client or resource adapter
connections from the process.
Last updated: April 18, 2014 05:01 AM CDT http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-iseries&topic=tjj_jms_thirdparty File name: tjj_jms_thirdparty.html