This chapter covers the following topics:
You can host and run your Oracle E-Business Suite Release 12.2 and Release 12.1.3 environments on Oracle Cloud Infrastructure Classic. My Oracle Support Knowledge Document 2066260.1, Getting Started with Oracle E-Business Suite on Oracle Cloud, is the primary source of information to start using Oracle E-Business Suite on Oracle Cloud Infrastructure Classic.
Follow the instructions in the getting started note to provision a new E-Business Suite environment on Oracle Cloud Infrastructure Classic or lift and shift your existing Oracle E-Business Suite environments to Oracle Cloud Infrastructure Classic. Once you have the environment up and running on Oracle Cloud Infrastructure Classic, you can monitor and manage these environments using the Oracle Application Management Suite.
Note: Also, see the Oracle E-Business Suite on Oracle Cloud web site for more references.
Oracle Application Management Pack for Oracle E-Business Suite has the capability to monitor and manage Oracle E-Business Suite environments residing on Oracle Cloud Infrastructure Classic.
After you provision a new Oracle E-Business Suite environment or lift and shift your existing Oracle E-Business Suite environment on Oracle Cloud Infrastructure Classic, you can use the Oracle Application Management Pack to do the following:
Discover Oracle E-Business Suite environments on Oracle Cloud
Monitor and manage Oracle E-Business Suite environments
Manage and compare configurations
Manage patches and patch migrations
Manage customizations and migrations
The Oracle Application Management Pack for Oracle E-Business Suite provides a command-line interface for the batch discovery of multiple Oracle E-Business Suite environments on Oracle Cloud Infrastructure Classic. This feature uses Oracle Enterprise Manager Command Line Interface (EM CLI).
Note: See the Enterprise Manager Center Command Line Interface documentation to understand more about EM CLI.
In order to discover Oracle E-Business Suite environments on Oracle Cloud Infrastructure Classic using EM CLI, you must complete the following sequence of steps (which are described in further detail in this section):
Complete prerequisite tasks.
Discover the Orchestration virtual machine.
Discover the Oracle E-Business Suite environment.
Before you perform a batch discovery of multiple Oracle E-Business Suite environments on Oracle Cloud using command-line Discovery, verify that the following tasks are completed:
Log in to each virtual machine (VM). This includes the Orchestration VM, Oracle Traffic Director (OTD) VM, application tier VM, and database tier VM.
On each VM, create the file oraInst.loc.em in the home directory of the oracle user. The contents of the file must be:
inst_group=oinstall inventory_loc=<location where the agent inventory needs to be stored>
Synchronize the EM CLI on the host where you executed the EM CLI command.
Set the Normal Host preferred credentials for the OMS host.
Configure a management agent as the hybrid cloud gateway agent to communicate with Oracle Cloud. See "Configuring a Management Agent as a Hybrid Cloud Gateway Agent" in the Oracle Enterprise Manager Cloud Control Administrator's Guide.
Note: Discovery can only be performed if the agent is installed as the oracle user.
Add the public key of the Orchestration VM's oracle OS user to its own authorized keys.
Note: Public and private keys for the oracle user on the Orchestration VM will be generated automatically when the first Oracle E-Business Suite instance is provisioned using the Orchestration VM and EBS Cloud Admin Tool
Use the SSH private key of the Orchestration VM's oracle OS user to create Global Named Credentials of type 'SSH Key Credentials' for the target type 'Host'. This will be used as agent credentials.
Create Global Named Credentials of type 'Database Credentials' for the target type 'Database Instance'. This will be the database monitoring credential.
Create Global Named Credentials of type 'E-Business Suite Database Credentials' for the target type 'Oracle E-Business Suite'. This will be the EBS monitoring credentials.
Create Global WebLogic Admin Named Credentials of type 'Oracle WebLogic Credentials' for the target type 'Oracle WebLogic Server'. The Oracle Application Management Pack uses this to start/stop WLS managed servers.
Use the EM CLI verb discover_ebs_opc to discover orchestration VM instances. The details of these instances must be provided as an XML file. Execute the following command to perform the discovery:
emcli discover_ebs_opc -input_file=ebs_opc_discovery_file:"<fully qualified path of input.xml>"
You can track the successful submissions from the Oracle Enterprise Manager UI to monitor jobs using the Job Name displayed as output of the previous command.
Note: If you have applied BP 1 on top of Oracle Application Management Pack 13.1.1.1.0, you can discover the Orchestration VM by using the Agent Gold Image. Two new elements, UseGoldAgentImage and GoldIMageVersion, have been introduced as input XML to support Gold Agents.
<?xml version="1.0" encoding="UTF-8" ?>
<!--Required elements are marked with Required. All other elements are optional. -->
<!--Required. Root element -->
<ProvisionedVMList>
<!-- Global parameters will be applied to all instances if not overridden. -->
<Global>
<!--Target name of the agent which is configured as Hybrid Cloud Gateway Agent to communicate with Oracle Cloud. -->
<GateWayAgent></GateWayAgent>
<!--Named credential of the Oracle Compute Cloud account. Use the Oracle Public Compute Cloud Username / Password to create Global Named credentials of type 'Oracle Public Cloud Domain Credentials' for target type 'Oracle Public Cloud Provisioned VM' -->
<OPCAccNamedCreds></OPCAccNamedCreds>
<!--OS Credentials with which Agent will be installed-->
<AgentUsrSshKeyCredName></AgentUsrSshKeyCredName>
<!--OS Credentials with which Agent will be installed same as AgentUsrSshKeyCredName-->
<AgentUsrSudoSshKeyCred></AgentUsrSudoSshKeyCred>
<!--OMS Oracle home directory path. This folder should contain "bin/emcli" -->
<OmsHome></OmsHome>
<!-- Agent install directory -->
<AgentInstallDirectory></AgentInstallDirectory>
<!--EM User name who has access to above named credentials. These credentials will be used login to emcli -->
<EmUsr></EmUsr>
<!--EM User Password -->
<EmPwd></EmPwd>
<!--Support to install gold agent is available starting from the BP1 on top of 13.1.1.1.0-->
<UseGoldAgentImage>Y</UseHoldAgentImage>
<GoldIMageVersion>version1</GoldIMageVersion>
</Global>
<!--Required, can repeat 1 to N times. This section contains Orchestration VM specific information. -->
<ProvisionedVM>
<!--Required. Oracle Pulbic Cloud Identity Domain Value -->
<OcIdentityDomain></OcIdentityDomain>
<!--Required. Oracle Public Cloud End Point URL -->
<OcComputeEndPoint></OcComputeEndPoint>
<!--Required. Public Host Name on which Orchestration VM installed -->
<PublicHostName></PublicHostName>
</ProvisionedVM>
</ProvisionedVMList>
The EM CLI verb discover_ebs_opc_env must be used to discover an Oracle E-Business Suite environment. The details of the environment must be provided as an XML file.
Execute the following command to perform the discovery:
emcli discover_ebs_opc_env -input_file=ebs_opc_env_discovery_file:"< fully qualified path of ebs_opc_env_discovery_file.xml>"
See the following schema with which the XML must be built and sample XML with comments included about each element.
Note: If you have applied BP 1 on top of Oracle Application Management Pack 13.1.1.1.0, you can install the agent using gold image. Two new elements have been introduced in the input XML to support the same UseGoldAgentImage and GoldIMageVersion.
<EnvironmentList>
<!--Pass the OMS Oracle home directory path. This folder should contain "bin/emcli" -->
<OmsHome></OmsHome>
<!--EM User name. Required to login to emcli" -->
<EmUsr></EmUsr>
<!--EM User password. Required to login to emcli -->
<EmPwd></EmPwd>
<!--Orchestration VMs discovered in EM -->
<ProvisionedVM>
<!--Orchestration VM target name -->
<ProvisionTargetName></ProvisionTargetName>
<!-- Global parameters will be applied to all instances if not overridden. -->
<Global>
<!--OS Credentials with which Agent will be installed-->
<AgentUsrSshKeyCredName></AgentUsrSshKeyCredName>
<!--OS Credentials with which Agent will be installed same as AgentUsrSshKeyCredName. -->
<AgentUsrSudoSshKeyCred></AgentUsrSudoSshKeyCred>
<!--Configure a Management Agent as Hybrid Cloud Gateway Agent to communicate with Oracle Cloud.-->
<GateWayAgent></GateWayAgent>
<!-- Database monitoring credentials. Required to add database instance to EM -->
<DbMonCredName></DbMonCredName>
<!-- EBS monitoring credentials. Required to discover EBS instance in EM -->
<EBSMonCredName></EBSMonCredName>
<!-- WebLogic Admin credentials. Required to discover EBS instance in EM -->
<WLSAdminCredName></WLSAdminCredName>
<!--Support to install gold agent is available starting from the BP1 on top of 13.1.1.1.0-->
<UseGoldAgentImage>Y</UseGoldAgentImage>
<GoldIMageVersion>version1</GoldIMageVersion>
</Global>
<Environment>
<!-- Environment provisioned in OPC. Get the details from the orchestration VM -->
<Name></Name>
<!-- Database target name in EM -->
<DbName></DbName>
<!-- Agent installation directory -->
<AgentInstallDirectory></AgentInstallDirectory>
</Environment>
</ProvisionedVM>
</EnvironmentList>