by Porus Homi Havewala Oracle Enterprise Manager 12c Release 5 , released in June 2015, allows an on-premise Enterprise Manager OMS (Oracle Management Service) to install Hybrid Cloud Agents on your Oracle Public Cloud (OPC) Database Servers and WebLogic servers – and this is the first time this has been made possible. This opens up an entire new world of hybrid cloud management , where you can use an on-premise Enterprise Manager to monitor and manage both on-premise and cloud databases, compare database, WLS, and server configurations, apply compliance standards equally, and also makes it possible to clone Oracle 12c PDBs and Java applications from on-premise to a cloud CDB, and back again – all via the on-premise EM console. The most powerful feature of Release 5 is that it is able to manage the Hybrid Cloud from a single management interface. So you can have your databases and WLS servers that are on the company premises, as well as your Oracle public cloud (OPC) based databases and WLS servers all managed via one central on-premise Enterprise Manager Installation. Normal EM12c agents are installed on your on-premise servers, and special hybrid cloud agents installed (via the push mechanism of Enterprise Manager) on your cloud servers. The hybrid cloud agents work through a Hybrid Gateway - this is one of your on-premise EM12c agents that has been designated as such. This is a specialized ssh tunnel of sorts. Once the agents start talking to the OMS, you are able to see all your databases either on-premise or on the cloud - and clone PDBs easily to and fro from the cloud via Enterprise Manager, as seen in the screenshot below. Besides this, you can also use the other features of the Enterprise Manager packs, such as Diagnostics, Tuning, Database Lifecycle Management (DBLM) and so on in the Hybrid Cloud. For example, as part of DBLM, you can perform configuration comparisons between on-premise and cloud databases or WLS servers or host servers, and also compliance checks. In this way you can make sure your entire enterprise cloud - on-premise as well as public cloud - is compliant, and adheres to configuration guidelines with controlled configuration deviations. In this article series, we will look at the steps for setting up the Hybrid Cloud via Enterprise Manager. We will go through the pre-steps, and then install a Hybrid Cloud Agent. Next, we will go through the steps of configuration management and compliance for the Hybrid Cloud, and finally we will test out the cloning of PDBs back and forth from the cloud. Pre-setup steps for the Hybrid cloud include setting up one of your OMS agents as the Hybrid Gateway agent, creating SSH keys for the OMS server, and creating a Named Credential with SSH key credentials for the hybrid cloud. We will first go through the pre-setup steps. Pre-setup: For the Hybrid Cloud capability, the following pre-steps are required on the EM12105 installation. Pre-Step 1: First, register any agent in your EM12c local (on-premise) installation as the Hybrid Gateway agent. Preferably, choose an agent which is not your main OMS server agent, i.e. the agent can be on one of your target servers which is not too heavily loaded with its own targets. The Enterprise Manager Command line interface (emcli) is used for the purpose of registering the Hybrid Gateway agent. (For more information on emcli, please refer to the documentation on http://docs.oracle.com/cd/E24628_01/em.121/e17786/toc.htm ) Login in as the oracle user, and move to where emcli is installed on your agent or oms server. Login first to emcli as sysman, and then issue the register command: ./emcli login -username=sysman ./emcli register_hybridgateway_agent -hybridgateway_agent_list='em12c.sainath.com:3872' This registers the agent as a hybrid gateway agent. There are ways to register an additional agent as a slave or secondary agent that can take over the monitoring if the master or primary gateway agent goes down, but for now we will only set up one agent in this example run. Important Note: If you have a lot of cloud database servers, don’t use only one gateway agent to communicate to all of these, instead set up multiple gateway agents to talk to different cloud servers. For example, one gateway agent can be used to talk to 5-10 cloud servers, another gateway agent can be used to talk to other cloud servers, and so on. The architecture in this case is very important, since it needs to be set up in a well-planned manner. This relationship between which gateway agent talks to which hybrid cloud agent is set up when the hybrid agent is installed on each cloud server, as we will see later on in this article series. Pre-Step 2: Next, generate SSH keys for the OMS Server as follows: Login to the OMS host as the Oracle Unix user, and type: ssh-keygen -t rsa Enter passphrase Important: Do not use a passphrase, just press enter. These keys will be used in a Named Credential in Enterprise Manager, and a passphrase is not supported for use with SSH keys in Named Credentials. The ssh-regkey utility has now generated two files in the .ssh sub-directory under the Oracle Unix user’s home, as seen below: id_rsa id_rsa.pub We will continue the Hybrid Cloud setup using Enterprise Manager, in Part II of this article series. Part II is here .
↧