Cloning Oracle E-Business Suite From On-Premises to Oracle Cloud Infrastructure Classic Using EBS Cloud Tools

 


Options



Before You Begin

Purpose

This tutorial guides you through the process of cloning your on-premises environment to Oracle Cloud, which is done in two phases:

  • Phase I: Back up your on premises Oracle E-Business Suite environment to Oracle Cloud Infrastructure Object Storage Classic.
  • Phase II: Provision your desired topology on Oracle Cloud Infrastructure Classic, restoring your application tier to Compute Classic and your database tier to either Compute Classic, Oracle Database Cloud Service (DBCS), or Exadata Cloud Service (Exadata CS).

Time to Complete

  • A minimum of 1 hour for the setup process.
  • Additional time, dependent on the size of the source environment and desired cloud topology, to:
    • Package the application tier code and the database backup.
    • Copy from the on-premises environment to Oracle Cloud Infrastructure Object Storage Classic (referred to as "Object Storage Classic" in this document).
    • Provision the desired topology.
    • (Conditional) Encrypt all non-system tablespaces using Transparent Database Encryption (TDE). This applies if your source database has not been encrypted and if the target database service is Oracle Database Cloud Service (DBCS) or Exadata Cloud Service (Exadata CS).

Background

The tables below show the certified Oracle E-Business Suite and Database releases as well as required patches for the cloning automation, based on the target database tier location.

Oracle Cloud Infrastructure Compute Classic: Automation Support and Requirements for Creating an On-Premises Backup as Part of the Lift and Shift

Note: Compute Classic only supports single-node (not Oracle RAC) databases.

Oracle E-Business
Suite Release
Required Oracle E-Business Suite
and Application Technology Stack Patches
Oracle Database Release
Required Database Patches

12.2.3 or later

  • AD-TXK Delta 10 (see Footnote 1)
  • Latest application technology stack patches (see Footnote 2)

12.1.0.2

Latest database patches (ETCC) (see Footnote 2)

11.2.0.4

Latest database patches (ETCC) (see Footnote 2)

12.1.3

In addition to the patches listed in Document 406982.1, Cloning Oracle Applications Release 12 with Rapid Clone, the following patches are required:

12.1.0.2

Latest database patches (ETCC) (see Footnote 2)

In addition to the patches listed in Document 406982.1, Cloning Oracle Applications Release 12 with Rapid Clone, the following patches are required:

11.2.0.4

Latest database patches (ETCC) (see Footnote 2)

Database Cloud Service (DBCS) Single Instance: Automation Support and Requirements for Creating an On-Premises Backup as Part of the Lift and Shift

Note: Database edition options: Enterprise Edition, Enterprise Edition High Performance, and Enterprise Edition Extreme Performance

Oracle E-Business
Suite Release
Required Oracle E-Business Suite
and Application Technology Stack Patches
Oracle Database Release
(see Footnote 3)
Required Database Patches

12.2.3 or later

  • AD-TXK Delta 10 (see Footnote 1)
  • Latest application technology stack patches (see Footnote 2)
  • Patch 26592812:R12.FND.C

12.1.0.2

April 2018 PSU or earlier

  • AD-TXK Delta 10 (see Footnote 1)
  • Latest application technology stack patches (see Footnote 2)

11.2.0.4

April 2018 PSU or earlier

12.1.3

In addition to the patches listed in Document 406982.1, Cloning Oracle Applications Release 12 with Rapid Clone, the following patches are required:

Container Database/Pluggable Database patches (see Footnote 5):

12.1.0.2

April 2018 PSU or earlier

In addition to the patches listed in Document 406982.1, Cloning Oracle Applications Release 12 with Rapid Clone, the following patches are required:

11.2.0.4

April 2018 PSU or earlier

Database Cloud Service (DBCS) Oracle RAC Database: Automation Support and Requirements for Creating an On-Premises Backup as Part of the Lift and Shift

Note: Database edition option: Enterprise Edition Extreme Performance

Oracle E-Business
Suite Release
Required Oracle E-Business Suite
and Application Technology Stack Patches
Oracle Database Release
Required Database Patches

12.2.3 or later

  • AD-TXK Delta 10 (see Footnote 1)
  • Latest application technology stack patches (see Footnote 2)
  • Patch 26592812:R12.FND.C

12.1.0.2

April 2018 Database Bundle Patch or earlier

  • AD-TXK Delta 10 (see Footnote 1)
  • Latest application technology stack patches (see Footnote 2)

11.2.0.4

April 2018 Database Bundle Patch or earlier

12.1.3

In addition to the patches listed in Document 406982.1, Cloning Oracle Applications Release 12 with Rapid Clone, the following patches are required:

Container Database/Pluggable Database patches (see Footnote 5):

12.1.0.2

April 2018 Database Bundle Patch or earlier

In addition to the patches listed in Document 406982.1, Cloning Oracle Applications Release 12 with Rapid Clone, the following patches are required:

11.2.0.4

April 2018 Database Bundle Patch or earlier

