X

An Oracle blog about Oracle Enterprise Manager and Oracle Management Cloud

  • March 22, 2019

Enterprise Manager on OCI Installation Phase 2 - Installing the EM App Into Your OCI Compartment

Dan Koloski
Vice President

Hi there!  If you're reading this blog post, you are in the process of installing the new Oracle Enterprise Manager (EM) app into Oracle Cloud Infrastructure (OCI),and you've already completed Phase 1 (OCI setup pre-requisites) and are ready to start on Phase 2:   Installing the EM App Into Your OCI Compartment. 

STOP.  IF YOU ARE NOT SURE IF YOUR OCI ADMINISTRATOR HAS COMPLETED THE PHASE 1 PREREQUISITES, CHECK WITH THEM BEFORE PROCEEDING.  The prerequisite steps only take a few minutes, but THEY MUST BE COMPLETED BEFORE STARTING THE EM APP INSTALLATION OR YOUR EM INSTALLATION WILL FAIL. 

OK, now that we've gotten that out of the way, we can proceed with the installation.  You will need to use the the name of the OCI Compartment as into which you should be installing your EM app.  In the example steps below, we are assuming the OCI administrator created a compartment called...

eminfra 

 

Licensing/Account Information (estimated time, 5 minutes):

  1. Read the Oracle Enterprise Manager License Policies to ensure you comply with the licensing requirements.    
  2. You’ll also need to set up and configure your OCI account and obtain the OCID of the Compartment where you intend to install the EM environment (see OCI sign-up and OCI Compartments for details).

Image 1:  A view of the OCI home page for your compartment

Image 1:  A view of the OCI home page for your compartment

 

Installing the EM image (estimated time, 5 minutes of work, then 30 minutes installation time)

  1. Select the EM image in the OCI Marketplace.  From the OCI Main Menu, Click on the Marketplace.  Search for Oracle Enterprise Manager 13.3 and Click on it.

Image 2:Searching for Enterprise Manager in the OCI Marketplace

Image 2: Searching for Enterprise Manager in the OCI Marketplace

  1. Review the Oracle Enterprise Manager Overview and Click on Launch Instance

Image 3:Enterprise Manager app overview

Image 3: Enterprise Manager app overview

  1. Select the Package Version, specify your OCI Compartment name, Accept the Terms of Use and click Launch Instance

Image 4:Selecting the Enterprise Manager version and specifying your OCI compartment

Image 4: Selecting the Enterprise Manager version and specifying your OCI compartment

  1. Create an Instance Name, select your desired OCI Availability Domain and Select the desired shape for VM. You can choose any shape that is available.

Image 5:Naming your EM app Instance, Selecting the Availability Domain and Shape

Image 5: Naming your EM app Instance, Selecting the Availability Domain and Shape

Image 6:Selecting the OCI Compute Shape for your EM image instance

Image 6: Selecting the OCI Compute Shape for your EM image instance

  1. Enter the ssh public key that will be used to access the instance as well as the Virtual Cloud Network and Subnet created in the prerequisites, and then Click on Create! 
     

Image 7:Entering the SSH key, selecting the VCN.

Image 7: Entering the SSH key, selecting the VCN.

 

<COFFEE BREAK!> 

Now you can go get some coffee while the Image is installed in your OCI compartment.  The installation takes approximately 30 minutes of elapsed time.

</COFFEE BREAK>

 

Logging into your new EM instance (estimated time: 5 minutes)

  1. Once your VM instance is running, Click on the instance and copy the Public IP Address.  SSH to the VM instance with the ssh key
$ ssh –i <private_ssh_key> opc@<public IP Address>

Image 8:Homepage of your OCI instance

Image 8: Homepage of your OCI instance

  1. Check the status of your newly-installed EM:  In the command line console, change your user to ‘oracle’ user by executing below in the command and then Check the OMS status using the EMCLI.

$ sudo su – oracle

$ /u01/app/em13c/middleware/bin/emctl status oms

Image 9: Sample output from the status oms command

Image 9: Sample output from the status oms command

  1. Change default passwords.  The password for the EM user sysman, EM Agent, Registration Password, Fusion Middleware user weblogic and Node Manager can be accessed in the below file (access as root user)"

$ cat /root/.oem/.sysman.pwd

Change the sysman password by executing the below command

$ /u01/app/em13c/middleware/bin/emctl config oms -change_repos_pwd
  1. Log in to your new EM Console
$ https://<public ip address>:7803/em
  1. Start monitoring …you can use a local agent to monitor your EM OMS and OMR while you get familiar with your installation.  In order to do that, make the following entry in the new hosts’s /etc/hosts file
emcc.marketplace.com <public IP address of the EM VM>

(if you do this, you can also start using this URL to log in to your new EM)

$ https://emcc.marketplace.com:7803/em

 

What if I need to troubleshoot the EM installation on OCI?

This installation is mostly automated, so we don’t expect you’ll need to do much troubleshooting.  It’s important to note that once your EM is installed and running, ongoing lifecycle management/maintenance/patching/upgrade of your Enterprise Manager is your responsibility, just as if you had installed it on-premises.  Similarly, if you are planning on using some of the larger OCI shapes, some configuration of the OMS and OMR may be required for your EM to fully take advantage of the increased CPU and Memory footprint…also just as if you had installed it on-premises.  Refer to the Cloud Control Administrator's Guide in our Enterprise Manager documentation for best practices.

But if you do need to troubleshoot a failed installation, the installation log is located at /var/log/emgc_install.log .

Make sure your OCI dynamic group and policies set properly if you find any authentication related errors in log file, and then rerun the below script after fixing the dynamic group and policies mentioned in prerequisites

$ sudo -s

$ cd /root/bootstrap

 $ . ./configure_db_and_oms.sh

Image 10:Sample OEM on OCI deployment log

Image 10: Sample EM on OCI deployment log

 

Congratulations, your installation is complete!
What's next?

In upcoming blog posts, we'll discuss how to get started with monitoring and managing targets, agent installation and agent lifecycle best practices for OCI-hosted Oracle Enterprise Manager instances.  You can also attend these free upcoming webinars to learn how to use your EM against specific targets such as Database, Exadata and others. 

Two last reminders:  Once your EM is installed and running, ongoing lifecycle management/maintenance/patching/upgrade of your Enterprise Manager is your responsibility, just as if you had installed it on-premises. Refer to the Cloud Control Upgrade Guide and Cloud Control Administrator's Guide for best practices in these areas.

Similarly, if you are planning on using some of the larger OCI IaaS Compute Options, some configuration of the OMS and OMR may be required for your EM to fully take advantage of the increased CPU and Memory footprint…also just as if you had installed it on-premises.  Refer to the Cloud Control Advanced Installation and Configuration Guide for more details.

 

How did it go?

If you've gone through the experience, we'd like to hear from you.  How did it go?  Suggestions for things we can make simpler?  Are you using it for dev/test, production or both?  What are you monitoring?  Join the conversation in the Oracle Enterprise Manager Forum

Finally, here's the link to the Oracle Cloud Marketplace again. Good luck and keep us posted on your progress.


Enjoy your new Oracle Enterprise Manager instance!

Image 16:  Enjoy your new Oracle Enterprise Manager instance!

Image 16:  Enjoy your new Oracle Enterprise Manager instance!