2 Getting Started

This chapter describes how to access and get started with the Orchestrator Studio 9.2.4. It contains the following topics:

2.1 Certifications (Formerly Known as Minimum Technical Requirements)

Customers must install the supported platforms for the release, which can be found in the Certifications tab on My Oracle Support: https://support.oracle.com. For the EnterpriseOne Orchestrator Studio 9.2.4, refer to the certifications for the JD Edwards EnterpriseOne AIS Server product.

For more information about JD Edwards EnterpriseOne minimum technical requirements, see this document on My Oracle Support: JD Edwards EnterpriseOne Minimum Technical Requirements Reference (Doc ID 745831.1). The document is available here:

https://support.oracle.com/rs?type=doc&id=745831.1

Note:

Orchestrator Studio 9.2.4 is not supported on Internet Explorer (IE).

2.2 Prerequisites

Complete the following prerequisites:

  • You must be running a minimum of EnterpriseOne Tools Release 9.2.4.

    Always apply the latest EnterpriseOne Tools software update to use the latest available features.

  • Deploy the Application Interface Services (AIS) Server 9.2.4.0.

    The Orchestrator Studio 9.2.4 is deployed along with the AIS Server 9.2.4.0 and can be accessed by using the AIS Server URL. Therefore, the Orchestrator Studio 9.2.4 does not require any other set-up or installation steps. The JD Edwards EnterpriseOne Orchestrator Studio 9.2.4 is installed on AIS Server instance.

    You can use an existing AIS Server or deploy a new AIS Server 9.2.4.0 instance through the Server Manager for running the orchestrations. It is recommended that you set up two AIS Server instances for an Orchestrator configuration, one for testing orchestrations and one for production. See "Create an Application Interface Services (AIS) Server as a New Managed Instance" in the JD Edwards EnterpriseOne Tools Server Manager Guide.

    Make sure that the AIS Server is configured with your EnterpriseOne system.

    You should set up an additional HTML Server instance for processing AIS Server requests only. This is recommended so that the performance of the EnterpriseOne HTML Server that is used by EnterpriseOne web client users is not impacted by AIS Server requests. For more information, see "Additional EnterpriseOne HTML Server Instance for Processing AIS Requests" in the JD Edwards EnterpriseOne Application Interface Services Server Reference Guide.

    Note:

    You will not be able to login to the Orchestrator Studio 7.3 or previous versions with the Application Interface Services (AIS) Server 9.2.4.0 instance.

    You will be able to login to the Orchestrator Studio 8.0 with AIS 9.2.4.0, but you will be able to create only V2 orchestrations. Orchestrator Studio 8.0 is intended only for maintenance and migration.

  • Ensure that the Orchestration feature is enabled and that all related UDO security is set up properly.

    For more information, see:

  • Ensure that the EnterpriseOne HTML Server and AIS Server keystores are set so that both are using either the demo keystore or the same certificate.

    If you want to configure your own keystore, see "Configuring EnterpriseOne HTML Server for JSON Web Token (JWT) (9.2.3.2)" or "Configuring EnterpriseOne HTML Server for JSON Web Token (JWT) (9.2.0.5)" in the JD Edwards EnterpriseOne Tools Security Administration Guide.

  • Ensure that the HTML Server is configured as a trusted node for the Security Server.

    See "Setting Up JD Edwards EnterpriseOne Single Sign-On" in the JD Edwards EnterpriseOne Tools Security Administration Guide.

Note:

Orchestrator Studio 9.2.4 is the latest version which requires a minimum of EnterpriseOne Tools 9.2.4. For instructions about implementing the prior versions of the Orchestrator Studio, see Chapter 2, "Implementing the Orchestrator Studio" in the JD Edwards EnterpriseOne Orchestrator Guide for Studio Version 8 and Prior.

2.3 Before You Begin

Orchestrator Studio 9.2.4 access requires a separate sign-in with a valid EnterpriseOne user ID and password. Before users can sign in to Orchestrator Studio 9.2.4, an administrator must add each EnterpriseOne user as an allowed user in Work With User/Role Security. See Managing Orchestrator Studio Security in this guide.

Also, orchestrations and orchestration components created in the Orchestrator Studio are saved and managed as user defined objects (UDOs) in EnterpriseOne. Therefore, an administrator must set up Orchestrator Studio users with the proper UDO security to access and use the Orchestrator Studio.

2.4 Accessing the Orchestrator Studio

To access the Orchestrator Studio 9.2.4:

  1. In a web browser, enter the URL to the Orchestrator Studio:

    http://<ais_server>:<port>/studio

    Note:

    Orchestrator Studio 9.2.4 is not supported on Internet Explorer (IE).
  2. On the Orchestrator Studio Sign In screen, enter your EnterpriseOne user credentials, environment, and role.

    Note:

    It is highly recommended that you enter an EnterpriseOne environment that is used for testing, not a production environment.
  3. Click the Login button.

2.5 Set Up a Temporary Directory on the AIS Server for File Transfers

In the Orchestrator Studio, you can create a connector service request to transfer files in and out of EnterpriseOne. When the Orchestrator executes this type of service request, as part of the process, files are saved to a temporary directory on the AIS Server. You must use Server Manager to set up this directory. In Server Manager, access the basic configuration settings for the AIS Server, and use the Temporary Directory setting to establish this directory.