IBM BJ0NJML Integration Guide - Page 240

Inbound Customization T Stop further processing of the transaction by throwing an exception In this case, the transaction remains in the queue to be retried. T Stop the message from being sent to the external system by throwing a skip_transaction exception In this case, the message is not saved in the system; the message is removed from the queue. T Log the transaction You identify the interface user exit class on the Enterprise Service tab in the Enterprise Services application. Enterprise Service Processing Class If you use a provided adapter, the enterprise service processing class contains the processing logic. You must implement your code in the first or second user exit. If you create an enterprise service, customization can be done in the enterprise service processing class by using the following method: public StructureData setDataIn(StructureData sData) This method can perform the following processes: T Validate data T Change external data by changing the ER record before it is mapped to the IR record and saved in the system T Stop further processing of the transaction throwing an exception. In this case the transaction remains in the queue to be retried T Stop the message from being processed into the system by throwing skip_transaction exception In this case, the message is not saved in the system; the message is removed from the queue. T Log the transaction You identify the interface processing class on the Enterprise Service tab in the Enterprise Services application. User Exit Postprocessing In the second exit, both the IR and ER are available for processing. Inbound transaction customization can be done in the second exit using the following method: public StructureData setUserValueIn(StructureData irData, StructureData erData) 226 Integration Guide