Receiver link exception handling

For each asynchronous receiver node, enter exception parameters.

Exception handling can be configured for the following nodes:

Configuration properties

The following are the exception properties of the asynchronous receiver nodes:

Table 1. Receiver link exception handling properties
Property Description
Alert Type Enter the type of Alert being raised when an exception occurs. For example, you can enter the text OrderCreate.

This displays in the Alert console and can be used to filter particular type of alerts.

Alert Queue Name Select the name of the alert queue to which the exceptions are sent.
Suspend API Select this field if a suspendable exception is returned by an extended API, the message is retained in the queue and the execution restarts after the Suspend Wait Time interval.

For details regarding the exception to be thrown, see the YIFRestartableAPI interface in the Sterling Selling and Fulfillment Foundation: Javadocs.

Suspend Wait Time Enter the time to wait before attempting to reprocess the message.
Is Reprocessible Select this field if the message received from an asynchronous source (like a message queue or database) and the error XML must be saved in the exception console when an exception occurs.

Messages marked as Reprocessible can be corrected in the Exception Console and submitted for reprocessing.

Note: There will only be one reprocess-timer thread per integration server. The reprocess-timer thread will run with a sleep delay of ONE minute and will process 50 reprocessible records at a time.
Check for Prior Exception Select this filed to check for prior exceptions before the execution of the service. Choosing this option implies that prior to executing the service, a check is made to see if any related errors exist for the message. This check must be implemented externally through the YIFErrorSequenceUE user exit.
Note: This option is applicable only when all the related services are associated to the same server.
Exception Group Enter a group of related services where exceptions are linked. For example, two services for receiving modifications on an order from external systems.
Note: This option is applicable only when all the related services are associated to the same server.
Prior Errors User Exit Enter the class name that implements YIFErrorSequenceUE user exit for checking prior related errors for the message.
Exception References Tab
Exception Reference Name Enter the name of the exception reference. Saved in the ERROR_REFERENCE column of the YFS_REPROCESS_ERROR table to indicate as Name=Value. For example, NAME1.
Exception Reference Value Enter the associated Exception Reference value. These name value/pairs are stored in the ERROR_REFERENCE field in the YFS_REPROCES_ERROR table for querying purposes.

Can be set to be static. For example, entering ‘1234' results in the ERROR_REFERENCE field to be populated with NAME1=1234.

Can also be set for dynamically extraction from the message using the following syntax xml://<full path of the element from root>/@<attribute name>.

For example, to get the sales order number from the createOrder input XML, use xml://Order/@OrderNo. This results in the ERROR_REFERENCE field to be populated with NAME1=<value of attribute OrderNo in the XML>.