Orchestrating Servers with the One-Click Provisioning Console

This section shows you how to orchestrate servers with the JD Edwards One-Click Provisioning Console.

After the infrastructure provisioning is completed, the JD Edwards Infrastructure Provisioning Console creates json files in this path:

/home/opc/JDERefArch_InfraProvisioning/E1InfraProvisionConsole/outputJson

The infraOutput.json file contains details about the production and non-production pathcodes as well as disaster recovery environment, if it was selected during infrastructure provisioning. This file also contains information about the public and private IP addresses and host name of the bastion and other provisioned instances.
The pdOrch.json file contains details of all the instances in the production environment, as well as disaster recovery environment, if it was selected during infrastructure provisioning. This file can be imported into the One-Click Provisioning Console.
The nonpdOrch.json file contains details of all the instances in the non-production environment. It is not possible to import this json file into the One-Click Provisioning Console. You can use the details in this file to orchestrate <import> the components manually in the One-Click Provisioning Console.

Prerequisite

You must have configured the administrator passwords for the WebLogic Server and the Server Manager Console in the Configure section of the JD Edwards One-Click Provisioning Console.

Orchestrating Servers with the One-Click Provisioning Console

Important: Instances for non-production environment are not automatically orchestrated on the One-Click Provisioning Console. Instead, you must manually orchestrate instances for non-production environments that were created through the Infrastructure Provisioning Console. For instructions, refer to the OBE "Orchestrating Using Advanced Mode" in this Learning Path.

You can get details of non-production environments that require manual orchestration at this location on the OpenTofu Staging Server: /home/opc/JDERefArch_InfraProvisioning/E1InfraProvisionConsole/outputJson/nonpdOrch.json

Use this procedure to edit orchestrated servers for production environments with the One-Click Provisioning Console:

On the JD Edwards Provisioning Console, select the Orchestrate tile.
If this is the first pass through a JD Edwards One-Click Provisioning orchestration, the following Global Settings screen will appear first. In the SSH Private Key section, click the View/Edit Private Key button.
On the pop-up window Private Key input for VM access, you must specify the values for either the SSH private key text, or browse and select the file that contains the SSH private key contents for accessing all the instances that are provisioned using this tool.
Select the SSH Private Key File option and then click the Choose File button. For more information regarding SSH keys, refer to the OBE "Generate Secure SHell (SSH) Key Pairs on Your Local System" of this Learning Path.

Important: Ensure that the SSH Private Key field is not empty. The One-Click Provisioning Console validates the private keys and it is not possible to save the Global Settings if this field is empty.
Browse and select the appropriate file, and then click OK. For example: OCI_Instance.openssh.
Note: If you click the View/Edit Private Key button again, you can see the Public Key for VM access window with the SSH Public key value in the SSH Public Key text field. To change the private key, click the Change button and provide the new value.
Click the Close button.
In the Windows Administrator Details section, enter the Windows user name and password. Ensure that the user name is entered as opc and that this user has the Administrator privileges.
Important: You must enter the same password for this Windows Server that you previously specified for the Deployment Server in the section of this OBE entitled: "Completing Configuration in the JD Edwards Infrastructure Provisioning Console" of this Learning Path.
In the Set EnterpriseOne Passwords section, enter and then confirm these passwords:
- JDE User Password Create the password for JD Edwards EnterpriseOne. In support of the long password functionality provided by JD Edwards Tools Release 9.2.4.5, the password must be between 12 and 30 characters. It can contain only alphanumeric characters, and can only include this special character: _ (underscore).
- Site Key Passphrase Enter the Passphrase for generating the Site Key. The Passphrase must start with a letter, end with an alphanumeric character, must be between 8 and 40 characters, and contain at least 2 uppercase letters, 2 lowercase letters, 2 numbers, and 2 underscore characters.
Tip: The conditions to set the passwords appear in the tooltip window when you click the fields.

