This chapter covers the following topics:
This section describes the steps required for discovering Oracle E-Business Suite instances provisioned on Oracle Cloud Infrastructure (OCI) using Hybrid Cloud Agents. Refer to "Enabling Hybrid Cloud Management" in the Oracle Enterprise Manager Cloud Control Administrator's Guide for more information.
The database for an Oracle E-Business Suite instance in OCI is a pluggable database when:
The Oracle Database version is 19c.
The Oracle Database version is 12.1.0.2 and the database is on a VM DB System or an Exadata DB System.
At this time, Oracle Application Management Pack does not support Oracle E-Business Suite discovery using pluggable database targets. However, by using the "Database SID" as the pluggable database name, we can discover Oracle E-Business Suite instances for which the database is a pluggable database.
If an Oracle E-Business Suite instance on OCI is using load balancer and is discovered in Oracle Enterprise Manager, the load balancer target is not monitored or discovered in Enterprise Manager.
When installing Enterprise Manager agents on Oracle E-Business Suite nodes, the fully qualified domain name (FQDN) should be resolvable from the OMS host and the gateway agent host.
All agents are installed using the oracle user.
Install the Enterprise Manager Agent on the host which from which you intend to communicate with Oracle E-Business Suite nodes on OCI.
Register the agent created above as "Hybrid Cloud Gateway Agent" using a command like:
emcli register_hybridgateway_agent -hybridgateway_agent_list="<agent host>:<agent port>" -ignore_network_check
Ensure that the FQDN of each of the Oracle E-Business Suite nodes resolves to the Public IP of the Oracle E-Business Suite node from the OMS Host and Hybrid Cloud Gateway Agent host.
Create a Named Credential which will be used to connect to Oracle E-Business Suite Nodes, using steps described in Creating a Named Credential with following properties:
Authenticating Target Type: Host
Credential type: SSH Key Credentials
Scope: Global
User Name: oracle
SSH Private Key: <Content of /u01/install/APPS/.ssh/id_rsa on Oracle E-Business Suite Cloud Manager VM or Oracle E-Business Suite Cloud Admin Tool VM from where the Oracle E-Business Suite instance is provisioned or any other private key with which we can connect to Oracle E-Business Suite Node>
Add ingress rules to the security lists associated with the subnets on which Oracle E-Business Suite App nodes and Oracle E-Business Suite database nodes are created (this information is provided while provisioning the Oracle E-Business Suite instance on OCI), using steps described in: Adding an Ingress Rule, with the following property:
Source Type: CIDR, Source CIDR: <CIDR that matches OMS Host IP and Hybrid Cloud Gateway Agent IP>, IP Protocol: TCP, Source Port Range: All, Destination Port Range: 22
Deploy the agent on all the Oracle E-Business Suite nodes, using the steps described in Deploying a Hybrid Cloud Agent.
For Oracle Database 19c, follow the steps described in Adding a Database Instance Target, but while adding the target, use "Database SID" as the pluggable database name provided while provisioning the Oracle E-Business Suite instance.
Note: The "Database SID" must be specified as the pluggable database name for Oracle E-Business Suite discovery to work.
For Oracle Database 12.1.0.2 or 11.2.0.4, follow the steps described in Adding a Database Instance Target.
For Oracle Database 19c or 12.1.0.2, follow the steps as described in Adding a Database Instance Target, but while adding the target, use "Database SID" as the pluggable database name provided while provisioning the Oracle E-Business Suite instance.
Note: The "Database SID" must be specified as the pluggable database name for Oracle E-Business Suite discovery to work.
For Oracle Database 11.2.0.4, follow the steps described in Adding a Database Instance Target.
Add a cluster target by performing steps in Adding a Cluster Target.
Add a cluster database target using the following instructions:
From the Enterprise Manager Console, in the Targets menu, select All Targets.
Search for and select the cluster target added above.
From the Cluster menu, select Discover Databases.
Click the Next button.
In the Database Discovery: Results page, under the "Cluster Database" section, select the check box associated with target listed, click on Configure.
In the Configure Cluster Database dialog, on the General tab, note down values of all the fields.
Click on the Instances tab.
Note down all values of all fields displayed for the two instances. Exactly two instances will be displayed.
Click the Cancel button.
Observe that you are on the Add Targets Manually page. You can navigate to this page by using the Setup menu, selecting Add Target, and then selecting Add Targets Manually.
Click on the Add Target Manually button.
Select target type as the Cluster Database.
Select/Enter Host as the first node in the cluster (host name can be derived from the values noted down in Instances tab above).
Click on the Add ... button.
Specify all values as noted in General tab above, except for the Service Name field, For the "Service Name" field, provide the pluggable database name provided while provisioning Oracle E-Business Suite instance.
Note: You must specify the pluggable database name for the Service Name for Oracle E-Business Suite Discovery to work.
Enter the dbsnmp user password.
Note: Ensure that the dbsnmp user account is working. You might need to unlock the user and set the password on the Oracle E-Business Suite database.
Add two instances with the properties as noted down in Instances tab above, except for the Database SID field. For the Database SID field, provide the pluggable database name provided while provisioning Oracle E-Business Suite instance.
Click on the Next button.
Click on the Submit button.
Click on the Close button in confirmation window.
Add a cluster target by performing the steps in Adding a Cluster Target.
Add a cluster database target using the following instructions:
From the Enterprise Manager console, in the Targets menu, select All Targets.
Search for and select the cluster target added above.
In the Cluster Target Home page, from the Cluster menu, select Discover Databases.
Click the Next button.
In the Database Discovery: Results page, under the "Cluster Database" section, select the check box associated with the target listed, specify the dbsnmp user password, and click Next.
Note: Ensure the dbsnmp user account is working. You might need to unlock the user and set the password on the Oracle E-Business Suite database.
Click the Save button.
Click the Close button in the confirmation window.
Add the cluster target by performing the steps in Adding a Cluster Target.
Add a cluster database target using the following instructions:
From the Enterprise Manager Console, in the Targets menu, select All Targets.
Search for and select the cluster target added above.
From the Cluster menu, select Discover Databases.
Click on the Next button.
In the Database Discovery: Results page, under the Cluster Database section, select the check box associated with the database you intend to discover and click the Configure button. Note that there can be multiple cluster databases listed based on the number of databases installed on Exadata DB System. The database name would have been provided while provisioning the Oracle E-Business Suite instance.
In the Configure Cluster Database dialog, on the General tab, note down values of all the fields.
Click on the Instances tab.
Note down all values of all fields displayed for the two instances. Exactly two instances will be displayed.
Click on the Cancel button.
Observe that you are on the Add Targets Manually page. You can navigate to this page by using the Setup menu, selecting Add Target, and then selecting Add Targets Manually.
Click on the Add Target Manually button.
Select target type as "Cluster Database".
Select/Enter Host as the first node in the cluster (hostname can be derived from the values noted down in Instances tab above).
Click on the Add ... button.
Specify all values as noted in the General tab above, except for the Service Name field. For the Service Name field, enter the pluggable database name provided while provisioning the Oracle E-Business Suite instance.
Note: You must specify the pluggable database name as the Service Name for Oracle E-Business Suite Discovery to work.
Enter the dbsnmp user password.
Note: Ensure that the dbsnmp user account is working. You might need to unlock the user and set the password on the Oracle E-Business Suite database.
Add two instances with the properties as noted down in Instances tab above, except for the Database SID field. For the Database SID field, provide the pluggable database name provided while provisioning Oracle E-Business Suite instance.
Click on the Next button.
Click on the Submit button.
Click on the Close button in confirmation window.
Add the cluster target by performing the steps described in Adding a Cluster Target.
Add a cluster database target using the following instructions:
From the Enterprise Manager console, in the Targets menu, select All Targets.
Search for and select the cluster target added above.
In the cluster target home page, from the Cluster menu, select Discover Databases.
Click the Next button.
In the Database Discovery: Results page, under the Cluster Database section, select the check box associated with the database you intend to discover and click the Configure button. Note that there can be multiple cluster databases listed based on the number of databases installed on Exadata DB System. The database name would have been provided while provisioning the Oracle E-Business Suite Instance.
Provide the dbsnmp user password, and click Next.
Note: Ensure that the dbsnmp user account is working. You might need to unlock the user and set the password on the Oracle E-Business Suite database.
Click the Save button.
Click the Close button in the confirmation window.
Follow the steps described in Discovering Oracle E-Business Suite.
This section describes the steps required for manually discovering Oracle E-Business Suite environments provisioned in Oracle Cloud Infrastructure Compute.
In order to manually discover Oracle E-Business Suite environments provisioned on Oracle Cloud Infrastructure, you must complete the following sequence of steps, which are described in further detail in this section:
Ensure prerequisites are fulfilled.
Take inventory of port numbers which will be opened from the Oracle E-Business Suite nodes, which will be used in later steps.
Create ingress rules in Oracle Cloud Infrastructure to open the "Enterprise Manager Upload Http SSL Port" from the Oracle E-Business Suite nodes to the OMS host and add corresponding firewall rules to the OMS host.
Create ingress rules in Oracle Cloud Infrastructure to open the required ports from OMS to the Oracle E-Business Suite nodes.
Add firewall rules on corresponding application, database nodes corresponding to the ingress rules that were created.
Ensure that fully qualified domain name of each of the Oracle E-Business Suite nodes is resolvable from the OMS host and the fully qualified domain name of the OMS host is resolvable from each of the Oracle E-Business Suite nodes.
Create required named credentials to connect to the Oracle E-Business Suite nodes.
Manually install a management agent on all Oracle E-Business Suite node.
Manually add Oracle E-Business Suite database related targets.
Manually discover the Oracle E-Business Suite instance.
Before you perform a manually discovery of Oracle E-Business Suite environments provisioned in Oracle Cloud Infrastructure Compute, verify that the following requirements are fulfilled:
Ensure that the Oracle E-Business Suite instance was provisioned using the EBS Cloud Admin Tool or Oracle E-Business Suite Cloud Manager.
From the OMS host, you should be able to connect using SSH to each of the Oracle E-Business Suite nodes. Adding the required ingress rule for this communication to work is covered in the following sections.
The database for the Oracle E-Business Suite instance in Oracle Cloud Infrastructure is a pluggable database (PDB) when:
The Oracle Database is 19c.
The Oracle Database is 12.1.0.2 and the database is on a VM DB System or an Exadata DB System.
At this time, Oracle Application Management Pack does not support Oracle E-Business Suite discovery using pluggable database targets. However, by using the "Database SID" as the pluggable database name, we can discover Oracle E-Business Suite instances for which the database is a pluggable database.
If an Oracle E-Business Suite instance on Oracle Cloud Infrastructure is using a load balancer and is discovered in Oracle Enterprise Manager, the load balancer target is not monitored or discovered in Enterprise Manager.
All agents are installed as the oracle user.
In order for EM agents to be able to upload to OMS, an ingress rule must be created on the subnet where the OMS is installed to allow communication on the "Enterprise Manager Upload Http SSL Port" (which is by default "4093") from all Oracle E-Business Suite nodes. Take note of the port number.
Note: You can find the port number used in <Middleware home>/install/portlist.ini on the OMS host.
Record the following port numbers for reference, which will be opened from the Oracle E-Business Suite nodes:
The database listener port on the subnet where database nodes are created. For example: 1521.
The WebLogic Admin port range (for both run and patch file systems) on the subnet where the Oracle E-Business Suite application nodes are created (Only for Oracle E-Business Suite Release 12.2 instances). For example: 7001-7003.
The port number used by the management agent installation on all subnets where the Oracle E-Business Suite nodes are present. For example: 3872.
Add ingress rules to the security lists associated with the subnet on which the OMS host is created, using steps in Adding an Ingress Rule with the following properties (multiple rules may have to be created to cover CIDRs of all Oracle E-Business Suite nodes):
Source Type: CIDR, Source CIDR: <CIDR for IPs of Oracle E-Business Suite nodes>, IP Protocol: TCP, Source Port Range: All, Destination Port Range: "Enterprise Manager Upload Http SSL Port"
Note: If the OMS host and Oracle E-Business Suite instances are on the same Virtual Cloud Network (VCN), the communication will happen using private IPs. In this case, the CIDR should match the private IP of the Oracle E-Business Suite node. If the OMS host and the Oracle E-Business Suite instances are on different VCNs, the communication will happen on public IPs. In this case, the CIDR should match the public IP of Oracle E-Business Suite node.
Log in to the OMS host as the root user.
For each ingress rule added, create a corresponding firewall rule using commands similar to following:
firewall-cmd --zone=public --add-rich-rule 'rule family=ipv4 source address=<CIDR for IPs of Oracle E-Business Suite nodes> port port=<port number> protocol=tcp accept' --permanent
firewall-cmd --zone=public --add-rich-rule 'rule family=ipv4 source address=<CIDR for IPs of Oracle E-Business Suite nodes> port port=<port number> protocol=tcp accept'
Note: If the OMS host and Oracle E-Business Suite nodes are on the same VCN, use the private IP of the OMS host when creating ingress rules. If the OMS host and Oracle E-Business Suite nodes are on different VCNs, use the public IP of the OMS Host when creating Ingress rules.
Add ingress rules to the security lists associated with the subnets on which the Oracle E-Business Suite App nodes are created (this information is provided while provisioning the Oracle E-Business Suite instance on Oracle Cloud Infrastructure), using steps in Adding an Ingress Rule with the following properties:
Source Type: CIDR, Source CIDR: <OMS host IP>/32, IP Protocol: TCP, Source Port Range: All, Destination Port Range: 22
Source Type: CIDR, Source CIDR: <OMS host IP>/32, IP Protocol: TCP, Source Port Range: All, Destination Port Range: <WebLogic admin server port range> for example: 7001-7003 (Required only for Oracle E-Business Suite Release 12.2 instances)
Source Type: CIDR, Source CIDR: <OMS host IP >/32, IP Protocol: TCP, Source Port Range: All, Destination Port Range: <agent install port> for example: 3872
Add ingress rules to the security lists associated with the subnets on which Oracle E-Business Suite database nodes are created (this information is provided while provisioning the Oracle E-Business Suite instance on Oracle Cloud Infrastructure), using steps in Adding an Ingress Rule with the following properties:
Source Type: CIDR, Source CIDR: <OMS host IP>/32, IP Protocol: TCP, Source Port Range: All, Destination Port Range: 22
Source Type: CIDR, Source CIDR: <OMS host IP>/32, IP Protocol: TCP, Source Port Range: All, Destination Port Range: <database listener port> for example: 1521
Source Type: CIDR, Source CIDR: <OMS host IP>/32, IP Protocol: TCP, Source Port Range: All, Destination Port Range: <agent install port> for example: 3872
Add firewall rules using the steps in Adding Firewall Rule When Local Firewall Uses "firewalld". Each rule should correspond to each of the ingress rules added previously for the Oracle E-Business Suite App nodes.
Add firewall rules using the steps in Adding Firewall Rule When Local Firewall Uses "firewalld". Each rule should correspond to each of the ingress rules added previously for each of the database nodes.
Add firewall rules using the steps in Adding Firewall Rule When Local Firewall Uses "iptables". Each rule should correspond to each of the ingress rules added previously for each of the database nodes.
In this case, no firewall rules need to be added. Do not attempt to add any firewall rules.
You must ensure that the fully qualified domain name (FDQN) of each of the Oracle E-Business Suite node is resolvable from the OMS host and that the FQDN of the OMS host is resolvable from each Oracle E-Business Suite node.
If the OMS host and Oracle E-Business Suite nodes are on the same VCN, no additional settings are required.
Although, if the OMS host and Oracle E-Business Suite nodes are on different VCNs, an update to the /etc/hosts file on OMS host and each of the Oracle E-Business Suite nodes is required so that the host names are resolvable as required. Ensure that the entries are created with public IPs of the hosts to FQDN for the host.
For example:
129.213.29.20 em132amp1.ampsubnet.my1811vcn.example.com em132amp1
Create named credentials which will be used to connect to the Oracle E-Business Suite nodes. Using the steps in Creating a Named Credential, create named credentials with the following properties:
Authenticating Target Type: Host
Credential Type: "SSH Key Credentials"
Scope: Global
User Name: oracle
SSH Private Key: <Content of /u01/install/APPS/.ssh/id_rsa on EBS Cloud Admin Tool VM / Oracle E-Business Suite Cloud Manager VM from where the Oracle E-Business Suite instance is provisioned or any other private key using which we can connect to the Oracle E-Business Suite node>
Follow the steps in section “Installing Management Agents” of the Oracle Enterprise Manager Cloud Control Basic Installation Guide to manually deploy the management agent on all Oracle E-Business Suite nodes.
To manually discover an Oracle E-Business Suite environment that was provisioned on Oracle Cloud Infrastructure, discovery can only be performed if the agent is installed by the oracle user.
When installing the agent by selecting the option “Add Target Manually”, make sure to use the fully qualified domain name.
Deselect “Configure Hybrid Cloud Agent” when deploying the agent manually.
If you are deploying the Oracle E-Business Suite instance node agent by the fully qualified domain name, there is an additional step necessary when the OMS host and Oracle E-Business Suite nodes are on different VCNs. You must log in to the OMS server and add the following entry to the local hosts file (/etc/hosts) for each Oracle E-Business Suite node:
<Public IP address><machine name with domain name><machine name>
For example: 192.0.2.1 myr63sdb.mydbsubnet.demo1811vcn.example.com myr63sdb
Follow the steps as described in Adding a Database Instance Target, although while adding the target, use "Database SID" as the pluggable database name provided while provisioning the Oracle E-Business Suite instance.
Note: The "Database SID" must be specified as the Pluggable database name for Oracle E-Business Suite discovery to work.
Follow the steps described in Adding a Database Instance Target.
Follow the steps as described in Adding a Database Instance Target, although while adding the target, use "Database SID" as the pluggable database name provided while provisioning the Oracle E-Business Suite instance.
Note: The "Database SID" must be specified as the Pluggable database name for Oracle E-Business Suite discovery to work.
Follow the steps described in Adding a Database Instance Target.
Add the cluster target by performing the steps described in Adding a Cluster Target.
Add a cluster database target using the following instructions:
From the Enterprise Manager console, in the Targets menu, select All Targets.
Search for and select the cluster target added above.
From the Cluster menu, select Discover Databases.
Click the Next button.
In the Database Discovery: Results page, under the Cluster Database section, select the check box associated with target listed, and click on Configure.
In the Configure Cluster Database dialog, on the General tab, note down the values of all the fields.
Click on the Instances tab.
Note down all values of all fields displayed for the two instances. Exactly two instances will be displayed.
Click on the Cancel button.
Observe that you are on the Add Targets Manually page. You can navigate to this page by using the Setup menu, selecting Add Target, and then selecting Add Targets Manually.
Click on the Add Target Manually button.
Select target type as "Cluster Database".
Select/Enter Host as the first node in the cluster (host name can be derived from the values noted down in Instances tab above).
Click on the Add ... button.
Specify all values as noted in the General tab above, except for the Service Name field. For the Service Name field, provide the pluggable database name provided while provisioning Oracle E-Business Suite instance.
Note: You must specify the Pluggable database name as the Service Name for Oracle E-Business Suite Discovery to work.
Enter the dbsnmp user password.
Note: Ensure that the dbsnmp user account is working. You might need to unlock the user and set the password on the Oracle E-Business Suite database.
Add two instances with the properties as noted down in the Instances tab above, except for:
Database SID - For the Database SID parameter, provide the pluggable database name provided while provisioning Oracle E-Business Suite instance.
Listener Machine Name - For this parameter, give the value of the corresponding host.
Click on the Next button.
Click on the Submit button.
Click on the Close button in confirmation window.
Add a cluster target by performing the steps in Adding a Cluster Target.
Add a cluster database target by using the following instructions:
From the Enterprise Manager console, in the Targets menu, select All Targets.
Search for and select the cluster target added above.
In the Cluster Target Home page, from the Cluster menu, select Discover Databases.
Click the Next button.
In the Database Discovery: Results page, under the Cluster Database section, select the check box associated with the target listed, specify the dbsnmp user password, and click Next.
Note: Make sure the dbsnmp user account is working. You might need to unlock the user and set the password on the Oracle E-Business Suite database.
Click on Configure.
Click on the Instances section.
Change the value of "Listener Machine Name" to be the same as that of "Host" for that particular instance, for each of the two instances.
Click the Save button.
Click Next.
Click the Save button.
Click the Close button in the confirmation window.
Add a cluster target by performing the steps described in Adding a Cluster Target.
Add a cluster database target using the following instructions:
From Enterprise Manager console, in the Targets menu, select All Targets.
Search for and select the cluster target added above.
From the Cluster menu, select Discover Databases.
Click on the Next button.
In the Database Discovery: Results page, under the Cluster Database section, select the check box associated with the database you intend to discover and click the Configure button. Note that there can be multiple cluster databases listed based on the number of databases installed on Exadata DB System. The database name would have been provided while provisioning the Oracle E-Business Suite instance.
In the Configure Cluster Database dialog, on the General tab, note down the values of all the fields.
Click on the Instances tab.
Note down all values of all fields displayed for the two instances. Exactly two instances will be displayed.
Click on the Cancel button.
Observe that you are on the Add Targets Manually page. You can navigate to this page by using the Setup menu, selecting Add Target, and then selecting Add Targets Manually.
Click on the Add Target Manually button.
Select target type as "Cluster Database".
Select/Enter Host as the first node in the cluster (hostname can be derived from the values noted down in the Instances tab above).
Click on the Add ... button.
Specify all values as noted in the General tab above, except for the Service Name field. For the Service Name field, enter the pluggable database name provided while provisioning the Oracle E-Business Suite instance.
Note: You must specify the pluggable database name as the Service Name for Oracle E-Business Suite discovery to work.
Enter the dbsnmp user password.
Note: Ensure that the dbsnmp user account is working. You might need to unlock the user and set the password on the Oracle E-Business Suite database.
Add two instances with the properties as noted down in the Instances tab above, except for:
Database SID - For the Database SID parameter, provide the pluggable database name provided while provisioning Oracle E-Business Suite instance.
Listener Machine Name - For this parameter, give the value of the corresponding host.
Click on the Next button.
Click on the Submit button.
Click on the Close button in confirmation window.
Add the cluster target by performing the steps in Adding a Cluster Target.
Add a cluster database target using the following instructions:
From the Enterprise Manager console, in the Targets menu, select All Targets.
Search for and select the cluster target added above.
In the Cluster Target Home page, from the Cluster menu, select Discover Databases.
Click the Next button.
In the Database Discovery: Results page, under the Cluster Database section, select the check box associated with the database you intend to discover and click the Configure button. Note that there can be multiple cluster databases listed based on the number of databases installed on an Exadata DB System. The database name would have been provided while provisioning the Oracle E-Business Suite instance.
Provide the dbsnmp user password, and click Next.
Note: Make sure the dbsnmp user account is working. You might need to unlock the user and set the password on the Oracle E-Business Suite database.
Click on Configure.
Click on the Instances section.
Change the value of "Listener Machine Name" to be same as that of "Host" for that particular instance, for each of the two instances.
Click the Save button.
Click on Next.
Click the Save button.
Click the Close button in the confirmation window.
At this point, manually discover the Oracle E-Business Suite instance by using the steps in the section Using the Discovery Wizard.
Make sure to adhere to the additional steps found in Additional Features for Discovery, especially:
Discovering Oracle E-Business Suite as the EM_MONITOR user (Recommended)
Discovering Oracle E-Business Suite as any database user (such as DBSNMP)
Navigate to the Enterprise Manager console. In the Setup menu, select Security.
Select Named Credentials.
Click on the Create button.
Specify a Credential Name (user defined).
Fill in other mandatory fields as required and click the Save button.
Log in to Oracle Cloud Infrastructure console.
Using the menu, navigate to Networking, select Virtual Cloud Networks, and then select your VCN.
Click Security Lists and then select the security list corresponding to the subnet to which you want to create an ingress rule.
Click Edit All Rules.
Click on the + Add Another Ingress Rule button. Specify Source Type, Source CIDR, IP Protocol, Source Port Range, and Destination Port Range:
Click on the Save Security List Rules button.
Log in to the node on which the firewall rule is to be created as the root user.
Execute the following commands:
firewall-cmd --zone=public --add-rich-rule 'rule family=ipv4 source address=<source CIDR> port port=<port number> protocol=tcp accept' --permanent
firewall-cmd --zone=public --add-rich-rule 'rule family=ipv4 source address==<source CIDR> port port=<port number> protocol=tcp accept'
If you want to specify a <port range>, use a format like <first port in range>-<last port in range>. For example, port=7001-7003; (both ports are inclusive).
Log into the node on which the firewall rule is to be created as the root user.
Execute the following commands:
iptables -I INPUT 1 -s <source cidr> -p tcp -m state --state NEW -m tcp --dport <port number> -j ACCEPT
If you want to specify a <port range> use format like --dport <first port in range> :<last port in range>. For example, --dport 1521:1523; (both ports are inclusive).
service iptables save
service iptables restart
From the Enterprise Manager console, in the Setup menu, select Add Target, and then select Add Targets Manually.
On the Add Targets Manually page, click the Install Agent on Host button.
Click the + Add button.
Enter the FQDN of the host on which the agent is being installed. Select a platform.
Click the Next button.
Specify Installation Base Directory and Instance Directory.
Select the Configure Hybrid Cloud Agent check box.
Select the Hybrid Cloud Gateway Agent.
Select an appropriate Named Credential.
Leave the Privileged Delegation Setting field blank (blank value).
Click on Next.
Click on Deploy Agent.
After the agent is installed successfully, run "<Installation Base Directory>/agent_<em version>/root.sh" as the root user.
From the Enterprise Manager console, in the Setup menu, select Add Target, and then select Add Targets Manually.
On the Add Targets Manually page, select Add Target Manually.
In the Add Target Manually dialog box, select "Database Instance" as Target Type.
For Host, choose the host on which the database is running.
Click Add ….
Specify all required properties and add the target.
From the Enterprise Manager console, in the Setup menu, select Add Target, and then select Add Targets Manually.
On the Add Targets Manually page, select Add Target Manually.
In the Add Target Manually dialog box, select "Cluster" as the Target Type.
For Host, choose or enter the first node in the cluster.
Click Add ….
Fill in all the values, using the steps described in My Oracle Support Knowledge Document 1908635.1, EM 13c, 12c: How to Discover the Cluster and Cluster Database (RAC) Target in EM Cloud Control, in section (c), "Discover the Cluster Target and Cluster Database Target manually," under "How to determine the values which need to be supplied."
Note: To determine "CRS_HOME" on OCI, execute the command ps -ef | grep tns. The output of the command will have the grid infrastructure home.
In the "Cluster Host and High Availability Services Targets" section, add the second host in the cluster.
Click the Save button.
Click the Close button in the confirmation window.
Wait for the cluster target status to be "Up".