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.
Adding JMS or MQ/JMS Custom Header Attributes
If you need to add a custom header to your JMS (default messaging) or MQ/JMS message in WebSphere , you have two options. You can specify it as a custom header on the import component in the assembly diagram, or you can use a Medation Module. You can add the custom header property in the […]
Asynchronous SCA One-Way Operations And How To Recover
From DeveloperWorks, comes the succinctly titled: <deep breath> Recovering from failed asynchronous SCA service invocations on WebSphere Process Server article Imagine this common scenario. You have a mission-critical Service Component Architecture (SCA) application running on IBM® WebSphere® Process Server. A message is sent to this application to invoke an asynchronous service, however, service invocation fails. […]
JMS Function Selectors & Method Bindings
JMS Function Selectors and Method bindings are properties that you define inside of an SCA JMS component that answer the question “Which {component,interface} pair should a message arriving on a queue be delivered to?”. I had intended to go and write up in lay-mans terms what it all meant, but luckily (for me) I stumbled […]