Orchestrating Using Quick Start Mode

To orchestrate a Quick Start deployment plan:

1. On Welcome to the JD Edwards Provisioning Console, click the Orchestrate icon.
   
   

   

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



3. On the Private Key input for VM access dialog box, you must either specify 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.
   
   Note: Ensure the uploaded file is in the legacy .openssh format which is supported in One-Click Provisioning. For Example: OCI_Instance.openssh.

Important: The private key in the legacy .openssh format starts with -----BEGIN RSA PRIVATE KEY----- and ends with -----END RSA PRIVATE KEY-----. While the new format starts with -----BEGIN OPENSSH PRIVATE KEY----- and ends with -----END OPENSSH PRIVATE KEY-----.
   
   To browse and select the file, select the SSH Private Key File option and then click the Choose File button. For more information regarding SSH Keys, refer to the OBE "Generating Secure SHell (SSH) Key Pairs on Your Local System."
   
   Important: Ensure that the SSH Private Key Text field is not blank. The One-Click Provisioning Console validates the private keys and you cannot save the Global Settings if this field is blank.

   

4. Browse and select the appropriate file, and then click OK.
   
   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.

   

5. Click the Close button.
6. 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 administrative privileges.
   
   Important: You must enter the same password for this Windows Server that you previously specified in the OBE "Logging in to the Windows VM" of this Learning Path.
   
7. 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, 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 a tooltip 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 record these values in the Preinstallation Worksheet.
8. Click the Save button to exit the Global Settings screen.
9. On the Choose your Orchestration Template window, click the Quick Start icon to create your Quick Start JD Edwards Deployment Plan.
   
   Note: Refer to the applicable OBEs of this Learning Path for instructions on using the Advanced mode, and Export and Import orchestration functions.

 

10. On Database Server Instance page, complete these fields to create and configure the Database Server instance.
    
    Server Configuration
    
    • Database Server Type
      The Database Server Type is populated by default as Oracle Database.
    • ATP-D
      You should only enable the ATP-D option if you are using an Oracle Autonomous Database Dedicated; this database is only supported in Oracle Cloud Infrastructure. This functionality is described in the Learning Path "Deploying JD Edwards EnterpriseOne on Oracle Cloud Infrastructure on Linux with Autonomous Database."
      
    • Platform
      This field is disabled and it is automatically populated as Linux.
    • Instance Name
      Create an instance name for your database instance.
    • Host Name
      Enter the host name.
    Database Configuration
    • DB Install Path
      Enter the DB installation path.
    • DB Admin Password
      Enter the password of the database administrator.
    • Net Service Name
      Enter the net service name.
    JD Edwards Database Configuration
    • Use ASM feature
      Enable this option if you are using RAC DB as your Database Server.
      
      If you disable ASM in your Orchestration, you must enter valid values for the install, table, and index directories for your Oracle database. For example:
      
      
      • /u01/DataDB
        
      • /u01/ORATABLE
      • /u01/ORAINDEX
      
      If you enable ASM in your Orchestration, you must enter valid values for your DISK group. By default the values for  are assumed to be DATA. Otherwise, you can enter any other name that you have created. An example screen is shown below as Database Server Instance - ASM Enabled.
    • JDE DB Install Directory
      Enter the installation path.
      
      Path Rules. All directories in the specified path must preexist, except the last directory in the path. Therefore you must manually create the directory structure except for the last directory, which the Provisioning Server deployment process creates. For example, if you specify /u01/ORCL/INSTALL, the /u01/ORCL directory must preexist and the Provisioning Server deployment creates the /INSTALL directory.
      
      
    • JDE DB Table Directory
      Enter the path to install the table data.
      
      Path Rules: All directories in the specified path must preexist, except the last directory in the path. Therefore you must manually create the directory structure except for the last directory, which the Provisioning Server deployment process creates. For example, if you specify /u02/ORCL/TABLE, the /u02/ORCL directory must preexist and the Provisioning Server deployment creates the /TABLE directory.
      
      
    • JDE DB Index Directory
      Enter the path to install the indexes.
      
      Path Rules: All directories in the specified path must preexist, except the last directory in the path. Therefore you must manually create the directory structure except for the last directory, which the Provisioning Server deployment process creates. For example, if you specify /u03/ORCL/INDEX, the /u03/ORCL directory must preexist and the Provisioning Server deployment creates the /INDEX directory.
      
      
    • Schemas
      Click the Schemas field and select the schemas you want from the auto-suggest text. The schemas available are: Shared, Development, Prototype, Production, and Pristine with Demo data.
      
      Note: It is mandatory to add the Shared schema.
      
      Important: At this point, you should ensure that you specify all the schemas you might plan to use. The schemas you choose to install on the Database Server can only be deployed once, which is specified at this point in the Provisioning Console. You can use the Provisioning Console to programmatically add additional schemas after  deploying the orchestration.
      
    • Demo Data
      Click the Demo Data field and select the demo data from the auto-suggest text. Demo data is available depending on the schema selected. For example, if you select the schema as Development, the Development demo data will be available.





11. Click the Next button. Because you will be connecting to an existing Oracle Cloud Infrastructure Service database instance, the system validates all the input that you provide. If the validation is successful, the JD Edwards  Enterprise Server page is displayed.
12. On Enterprise Server Instance page, complete these fields to create and configure the Enterprise Server instance.
    
    Server Configuration
    • Platform
      This field is disabled and it is automatically populated as Linux.
    • Instance Name
      Create an instance name for the Enterprise Server. The conditions to set the instance name is 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.



