User exits are points at which customers or partners can link their own Java code into predefined product operations. In Sterling B2B Integrator and Sterling File Gateway, the mailbox component exposes user exits that are hooked into message add, message delete and message extract operations, and these were introduced during the 5.2 release stream. A class that implements the relevant Java interface is registered in MailboxUserExits.xml in the properties directory, under the matching user exit bean. The code then runs whenever a message is placed in a mailbox through the Mailbox Add service. This lets an implementer add custom logic such as allowing or blocking file extensions, checking file names or upload times, or starting a business process immediately when a message arrives instead of waiting for the scheduled routing rule evaluation. The WebSphereMQ Suite Put Service and the JMS Send Service are transport services that hand messages to external queues. They do not expose a comparable user exit hook. The Message Add Service is also not the documented user exit point, so the Mailbox Add Service is the correct choice.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit