This chapter contains the following topics:
Note:As an alternative to following the instructions in the chapter, you can use the createorchinstance Server Manager REST API to create the Orchestrator Studio instance. See REST API for Server Manager guide.
Important:Support for deploying the EnterpriseOne Orchestrator Studio with Server Manager starts with the 126.96.36.199 Tools Release for Server Manager and Orchestrator Studio version 5.0.0.
The JD Edwards EnterpriseOne Orchestrator Studio was built with Oracle Application Development Framework (ADF). Applications built with Oracle ADF must be deployed on an Oracle WebLogic Server with ADF runtime, hereafter referred to as an ADF Server.
This chapter describes how to use Server Manager to install the EnterpriseOne Orchestrator Studio on an ADF Server instance.
You cannot deploy the EnterpriseOne Orchestrator Studio on the same ADF Server instance used for running other EnterpriseOne ADF applications. When you install the Orchestrator Studio through Server Manager, the steps include deploying an ADF Server instance for running the Orchestrator Studio.
Note:This document covers installations for Oracle WebLogic Server version 12c (also known as 12.1.3 and 12.2.x). Follow the Oracle Certifications to determine which version is supported for your particular environment.
Installing the EnterpriseOne Orchestrator Studio 5.0.0 or higher through Server Manager requires the following prerequisites:
A minimum of:
EnterpriseOne Tools 188.8.131.52 to support Orchestrator Studio 5.x.0.
EnterpriseOne Tools 9.2.2 to support Orchestrator Studio 6.0.1.
EnterpriseOne Tools 184.108.40.206 to support Orchestrator Studio 6.1.0.
EnterpriseOne Tools 9.2.3 to support Orchestrator Studio 7.x.0.
An EnterpriseOne Application Interface Services (AIS) Server configured with an EnterpriseOne HTML Server. See Create an Application Interface Services (AIS) Server as a New Managed Instance for more information.
You can use an existing AIS Server or deploy a new AIS Server instance through Server Manager for the sole purpose of running orchestrations. It is recommended that you set up two AIS Server instances for an Orchestrator configuration, one for testing orchestrations and one for production.
For an AIS Server deployed on Oracle WebLogic Server, there is an additional required configuration that enables the Orchestrator Client (the tool for testing orchestrations) to run properly. See "Configuring Oracle WebLogic Server Domain for HTTP Basic Authentication" in the JD Edwards EnterpriseOne Application Interface Services Server Reference Guide.
An Oracle Fusion Middleware WebLogic Server with ADF runtime installed.
For Oracle WebLogic Server 12.1.3, you have to install Oracle WebLogic Server and then configure it with the runtime libraries for Oracle ADF. For instructions on how to install Oracle WebLogic Server with ADF Runtime, see "Setting Up Oracle WebLogic Server with ADF Runtime" in the JD Edwards EnterpriseOne Tools Deploying and Developing Oracle Application Development Framework (ADF) Applications for EnterpriseOne Guide.
If using Oracle Fusion Middleware Infrastructure 220.127.116.11 to install Oracle WebLogic Server, it comes preconfigured to support ADF applications; the additional configuration of ADF runtime libraries is not required. Oracle Fusion Middleware Infrastructure also provides an option to install Oracle WebLogic Server separately, which after installing, requires configuring it with the runtime libraries for Oracle ADF.
A Management Agent installed on the target machine where Oracle WebLogic Server resides.
The Oracle WebLogic Server registered with the Server Manager Management Agent.
A J2EE Container installed in this domain. See Install JDBC Drivers to the J2EE Server (WLS or WAS).
The Orchestrator Components download contains files for deploying the EnterpriseOne Orchestrator Studio.
Access the Oracle Update Center.
In the Type field, select EnterpriseOne Orchestrator, and then make sure that All Releases is selected in the Release field.
Download the Orchestrator Components file, making sure the version is supported with your EnterpriseOne Tools release.
The download contains additional files that are not needed for the Orchestrator Studio installation. The additional files are for developing custom Java for orchestrations. See "API and JAR Files for Developing Custom Java for Orchestrations" in the JD Edwards EnterpriseOne Tools Orchestrator Guide.
To install an Orchestrator Studio instance using the Server Manager Console:
In the Managed Software Components window of the Server Manager Console, click Choose File, select the Orchestrator Components file downloaded from the Update Center and click Open.
Verify that the EnterpriseOne Orchestrator components are uploaded as shown in the following example. Select the Enterprise Orchestrator components, and then click Distribute.
In the Managed Software Components window, select required Managed Instances, and then click Distribute Software.
The Distributed EnterpriseOne Orchestrator Components will be available in the selected Server Manager Agent as shown in the following example.
To create a new EnterpriseOne Orchestrator instance, select EnterpriseOne Orchestrator Studio Server in the Deploy a New EnterpriseOne Web Component window.
On Create/Register a Managed Instance, Instance Properties, complete these fields:
Use the pull-down to select the Server Group to which you want this instance to belong.
Enter a unique name for the instance name.
Select the already created J2EE Container for creating the EnterpriseOne Studio Server Instance.
Enter the HTTP Port.
Select EnterpriseOne Orchestrator Studio Components available in the drop-down menu as required.
Propagate Application Interfaces Services
Select the value from the drop-down menu as required.
The Orchestrator Studio connects with a working AIS Server in order to function. In the CONFIGURATION section, enter the AIS Server Details, and then click Continue.
The Orchestrator Studio instance is created successfully as shown in the following example. You can start the EnterpriseOne Orchestrator Studio instance after it is created.
You can also modify the configuration entries after the installation is created successfully.
It is not required to install the Database JDBC Driver into the Orchestrator Studio instance since it does not connect to the EnterpriseOne Database directly.
After installing the Orchestrator Studio, you need to set up the Orchestrator Studio as described in the "Setting Up the Orchestrator Studio" section of the JD Edwards EnterpriseOne Tools Orchestrator Guide.