Setting Up Orchestration Error and Exception Tracking (Release 9.2.2.4)
In Server Manager, you can enable error and exception handling for orchestrations. When enabled, each exception in an orchestration is saved as a single serialized JSON object and stored in a directory on the AIS Server. In addition to storing these files, the directory serves as a buffer for storing orchestration requests if the EnterpriseOne system is down.
When an orchestration exception occurs, the AIS Server log states that the exception was saved to a file and provides the file location. For information on how to enable logging on the AIS Server, see Enable Debugging on the AIS Server.
The following list identifies the types of default errors and exceptions that can occur during orchestration processing:
JSON payload parse failure.
Any non 200 status response from the HTML Server, which includes connection failures and security errors.
Any non 200 status response from external REST calls (includes connection failures).
Any failure to connect to an external database.
Any failure to find orchestration components due to security errors.
Invalid orchestration inputs.
Invalid form service request, data request, or cross reference request due to failure to execute.
Cross reference or whitelist not found when an orchestration is terminated.
Any exception thrown from a Groovy script in a rule or service request.
In addition, you can specify error level handling for form service request responses when you set up exception handling in Server Manager.
To enable exception handling for orchestrations:
In Server Manager, under the Advanced configuration settings for the AIS Server, locate the General settings section.
In the General settings, click the Save Orchestration Exceptions check box.
This enables exception handling. If desired, perform the following steps to set up additional exception handling features.
In the "Full path to exceptions directory" fields, you can include a path to a directory on the AIS Server.
If you do not complete this field, files will be saved to a temporary directory on the AIS Server.
If you want to specify the level of error handling for form service requests, enter either or both of the following values in the Exception Scenario List field:
FSR_ERROREnter if you want errors returned by a form request to be handled as a failure.
FSR_WARNINGEnter if you want warnings returned by a form request to be handled as a failure. This level of error handling works only for form requests configured with the "Stop on Warnings" option selected in the Orchestrator Studio.