In the previous part of this article series, we looked at the pre-steps and other requirements for setting up the hybrid cloud, such as having an Oracle Public Cloud (OPC) database server ready, and setting up the SSH connectivity from the OMS server to the OPC database server.
We will now continue with the actual installation of the cloud agent.
Installing the Cloud Agent
Log in to the Enterprise Manager console as SYSMAN/welcome1.
Select Setup.. Add Target.. Add Targets Manually.
Select “Add Host Targets” and click on “Add Hosts”
In the Add Host Targets screen, type in the IP address of the Oracle Public Cloud database server.
Select the platform as Linux x86-64 (the only one that can be chosen at the time of writing for the hybrid cloud). Click on Next.
Since you have typed in an IP address, a warning appears:
Ignore this warning about not using a fully qualified host name.
The Installation Details screen appears.
Note about using the IP Address:
If you want to use a full Host name for this IP address, you will need to add it to /etc/hosts on the OMS server as well on the Oracle Public Cloud database server in advance.
Otherwise, the “emctl secure agent” command which is run by Enterprise Manager at the end of the agent install procedure will not work.
On this page, enter the Installation base directory for the agent.
Adhering to Cloud database standards which are derived from the earlier well-known Oracle Flexible Architecture (OFA) standards, this is put under /u01/app/oracle/product where other Oracle database software has been installed when the OPC database server was created.
As the Named Credential, select “NC_OPC_DBCS”. This named credential uses SSH key credentials, and was pre-created with the SSH private and public keys of the OMS server.
Important: You need to expand Optional Details, and tick on “Configure Hybrid Cloud Agent”. Select the agent, which is the only agent on the OMS server.
Note that if this is not ticked and the Hybrid Cloud agent is not selected, the cloud agent install on the OPC database server will proceed but will ultimately fail.
Click on Next. The Review page appears.
Click on “Deploy Agent”. The procedure starts.
The first step is the Agent’s “Initialization” as seen below, followed by remote pre-requisite checks and then the actual deployment.
While the deployment is in progress, you can monitor it if you SSH to the Oracle Public Cloud database server. Change directory to the Agent home.
You will see that the size of the Cloud agent that is installed has been considerably reduced from the normal agent size, as seen below.
[oracle@AHUTESTSERVER]$ cd /u01/app/oracle/product/agentHome
[oracle@AHUTESTSERVER agentHome]$ du -hs .
248M .
The “Remote Prerequisite” step also completes.
A warning is displayed about the root privileges required to run the root.sh script at the end of the agent install. Ignore this warning, and continue with deployment using the menu.
The Agent deployment is successful.
You now need to run the root.sh script key manually.
You can use Putty to do this. Login as the opc unix user to the Cloud database server, and then “sudo –s” to work as root as seen below.
As root, run the root.sh script (copy and paste the full path and name from the deployment summary screen). Note that this is important for proper agent functioning.
You can also SSH to the Oracle Public Cloud server from the OMS server, and check the status of the agent.
[oracle@em12c ~]$ ssh <IP Address of OPC server>
Authorized uses only. All activity may be monitored and reported.
On the Oracle Public Cloud server, check where the agent has been installed via the first command below, and then move to the bin directory that is displayed.
[oracle@AHUTESTSERVER ~]$ cat /etc/oragchomelist
/u01/app/oracle/product/agentHome/core/12.1.0.5.0:/u01/app/oracle/product/agentHome/agent_inst
[oracle@AHUTESTSERVER ~]$ cd /u01/app/oracle/product/agentHome/agent_inst/bin
Check the status of the agent via the following command:
[oracle@AHUTESTSERVER bin]$ ./emctl status agent
Oracle Enterprise Manager Cloud Control 12c Release 5
Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
Agent Version : 12.1.0.5.0
OMS Version : 12.1.0.5.0
Protocol Version : 12.1.0.1.0
Agent Home : /u01/app/oracle/product/agentHome/agent_inst
Agent Log Directory : /u01/app/oracle/product/agentHome/agent_inst/sysman/log
Agent Binaries : /u01/app/oracle/product/agentHome/core/12.1.0.5.0
Agent Process ID : 18092
Parent Process ID : 18032
Agent URL : https://<IP Address of OPC server>:3872/emd/main/
Local Agent URL in NAT : https://<IP Address of OPC server>:3872/emd/main/
Repository URL : https://<IP Address of OPC server>:1748/empbs/upload
Started at : 2015-06-05 09:54:22
Started by user : oracle
Operating System : Linux version 2.6.39-400.109.1.el6uek.x86_64 (amd64)
Last Reload : (none)
Last successful upload : 2015-06-05 09:55:47
Last attempted upload : 2015-06-05 09:55:47
Total Megabytes of XML files uploaded so far : 0.19
Number of XML files pending upload : 0
Size of XML files pending upload(MB) : 0
Available disk space on upload filesystem : 68.90%
Collection Status : Collections enabled
Heartbeat Status : Ok
Last attempted heartbeat to OMS : 2015-06-05 09:59:27
Last successful heartbeat to OMS : 2015-06-05 09:59:27
Next scheduled heartbeat to OMS : 2015-06-05 10:00:28
---------------------------------------------------------------
Agent is Running and Ready
The Hybrid Agent is up and running - and its xml files are also being uploaded via the hybrid gateway back to the on-premise Enterprise Manager repository.
We will continue the Hybrid Cloud setup using Enterprise Manager, in Part IV of this article series. The next step will be to discover the Cloud database and listener in Enterprise Manager.