Use 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 WAS.

Subtopics

• Use JMS to connect to a WAS default messaging provider messaging engine
  The Thin Client for JMS with WAS is an embeddable technology that provides Java Message Service (JMS) V1.1 connections to a WAS default messaging provider messaging engine.
• Secure JMS client and JMS resource adapter connections
  There are two approaches to configuring SSL for the Thin Client for JMS with WAS and the Resource Adapter for JMS with WAS. 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.
• Add tracing and logging for stand-alone clients
  We can add tracing and logging to help analyze performance and diagnose problems.

Example: Programmatically configuring a resource for the default messaging provider