Important: It is highly recommended that you keep a record of these critical passwords. If you have not already done so, you should ensure these values are recorded on the Pre-Install Worksheet.
Click the Save button to exit the Global Settings screen.
On Choose your Orchestration Template, click Advanced.
Click on Orchestrate to modify the JD Edwards Deployment Plan.
As shown above, the system displays a list of orchestrated servers with an error (red X icon) if any user input is required. To remedy, you must edit the instance.
Click on the orchestrated instance and click the Edit function.
For each orchestrated server enter the required inputs:
Database Server
- DB Admin Password
  Note: This password must be the same as the password you entered for the Database Server in the section of this Learning Path entitled: "Completing Configuration in the JD Edwards Infrastructure Provisioning Console".
- JDE DB Install Directory (for example, /u01/DataDB)
- JDE DB Table Directory (for example, /u01/ORATABLE)
- JDE DB Index Directory (for example, /u01/ORAINDEX)
  Note: These are example paths for when Use ASM feature is disabled. If Use ASM feature is enabled see the following document: E1: OCI: What Significance Does The 'Use ASM Feature' Option Have In One-click Provisioning? (Doc ID 2880000.1)
Enterprise Server
To configure the Enterprise Server, complete the following sections:
Server Configuration
- Platform
  This field is disabled and is automatically populated as Linux.
- Instance Name
  Create an instance name for the Enterprise Server. The conditions to set the instance name are displayed in the tooltip when you click the field.
- Host Name
  Enter the host name.
Enterprise Server Preferences
- Server Type
  Select one or both of the available server types for this Enterprise Server.
  Single Enterprise Server. If you are deploying only a single Enterprise Server, select both Logic and Batch as the server types.
  Multiple Enterprise Servers. If you are deploying multiple Enterprise Servers, at least one server must be specified as a Logic server for each pathcode. The other servers can be specified as Batch servers.
- Pathcodes
  Click the Available Pathcodes field and select the pathcodes required from the auto-suggest text. The four available pathcodes are: Development, Prototype, Pristine, and Production.
  Important: It is good practice to select pathcodes here that correlate to the schemas you selected for the Database Server. The Provisioning Console programmatically enforce this correlation. If you select pathcodes on the Enterprise Server that are a superset of the database schemas you selected, the Enterprise Server will not be able to access the data required to function correctly. In the Provisioning Console, the pathcodes that you specify at this point for installation on the Enterprise Server can be deployed only once. You can use the Provisioning Console to programmatically add additional schemas after deploying the orchestration.
- Oracle JDBC Driver Details
  This driver is required for connectivity between the Enterprise Server and the Oracle database server.
  Click the Browse button to select each of the required components for the Oracle JDBC driver. For example:
  - odbc8.jar
  - ons.jar
  - ucp.jar
  Note: Refer to Oracle Certifications for the version of the supported driver and associated components.
  - HA enabled
    Turn on this toggle button if you want to provision multiple Enterprise Servers on same pathcode using a virtual hostname.
Web Server
- WebLogic Password
  Note: This password must be the same as the password you entered for the WebLogic Server in the section of this Learning Path entitled: "Completing Configuration in the JD Edwards Infrastructure Provisioning Console".
- HA enabled Turn on this toggle button if you want to provision multiple Enterprise Servers on same pathcode using a virtual hostname.
  Add correct dependencies while orchestrating servers:
  - for htm4a1 instance, dependent server is logic1
  - for ais1 instance, dependent server is htm4a1
  - for htm1 instance, as it is standalone JAS server, you need to toggle button for standalone JAS and set dependent AIS server with ais1
Deployment Server
- Location
  Note: This value is the base location for your JD Edwards EnterpriseOne machines. For example, typical values might be a city name (such as Denver or Austin), a geographical region name (such as US or India), or a general location name (such as Corporate).
For each orchestrated server that you edit, save the instance details.
After you have finished editing and saving the instance details, click on the Back button at the top right of the form. Then you can proceed to the following section entitled: "Deploying an Orchestration".