Exadata Cloud Service (Exadata CS): Automation Support and Requirements for Creating an On-Premises Backup as Part of the Lift and Shift
Oracle E-Business
Suite Release
Required Oracle E-Business Suite
and Application Technology Stack Patches
Oracle Database Release
(see Footnote 4)
Required Database Patches

12.2.3 or later

  • AD-TXK Delta 10 (see Footnote 1)
  • Latest application technology stack patches (see Footnote 2)
  • Patch 26592812:R12.FND.C

12.1.0.2

January 2018 Database Bundle Patch or earlier

  • AD-TXK Delta 10 (see Footnote 1)
  • Latest application technology stack patches (see Footnote 2)

11.2.0.4

January 2018 Database Bundle Patch or earlier

12.1.3

In addition to the patches listed in Document 406982.1, Cloning Oracle Applications Release 12 with Rapid Clone, the following patches are required:

Container Database/Pluggable Database patches (see Footnote 5):

12.1.0.2

January 2018 Database Bundle Patch or earlier

In addition to the patches listed in Document 406982.1, Cloning Oracle Applications Release 12 with Rapid Clone, the following patches are required:

11.2.0.4

January 2018 Database Bundle Patch or earlier

Footnotes
  • Footnote 1: Even if your instance already has AD-TXK Delta 10 applied, refer to My Oracle Support Knowledge Document 1617461.1, Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2, and ensure any additional one-off patches listed for AD and TXK are also applied on your instance.
  • Footnote 2: For more information, refer to My Oracle Support Knowledge Document 1594274.1, Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes.
  • Footnote 3: When placing your 12.1.0.2 or 11.2.0.4 database tier on DBCS single-instance, you will get to choose one of the following available Oracle E-Business Suite certified database patch set updates:
    • April 2018
    • January 2018
    • October 2017
  • 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).
  • Footnote 5: The following patches are specific to container database/pluggable database (CDB/PDB) support and would only be needed when an Oracle E-Business Suite Release 12.1.3 instance is used with Oracle Database 12c and is being migrated to Oracle Cloud.

Notes:

  • This procedure supports the cloning of Linux source systems to Oracle Linux target systems. If your environment is not currently running on Linux, please refer to My Oracle Support Knowledge Document 2066260.1, Getting Started with Oracle E-Business Suite on Oracle Cloud and see "Can I migrate my Oracle E-Business Suite instances on any operating system to Oracle Cloud?” in Section 9: Frequently Asked Questions.
  • This procedure creates a backup of your primary application tier.
  • The maximum database size supported by this migration procedure is dependent on the cloud service you choose and whether you intend to perform local or remote backups. Refer to the relevant cloud service documentation for guidance:
  • The source database must be in ARCHIVELOG mode in order to perform a hot backup.
  • The source database components need to be in sync with the components provisioned in DBCS or Exadata CS, and the versions of the database components should be at the same level. Also, there should not be any additional database components. Validation of components is done behind the scene for lifting the instance. Any mismatches are reported during that process.
  • For adequately low latency between the application and database tiers, your Compute Classic and Oracle Database Cloud Service should be co-located in the same datacenter.
  • Database encryption using Transparent Data Encryption (TDE)
    • When cloning an Oracle E-Business Suite Release 12.2 or 12.1.3 environment, if tablespace or column encryption is enabled in the source on-premises environment using TDE, the tablespace or column encryption will be replicated in the database on Compute Classic, DBCS, or Exadata CS.
    • When cloning an Oracle E-Business Suite Release 12.2 or 12.1.3 environment, if encryption has not been enabled for the source on-premises environment using TDE, all non-system tablespaces will automatically be encrypted with TDE if the target database service is on DBCS or Exadata CS.
    • TDE on Oracle Cloud Infrastructure Classic will be configured with wallets using automatic login.
    • If the on-premises wallet is not password based, the lift will fail. Check and convert your wallet to password based if necessary. See: Oracle Database Advanced Security Guide.
  • For Oracle E-Business Suite Release 12.2 with Oracle Database 12.1.0.2, note that databases running in Oracle RAC mode can be restored only to RAC. Similarly, single instance databases can only be restored as single node databases.
  • Simultaneous cloning or deletion of multiple databases on the same Exadata CS service is currently not supported.
  • If you 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."

What Do You Need?

  • 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

    Oracle Cloud Infrastructure Object Storage Classic
    (Conditional)

    N/A

    N/A

    N/A

    Size of application tier code + database (object)

    N/A

    EBS Cloud Admin Tool virtual machine (VM)

    1

    1

    7.5 GB

    Required: 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)

    Release 12.2 = 15 GB per VM

    Release 12.1 = 7.5 GB per VM

    Strictly dependent on your on-premises environment. The minimum requirements are shown below:

    • 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-node database

    1

    2

    15 GB

    Dependent on the size of your database and backup options chosen

    1

    DBCS
    Oracle RAC

    2

    4 x 2

    15 GB x 2

    Dependent on the size of your database and backup options chosen

    2

    Exadata CS
    Oracle RAC
    (See Footnote 3)

    2

    8 x 2

    240 GB x 2

    42 TB

    2

    Virtual Private Network (VPN)

    For information regarding VPN options, see Network Cloud Offerings.

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

