Populating MQ headers in WebSphere Enterprise Service Bus using a custom MQ SendExit
From the developerWorks archives
Date archived: January 3, 2017 | First published: June 13, 2012
The WebSphere MQ binding provided with WebSphere ESB and WebSphere Process Server enables communication between native MQ applications and a Service Component Architecture (SCA) environment. The WebSphere MQ bindings simplify the sending and receiving of MQ messages, but MQ header field cannot be populated with MQ bindings in WebSphere Integration Developer. This article shows you how to use a custom MQ SendExit to populate MQ headers required by native MQ applications, and includes sample code to set AppIdentityData in the MQ header.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.