EBS Clone using Cloud Manager

Clone an Oracle E-Business Suite Environment with the Database on Oracle Cloud Infrastructure Compute

This cloud-native cloning feature, applicable for Oracle E-Business Suite environments in which the database runs on Oracle Cloud Infrastructure Compute, has the following key attributes:

• You can run the cloning procedure on Compute either when the Oracle E-Business Suite services (application tier and database tier) are running, or when they are shut down.
• When cloning on Compute, you can assign the clone a different database tier shape than the source environment.
• If the source environment has an application tier node and database on a single Compute VM, then the clone will also have its application tier node and database on a single Compute VM.
• On Compute, the clone inherits the middleware technology licensing model of the source environment, either Bring Your Own License (BYOL) or Universal Credit Management (UCM).

Access the Clone Environment Page

1. Click the Navigator icon and select Environments.
2. For a successfully created environment, click the Action icon and select Clone.
3. Alternatively, in the environment details page for a single environment, click the Clone button.

1. Enter Environment Details

On this page the details for the source environment are shown:

• Environment name
• EBS Compartment
• Network Profile
• Availability Domain
• File System Type

1. Enter values for the clone details:

• Environment Name: Enter a name for your environment. For example: EBSClone
• EBS Compartment: The compartment for the cloned environment. You can select an EBS compartment that is different than that for the source environment.
• Network Profile: Select a network profile for the cloned environment. The list of available network profiles is dependent on the EBS compartment that you selected above. From this list of network profiles, select a network profile that includes the same Availability Domain as that of the source.

Note that if you are cloning a File Storage service-enabled environment, you can choose a different network profile than that of the source environment, but it also must have File Storage service enabled.

Note: The source environment and the cloned environment can also have different mount targets.

• Source Apps Password: Enter the password for the Oracle E-Business Suite APPS schema for the source environment.
• Source WebLogic Server password: For an Oracle E-Business Suite Release 12.2 environment only, enter the Oracle WebLogic Server administration password.

1. Optionally enter tagging information in the Tags region.

• Tag Namespace: Select a predefined tag namespace or select None (add a free-form tag).
• Tag Key: Enter the name you use to refer to the tag.
• Value: Enter the value for the tag key.

1. Click Next.

Enter Database Tier Information for Oracle Cloud Infrastructure Compute (Compute VM)

If your cloned environment is on Oracle Cloud Infrastructure Compute (Compute VM), then follow these steps to enter the database tier information as required.

