When a response from a network element is received that is mapped to a RETRY user-defined exit type (UDET), the Number of Retries value informs the system how many times the command should be retried before it is failed, and the Retry Time Interval is the amount of time between each retry.
As different network elements often have different retry requirements, it is necessary to provide a flexible retry mechanisms that enables retry properties to be specified at the network element instance level and at the atomic action level (this is in addition to the ability to configure a single set of system-wide retry properties, which apply to all atomic actions and all network elements that trigger a retry).
Flexible retry configuration in ASAP enables specification of retry properties in the following locations:
ASAP.cfg: This configuration file contains values for the Number of Retries and Retry Interval which will be used whenever a retry occurs, on any network element or atomic action, if no other values are configured elsewhere.
Work Order: If the Number of Retries and Retry Time Interval are specified on a work order, the values will override those defined elsewhere in the system (including the ASAP.cfg file, atomic action level, or network element instance level).
Atomic Action: If you specify the Number of Retries and Retry Interval at the atomic action level, if a retry is encountered on any of the action processors mapped to that atomic action, the values you specify will be used. These values will override those defined at the network element instance level and at the ASAP.cfg level.
Network Element Instance: If you specify the Number of Retries and Retry Interval on the Network Element editor, any command triggering a retry against this network element instance will use the retry values you specify. These values will override those defined at the ASAP.cfg level.
NE Template: If you specify the Number of Retries and Retry Interval on the NE Template editor, any network element created from the template will inherit the retry values you specify.
Dynamic NE Template: If you specify the Number of Retries and Retry Interval on the Dynamic NE Template editor, any network element instances dynamically created using the template will inherit the retry values you specify. These values will override those defined at the ASAP.cfg level.
Example 1: Configuring Retry Properties at the Network Element Instance Level
Example 2: Configuring Retry Properties at the Atomic Action Level
Understanding the Java Processor Class
Understanding Java with Code Generation