Process Overview

To clone your Oracle E-Business Suite environment, you must perform the following steps:

  1. Deploy or update the EBS Cloud Admin Tool.
  2. Determine cloud service account details.
  3. Install the Oracle E-Business Suite Cloud Backup Module on-premises.
  4. Create stage areas on-premises and prepare to take a backup.
  5. Back up your environment to Object Storage Classic using the Oracle E-Business Suite Cloud Backup Module.
  6. Create your Oracle E-Business Suite environment on Oracle Cloud from your backup.
  7. (Conditional) Implement workaround for Oracle Database 11.2.0.4 on DBCS Oracle RAC.
  8. Secure access to your environment.
  9. (Conditional) Enable Oracle OLAP, Partitioning, and Spatial options.
  10. Perform post-cloning tasks.

Deploying or Updating the EBS Cloud Admin Tool

Deploy the EBS Cloud Admin Tool to your cloud domain, by following the Oracle by Example tutorial Deploying the EBS Cloud Admin Tool to Oracle Cloud Infrastructure Classic.

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 Infrastructure Classic.

Determining Cloud Service Account Details

Refer to the "Determining 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:

  • Oracle Cloud Infrastructure Compute Classic Service Instance ID - Required
  • Oracle Cloud Infrastructure Compute Classic REST endpoint - Required
  • Oracle Cloud Infrastructure Object Storage Classic REST endpoint - Required
  • Oracle Database Cloud Service REST endpoint - Conditional

Installing the Oracle E-Business Suite Cloud Backup Module On-Premises

You must install the Oracle E-Business Suite Cloud Backup Module on an on-premises Linux server with at least 500 MB of free space and the wget libraries installed. The on-premises Linux server can be one of the Oracle E-Business Suite nodes or another server that resides in your intranet. This server will be referred to as the backup module server for the remainder of this tutorial.

The Oracle E-Business Suite Cloud Backup Module requires Perl version 5.14 or later with the JSON module installed. You must either ensure that the default Perl installation on the backup module server meets these requirements, or run the Oracle E-Business Suite Cloud Backup Module using the Perl binary provided in the patch.

Notes:

  • If you are revisiting this note and have already deployed the Oracle E-Business Suite Cloud Backup Module, to retrieve the latest version you must do so again. First make a copy of cln.props to save any customizations, then download the new patch. When you run the latest version of the module, you can refer to your saved cln.props file to determine the values to enter at the prompts.
  • Ensure that your Oracle E-Business Suite on-premises environment meets patching prerequisites prior to running the Oracle E-Business Suite Cloud Backup Module. These prerequisites are listed in "Certified Oracle E-Business Suite and Database Releases" in the Background section.