1. Enter a Database Name.
2. Enter the admin password for the database of your cloned environment. This password is used for the SYS user as well and it must not contain the username 'SYS'. If TDE is enabled for the environment, then this password is also used as the TDE wallet password. The password must be 9 to 30 characters and contain at least two uppercase, two lowercase, two special, and two numeric characters. The special characters must be underscores (_), number signs (#), or hyphens (-). Re-enter the password in the next field to confirm it.
3. Enter a new APPS password for your cloned environment. The password must contain only alphanumeric characters.
4. If Oracle E-Business Suite System Schema Migration has been completed on the source environment, then enter a new EBS_SYSTEM password. This password must contain alphanumeric characters only. For more information on the Oracle E-Business Suite System Schema and the EBS_SYSTEM password, see My Oracle Support Knowledge Document 2755875.1, Oracle E-Business Suite Release 12.2 System Schema Migration.
5. For a Release 12.2 environment, enter a new WebLogic Server password for your cloned environment.
6. The following information is provided as read-only:

• Database Service Type
• Logical FQDN

1. You can optionally update the following:

• VM Shape
• Number of OCPUs
• Amount of memory (GB)

1. Click Next

Enter Application Tier Information

Zone information from the source environment will appear by default.

You can change the shape for an application tier node

1. Toggle Start Application Tier Services to indicate whether application tier services should start when the clone is complete.
2. You must edit the zones. Click Edit for each zone.
3. Enter the Zone name. Note that you cannot change the type of the zone.
4. In the Web Entry Point region, choose one of the following web entry types: New Load Balancer (LBaaS), Use OCI Load Balancer to select an existing OCI load balancer, Manually Configured Load Balancer to select a manually deployed existing load balancer, or Application Tier Node to choose the primary application tier as the entry point.
5. If you chose New Load Balancer as the web entry type, a new flexible shape load balancer will be created. Select the maximum bandwidth for your new load balancer. For example: 100 Mbps. The minimum bandwidth will default to 10 Mbps.
6. Enter values for the following web entry properties.

• Protocol: Select the protocol for access to the environment, either http or https.
• Hostname: Enter a hostname. For example: myhost
• Domain: Enter a domain name. For example: com
• Port: Select the port. If there is no load balancer, then the port is automatically populated depending on the protocol: 8000 for http and 4443 for https. Otherwise, select the appropriate port for use with your load balancer, such as 80for http or 443 for https. Note that to allow access to the Oracle E-Business Suite login URL, your network administrator must define an ingress rule in the load balancer security list configuring the load balancer port to be open for public access. See Create Network Resources For Deploying Oracle E-Business Suite Environments.

1. Under Storage, the File System Type is the same as that for the source environment.

1. Enter the details

If your source environment is using File Storage service, then you are prompted for the File Storage Mount Target. If the File Storage Mount Target for the network profile specified earlier matches any of the Mount Targets in the network compartment created on the Oracle Cloud Infrastructure, then that Mount Target appears in the list.

For a Shared File System Type, you can also specify Mount Options. Default parameters are shown. You can edit these options, but specifying a mount option or parameter that is not supported or recommended for a shared storage file system deployment may result in a provisioning failure. Exercise extreme caution when editing these parameters, as options are not validated in this page.

1. Review the properties for each node in the Application Tier Nodes information.

• Logical FQDN
• Shape: You can change the shape of the node. When choosing a flexible shape, for example, VM.Standard.E3.Flex, use the sliders to choose the number of OCPUs and the amount of memory (GB).
• Storage
• Fault Domain

1. Click Save Zone.
2. When you are finished editing your zones, click Next.

1. Enter extensibility options.

Specify Your Extensibility Options

You can optionally extend the cloning job to meet your own requirements. By default, Oracle E-Business Suite Cloud Manager follows a standard job definition for cloning. However, Oracle E-Business Suite Cloud Manager administrators can also create extended job definitions that include additional tasks as part of the cloning job. In this case you can select the appropriate extended job definition for Oracle E-Business Suite Cloud Manager to follow when cloning your source environment. If you select an extended job definition, you may need to enter values for input parameters required by the additional tasks in that job definition.

Additional Information: For more information on using the Extensibility Framework to extend job definitions, see Set Up the Extensibility Framework.

Additionally, whether you are using the standard cloning job definition or an extended job definition, you can choose to have Oracle E-Business Suite Cloud Manager pause at specified points during the cloning job. For example, if you want to perform your own validations after a particular phase before allowing Oracle E-Business Suite Cloud Manager to proceed to the next phase, you can add a pause at that point. You can then resume the cloning job when you are ready to proceed. See Monitor Job Status.

Specify Your Job Definition

1. Optionally select an extended job definition for cloning your environment in the Job Definition field.
2. In the Task Parameters tab, specify any parameter values required for the additional tasks in the job definition. Some parameters may include default values, which you can override as needed.

Specify Your Job Definition Details

1. Click the Job Definition Details tab. This tab displays a list of the phases in the job definition and the tasks within each phase.
2. To specify that Oracle E-Business Suite Cloud Manager should pause its processing before a particular phase, click the Actions icon next to that phase, and then select Add Pause.

Note: Pauses occur before the phase at which they are defined.

1. Click Next.

1. Enter ssh Key details.

Enter SSH Keys

Optionally upload SSH keys for users.

Note: You cannot add keys after the provisioning process is completed.

1. Click Add Key.
2. Specify the tiers for the SSH key. Choose All Tiers, Application Tier, or Database Tier.
3. Specify the pertinent OS User type. Choose All Users, Operating System Administrator, or Application Administrator.
4. Upload the SSH key file. The file name will default in.
5. The system will validate the SSH key. Click Next to continue.

1. Review Your Colone Environment Flow Details

Review the details for the cloned environment on this page.

1. Review the following:

• Clone Details: Environment Name Installation TypeEBS VersionDB Version Network Profile
• Database Details: Database Service Type Shape Enable TDE Database Name PDB Name Node Count DB Software Edition License Type
• Application Tier Details: Middleware Licensing Model Start Application Services (Yes/No)Zone information, including Web entry details Storage information. For a shared file system, the File Storage service mount target and mount options are shown Information on nodes Details for Custom Tasks or Paused Tasks, if any SSH Keys information, if any

1. To create the cloned environment, click Submit.
2. You can check the status of the job to clone the source environment in the Jobs page.

Perform Post-Cloning Tasks

After the environment is successfully cloned, perform any necessary post-cloning steps and access the cloned environment following the instructions provided in Perform Post-Provisioning and Post-Cloning Tasks.

Disclaimer: "The views expressed in this post are my own and do not necessarily reflect the views of Oracle."