Oracle Enterprise Manager Ops Center 12c is a comprehensive solution to manage all Oracle systems deployed in traditional, virtualized and cloud environments. Ops Center 12c introduces unique capabilities for establishing, managing, and supporting Infrastructure as a Service (IaaS) clouds, and it’s a key component to help Oracle customers adopt cloud computing faster and with less effort and risk.
I’ll try to show how to install Enterprise Manager Ops Center 12c on Oracle Linux 5.5 (64bit). My previous installation guide for Oracle Linux 5.6 can help you to install 5.5 Linux (or you can just install Ops Center on Oracle Linux 5.6): How to Install Oracle Linux 5.6
Installation of OCDoctor
OCDoctor is an utility to assist users in various stages of the Ops Center deployment. It is updated on a regular basis to help you identify and resolve known issues or suggest ways to improve performance.
You can download it from: https://updates.oracle.com/OCDoctor/OCDoctor-latest.zip
If you have already OCDoctor (not downloaded the latest version from internet), make sure that it updates itself:
1 |
./OCDoctor.sh --update |
After updating OCDoctor, run it to check prerequisites:
1 2 3 |
unzip OCDoctor-latest.zip cd OCDoctor ./OCDoctor.sh --ec-prereq |
Examine the output and fix the errors. When I run, it showed the following errors (and warnings):
1 2 3 4 5 6 7 8 9 10 11 |
ERROR: Not enough Main Memory! 6 GB is the minimum supported, but only 4053 MB found WARNING: Not enough recommended disk space on /var/opt. Required is 20G, but 70G is recommended. You have 35G. WARNING: RPM expect-5.43.0 is MISSING WARNING: RPM perl-DBD-Pg is MISSING WARNING: RPM dhcp is MISSING WARNING: RPM perl-XML-Parser is MISSING WARNING: RPM ncompress is MISSING WARNING: RPM httpd is MISSING WARNING: RPM keyutils is MISSING |
I’ll ignore the first error because I can’t add my virtual PC extra RAM. I’ll also ignore second warning because I have already 35G space and it will be enough for installation (tested).
To install required RPMs, I’ll set up Oracle’s Public YUM server: public-yum.oracle.com/
1 2 3 |
cd /etc/yum.repos.d wget http://public-yum.oracle.com/public-yum-el5.repo vi public-yum-el5.repo |
I’ve changed “enabled=0” to “enabled=1” under “[el5_u5_base]”. Now we’re ready to use public YUM server to install missing packages:
1 2 3 |
yum install expect-5.43.0 perl-DBD-Pg dhcp perl-XML-Parser yum install httpd keyutils ncompress yum install compat-libcom_err |
Important: Ops Center installer asked me to install “compat-libcom_err” although OCDoctor doesn’t show it as a missing RPM.
After installing missing RPMs, I re-run the OCDoctor to be sure that my system satisfies the prerequisites. If everything looks OK, we can start installing Ops Center 12c.
Installation of OPS Center 12c
Enterprise Manager Ops Center has a text based installer. You can download the setup file from Oracle.com:
http://www.oracle.com/technetwork/oem/ops-center/oem-ops-center-188778.html
Important: If you’ll use local database, you also need to download Oracle DB 11.2.0.3 from MOS and then put the zip files into /var/tmp/downloads folder:
1 2 |
cp p10404530_112030_Linux-x86-64_1of7.zip /var/tmp/downloads/ cp p10404530_112030_Linux-x86-64_2of7.zip /var/tmp/downloads/ |
We don’t need to extract the zip files of the database, Ops Center Installer will do all work. Now extract the Ops Center installation zip:
1 |
tar -xvzf enterprise-controller.Linux.i686.12.1.0.2001.tar.zip |
After you run the above command, go into “xvmoc_full_bundle” folder and run the installer as “root” user. Installer will ask your email to be able to install Oracle Configuration Manager. It’s an optional step and does not effect the installation but I recommend you to install Oracle Configuration Manager.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 |
cd xvmoc_full_bundle ./install Ops Center Enterprise Controller Installer (version 12.1.0.2001 on Linux) 1. Check for installation prerequisites. [Completed] 2. Check that required RPM packages are present. [Completed] 3. Configure file systems. [Completed] 4. Install prerequisite packages. [Not Completed] 5. Install Agent components. [Not Completed] 6. Create Deployable Proxy Bundles. [Not Completed] 7. Install application packages. [Not Completed] 8. Run postinstall tasks. [Not Completed] 9. Install IPMI tool. [Not Completed] 10. Set database credentials. [Not Completed] 11. Install and Configure Oracle Database. [Not Completed] 12. Seed Ops Center Database Schema [Not Completed] 13. Install Service container components. [Not Completed] 14. Install Core Channel components. [Not Completed] .......................... 21. Initialize and start services. [Not Completed] (3 of 21 Completed) Executing current step: Install prerequisite packages... |
When the installer passed first steps, all you need is to wait. Installation will smoothly complete.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 |
This installer has determined that some rpms currently installed on this system have later versions than those currently required by Oracle Enterprise Manager Ops Center. If you encounter any problems related to these substitutions, you might need to obtain and install the exact version of the software required by the installer before re-installing Oracle Enterprise Manager Ops Center. Ops Center Enterprise Controller installation is complete. Please point your browser to: http://opscenter12.gokhanatil.com to begin using Ops Center Enterprise Controller. |
Installation is done. Now we need to connect to web interface of Ops Center to complete the configuration. We open our favorite browser and enter hostname of our server (i.e http://opscenter12.gokhanatil.com) to connect Ops Center.
We need to enter “root” as username and password of the root user to login.
Ops Center warns us again about memory and disk space, we also see a warning about Java environment. I’ll ignore this warning, I think Java environment is only needed for the “terminal” connection Java applet.
In this step, enter the hostname of Ops Center. In most cases, Ops Center will already detect it correct so you’ll probably leave it as it is. Then select how you’ll install proxy servers. As you know, Ops Center communicate with target systems through Proxy controllers and we may need to deploy multiple proxy controllers for separate networks. In this installation, I’ll use only one proxy controller, and it’ll be deployed to the same server with my Ops Center.
Select the correct network interface from the pull-down menu and click next. Proxy controller will manage the systems which can connect through this network interface.
Proxy controller is online, go to next step.
Enterprise Manager Ops Center 12c has a new feature called Automated Service Requests (ASR). If your server is connected to the internet, I recommend you to choose the connected mode to be able to use this new feature. You’ll also need to enter MOS credentials to be able to work in connected mode.
Accept the default values or enter the locations to store Software library. You can use NFS shares.
You may configure DHCP for OS Provisioning for selected the network interfaces, or you can configure it later.
Review your settings, and click “finish” if everything is OK. It’s possible to go back to any step and change the settings, or even cancel the configuration and restart it from the beginning (step 1).
We have completed the configuration and Ops Center is ready to use.
Adding New Assests to OPS Center
We’re ready to add an asset (a target system to manage) to our Ops Center 12c.
Log in to Ops Center, you’ll see the assets page. There’s a sliding menu at right side, click the double arrows to open it, and then click “add assets”. Then click “Add and manage various types of assets” and click next.
Create a new discovery profile.
Enter a name for discovery profile, and choose the target types you want to discover and click next. You’ll see the page you can enter tags that can be used for discovery. I’ll not use tags so click next again.
Define an IP range and click add, then click next.
Create a new management credential to discover (and then to manage) your assets. Click next, review the information you entered and click “finish” to create the discovery profile. As you can see, it’s also possible to manage and monitor targets without deploying agents (new feature of Ops Center 12c)!
Now click “add now” to start discovering target systems. Ops Center will create a job for discovery process.
You can get more information about the job created for discovering assets. Click the quick link at the bottom of the page, or open the jobs and find the running job.
When the job completed (it takes some time depending on how many target systems will be discovered and subnet range), you can start managing and monitoring the new assets. As I see, in Ops Center 12c, discovering and adding steps are merged and now it takes less steps to add an asset to the Ops Center.
Pingback: Integrate EM OPS Center 12c, EM Cloud Control 12c and Oracle VM Manager « OEM Cloud Control: Rob Zoeteweij
Wajid
Gokhan Atil
Kavita
Gokhan Atil
Simon McCartney
Gokhan Atil
Srinivas
Thanigai
Gokhan Atil
David Mckenna
Gokhan Atil
Sei
Gokhan Atil
Sei
Gokhan Atil
Douglas Adams
Gokhan Atil
shafiur
Gokhan Atil
bharat
Gokhan Atil
Peter
Gokhan Atil
Roy
Prince
gustavo maurizio
Gokhan Atil
Heng
K C
Jprado
Gokhan Atil
Jprado
ELMSIEH
sandhya
Martin Peters
Lucky
noon
Atul
Abdelaziz bendoumah
NaN
Paulpop
Matt
Rajesh
Gokhan Atil
Rajesh
Gokhan Atil
Rajesh
Rajesh
Gokhan Atil
mayank
Gokhan Atil
Ravi
Gokhan Atil
Amit
Gokhan Atil
Asif
Saqib
Syamsul akbar
Muhammad Mustafeez
Gokhan Atil
Mohammed
Gokhan Atil
Mohammed