Provisioning a New Oracle E-Business Suite Installation on Oracle Cloud Infrastructure Classic Using the EBS Cloud Admin Tool


Options



Before You Begin

Purpose

In this tutorial, you will learn how to use the EBS Cloud Admin Tool, ProvisionEBS.pl, to create a new multi-node installation of Oracle E-Business Suite, Oracle Distributed Yard Management, or Oracle Distributed Warehouse Management.

The table below shows the choices available.

Products Available for Deployment Service Running Application Tier Service Running Database Tier
  • Oracle E- Business Suite Release 12.2.7 with the following: (see Footnote 1)
    • Oracle Database Release 12.1.0.2
  • Oracle E- Business Suite Release 12.2.6 with either of the following:
    • Oracle Database Release 12.1.0.2
    • Oracle Database Release 11.2.0.4
  • Oracle E-Business Suite Release 12.1.3 with either of the following:
    • Oracle Database Release 12.1.0.2
    • Oracle Database Release 11.2.0.4

Oracle Cloud Infrastructure Compute Classic

  • Oracle Cloud Infrastructure Compute Classic
    • Oracle Cloud Infrastructure Compute Classic only supports single-node (not Oracle RAC) databases
  • Oracle Database Cloud Service (DBCS)
    (see Footnote 2)
    • Oracle E-Business Suite Release 12.2:
      • 12.1.0.2 DBCS (single instance only)
      • 11.2.0.4
    • Oracle E-Business Suite Release 12.1.3
      • 11.2.0.4 (only)
    • Database edition options (see Footnote 3):
      • Enterprise Edition - General Purpose
      • Enterprise Edition - High Performance
      • Enterprise Edition - Extreme Performance (required for Oracle RAC option)
    • Billing options: hourly or monthly
  • Exadata Cloud Service (Exadata CS)
    (see Footnote 4)
    • Oracle E-Business Suite Release 12.2
      • 12.1.0.2
      • 11.2.0.4
    • Oracle E-Business Suite Release 12.1.3
      • 11.2.0.4 (only)

Oracle Distributed Yard Management 12.2 with Database 12.1.0.2

Oracle Cloud Infrastructure Compute Classic

Oracle Cloud Infrastructure Compute Classic

  • Oracle Cloud Infrastructure Compute Classic only supports single-node (not Oracle RAC) databases

Oracle Distributed Warehouse Management 12.2 with Database 12.1.0.2

Oracle Cloud Infrastructure Compute Classic

Oracle Cloud Infrastructure Compute Classic

  • Oracle Cloud Infrastructure Compute Classic only supports single-node (not Oracle RAC) databases

Footnote 1: If you plan to provision an Oracle E-Business Suite Release 12.2.7 environment, you must first ensure that your EBS Cloud Admin Tool is at Version 18.3.1. For information on updating your EBS Cloud Admin Tool to Version 18.3.1, refer to Oracle by Example tutorial Deploying the EBS Cloud Admin Tool to Oracle Cloud Infrastructure Classic.

Footnote 2: When placing your 12.1.0.2 or 11.2.0.4 database tier on DBCS single-instance, you will choose one of the following available Oracle E-Business Suite certified database patch set updates:

  • April 2018
  • January 2018
  • October 2017

Footnote 3: If you plan to use Oracle OLAP, Partitioning, and/or Spatial options for your custom code, you must choose "Database Enterprise Edition - High Performance" or "Database Enterprise Edition - Extreme Performance."

Footnote 4: When placing your 12.1.0.2 or 11.2.0.4 database tier on Exadata CS, you will choose the available Oracle E-Business Suite certified database bundle patch (January 2018).

Note: When used to create a new environment, the EBS Cloud Admin Tool provides the option to assign logical host names to your application tier nodes and to your database tier node when it is hosted on Oracle Cloud Infrastructure Compute Classic. For more information about the principles of using logical host names, refer to My Oracle Support Knowledge Document 1968231.1, Configuring Oracle E-Business Suite Release 12.x Using Logical Host Names.

Time to Complete

  • A minimum of 15 minutes to create the EBS Cloud Admin Tool virtual machine.
  • Additional time to provision your chosen Oracle E-Business Suite topology. This will vary with the number of nodes specified. Note that if the target database service is DBCS or Exadata CS, additional time is taken to encrypt all non-system tablespaces using Transparent Database Encryption (TDE).

What Do You Need?

To perform the steps in this tutorial, you must have:

  • An understanding of the relevant information in My Oracle Support Knowledge Document 2066260.1, Getting Started with Oracle E-Business Suite on Oracle Cloud.
  • Additional cloud service resources that match or exceed the following minimum requirements:
    Description of Requirements Number of Virtual Machines (VM) OCPUs Memory Storage External IPs

    Provisioning Virtual Machine (VM)

    1

    1

    7.5 GB

    20 GB (block)

    1

    Oracle Traffic Director (OTD) VM

    1

    1

    7.5 GB

    25 GB (block)

    1

    Application tier VM

    n (where 'n' is number of application tier nodes in the target environment)

    n*m (where 'm' is the number of OCPUs in the shape selected for the application tier; the minimum for 'm' is 1)

    15 GB per VM

    • Shared application tier: 170 GB + 40 GB for each additional application tier (block)
    • Non-shared application tier: 170 GB x n (block)
    • Per language: 16 GB (block)

    n

    Database Tier

    Oracle Cloud Infrastructure Compute Classic or DBCS single instance database

    1

    2

    15 GB

    Vision demo: 300 GB

    Fresh install: 150 GB

    1

    DBCS
    Oracle RAC

    2

    4 x 2

    15 GB x 2

    Vision demo: 650 GB

    Fresh install: 500 GB

    2

    Exadata CS
    Oracle RAC
    (See Footnote 1)

    2

    8 x 2

    240 GB x 2

    42 TB

    2

    Footnote 1: These are the minimum specifications provided by an Exadata CS Quarter Rack.

