Before You Begin

This 20-minute tutorial shows you how to edit an orchestration to handle errors during execution of an orchestration.

Background

In the JD Edwards EnterpriseOne Orchestrator Studio, you can set up error handling for individual orchestration steps. In an orchestration step, you can determine how the Orchestrator handles an error.
You need to account for possible errors within the steps that drive your orchestrations to be able to have predictable results.

What Do You Need?

• Orchestrator Studio 9.2.4 or higher deployed in a JD Edwards EnterpriseOne test environment with a minimum of EnterpriseOne Tools 9.2.4.
• Access to the Orchestrator Studio and permissions to create orchestration and service request components, which are managed as user defined objects (UDO) in EnterpriseOne.See “Managing Orchestrator Studio Security” in the JD Edwards EnterpriseOne Tools Orchestrator Studio Guide.
• Access to the Orchestrator Monitor application (P980060X), which is granted through EnterpriseOne application security.
• Created the Enter Sales Orders orchestration as described in the tutorial - Creating an Orchestration to Enter Sales Orders in EnterpriseOne.

Adding the Error Handling Option to an Orchestration to Handle Error Conditions

1. Access the Orchestrator Studio.
2. On the Orchestrator Studio Home page, click the Orchestrations icon.
3. On the side panel, locate and select the Enter Sales Orders orchestration.
4. On the Orchestration design page, click the Enter Sales Order form request in the orchestration flow and then click the Error Handling icon.
5. On the Error Handling dialog-box, enter the following in the User Defined Error Text field:
   Enter Sales Orders has finished in error.
6. Select Abort for the On Error option.

   

7. Click Save on the Orchestration design page.

Testing an Orchestration to Handle Error Conditions

1. Open the Orchestration design page for the Enter Sale Order orchestration.
2. Click the Start icon in the orchestration flow and then click the Run Orchestrations icon.
3. On the Run Orchestrations page, click Refresh Cache.
4. Enter the following data as inputs:
   • Business Unit = 35
   Note: Business Unit 35 is an invalid value for this environment resulting in an error.
   • Long Address Number = 4242
   • Quantity Ordered = 10
   • Item Number = 220
5. Click Run to execute the orchestration.
   The orchestration response should look like this:

   

   The orchestration should result in an error because an invalid Business Unit was entered as an input. The orchestration response indicates that the specified Business Unit is not set up. The response also displays the userDefinedErrorText, which is the error text added to the orchestration.
6.  Click Close.

Viewing Exceptions in Orchestrator Monitor

In this task, you can view detailed information of errors in the Orchestrator Monitor. You can drill down to specific instances to troubleshoot the cause of errors.Access the Orchestrator Studio

1. Access the Orchestrator Studio.
2. On the Orchestrator Studio Home page, click the Orchestrator Monitor icon.
3. Sign in to the Orchestrator Monitor with your assigned user ID.
   The Orchestrator Monitor opens to a graphical view of Exceptions displaying the orchestrations that have ended in error.
4. Click the Health tab.
   The gird displays record for all the orchestrations including the Enter Sales Orders orchestration. It displays the data about the successes and failures for that orchestration.

   

5. Expand the row to find additional performance details.

   

   The bar chart displays information about the last 10 instances that the orchestration was executed. The green bars display successful completions of the orchestration and the time in seconds it took to complete. The red bars display exceptions.
6. Click the Exceptions tab and then select the List option to view the specific entries where the orchestration failed.
7. Expand the row to view additional details about the specific error instance, including the Input JSON sent to the orchestration and any Exception Messages sent back from EnterpriseOne.

   

8. Click the Exception Message button to see a detailed error message from the EnterpriseOne application.

   

9. Click Input JSON to see the input that caused the orchestration to fail.
   From the error message and the input, a business analyst can notice that the Business Unit is providing invalid input to the orchestration.

   

Want to Learn More?

• Orchestrator Health and Exception Monitoring