We’re looking for guidance on configuring the MuleSoft JMS connector to read IBM MQ messages in raw binary format. This is to address a specific requirement where mainframe jobs are placing messages on MQ with RFH2 headers.
The default IBM MQ connector attempts to parse these messages and fails due to the presence of the RFH2 headers. Based on our research and MuleSoft documentation, one of the recommended approaches is to use the JMS connector instead of the IBM MQ connector, or alternatively, implement a custom Java class to handle the message payloads correctly.
Has anyone encountered a similar scenario and successfully configured the JMS connector to handle such messages without parsing errors? Any code snippets, configuration tips, or guidance on handling RFH2 headers with MuleSoft would be greatly appreciated.
#Trailhead Challenges