10 Testing Orchestrations in the EnterpriseOne Orchestrator Client

This chapter contains the following topics:

10.1 Understanding the Orchestrator Client

The EnterpriseOne Orchestrator Client is a web application for testing orchestrations. It is available with a deployed AIS Server and runs in a web browser. You can access the Orchestrator Client from the Orchestrator Studio. Oracle recommends that you use the Orchestrator Client with an EnterpriseOne test environment, as any tests performed result in EnterpriseOne transactions that add data to the database.

In the Orchestrator Client, you can test your personal orchestrations or shared orchestrations to which you have been granted access. When you select an orchestration to test, the Orchestrator Client displays the inputs defined for the orchestration in the Inputs area, where you enter values for the inputs and then run the test. As an alternative, the Orchestrator Client gives you the option to enter raw JSON code for the input.

Figure 10-1 shows an example of testing an orchestration designed to place a customer on credit hold, where customer number 3001 was entered for the Customer input:

Figure 10-1 JD Edwards EnterpriseOne Orchestrator Client

Description of Figure 10-1 follows
Description of ''Figure 10-1 JD Edwards EnterpriseOne Orchestrator Client''

The Orchestrator Client displays a green check mark if the orchestration completes successfully. The Input area displays the orchestration request in JSON, and the Output area displays the orchestration response in JSON. If the orchestration was unsuccessful, the Orchestrator Client displays an "x" symbol and the Output area displays the error in JSON.

To execute the test, the Orchestrator Client invokes the orchestration on the AIS Server, passing the test values to the orchestration and in turn to the orchestration's service request to perform a transaction in EnterpriseOne. The Orchestrator Client passes the request to the AIS Server in JSON format. The AIS Server provides a JSON over REST interface (HTTP), a light-weight interface that enables AIS clients to interact with EnterpriseOne applications and forms.

10.1.1 Using cURL to Simulate Testing from a Third-Party Application or IoT Device

As an alternative to testing orchestrations in the Orchestrator Client, you can simulate a test from third-party applications or IOT devices using cURL, an open source command-line tool for transferring data with URL syntax via various protocols, including HTTPS.

When an orchestration is saved in the Orchestrator Studio, the name of orchestration is used to define an endpoint on the AIS Server. The endpoint URL is:

http://<server>:<port>/jderest/orchestrator/<orchestrationname>

To invoke this orchestration, third-party applications or devices use a post operation to this url, where <orchestrationname> is the name of the orchestration. In the body of the post, pass the JSON string expected by the orchestration. You can find this JSON string in the Orchestrator Client, which displays the JSON string in the Input box when you test an orchestration.

10.2 Testing an Orchestration in the EnterpriseOne Orchestrator Client

To access the Orchestrator Client:

  1. On the Orchestrator Studio Home page, click the Tools link in the upper-right corner.

  2. On the Tools page, click the Orchestrator Client icon.

  3. On the Orchestrator Client Sign In screen, enter your EnterpriseOne User credentials, environment, and role.

    It is highly recommended that you enter an EnterpriseOne environment used for testing, not a production environment.

  4. Click the Login button.

To test an orchestration:

  1. In the Orchestrator Client, click the Orchestrator Name drop-down list and select an orchestration.

    The Orchestrator Client displays the inputs or name-value pairs in the Inputs area, which should be defined in the orchestration as the expected input to the orchestration. If the inputs do not appear, return to the Orchestrator Studio and define inputs for the orchestration before continuing.

  2. In the Value column, enter a value for each input.

    These are the values that the orchestration will pass to EnterpriseOne.

  3. If needed, you can click the add icon (plus symbol) to add and define additional inputs.

  4. Click the Generic Inputs check box if the orchestration uses the generic format for inputs.

    Leave it unchecked if the orchestration uses the standard JD Edwards EnterpriseOne format.

    For more information about input formats, see Supported Input Message Formats.

  5. Click Run to test the orchestration.

    The Input and Output areas show the orchestration input and response respectively in JSON format.

    If the test was successful, the Orchestrator Client displays a green check mark next to the Input and Output areas. If desired, you can access EnterpriseOne and confirm that the transaction was completed by the orchestration.

    If unsuccessful, the Orchestrator Client displays an "x" symbol and the Output area displays the error response in JSON format. If the orchestration fails, modify the orchestration and test it again. Make sure to click the XML Cache Refresh button to ensure the modified files are used in the next test.

    With EnterpriseOne Tools 9.2.3.4, you can use the Refresh Cache button on the Orchestrator Client page to access the components (such as service requests, orchestrations, and so on) those created outside of your current session. For the objects that were shared while the session is open, you will have to close it and sign in again to access the shared objects.

  6. To test another orchestration or start over, click the Clear button to reset the Orchestration Client, which clears all values in the form.

To use JSON input for the orchestration test:

  1. Click the JSON Input check box.

  2. Enter the input in JSON format directly in the Input area.

  3. Click the Format button to verify that the syntax of the JSON is correct.

    If not formatted correctly, a dialog box displays an error message about the JSON.

  4. Click Run to test the orchestration.