From DeveloperWorks, Securing JMS connections to WebSphere Enterprise Service Bus V6.1

Security is an integral part of SOA, and since WebSphere ESB is at the heart of many SOA solutions, the security of a WebSphere ESB server and its transports is vital to the enterprise systems that use it. Messaging, such as the JMS implementation provided by WebSphere ESB, is particularly important for business applications because of its reliability, performance, and asynchronous nature. This article shows you how to implement security with an example using WebSphere ESB V6.1 and a J2EE client container application communicating via JMS messaging.

Securing the messaging engine is a task that most customers need to do but documentation of all the steps was hard to come by. This article puts them to light to make the entire process easier.

Related Posts

• WebSphere Application Server: High Availability to JMS Clients?
• WebSphere Integration Developer & WebSphere Process Server v6.1.2 released
• Web services with SOAP/JMS in IBM WebSphere Process Server
• Make SOA real with IBM WebSphere Enterprise Service Bus and IBM WebSphere DataPower SOA Appliances
• WebSphere Enterprise Service Bus – Mediation Flow Component: No Refactoring for WSDL Faults

You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.