Process Overview

To create and configure a multi-node instance of Oracle E-Business Suite, Oracle Distributed Yard Management (DYMS), or Oracle Warehouse Management (DWMS) in Oracle Cloud Infrastructure Compute Classic, you must complete the following tasks in the order shown below:

  1. Deploy or update the EBS Cloud Admin Tool.
  2. Validate SSH connectivity to the EBS Cloud Admin Tool instance.
  3. Determine cloud service account details.
  4. Perform your installation.
  5. (Conditional) Implement workaround for Oracle Database 11.2.0.4 on DBCS RAC.
  6. Secure access to your environment.
  7. (Conditional) Enable Oracle OLAP, Partitioning, and Spatial options.
  8. Perform post-installation steps.

Deploying or Updating the EBS Cloud Admin Tool

If you have not done so previously, deploy the EBS Cloud Admin Tool to your Compute Classic domain by following the Oracle by Example tutorial Deploying the EBS Cloud Admin Tool to Oracle Cloud.

If you have already deployed the EBS Cloud Admin Tool, you must ensure it is on the latest codeline by following the instructions in section "Update EBS Cloud Admin Tool to Latest Codeline" of the Oracle by Example tutorial Deploying the EBS Cloud Admin Tool to Oracle Cloud.

Note: Only perform this procedure once per domain, as running the EBS Cloud Admin Tool from multiple VMs in the same domain can give undefined results and is not supported.

Record the following information for later use:

  • Names and locations of your public and private SSH keys, and your key passphrase.
  • The external IP address of your EBS Cloud Admin Tool instance.

Validating SSH Connectivity to EBS Cloud Admin Tool Instance

In order to validate SSH connectivity, log in to your EBS Cloud Admin Tool instance using SSH. You will need to remain logged on to the instance to perform subsequent operations.

For more information, refer to section "Connect to Your Oracle Cloud Instance Via SSH" in the Oracle by Example tutorial Common Tasks for Oracle E-Business Suite in Oracle Cloud Infrastructure Classic.

Determining Cloud Service Account Details

Before you can provision a new Oracle E-Business Suite installation using the EBS Cloud Admin Tool, you must determine account details required by the tool.

Refer to the "Determine Cloud Service Account Details" section in the Oracle by Example tutorial Common Tasks for Oracle E-Business Suite in Oracle Cloud Infrastructure Classic to identify and record the following for later use:

  • IDCS Global User ID (IDCS GUID) - Conditional
  • Oracle Cloud Infrastructure Compute Classic Service Instance ID - Required
  • Oracle Cloud Infrastructure Compute Classic REST endpoint - Required (Formerly known as the Oracle Compute Cloud Service REST endpoint)
  • Oracle Cloud Infrastructure Object Storage Classic REST endpoint - Required (Formerly known as the Oracle Storage Cloud Service REST endpoint)
  • Oracle Database Cloud Service REST endpoint - Conditional

Performing Your Installation

In this section, you will use the EBS Cloud Admin Tool to create either an Oracle E-Business Suite, an Oracle Distributed Yard Management, or an Oracle Distributed Warehouse Management environment with the desired topology. The application tier will run on Oracle Cloud Infrastructure Compute Classic and you have the option to run the database on the Oracle Cloud Infrastructure Compute Classic or Database Cloud Service (DBCS).