13. Click the Next button. Because you will be connecting to an existing Oracle Cloud Infrastructure Service EnterpriseOne instance, the system validates all the input that you provide. If the validation is successful, the JD Edwards HTML Server page is displayed.
14. On the HTML Server Instance page, complete these fields to create and configure the HTML Server instance.
    
    Server Configuration
    • Platform
      This field is disabled and it is automatically populated as Linux.
    • Instance Name
      Create the instance name of the HTML Server instance.
    • Host Name
      Enter the host name.
    • Port
      Enter a unique (available) port number for this server that will use an SSL connection. This port number must be between 1024 and 65535. This port number is used by HTTPS to create a container and deploy the web component. Ensure the availability of a port that is one less than the port number that you enter here. That is, if you specify port 8081, you must also ensure that port 8080 is available.
      
      Important: For each SSL port that you open in the firewall, you must also open a companion port for non-SSL access required for Server Manager. The numeric value for the companion port must be one less than the value specified for the SSL port. For example, if you specify a port value of 8081 for SSL, in the firewall you must also open a port one less than that value; in this case you must open port 8080. Refer to the section "Enable Inbound Ports in the Firewall for Compute Instances" in the OBE "Performing Common Setup for All Linux Servers" of this Learning Path.
      
    Web Server Preferences
    
    • Pathcode
      Select the required pathcode from the drop-down menu.
    Important: Using the Quick Start mode, you can specify only a dedicated HTML Server for AIS. If you want to create a standard HTML Server, which is strongly recommended for Production environments, you must use the Advanced Deployment mode. For a description of each HTML Server type, refer to the OBE "Fundamentals" of this Learning Path.
    
    Important: Each dedicated HTML Server and AIS Server pair can support only one pathcode. If you want additional HTML instances to support additional pathcodes, you must configure additional HTML Server pairs using the Advanced deployment mode of the Provisioning Console. For more information, refer to the OBE "Orchestrating Using Advanced Mode" of this Learning Path.
    WebLogic Details
    • User Name
      Enter the user name.
    • Password
      Enter the WebLogic Server password.
    • Admin Port
      Enter the port number to access the WebLogic Administration Console.
    • Install Path
      Enter the installation path of the WebLogic instance.
    • JDK Install Path
      Enter the JDK installation path.

    

15. Click the Next button. The system validates the input. If the validation is successful, the AIS Server Instance page is displayed.
16. On AIS Server Instance page, complete these fields to configure your AIS Server instance.
    
    Same as HTML Server
    This option is selected by default. You cannot deselect it because this AIS Server must be paired with the dedicated HTML Server that you configured in the preceding step.
    
    Server Configuration
    
    • Platform
      This field is disabled and it is automatically populated as Linux.
    • Instance Name
      Create an instance name for the WebLogic Server.
    • Host Name
      Enter the host name.
    • Port
      Enter a unique (available) port number for this server that will use an SSL connection. This port number must be between 1024 and 65535. This port number is used by HTTPS to create a container and deploy the web component. Ensure the availability of a port that is one less than the port number that you enter here. That is, if you specify port 8081, you must also ensure that port 8080 is available.
      
      Important: For each SSL port that you open in the firewall, you must also open a companion port for non-SSL access required for Server Manager. The numeric value for the companion port must be one less than the value specified for the SSL port. For example, if you specify a port value of 8081 for SSL, in the firewall you must also open a port one less than that value; in this case you must open port 8080. Refer to the section "Enable Inbound Ports in the Firewall for Compute Instances" in the OBE "Performing Common Setup for All Linux Servers" of this Learning Path.
      
      
    Web Server Preferences
    
    • Type
      This field is disabled and is automatically populated as AIS Server.
    • HTML Server Instance
      Select the instance of the previously defined dedicated HTML Server from the drop-down menu.
    
    WebLogic Details
    • User Name
      Enter the user name.
    • Password
      Enter the WebLogic password.
    • Admin Port
      Enter the admin port number.
    • Install Path
      Enter the installation path of the WebLogic instance.
    • JDK Install Path
      Enter the JDK installation path.

    

17. Click the Next button. The system validates the input. If the validation is successful, the JD Edwards Deployment Server page is displayed.
18. On JD Edwards Deployment Server page, complete these fields to create and configure your Deployment Server instance.
    
    Server Configuration
    • Instance Name
      Create a name for the Deployment Server instance. The conditions to set the instance name is displayed in the tooltip when you click the field.
    • Host Name
      Enter the host name.
    • Windows User
      Enter the name of the Windows user.
    • Windows Password
      Enter the password of the Windows user.
    Deployment Server Preferences
    • Location
      Enter the location.
      
      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).
      
    • Installation Drive
      Enter the drive for the installation.
    • Pathcodes
      This field is automatically populated.



19. Click the Finish button.
    

    
20. Click OK in the success message window.
21. The summary window is displayed. In the summary window, you can see that one instance is created for each of the servers. Click the Back button to proceed to deploy your services as described in  the OBE "Deploying an Orchestration" of this Learning Path.

     

Note: You can click Options in the menu bar and then select the menu item to change your Global Settings or to reset your settings (that is, delete your configuration details, global settings, and orchestration data). Also optionally, you can further customize a completed Quick Start Deployment Plan using the Advanced deployment function of the JD Edwards Provisioning Console. For more information, refer to the OBE "Orchestrating Using Advanced Mode" of this Learning Path.