Perform the following steps to download the utility:

  1. Download Patch 26725016 from My Oracle Support to the backup module server.
  2. Using the commands below, change to the directory where you downloaded the patch file and extract the downloaded patch.
    $ cd <download folder>
    $ unzip p26725016_R12_Generic.zip

    Unzipping the patch zip file creates a directory named RemoteClone.

  3. Change to the RemoteClone directory and change the permission to “execute” for all the downloaded scripts.
    $ cd RemoteClone
    $ chmod +x *.pl
    $ chmod +x lib/*.sh

Creating Stage Areas and Prepare to Take a Backup

You will create stage areas for the on-premises application tier and the on-premises database tier.

On-Premises Application Tier Stage Area Creation

The size of the application tier stage is calculated as being 30% of the size of the application tier file system.

For example, in Oracle E-Business Suite Release 12.2 you would calculate 30% of the size of the run file system as follows.

$ cd /u02/ebs122
$ . EBSapps.env run
$ cd $RUN_BASE
$ du -sh 
40G .

In this example, the run file system on the application tier contains 40 GB. 30% of this is 12 GB. That will be the size of the stage area on the application tier.

For Oracle E-Business Suite Release 12.1.3, you would calculate 30% of the size of the application tier file system as follows:

$ cd <APPL_TOP>
$ . APPS<CONTEXT_NAME>.env
$ cd $APPL_TOP
$ du -sh
22G .

In this example, the application tier file system is 22 GB. 30% of this is 7 GB. That will be the size of the stage area on the application tier.

Create a directory to hold the application tier stage on the application tier and ensure that it has the required amount of space, as previously calculated.

On-Premises Database Tier Stage Area Creation

Create a directory to hold the backup utilities, as well as to store temporary files used to process the backup. Ensure that it has at least 20 GB of free space.

Backing Up Your Environment Using the Oracle E-Business Suite Cloud Backup Module

The Oracle E-Business Suite Cloud Backup Module, EBSCloudBackup.pl, is used to back up your Oracle E-Business Suite environment to Object Storage Classic. This module captures all the information and creates the cln.props file.

Before you execute EBSCloudBackup.pl, ensure that the following prerequisites have all been met:

  1. All nodes must have SSH enabled.
  2. SSH equivalence must be set up between the database node and the primary application tier node. This will allow the required SSH communication between the servers.
  3. The SSH configuration files (~/.ssh/config) must have the entry "ServerAliveInterval 100" for the application tier, database tier, and backup module server.
  4. (Conditional) If you are backing up your Oracle E-Business Suite environment to Object Storage Classic, then ensure that the following conditions are met:
    1. The replication policy must be set on your Object Storage Classic service. Review "Selecting a Replication Policy for Your Service Instance" in Using Oracle Cloud Infrastructure Object Storage Classic for guidelines and instructions.
    2. The Object Storage Classic REST endpoint URL must be reachable either directly or through a proxy server to Object Storage Classic.
  5. Ensure that all executables under the database ORACLE_HOME/bin are owned by the oracle user, and not by the root user.

This will allow users to connect to all nodes required for the Oracle E-Business Suite Cloud Backup Module, EBSCloudBackup.pl.

Perform the following steps to back up your the Oracle E-Business Suite environment to Object Storage Classic using the Oracle E-Business Suite Cloud Backup Module:

  1. Change to the RemoteClone directory on the backup module server if you have not already done so.
  2. Run EBSCloudBackup.pl using the following command:
    $ perl EBSCloudBackup.pl

    If the backup module server does not already have the required Perl version with the JSON module installed, then the script returns an error message. In such a case, you can run the script using the Perl binary provided in the Oracle E-Business Suite Cloud Backup Module patch files, with the following command.

    $ 3pt/perl/bin/perl EBSCloudBackup.pl

    If you are using an Oracle E-Business Suite application tier node or database tier node as the backup module server, note that you should not source the Oracle E-Business Suite environment before running the Oracle E-Business Suite Cloud Backup Module.

  3. On the "Migrate Oracle E-Business Suite - Options" screen, select option 1 to create the backup and upload it to Object Storage Classic.
    ==============================================
    Migrate Oracle E-Business Suite - Options
    ==============================================
    
    Migrate Oracle E-Business Suite - Enter Selection:
    1:   Create E-Business Suite Backup and Upload to Oracle Cloud Infrastructure Classic
    2:   Create E-Business Suite Backup and Upload to Oracle Cloud Infrastructure
    3:   Exit
    
    Enter your choice from above list:  1
  4. Next, determine whether you plan to access the source database through a proxy server (option 1) or access the database directly (option 2) in the "Enter Source Database Tier - Proxy Details" screen. Choose option 2 to access the source database tier without through a proxy server.
    ===========================================
    Enter Source Database Tier - Proxy Details
    ===========================================
    
    [Ctrl-B: Back, Ctrl-H: Main Menu]
    
    1: Yes
    2: No
    
    Enter your choice from above list: 2                   

    Note: If you choose option 1, before proceeding to the next step, specify the proxy server protocol, host, port, user name, and password information used to establish communication between the source database server and Object Storage Classic.

    ===========================================
    Enter Source Database Proxy details
    ===========================================
    
    [Ctrl-B: Back, Ctrl-H: Main Menu]
    
    Proxy Protocol           : https  			
    Proxy Host : www-proxy.example.com
    Proxy Port : 80
    Proxy user name :
    Proxy user password :
  5. Enter your source database tier details on the "Migrate Oracle E-Business Suite - Enter Source Database Tier Details" screen.

    When entering the host name, ensure that you enter the fully qualified host name including the domain of source database server.

    You must enter an operating system user name used to connect to the source database server using SSH. You can choose to authenticate the database OS user either with the associated OS user password or with the SSH key and passphrase defined for the custom private key. The prompts for the custom private key and passphrase appear only if you do not enter an OS user password. If you do not enter either a password or a custom private key, then the script indicates that the default SSH key will be used and prompts you to confirm that you want to continue with the SSH key at the indicated location. Additionally, specify the location of the stage area directory on the database server that stores temporary files during the backup creation process, and the location of the context file on the source database tier, including the complete context file path.

    =====================================================================
    Migrate Oracle E-Business Suite - Enter Source Database Tier Details
    =====================================================================
    
    [Ctrl-B: Back, Ctrl-H: Main Menu]
    
    Enter Fully Qualified Hostname                     : demo.example.com
    OS User Name                                       : oracle
    OS User Password [skip if not applicable]          : password
    OS User Custom Private Key [skip if not applicable]: OS User Passpharse [skip if not applicable] : Stage Directory : /u01/install/stage/dbStage Context File : /u01/install/APPS/12.1.0/appsutil/EBSDB_apps.xml You have not entered Password or Custom Private Key location We will be using default SSH key at /home/oracle/.ssh/id_rsa Do you want to continue (Yes | No): yes Validating the details..
  6. Next, when prompted for the "Enter Source Apps Tier Proxy Details" menu, determine whether you plan to access the source application tier through a proxy server (option 1) or access it directly (option 2) in the "Enter Source Application Tier Proxy Details" screen. Choose option 2 to access the source application tier directly without through a proxy server.

    ===========================================
    Enter Source Application Tier Proxy Details
    ===========================================
    
    [Ctrl-B: Back, Ctrl-H: Main Menu]
    
    1: Yes
    2: No
    
    Enter your choice from above list: 2                  

    Note: If you plan to access the source application tier through a proxy server (option 1), enter the proxy details on the "Enter Source App Tier Proxy details" screen before proceeding to the next step.

    ===========================================
    Enter Source App Tier Proxy details
    ===========================================
    
    [Ctrl-B: Back, Ctrl-H: Main Menu]
    
    Proxy Protocol           : https  			
    Proxy Host : www-proxy.example.com
    Proxy Port : 80
    Proxy user name :
    Proxy user password :
  7. Enter your source application tier details on the "Migrate Oracle E-Business Suite - Enter Source Application Tier Details" screen.

    When entering the host name, ensure that you enter the fully qualified host name including the domain of source primary application tier server.

    You must enter an operating system user name used to connect to the source primary application tier server using SSH. You can choose to authenticate the primary application tier server OS user either with the associated OS user password or with the SSH key and passphrase defined for the custom private key. The prompts for the custom private key and passphrase appear only if you do not enter an OS user password. If you do not enter either a password or a custom private key, then the script indicates that the default SSH key will be used and prompts you to confirm that you want to continue with the SSH key at the indicated location. Additionally, specify the location on the stage area directory on the primary application tier server that stores temporary files during the backup creation process, the location of the context file on the source application tier, including the complete context file path, and the password for the Oracle E-Business Suite APPS schema.

    For Oracle E-Business Suite Release 12.2 only, you need to specify the Oracle WebLogic Server administrator password for the source environment.

    ========================================================================
    Migrate Oracle E-Business Suite - Enter Source Application Tier Details
    ========================================================================
    
    [Ctrl-B: Back, Ctrl-H: Main Menu]
    
    Enter Fully Qualified Hostname                     : demo.example.com
    OS User Name                                       : oracle
    OS User Password [skip if not applicable]          : password
    OS User Custom Private Key [skip if not applicable]:
    OS User Passpharse [skip if not applicable]        : 
    
    Stage Directory                                    : /u01/install/stage/dbstage
    Context File : /u01/install/APPS/fs1/inst/apps/EBSDB_apps/appl/admin/EBSDB_apps.xml APPS Password : password
    You have not entered Password or Custom Private Key location We will be using default SSH key at /home/oralcmqa/.ssh/id_rsa Do you want to continue (Yes | No): yes Validating the details... Wls Admin Password: password
  8. When prompted, enter the following backup information on the "Enter OSS - Backup Details" screen:
    • Backup Identifier Tag - Enter a name to uniquely identify your backup. This will be used as a prefix when creating 2 containers: a generic container for the application tier and database tier ORACLE_HOME backup and a database container for the database RMAN backup. For example:

      • <My_Unique_Backup_Name>Generic
      • <My_Unique_Backup_Name>DB
    • Backup Thread Count (Optional) - Specify number of threads used for uploading application and database tier file system backups. The minimum value is 1. The maximum value must be less than or equal to:
      • 2* cpu_count, for a cpu_count lower than 8
      • 1.5* cpu_count, for a cpu_count of 8 or more
    • Backup Archive Type - Specify tgz (recommended) to compress the backups before the upload. If tar is selected, then no compression will be done.
    • RMAN Backup Channel Count (Optional) - Specify number of RMAN staging channels. The minimum value is 1. The maximum value must be less than or equal to:
      • 2* cpu_count, for a cpu_count lower than 8
      • 1.5* cpu_count, for a cpu_count of 8 or more
    • Backup Encryption Password - Specify a password to encrypt the application tier file system, database tier file system, and database RMAN backup when TDE is not enabled.
    ===========================
    Enter OSS - Backup Details
    ===========================
    
    [Ctrl-B: Back, Ctrl-H: Main Menu]
    
    Backup Identifier Tag                 : EBS122EXAMPLE
    Backup Thread Count                   : 4
    Backup Archive Type ( tar | tgz )     : tgz
    RMAN Backup Channel Count             : 2
    Backup Encryption Password            : password
  9. On the "Enter Oracle Cloud Infrastructure Classic Proxy Details" screen, determine if you access the cloud service endpoint through a proxy server (option 1) or access it directly without through a proxy server (option 2). Choose option 2 in this example.
    =======================================================
    Enter Oracle Cloud Infrastructure Classic Proxy Details
    =======================================================
    
    [Ctrl-B: Back, Ctrl-H: Main Menu]
    
    1: Yes
    2: No
    
    Enter your choice from above list: 2                  

    Note: If your cloud service endpoint access is through a proxy server, choose option 1. On the "Enter Oracle Cloud Infrastructure Classic Proxy details" screen, enter the proxy details that you want to use to establish communication between the backup module server and the cloud service endpoint before proceeding to the next step.

    =========================================================
    Enter Oracle Cloud Infrastructure Classic Proxy details
    =========================================================
    
    [Ctrl-B: Back, Ctrl-H: Main Menu]
    
    Proxy Protocol           : https  			
    Proxy Host : www-proxy.example.com
    Proxy Port : 80
    Proxy user name :
    Proxy user password :
  10. Enter your Oracle Cloud Infrastructure Classic information:
    • Oracle Storage Cloud Service Endpoint - Specify the Oracle Cloud Infrastructure Object Storage Classic REST endpoint.
    • Oracle Cloud Identity Domain - Specify the Oracle Cloud Compute domain.
    • Target Database Type - Specify the Database Cloud Service property. Possible values are Compute, DBCS, or EXACS.
    ===================================================================================                   
    Migrate Oracle E-Business Suite - Enter Oracle Cloud Infrastructure Classic Details
    ====================================================================================
    [Ctrl-B: Back, Ctrl-H: Main Menu]
    Oracle Cloud User Name : john.smith@oracle.com Oracle Cloud User Password : password
    Oracle Storage Cloud Service Endpoint : https://domainname.storage.oraclecloud.com/v1/Storage-domainname Oracle Cloud Identity Domain : oracleebsexample
    Validating the details... Target Database Type - (Compute | DBCS | EXACS ): DBCS
  11. After entering required information, you are prompted to review the migration details you have specified earlier.

    Please note that the Mode field indicates the transfer location for the backup. It is displayed as either one of the following values based on your database release and target database type.

    • CDB - Environments with 12.1.0.2 databases where the target database service is DBCS or Exadata CS.
    • OSS - Environments with 12.1.0.2 databases where the target database service is Compute.
    =====================================================================
    Migrate Oracle E-Business Suite - Review  
    =====================================================================
    
    [Ctrl-B: Back, Ctrl-H: Main Menu]
    
    Mode                           : CDB
    Source Database Details:

    Host Name : demo.example.com
    OS User Name : oracle
    Stage Directory : /u01/install/stage/dbstage
    Context File : /u01/install/APPS/12.1.0/appsutil/EBSDB_apps.xml
    Source Application Tier Details:
    Hostname : demo.example.com
    OS User Name : oracle
    Stage Directory : /u01/install/stage/appstage Context File : /u01/install/APPS/fs1/inst/apps/EBSDB_apps/appl/admin/EBSDB_apps.xml OSS - Backup Details:
    Backup Identifier Tag : EBS122EXAMPLE Backup Thread Count : 4 Backup Archive Type : tgz RMAN Backup Channel Count : 2 Oracle Cloud Infrastructure Classic Details:

    Oracle Cloud User Name : john.smith@oracle.com
    Oracle Storage Cloud Service Endpoint : https://domainname.storage.oraclecloud.com/v1/Storage-domainname Oracle Cloud Identity Domain : oracleebsexample
    Target Database Type : DBCS ================================================= Proceed With Selected Action =================================================
    [Ctrl-B: Back, Ctrl-H: Main Menu]
    1: Yes 2: No Enter your choice from above list: 1

    Select option "1: Yes" to proceed with the migration.

Note: If for any reason EBSCloudBackup.pl fails and you need to rerun the script, it will continue from the point of failure.

Caution: If you interrupt processing with Ctrl-C, the restart capability may not function as expected.

This script performs the following validation tasks:

  • Validate OS level authentications.
  • Validate if the Oracle Database version is certified.
  • Validate if the database is archivelog enabled.
  • Validate Transparent Data Encryption (TDE) password-based checks, including wallet status and wallet type checks.
  • Validate if mandatory patches are present.
  • Create a database backup.
  • Execute remote calls to the applications tier to create a tar package to containing the applications files.
    • For Oracle E-Business Suite Release 12.2, this will include the contents of the EBSapps directory (which contains APPL_TOP, COMMON_TOP, OracleAS 10.1.2, and a packaged version of Oracle Fusion Middleware home) on the run file system.
    • For Oracle E-Business Suite Release 12.1.3, this will include contents of the APPL_TOP, COMMON_TOP, OracleAS 10.1.2, and OracleAS 10.1.3 directories.
  • Transfer the application tier tar package and database backup to a new container in your Object Storage Classic account.

Creating Your Oracle E-Business Suite Environment on Oracle Cloud From Your Backup

After you have backed up your environment using the Oracle E-Business Suite Cloud Backup Module, you will use the backup to create a new environment with your desired topology.

Refer to the these instructions in section "Creating a New Environment from a Backup" of the Managing Oracle E-Business Suite on Oracle Cloud Infrastructure Classic Using the EBS Cloud Admin Tool Oracle by Example tutorial.

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

If you chose to lift and shift an environment with Oracle Database 11.2.0.4 from on-premises to DBCS Oracle 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 Oracle 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 in this section 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 Compute Classic 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, test1226-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, test1226-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 Oracle XML Gateway, perform the steps in "Configure Oracle 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 (DN) 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 (CN) 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 illustrate 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.
    The example below uses three certificate files:
    • The server certificate, server.crt
    • An intermediate CA certificate, intCA.crt
    • The CA's root certificate, rootCA.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 Oracle E-Business Suite 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 Oracle E-Business Suite 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-Cloning Tasks

Apply Oracle E-Business Suite Patches

Apply the listed Oracle E-Business Suite patches to the releases shown:

Apply One-Off Database Patches

If you applied any one-off database patches to your on-premises database (that is, in addition to any recommended by ETCC), you must now reapply them to your database in DBCS or Exadata CS.

    • For Oracle E-Business Suite Release 12.2, ETCC recommended database patches have been applied. If you have applied any additional one-off database patches, you must re-apply the additional one-off patches to your database in DBCS or Exadata CS after the restore is complete.
    • For Oracle E-Business Suite Release 12.1, you must re-apply the additional one-off patches to your database in DBCS or Exadata CS after the restore is complete.

Configure Workflow Mailer (Optional)

In order to send Oracle Workflow mailer notifications by email, you must configure a mail server that your Oracle E-Business Suite environment can access. See the Oracle by Example tutorial Configuring Oracle Workflow Notification Mailer with Mail Servers for Oracle E-Business Suite on Oracle Cloud Infrastructure Classic Using the EBS Cloud Admin Tool.

Configure Optional External Integrations

You may have deployed optional external integrations with your Oracle E-Business Suite environment. You can use the EBS Cloud Admin Tool to assist with configuring the following:

Want to Learn More?

Change Log

Date Description
2019-04-24
  • Updated footer.
2018-09-14
  • Made various updates throughout document for 18.3.1 release.
  • Changed the section title from "Installing and Configuring the EBS Cloud Backup Utility On-Premises" to "Installing the Oracle E-Business Suite Cloud Backup Module On-Premises", added installation information, and removed cln.props table.
  • Changed the section title from "Backing Up Your Environment Using the EBS Cloud Backup Utility" to "Backing Up Your Environment Using the Oracle E-Business Suite Cloud Backup Module" and updated the content with the backup module menu screens.
2018-08-10
  • Updated "Before You Begin" section with revisions for database patch set updates and bundle patches.
2018-07-06
  • Updated "Before You Begin" section with information for Oracle E-Business Suite Release 12.1.3 with Oracle Database Release 12.1.0.2 on Database Cloud Servce Single Instance, Database Cloud Service Oracle RAC Database, and Exadata Cloud Service.
  • Made various minor grammatical updates throughout document.
2018-06-29
  • Minor formatting enhancements.
2018-06-26
  • Updated content in "Before You Begin" section by replacing January 2018 Database Bundle Patch with April 2018 Database Bundle Patch in the Database Cloud Service (DBCS) Oracle RAC Database table.
  • Added Oracle E-Business Suite 12.1.3 information in "On-Premises Application Tier Stage Area Creation" subsection of "Creating Stage Areas and Prepare to Take a Backup" section.
  • Added new section "Implementing Workaround for Oracle Database 11.2.0.4 on DBCS Oracle RAC (Conditional)."
2018-06-20
  • Updated content in "Before Your Begin" section by adding database option information.
  • Updated Step 4 cln.props table in "Installing and Configuring the EBS Cloud Backup Utility On-Premises" section.
2018-06-12
  • Made various updates throughout document for 18.2.1 release.
  • Updated content and tables in "Before Your Begin" section.
  • Removed sections "Validating SSH Connectivity to the EBS Cloud Admin Tool VM (Conditional)" and "Creating the EBS Cloud Admin Tool VM Stage Area (Conditional)." The method to create a backup to a stage area on the provisioning VM and subsequent operations have been obsoleted.
  • Made updates to "Installing and Configuring the EBS Cloud Backup Utility On-Premises" section, including changes to cln.properties table.

2018-05-18

  • Added Patch 26592812:R12.FND.C as required patch for Database 12.1.0.2 in DBCS and Exadata tables of "Background" section.

2018-05-17

  • Updated database patch requirements for Database Cloud Service (DBCS) Single Node table in "Background" section.

2018-04-30

  • Updated required database patch requirements in tables within the "Before You Begin" section.

2018-03-27

  • Updated conditional step in section "Backing Up Your Environment Using the EBS Cloud Backup Utility."

2018-02-20

  • Updated tables in "Before You Begin" section.
  • Changed title from "Determining Cloud Service REST Endpoints" to "Determining Cloud Service Account Details" and updated content of section.
  • Updated various screensots and content per changes in 18.1.1 release.
  • Cleaned up cln.props table.

2017-12-20

  • Updated Background section table and associated notes.

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.
  • Updated table in "Background" section.
  • Updated "Determining Cloud Service REST Endpoints" section and various locations in doc to reflect service name changes.

2017-10-12

  • Corrected FMW_Home to FMW_HOME in command lines in document.
  • Removed typo in "Deploy a CA-Issued Certificate (Conditional)" subsection.

2017-09-27

  • Removed content from "Creating Your Oracle E-Business Suite Environment on Oracle Cloud From Your Backup" and made reference to the "Managing Oracle E-Business Suite on Oracle Cloud Using the EBS Cloud Admin Tool" OBE
  • Added "Enabling Oracle OLAP, Partitioning, and Spatial Options (Conditional)" section and relevant note in Background section.
  • Made various updates for 1.7.3 release.

2017-08-15

  • Updated various text and EBS Admin Tool UI screens throughout document for 1.7.2 release.
  • Updated minimum requirements table.
  • Updated "Securing Access to Your Environment."
  • Updated screens in "Creating the EBS Cloud Admin Tool VM Stage Area" and "(Conditional) Creating the EBS Cloud Admin Tool VM Stage Area" sections.
  • Updated "Limit HTTP Access to a Subset of IP Addresses" to HTTPS and made related changes in content.
  • Updated content with TDE information in "Time to Complete" and "Background" subsections.
  • Updated step in "Creating Your Oracle E-Business Suite Environment on Oracle Cloud From Your Backup."
  • Added row for OC_CLOUD_BACKUP_DIR in cln.props table.
  • Updated steps in section "Backing Up Your Environment Using the EBS Cloud Backup Utility."
  • Updated patches required in "Performing Post-Cloning Tasks."

2017-06-30

  • Made changes to "Creating Your Oracle E-Business Suite Environment on Oracle Cloud From Your Backup" with modified DBaaS backup instructions; also updated the Installation Summary screenshot.

2017-06-08

  • Added ETCC requirement information to "Background" subsection.
  • Updated description of CUSTOM_PRIVATE_KEY_LOC.STAGE in cln.props table of "Installing and Configuring the EBS Cloud Backup Utility On-Premises."

2017-05-03

  • Made changes to table in "What Do You Need?" section.
  • Updates section "Validating SSH Connectivity to the EBS Cloud Admin Tool VM."
  • Made minor updates to links.

2017-05-02

  • Updated "Background" section notes, clarifying current cloning/deleting limitations on Exadata CS and use of the STAGE area not being supported on on-premises EBS environments running Database 12c.
  • Made changes to table in "What Do You Need?" section.
  • Added content to updated "Deploying or Updating the Oracle E-Business Suite Cloud Admin Tool" section.
  • Updated "Installing and Configuring the EBS Cloud Backup Utility On-Premises" increasing amount of free space need for patch to 500MB.
  • Fixed typo in "Creating the EBS Cloud Admin Tool VM Stage Area."
  • Added note to "Creating Your Oracle E-Business Suite Environment on Oracle Cloud From Your Backup" section to include note about updating the EBS Cloud Admin Tool to the latest codeline; inserted additional information to Footnote 2 in step 13; updated UI; added step 15 concerning reserved IP selection for application tier.
  • Updated to 2017-03-28 OBE template.

2017-04-19

  • Updated Certified Oracle E-Business Suite and Database Releases table in Background section, changing references from AD-TXK Delta 8 to AD-TXK Delta 9.
  • Added note in Background section to specify that this OBE supports the cloning of Linux source systems to Oracle Linux target systems.

2017-03-31

  • Added note in "Background" section concerning provisioning multiple databases on Exadata CS.
  • Updated Environment Details screenshot in "Creating Your Oracle E-Business Suite Environment on Oracle Cloud From Your Backup" section.

2017-03-30

  • Updated "Background" and "What Do You Need?" sections with Exadata CS content.
  • Added note in "Background" section concerning EBS 12.2 with Database 12.1.0.2.
  • Updated steps in "Creating Your Oracle E-Business Suite Environment on Oracle Cloud From Your Backup."
  • Added "Securing Access to Your Environment" section.
  • Moved "Change Passwords" content into new "Securing Access to Your Environment" section.

2017-03-27

  • Made clarifications to the listing of certified EBS and Database releases in the table found in "Background" section.
  • Added clarification to table in "What Do You Need?" section.
  • Updated cln.props table in "Installing and Configuring the EBS Cloud Backup Utility On-Premises."
  • Updated steps in section "Creating Your Oracle E-Business Suite Environment on Oracle Cloud From Your Backup."
  • Made changes to listing of patches in the "Apply Oracle E-Business Suite Patches" subsection.
  • Made various minor grammatical updates throughout document.

2017-03-16

  • Updated "Purpose" statement.
  • Updated screen in "Creating the EBS Cloud Admin Tool VM Stage Area" section.
  • Added prerequisite to "Backing Up Your Environment Using the EBS Cloud Backup Utility" section.

2017-03-14

  • Rearranged order of process steps.
  • Added "Determining Cloud Service Endpoints" section.
  • Updated "What to Learn More?" section references.
  • Updated steps in "Creating the EBS Cloud Admin Tool VM Stage Area."

2017-03-03

  • Updated links in "What Do You Need?" section.
  • Initial publication.