Perform the following steps.

  1. While logged on to the EBS Cloud Admin Tool instance (VM), switch from the opc user to the oracle user by running the following command:
  2. $ sudo su - oracle     
  3. Start the EBS Cloud Admin Tool by running the following command:
  4. $ perl /u01/install/APPS/apps-unlimited-ebs/ProvisionEBS.pl

    This will present a series of prompts that allows you to specify your installation topology or choose other actions.

    Note: If execution of ProvisionEBS.pl fails for any reason (such as a network timeout), you should re-run it. The script detects if a previous session failed, and will prompt the user whether to continue with that session.

    If you are unable to recover, delete the installation artifacts and free up your cloud resources by following the steps in "Cleaning Up After a Failed Provisioning" in the Managing Oracle E-Business Suite on Oracle Cloud Using the EBS Cloud Admin Tool Oracle by Example tutorial.

  5. On the first screen, choose option "1: Create New Environment."
    ===========================================
    Provision Oracle E-Business Suite - Options
    ===========================================
    
    Provision Oracle E-Business Suite - Enter Selection:
    1: Create New Environment
    2: Create Environment from Backup
    3: Manage Environments
    4: Administer Orchestration VM
    5: Manage Oracle Storage Cloud Service (OSCS) Backups
    6: Clean Up After a Failed Provisioning
    7: Exit
    
    Enter your choice from above list: 1
  6. Next, enter your cloud credentials, including the previously-obtained Cloud Service account details.
    The first time you run the tool, the screen will look similar to this (where your entries are to the right of the colon separator):
    ==================================================================
    Provision Oracle E-Business Suite - Enter Oracle Cloud Credentials
    ==================================================================
    
    [Ctrl-B: Back, Ctrl-H: Main Menu]
    
    Oracle Compute Cloud Service Endpoint                   : https://xxx.compute.us.oraclecloud.com
    Oracle Storage Cloud Service Endpoint                   : https://xxx.storage.oraclecloud.com/v1/Storage-xxx
    Oracle Cloud Compute Service Instance ID                : mycloudserviceid
    Oracle Cloud Identity Domain                            : myclouddomain
    Oracle Cloud Data Center Code (examples: em1, us2, ap3) : em1
    Oracle Cloud User Name                                  : john.smith@example.com
    Oracle Cloud Password                                   : <password>
     
    Validating Compute credentials. Please wait.

    On subsequent runs, the screen will show default values presented in brackets which coincide with values entered in the previous execution of the utility. If a response is left blank, the default value will be used.

    The REST endpoints are used to identify the location of services at the site level within a datacenter. These endpoints are required in order to create the security artifacts associated with Oracle Compute Cloud instances (VMs). If the provisioning VM is located at a different site from your application tier VM (identified by the Compute Classic endpoint), you will be prompted to provide the provisioning VM REST endpoint, as seen below:

    Enter Oracle Compute Cloud Service Endpoint for Provisioning VM :
  7. Next, select the Oracle E-Business Suite release and Oracle Database version for your new environment.
    ==============================================================
    Provision Oracle E-Business Suite - Choose Release Combination
    ==============================================================
    
    [Ctrl-B: Back, Ctrl-H: Main Menu]
    
    1: EBS 12.2.7 with Database 12.1.0.2 - Fresh
    2: EBS 12.2.7 with Database 12.1.0.2 - Demo
    3: EBS 12.2.6 with Database 12.1.0.2 - Fresh
    4: EBS 12.2.6 with Database 12.1.0.2 - Demo
    5: EBS 12.2.6 with Database 11.2.0.4 - Fresh
    6: EBS 12.2.6 with Database 11.2.0.4 - Demo
    7: EBS 12.1.3 with Database 12.1.0.2 - Fresh
    8: EBS 12.1.3 with Database 12.1.0.2 - Demo
    9: EBS 12.1.3 with Database 11.2.0.4 - Fresh
    10: EBS 12.1.3 with Database 11.2.0.4 - Demo
    11: Distributed Yard Management System 12.2
    12: Distributed Warehouse Management System 12.2 Choose EBS release from above list:
  8. Next, choose the service that will host the database. Note that the available choices are dependent on the release combination chosen, and therefore your screen may vary.
    ================================================================
    Provision Oracle E-Business Suite - Choose Service for Database
    ================================================================
    
    [Ctrl-B: Back, Ctrl-H: Main Menu]
    
    1: Compute
    2: DBCS
    3: DBCS-RAC
    4: Exadata CS-RAC
    
    Choose target database type from above list: 
    Upon provisioning the Oracle E-Business Suite Release 12.2 or 12.1.3 database to DBCS or Exadata CS, all non-system tablespaces are automatically encrypted using the Transparent Data Encryption (TDE). TDE will be configured using a wallet with automatic login.

    If you select option "2: DBCS" or "3: DBCS-RAC", you will be prompted for information about your instance on the Oracle Database Cloud Service.

    Enter the Oracle Database Cloud Service REST endpoint, and then enter either the Oracle Database Cloud Service Identity Domain or the IDCS Global User ID (IDCS GUID) when prompted for the identity domain. If you are using a traditional account, you will enter the Oracle Database Cloud Service Identity Domain. If you are using an IDCS-based account, you will enter the IDCS GUID.

    Enter Oracle DBaaS Cloud Service Endpoint          : mydbcsendpoint (e.g., https://psm.us.oraclecloud.com)
    Enter Oracle DBaaS Identity Domain                 : mydbaasdomain [or myidcsguid]

    Then, choose an hourly or monthly billing frequency:

    ==============================================================
    Provision Oracle E-Business Suite - Billing Frequency for DBCS
    ==============================================================
    
    [Ctrl-B: Back, Ctrl-H: Main Menu]
    
    1:   Hourly -- Pay per hour for number of hours used
    2:   Monthly -- Pay fixed amount for month regardless of number of hours used
    
    Enter your choice from above list: 

    Now, choose the desired software edition for DBCS:

    =============================================================
    Provision Oracle E-Business Suite - Software Edition for DBCS
    =============================================================
    
    [Ctrl-B: Back, Ctrl-H: Main Menu]
    
    1:   Enterprise Edition - General Purpose
    2:   Enterprise Edition - High Performance
    3:   Enterprise Edition - Extreme Performance
    
    Enter your choice from above list:
    Note: If you selected DBCS-RAC as the service to host the database, you must choose "Enterprise Edition - Extreme Performance" for the DBCS software edition.

    If you select option "4: Exadata CS-RAC" as the service to host your database, you will be prompted for the Exadata CS credentials:
    ==========================================================
    Provision Oracle E-Business Suite - ExadataCS Credentials
    ==========================================================
    
    [Ctrl-B: Back, Ctrl-H: Main Menu]
    
    Enter Exadata CS Cloud Endpoint                           : https://dbaas.oraclecloud.com
    Enter Exadata CS Cloud Identity Domain                    : myexadomain
    Enter Exadata CS Cloud User Name                          : john.smith@example.com
    Enter Exadata CS Cloud Password                           : <password>
  9. On the next screen, you will be prompted to choose your application tier topology.
    ======================================================
    Provision Oracle E-Business Suite - App Tier Topology
    ======================================================
    
    [Ctrl-B: Back, Ctrl-H: Main Menu]
    
    1: Provision Single App Tier
    2: Provision Multiple Shared App Tiers
    3: Provision Multiple Non-Shared App Tiers
    
    Enter your choice from above list: 
  10. You will now be prompted to enter environment details, including:
    1. The desired number of application tier nodes
    2. A unique name for your environment
    3. A database SID
    4. An available certified bundle patch or PSU (if applicable)
    5. A shape for each VM
      1. Application tier VM
      2. Database tier VM
      3. Oracle Traffic Director VM

      =======================================================
      Provision Oracle E-Business Suite - Environment Details
      =======================================================
      
      [Ctrl-B: Back, Ctrl-H: Main Menu]
      
      Specify a unique alphanumeric name (in lower case) for the new environment: mytestenv
      
      Enter Database SID: mytestsid
      
      { Enter pluggable database name: mytestsidp } *See Footnote 1
      
      { Available EBS certified < PSU | Bundle Patch >:
      1. <NAME1> - DATABASE PATCH SET UPDATE <PATCH LABEL> - <PATCH NUMBER>
      2. <NAME2> - DATABASE PATCH SET UPDATE <PATCH LABEL> - <PATCH NUMBER>
      ...
      Select < PSU | Bundle Patch> from above list:  1 } *See Footnote 2 Available Shapes ---------------- 1: oc1m 2.0 15360 2: oc2m 4.0 30720 3: oc3 2.0 7680 4: oc3m 8.0 61440 5: oc4 4.0 15360 6: oc4m 16.0 122880 7: oc5 8.0 30720 8: oc5m 32.0 245760 9: oc6 16.0 61440 10: oc7 32.0 122880 11: oc8 48.0 184320 12: oc8m 48.0 368640 13: oc9 64.0 245760 14: oc9m 64.0 491520 15: ocio1m 2.0 15360 16: ocio2m 4.0 30720 17: ocio3m 8.0 61440 18: ocio4m 16.0 122880 19: ocio5m 32.0 245760 Choose Shape for Operating System to configure Application Tier VM: 3

      Choose Shape for Operating System to configure OTD VM: 3 { Enter desired number of application tier nodes: 2 } *See Footnote 3 { Choose shape for DBCS: 2 Enter DBCS Admin Password: <password> Re-enter DBCS Admin Password: <password> } *See Footnote 4 { Enter Exadata CS Admin Password: <password> Enter Exadata Cloud Service cluster name: myexacluster Enter Exadata Cloud Service system name: myexasystem Enter Exadata Cloud Service VM IP addresses: xxx.xxx.xxx.x,xxx.xxx.xxx.x } *See Footnote 5

      Footnote 1: If you have chosen DBCS, DBCS-RAC or Exadata CS and Oracle Database 12.1.0.2, you will be prompted for the parameter shown.

      Footnote 2: If your target database service is either DBCS or Exadata CS, you will be prompted to choose an available Oracle E-Business Suite certified database PSU or bundle patch, respectively. 

      Footnote 3: The location of this prompt will vary depending on the service chosen to host the database.

      Footnote 4: If your target database service is DBCS or DBCS-RAC, you will be prompted for the parameter shown. If your target database service is DBCS-RAC, you will need to choose a shape that contains a minimum of 4 OCPUs.

      Footnote 5: If your target database service is Exadata CS, you will be prompted for the parameters shown.

  11. You now have the option to use existing reserved IPs for all of your VMs, as shown in the following example screen:
    =======================================
    Specify IP Reservations for Compute VMs
    =======================================
    
    [Ctrl-B: Back, Ctrl-H: Main Menu]
    
    1: Yes
    2: No
    
    Enter your choice: 1
    
    Available IP Reservations
    ----------------------------
    1: /Compute-testdomain/john.smith@example.com/tst-app01-res 192.168.99.101
    2: /Compute-testdomain/john.smith@example.com/tst-lb01-res 192.168.99.102
    3: /Compute-testdomain/john.smith@example.com/tst-db01-res 192.168.99.103
    
    IP reservation for compute app01 node: 1
    IP reservation for compute OTD node: 2
    IP reservation for compute DB node: 3

    Note: We recommend using IP reservations in order to guarantee the IP address assigned to each one of your nodes is always the same.

  12. On the next screen, choose an SSH key from the list of available SSH keys.
    ======================================================
    Provision Oracle E-Business Suite - Available SSH Keys
    ======================================================
    
    [Ctrl-B: Back, Ctrl-H: Main Menu]
    
    Available SSH Keys
    --------------------------------------------------------------------
    1:   /Compute-xxx/john.smith@example.com/mykey01
    2: /Compute-xxx/john.smith@example.com/mykey02
    3: /Compute-xxx/john.smith@example.com/mykey03 Choose an SSH key from above list:
  13. You will now be prompted to specify whether you would like to use logical host names for your application and database tier nodes.
    =====================
    Use Logical Hostname?
    =====================
    
    [Ctrl-B: Back, Ctrl-H: Main Menu]
    
    1: Yes
    2: No
    
    Enter your choice: 

    If you choose to use logical hostnames, you will enter a fully qualified host name plus domain name (e.g., "app1.mydomain.com") of 20 characters or less for each application tier and database tier. Multiple entries must be delineated by commas, as seen in the following example:

    Enter logical hostnames (e.g. myhost1.example.com) for all Application tiers: app1.mydomain.com,app2.mydomain.com
    Enter logical hostnames (e.g. myhost1.example.com) for all Database tiers: db1.example.com
  14. The next screen allows you to choose whether or not you would like to conduct any post-provisioning steps.
    ================================================
    Do you want to run any post provisioning steps ?
    ================================================
    
    [Ctrl-B: Back, Ctrl-H: Main Menu]
    
    1: Yes
    2: No
    
    Enter your choice: 1

    If you enter "1: Yes", you will be presented with a screen similar to the Oracle E-Business Suite Release 12.2 example below:

    List of Post-Provisioning Steps
    -------------------------------
    1: Install RPMs
    2: License Products
    3: Convert Forms to Socket Mode
    4: Change APPS Password
    5: Run AutoConfig
    6: Change Database Archive Mode
    7: Change System Passwords
    8: Stop Application Tier Services
    9: Grant OAM Monitoring Role to EBS Monitoring User
    10: Mailer Configuration
    11: Change Oracle WebLogic Server Admin Password
    12: Create New Oracle WebLogic Server Monitoring User
    13: Run fs_clone
    14: All of the Above
    
    Choose post provisioning steps (e.g. 2,3,5) :

    Note: The post-provisioning selection input must not contain spaces.
    The following table includes a description of each option and the list of inputs required for that step:

    Optional Post-Provisioning Step Description and Required Inputs (If applicable) Applies to Release(s)
    Install RPMs

    Install additional RPMs, such as those required by third-party applications.

    Required inputs:

    • Storage cloud container name
    • Storage cloud directory location where RPMs are stored
    • Storage endpoint URL
    • Storage cloud identity domain
    • Storage cloud user name
    • Password for storage
    12.2, 12.1.3
    License Products

    License Oracle E-Business Suite products.

    Required inputs:

    • Products to license (comma delimited list of product shortnames)
    12.2, 12.1.3
    Convert Forms to Socket Mode

    Convert from Forms servlet mode (the default) to Forms socket mode.

    Required inputs:

    • Socket port number for forms
    12.2, 12.1.3
    Change APPS Password

    Change the APPS password upon completion of the installation.

    Required inputs:

    • New APPS password for target instance
    12.2, 12.1.3
    Run AutoConfig

    Run AutoConfig upon completion of the installation.

    Required inputs: None

    12.2, 12.1.3
    Change Database Archive Mode

    Enable or disable database archiving.

    Required inputs:

    • Database archiving mode (specify enable, disable, or unchanged)
    12.2, 12.1.3
    Change System Passwords

    Change system passwords upon completion of the installation.

    Required inputs:

    • New SYS password for target instance
    • New DBSNMP password for target instance
    • New SYSADMIN password for target instance
    • New SYSTEM password for target instance
    12.2, 12.1.3
    Stop Application Tier Services

    Stop the application tier services upon completion of the installation.

    Required inputs: None

    12.2, 12.1.3
    Grant OAM Monitoring Role to EBS Monitoring User

    Grant OAM monitoring role to EBS monitoring user.

    Required inputs:

    • EBS monitoring user name
    • New WebLogic admin password
    12.2, 12.1.3
    Mailer Configuration

    Configure Workflow mailer upon completion of the installation.

    Required inputs:

    • Fully qualified host name of outbound mail server
    • Outbound email account user name
    • Fully qualitied host name of inbound mail server
    • Inbound email account user name
    • Inbound email reply-to address
    • Inbound email account password
    12.2
    Change Oracle WebLogic Server Admin Password

    Change the WebLogic admin server password upon completion of the installation.

    Required inputs:

    • WebLogic server password for target instance
    12.2
    Create New Oracle WebLogic Server Monitoring User

    Add a new WebLogic monitoring user.

    Required inputs:

    • WebLogic monitoring user name
    • WebLogic server password for target instance
    12.2
    Change PID and Lock File Location

    Change the PID and lock file location.

    Required inputs:

    • PID file location
    • Lock file location
    12.1.3
    Run fs_clone

    Run fs_clone upon completion of the installation.

    Required inputs: None

    12.2
    All of the Above

    Run all post-provisioning steps available for your release of Oracle E-Business Suite.

    Required inputs: All applicable inputs required as listed in this table.

    12.2, 12.1.3
  15. The Review screen allows you to review and confirm your choices. When you do so, provisioning will start and the Oracle E-Business Suite topology that you specified will be created. A summary of the setup will be provided upon successful completion of instance creation.

    Note: You must wait until configuration is complete before continuing with any of the steps below. Successful completion can be verified by checking the Installation Summary Log provided at the end of the operation. If any of the post-provisioning steps fail, a warning is shown in the console and in the logs. Check the log files and execute the failed step manually before further proceeding.

Implementing Workaround for Oracle Database 11.2.0.4 on DBCS RAC (Conditional)

If you chose to provision Oracle Database 11.2.0.4 on DBCS RAC, after provisioning is complete, perform the following steps to avoid a known issue which may result in an ORA-29516 failure:

  1. Connect to a DBCS RAC node as the opc user.
  2. Run the following command:
    $ raccli update server -allnodes -tag 28184212

Securing Access to Your Environment

We recommend following the guidance to ensure your environment is adequately protected.

Change Oracle E-Business Suite Account Passwords

You had the option to change your Oracle WebLogic server and Oracle E-Business Suite account passwords when performing your installation (see step 12 in "Perform Your Installation.") If you did not, you must change these passwords now.

Refer to the "Change E-Business Suite Account Passwords" section in the Oracle by Example tutorial Common Tasks for Oracle E-Business Suite on Oracle Cloud Infrastructure Classic.

Limit HTTPS Access to a Subset of IP Addresses

Create a Security IP List

We recommend that you avoid exposing your Oracle E-Business Suite environment to the public internet. To do so, first work with your network administrator to identify a restricted IP range (or ranges) from which to permit connections.

After you have identified the appropriate IP addresses, add them to a new security IP list with a name such as Allowed-External-Addresses. You will make use of this security IP list in the next subsection, where you will create a new security rule that defines allowed access to the load balancer associated with your new environment.

For detailed instructions, refer to "Creating a Security IP List" in section Managing Security IP Lists of Using Oracle Compute Cloud Service (for PaaS).

Create a Security Rule

In this section, you will disable a predefined security rule and create a new security rule to restrict source connections to your load balancer to those IP addresses defined in your security IP list.

First, proceed as follows to disable the predefined security rule.

  1. Navigate to the Oracle Compute Cloud Service console, and click on the Network tab.
  2. Disable the predefined security rule by performing the following steps:
    1. Select Security Rules from the navigation menu on the left.
    2. Search for the security rule with a name of the form <env name>-secrule-otd-https (for example, mytestenv-secrule-otd-https).
    3. Click on the menu to the right of this security rule, and choose Update.
    4. On the Update screen:
      1. Toggle Status from Enabled to Disabled.
      2. Click on Update to disable the security rule and exit the dialog.

Now perform the following steps to create your new security rule:

  1. Select Security Rules from the navigation menu on the left.
  2. Select Create Security Rule and then do the following:
    1. Name: Enter a name for the rule. We recommend that the name you choose begins with your unique environment name, followed by "-secrule-otd-seciplist" to distinguish it from other rules.
    2. Status: Select Enabled.
    3. Security Application: Select https.
    4. Source: Select the Security IP List radio button, and enter the name of the security IP list you created in the previous subsection (for example, Allowed-External-Addresses).
    5. Destination: Select the Security List radio button. Then, from the Security List drop-down list, select the security list associated with the OTD instance that was installed as part of your new environment (for example, mytestenv-otd).
    6. Description: Enter a description for the rule (for example, Permit Allowed-External-Addresses access to OTD).
    7. Click Create.

Now, only the addresses defined in your security IP list are allowed to connect to your load balancer.

Complete Oracle Traffic Director (OTD) with HTTPS Configuration

When you used the EBS Cloud Admin Tool, ProvisionEBS.pl, to generate your environment, the environment was automatically SSL-enabled using a self-signed certificate. Those access details are included in the Installation Summary log that is presented at the end of the environment creation process.

You can continue to use the self-signed certificate or replace the self-signed certificate with a certificate issued by a Certificate Authority (CA) - the latter is recommended for production use. If you choose to continue to use the self-signed certificate, follow the steps below in "Using the Self-Signed Certificate". If you choose to use a CA-issued certificate, follow the steps below in "Deploy a CA-Issued Certificate."

For both self-signed certificates and CA-issued certificates:

  1. Populate the truststores by following the steps in "Populate the Truststores (Mandatory)."
  2. If you are using XML Gateway, perform the steps in "Configure the XML Gateway (Conditional)."

Using the Self-Signed Certificate

When you connect to Oracle E-Business Suite configured with the self-signed certificate, your browser will display an error saying that the security certificate is not trusted. Follow the documentation from your browser provider to install a new root certificate.

Deploy a CA-Issued Certificate (Conditional)

To use a CA-issued certificate, perform the following steps:

  1. Obtain and document the OTD VM public IP address by viewing the Installation Summary log.
  2. Create a DNS entry in your own domain that points to the public IP address of the OTD VM.
  3. Using this IP address, refer to "Connect to Your Oracle Cloud Instance Via SSH" in the Oracle by Example tutorial Common Tasks for Oracle E-Business Suite in Oracle Cloud Infrastructure Classic to set up SSH to connect to your cloud instance.
  4. SSH to the OTD VM.
  5. While logged on to the OTD VM, switch from the opc user to the oracle user by running the command:
    $ sudo su - oracle
  6. Create a wallet for OTD.
    First, you must determine the values that are required for the Distinguished Name for the Subject in the certificate. The fully qualified name you entered into DNS for OTD's public IP address must be used in the Common Name attribute and in the Subject Alternative Name.
    Other attribute values such as Country, State, Locality, Organization, and Organizational Unit may be optional or have particular fixed values dictated by your Certificate Authority or your company's internal policies.
    The following example commands use of the orapki utility to create a wallet with an RSA key pair.
    PATH=/u01/oracle/product/traffic-director/oracle_common/bin:$PATH
    export PATH
    mkdir ~/wallet && cd ~/wallet
    DN='CN=ebs.example.com,O=Example Inc,C=US'
    
    PASS=xxxx1111  # Wallet Password
    orapki wallet create  -wallet . -pwd $PASS
    orapki wallet add  -wallet . -dn "$DN" -keysize 2048 -sign_alg sha256 -pwd $PASS
    orapki wallet export -wallet . -dn "$DN" -request server.csr -pwd $PASS
    echo 'DN is: ' $DN
  7. Submit the Certificate Signing Request in server.csr to the certificate authority of your choice.
    When you receive the signed certificate, you will also receive the corresponding root CA certificate and any required immediate CA certificate that will make up the certificate chain (or you will receive instructions on how to download these certificates). These certificates must be imported into the wallet, starting from the root.
    In the example below, we assume that you have received 3 certificate files, the server certificate, one intermediate CA certificate, and the CA's root certificate. In the example, these files are called server.crt, intCA.crt, and rooCA.crt.
    orapki wallet add -wallet . -trusted_cert -cert rootCA.crt -pwd $PASS
    orapki wallet add -wallet . -trusted_cert -cert intCA.crt  -pwd $PASS
    orapki wallet add -wallet . -user_cert    -cert server.crt -pwd $PASS
  8. Now, make the wallet auto_login (creates cwallet.sso) and list the contents of the wallet to make sure it is as intended.
    orapki wallet create  -wallet . -auto_login -pwd $PASS 
    orapki wallet display -wallet . 
  9. Copy the auto_login wallet file to the runtime locations.
    OTD_DIR=/u01/oracle/config/traffic-director/opc-lb/config/fmwconfig/components/OTD
    cp cwallet.sso $OTD_DIR/<OTD_VM_HOSTNAME>/config/
    cp cwallet.sso $OTD_DIR/instances/<OTD_VM_HOSTNAME>/config/
  10. Replace the content of the subject element in server.xml file the with the Distinguished Name of the Subject (variable $DN above). The server.xml file is found in two different locations:
    • /u01/oracle/config/traffic-director/opc-lb/config/fmwconfig/components/OTD/<OTD_VM_HOSTNAME>/config/server.xml
    • /u01/oracle/config/traffic-director/opc-lb/config/fmwconfig/components/OTD/instances/<OTD_VM_HOSTNAME>/config/server.xml

    In each server.xml file, find tag <ssl><cert><subject>CN=EBS_Custom_Server_Cert,O=oracle,C=US</subject></cert></ssl>. Replace the CN value with the customer certificate CN value.

    Note: You can check the CN value of a certificate with the following command:

    $ orapki wallet display -wallet <certificate_path>
  11. Stop and restart the server with the following commands:
    $ cd /u01/oracle/config/traffic-director/opc-lb/config/fmwconfig/components/OTD/instances/<OTD_VM_HOSTNAME>/bin 
    $ ./stopserv
    $ ./startserv

Populate the Truststores (Mandatory)

  1. Import the root CA certificate for oacore/oafm/forms JDK.
    Note: If this is a root certificate from a commercial CA, then the certificate may already exist in the truststore. If the certificate is in the truststore you will receive an error that you can ignore.
  2. Import the root certificate into the database DB wallet (Self-Signed and CA-issued Certificates)

Configure Application Tier Components (Mandatory)

Conduct Preparatory Steps
  1. Connect to the primary application tier VM:
    1. Obtain and document the primary application tier VM public IP address by viewing the Installation Summary log.
    2. Using this IP address, connect to the admin server using SSH by following the instructions in "Connect to Your Oracle Cloud Instance Via SSH" in the Oracle by Example tutorial Common Tasks for Oracle E-Business Suite in Oracle Cloud Infrastructure Classic.
  2. While logged on to the primary application tier VM, switch from the opc user to the oracle user by running the following command:
  3. $ sudo su - oracle
  4. Set the environment by running the following command:
    $ . /u01/install/APPS/EBSapps.env run
  5. Navigate to the directory shown:
    $ cd $FMW_HOME/oracle_common/common/bin/
  6. Download the txkUpdateServerArgs.py script by executing the following command:
    $ wget https://us6.storage.oraclecloud.com/v1/storagesvc-a425918/Patches/EBS/12.2/txk/txkUpdateServerArgs.py
Configure WLS OACORE Managed Server Startup Parameters

To configure WLS OACORE managed server startup parameters, run the following command and enter the values shown when prompted:

$ wlst.sh txkUpdateServerArgs.py --action=setServerStartArgument

Enter Context File Path: <context file with absolute path>
Enter the WebLogic Server password: <password>
Enter server type [oacore, forms, oafm]: oacore
Enter the start argument to add to oacore servers: -DUseSunHttpHandler=true 
Configure Integrated SOA Gateway (Self-Signed Certificate only)
  1. Execute the following command to determine the context file with absolute path:
    $ echo $CONTEXT_FILE
  2. To set the custom hostname verifier, execute the following command, and enter the values shown when prompted:
    $ wlst.sh txkUpdateServerArgs.py --action=setWildcardHostnameVerifier
    
    Enter Context File Path: <context file with absolute path>
    Enter the WebLogic Server password: <password>
    Enter server type [oacore, forms, oafm]: oafm
Configure Integrated SOA Gateway (Self-Signed Certificate and CA-Issued Certificate)

To set the SSL protocol version start argument, execute the following commands and enter the values shown when prompted:

$ $FMW_HOME/oracle_common/common/bin/wlst.sh txkUpdateServerArgs.py --action=setServerStartArgument

Enter Context File Path: <context file with absolute path>
Enter the WebLogic Server password: <password>
Enter server type [oacore, forms, oafm]: oafm 
Enter the start argument to add to oafm servers: -Dweblogic.security.SSL.protocolVersion=TLS1

$ $FMW_HOME/oracle_common/common/bin/wlst.sh txkUpdateServerArgs.py --action=setServerStartArgument

Enter Context File Path: <context file with absolute path>
Enter the WebLogic Server password: <password>
Enter server type [oacore, forms, oafm]: oacore 
Enter the start argument to add to oafm servers: -DUseSunHttpHandler=true

Configure Oracle XML Gateway (Conditional)

If you are connecting to the system using Oracle XML Gateway, perform the steps provided in the following documents according to your Oracle E-Business Suite release:

Enabling Oracle OLAP, Partitioning, and Spatial Options (Conditional)

If you placed your database tier on the Oracle Database Cloud Service and chose "Database Enterprise Edition - General Purpose", you must now enable the Oracle OLAP, Partitioning, and Spatial options as they are required by Oracle E-Business Suite.

Follow the instructions below, according to your database release:

Performing Post-Installation Steps

If you have provisioned a fresh install of Oracle E-Business Suite, before you can use the applications you must first activate your chosen products and languages, and then perform the relevant functional setups. Refer to "Activate Products and Languages" and "Conduct Functional Implementations" below for more information.

Note: If you have provisioned Oracle Distributed Yard Management, before you activate products you must perform additional steps as listed in My Oracle Support Knowledge Document 1672903.1, Oracle Yard Management, Deployment Steps For ADF Components.

Configure Workflow Notification Mailer

To be able to email Oracle Workflow notifications, you must configure email servers your Oracle E-Business Suite instance can access. Refer to the Oracle by Example tutorial Configuring Oracle Workflow Notification Mailer with Mail Servers for Oracle E-Business Suite Using the EBS Cloud Admin Tool.

Activate Products and Languages

You activate your chosen products and languages by running the License Manager utility. For detailed instructions, refer to:

Note: In a Vision Demo installation, you can also use License Manager to activate languages other than the default of American English.

Conduct Functional Implementations

After you have activated your desired products and languages, you may proceed with your functional implementation.

Want to Learn More?

Change Log

Date Description
2019-04-24
  • Updated footer.
2018-09-14
  • Added updates for support for Oracle E-Business Suite Release 12.2.7 in the "Purpose" subsection and "Performing Your Installation" section.
2018-08-28
  • Updated "Provision Oracle E-Business Suite - Environment Details" screen in step 8 of the "Performing Your Installation" section.
2018-08-10
  • Added updates for certified Oracle Database patch set updates and bundle patches in the "Purpose" subsection and "Performing Your Installation" section.
2018-06-29
  • Minor formatting enhancements.
2018-06-26
  • Added new section "Implementing Workaround for Oracle Database 11.2.0.4 on DBCS RAC (Conditional)."

2018-06-12

  • Made updates for 18.2.1:
    • Made clarifications and updates in tables of "Purpose" subsection.
    • Updated screens in step 8 of "Performing Your Installation."
  • Made various updates throughout document for standardization.

2018-03-09

  • Added IDCS GUID to "Determining Cloud Service Account Details" section.
  • Updated step 6 of "Performing Your Installation."

2018-02-20

  • Updated screens for 18.1.1 and made minor wording edits in "Perform Your Installation."
  • Updated table of options in "Purpose" section.
  • Changed section title "Determine Cloud Service REST Endpoints" to "Determining Cloud Service Account Details." Updated contents of section.

2017-12-20

  • Updated section "Perform Post-Installation Steps" - revised intro and removed "Conditional" from substeps.

2017-11-20

  • Minor update to "What Do You Need?" section.

2017-11-08

  • Made various updates in document to reflect updates in product/service name changes as well as in UI.
  • Updated "Determine Cloud Service REST Endpoints" section and various references to endpoints throughout document to reflect updated service names.

2017-10-11

  • Added note to step 9 of "Perform Your Installation" section.
2017-09-27
  • Updated various text and EBS Cloud Admin Tool UI screens throughout document for 1.7.3 release.
  • Added post-provisioning steps in "Perform Your Installation" section.
  • Added "Enable Oracle OLAP, Partitioning, and Spatial Options (Conditional)" section and added relevant information in Background section.
2017-08-15
  • Updated various text and EBS Admin Tool UI screens throughout document for 1.7.2 release.
  • Updated "Time to Complete" subsection.
  • Updated sub-sections of "Securing Access to Your Environment" as well as added new subsection "Complete Oracle Traffic Director (OTD) with HTTPS Configuration."
  • Moved "Configure Workflow Notification Mailer" section to subsection in "Perform Post-Installation Steps."
  • Updated "Limit HTTP Access to a Subset of IP Addresses" to HTTPS.
  • Updated steps in "Perform Your Installation."
2017-06-30
  • Updated "Perform Your Installation" with modified DBaaS backup instructions.

2017-05-04

  • Renamed section "Prepare for Your Installation" to "Determine Cloud Service REST Endpoints."
  • Removed subsection "Edit Image List."

2017-05-02

  • Made changes to minimum requirements table in "What Do You Need?"
  • Updated "Deploy or Update the EBS Cloud Admin Tool" section.
  • Edited note in "Perform Your Installation" concerning the usage of the latest codeline.
  • Updated to 03/28/17 OBE template.

2017-04-28

  • Added reference to new Section "Update EBS Cloud Admin Tool to Latest Codeline" in OBE "Deploying the EBS Cloud Admin Tool to Oracle Cloud".
  • Changed reference from "AD-TXK Delta 8 + AD-TXK Delta 8 Oracle Cloud Bundle 1 (Patch 25644266)" to "AD-TXK Delta 9".
  • Added step to "Creating Your Oracle E-Business Suite Environment on Oracle Cloud From Your Backup" concerning reserved IP selection for application tier.

2017-03-31

  • Updated "Background" and "What Do You Need?" sections with Exadata CS and other content for supported release combinations.
  • Corrected code for Table of Contents display.

2017-03-30

  • Subsumed section "Change Oracle E-Business Suite Account Passwords" into new section "Secure Access to Your Environment", and added further content.

2017-03-10

  • Changed title of OBE to "Provisioning a New Oracle E-Business Suite Installation on Oracle Cloud Using the EBS Cloud Admin Tool".

2017-03-07

  • In section "Determine Cloud Service Endpoints", changed the two DBCS-related endpoints from "Optional" to "Conditional".

2017-03-03

  • Initial publication.