1. Orchestrator Guide for Studio Version 8 and Prior
  2. Creating an Orchestration

Creating an Orchestration

> tutorial: See the following tutorials on how to create an orchestration:Creating and Testing an OrchestrationCreating an Orchestration with Multiple Components

To create an orchestration:

  1. On the Orchestrator Studio Home page, click the Orchestrations icon.

  2. On the Orchestrations page, click the New Orchestration button.

  3. On the Orchestration design page, enter a unique name for the orchestration in the Orchestration field. Do NOT include special characters in the name.

    All orchestrations created in Orchestrator Studio 5.0.1 or higher are saved as version 2 orchestrations. You cannot change this value in the Orchestrator Version drop-down list. If you want to update a version 1 orchestration created in a previous version of the Orchestrator Studio, see Updating Version 1 Orchestrations to Version 2 Orchestrations.

    Note: When you save an orchestration, the orchestration name 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.

  4. Click the Product Code drop-down list to select a product code to associate with the orchestration.

    This gives an administrator the option to manage UDO security for orchestration components by product code.

  5. In the space provided, enter a short description with a maximum of 200 characters. This description appears below the orchestration name in the component list.

  6. Click the Edit Long Description button to provide more detail about the component.

    Use this field to describe the purpose of the orchestration and any details that differentiate the orchestration from other orchestrations that you create.

  7. Click the Input Format drop-down menu and select the appropriate format:

    • JDE Standard (default)

    • Oracle Cloud IoT

    • Generic

    See Supported Input Message Formats for more information about which input format to use.

  8. At this point, you can click Save before defining inputs or steps for the orchestration.

    The Orchestrator Studio saves the orchestration as a "Personal" UDO. Next, add inputs to the orchestration as described in Adding Inputs to an Orchestration.

You can also use the Save As button and rename an existing orchestration to create a new one.

Caution: If you use Save As to create a copy of an orchestration, only the orchestration is copied. The Orchestrator Studio does NOT create a copy of the components that are associated with the orchestration's steps. That is, both the original orchestration and the new orchestration use the same components that comprise the orchestration. Therefore, in the new orchestration, do NOT modify the components in any way that would break other orchestrations that use the same components.