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 WebSphere WebSocket Support Configuration (Release 9.2.4.3)

Starting with Tools Release 9.2.3.4, the Orchestrator Studio sends notifications during a session timeout. In the case of a timeout, you will be automatically redirected to the Orchestrator Studio login page. This session management functionality relies on the WebSocket technology.

When the Orchestrator Studio is deployed on WebSphere, you must enable the WebSocket functionality using the WebSphere WebSocket configuration.

You can observe the following symptoms if you have not used the WebSphere WebSocket configuration:

  • When you access the Orchestrator Studio using a web browser, the console will display the following error message:

    Figure 2-1 WebSocket Connection Error

    This image is described in surrounding text.
  • The notification that the user's session has timed out will not be displayed. The user will not be redirected to the login page when a session times out..

2.5.1 WebSphere Configuration

The WebSphere configuration involves the following two steps:

  1. Expose the back-end port of the AIS Server as a host alias when you configure virtual hosts for the application.

  2. Configure the "Address include list" or the "Hostname include list" option or both the options to restrict communication on the back-end port to only itself or the machine that is hosting the application.

After you complete these two configurations in the WebSphere console, you must bounce the AIS Server using the Server Manager console.

2.5.1.1 Configuring the Virtual Hosts

Finding the AIS Server Back-End Port

  1. Login to the WebSphere console.

  2. Navigate to Servers, Server Types, WebSphere application servers.

  3. Select the AIS server.

  4. Select the Ports.

    You can expand the drop-down list to see the ports or click on the option to view all the ports.

  5. Search for the WC_defaulthost port and make a note of the port.

    If you are using SSL, make a note of the WC_defaulthost_secure port.

Exposing the Back-End Ports as Virtual Hosts

  1. Navigate to Environment, VirtualHosts.

  2. Select the AIS server that you want to configure.

  3. Select Host Aliases.

  4. Click New.

  5. Enter * in the Host Name field.

  6. Enter the port number in the Port field.

    Repeat the steps 1-6 for the SSL or non-SSL port.

  7. Click Apply.

  8. Click Save to save the settings directly to the master configuration.

You will have two or three (if supporting SSL port also) ports listed. The following example displays the configuration for a non-SSL port:

Figure 2-2 Non-SSL Port Configuration

This image is described in surrounding text.

For information about configuring virtual hosts, see:

http://publib.boulder.ibm.com/httpserv/ihsdiag/plugin_questions.html#wsoc

2.5.1.2 Including the Address or Host Configuration

  1. Login to the WebSphere console.

  2. Navigate to Servers, Server Types, WebSphere application servers.

  3. Select the AIS server.

  4. Select Ports.

    You can expand the drop-down list to see the list of ports or click the option to view all the ports.

  5. Search for the WC_defaulthost or WC_defaulthost_secure port or both the ports depending on the port that you are using.

  6. Click the 'View associated transports' link in the last column.

  7. Click WCInboundDefault.

  8. Click TCP inbound channel (TCP 2).

  9. In the "Address include list" field, enter the IP address of the machine on which the AIS Server is deployed.

  10. Click Apply.

  11. Click Save to save the configurations directly to the master configuration.

    Figure 2-3 TCP Inbound Channel Configuration

    This image is described in surrounding text.

For information on configuring the Address or Host, see:

https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.multiplatform.doc/ae/urun_chain_typetcp.html

Important:

  • After you complete these configurations, you must ensure that you bounce the AIS server.

  • You have to reapply these configurations after every deployment of an AIS Server component from Server Manager.

2.6 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.