This article is about installing Oracle Enterprise Manager 11g Release1 using an existing database. Grid Control 11g uses WebLogic Server instead of OC4J which was traditional with Grid Control versions 10.1 and 10.2; Grid Control 11g will deploy from an existing Weblogic Server during the Grid Control Installation.

Hardware Requirements
This is the extract from Oracle Grid Control Installation document.
These are the minimum physical memory (RAM) required for installing an OMS and a standalone Management Agent
[TABLE=2]
Recommended Physical Memory and Hard Disk Space for Oracle Management Repository
[TABLE=3]
Prerequisites and Preparation

Significant difference from an earlier version of Grid Controls is the introduction of Web logic Server. Web logic Server replaces OC4J which was used prior to 11gR1. So before installing Grid Control 11gR1, you must first prepare the Weblogic Server and Database installations that will support the Management Server and Management Repository. Grid Control 11.1.0.1.0 installation merely installs and deploys a web application. Supporting components such as WebLogic Server (and its prerequisite jdk for 64bit platforms) and the Oracle Database must be installed before hand and should be ready to receive the Grid Control 11.1.0.1.0 product.

Repository database version needs to be any one of the following versions.
10.2.0.4.0
11.1.0.7.0
11.2.0.1.0
11.2.0.2.0
Oracle Enterprise Edition is requirement for Grid Control 11.1.0.1.0. Partitioning and fine grained access controls are required active features, so the database must be an Enterprise Edition type.

Installing Web logic server

Check with oracle metalink for updated information

a) The only version of the Web Logic Server that can be used to deploy Grid Control is 10.3.2.
10.3.1 and 10.3.3 ARE NOT supported versions. 10.3.2 IS the ONLY supported version.

b) The WebLogic Server should be installed from the Oracle WebLogic Server 11gR1 (10.3.2) – Package Installer source from the Oracle Technology Network web site.

c) For 64-bit platforms, JDK needs to be installed. Make sure that you always download the JDK for your respective platform from the trusted site. For example, SUN JDK from Oracle, Aix from IBM and so on.

Follow the below Steps to Install the 11.1.0.1 Grid control in your environment
Install JDK 1.6 for Linux (for x86_64 bit only)

Download jdk 1.6 from Oracle/Sun for the Linux x86_64. jdk 1.6.0_18 is recommended due to potential problems with newer versions. Update 18 can be retrieved from the versions archive site at this URL: http://java.sun.com/products/archive/

Create Oracle Grid Control Install Home directory as oracle user

$ mkdir /opt/app/oracle/Middleware/
• Execute the extraction and installation with this command as oracle (example):

Copy the jdk-6u18-linux-x64.bin to /opt/app/oracle/Middleware/

$ cd /opt/app/oracle/Middleware/
$ ./jdk-6u18-linux-x64.bin

Note 1. Make sure that JDK is installed under the Middleware Oracle home
Note 2. Make sure that after Grid Control 11g Install/upgrade you do not upgrade the JDK under this Middleware Oracle home
Note 3. Software that should be installed must be JDK and not JRE

• Finish Installation

At the end of jdk installation, press “Enter”.

A web page will be presented that can be reviewed or dismissed.

• Installation Results

Back in the command session, the jdk installation is complete and has returned an OS prompt.

Notice the extracted jdk directory in the same location as the stage (example):

./jdk1.6.0_18/
./jdk-6u18-linux-x64.bin

Looking deeper, observe the java that is required is located under the …/jdk1.6.0_18/bin/ directory. This will be the java used for WebLogic Server installation in support of Grid Control installation on this host.

• Verification of java version

A simple version verification shows that the jdk is ready for use:

$ /u02/jdk16/jdk1.6.0_18/bin/java -version
Java versions “1.6.0_18”
Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
Java HotSpot(TM) 64-Bit Server VM (build 16.0-b13, mixed mode)

Install WLS 10.3.2

Download WLS 10.3.2 from http://www.oracle.com/technetwork/middleware/weblogic/downloads/wls-main-097127.html

• Go to the OTN http://www.oracle.com/technetwork/middleware/weblogic/downloads/wls-main-097127.html Click on “Oracle WebLogic Server 10.3.2” See all files.



• Download http://download.oracle.com/otn/linux/middleware/11g/wls/wls1032_generic.zip

Go to the location where you have downloaded the WLS binaries

For Linux 32-bit, Invoke ./wls1032_.bin

For 64-bit platforms,

Rename wls1032_generic.zip to wls1032_generic.jar

Then Invoke it like:

Click next on “Welcome” Screen
Enter Middleware Home Directory and click next on “Choose Middleware Home Directory” Screen

Enter email if needed or unchck the check box then click next on “Register for Security Updates” Screen

Select “Typical “In the Choose Install Type screen and click next

Verify “JDK Selection” Screen and click Next

Verify “Choose Product Installation Directories” Screen and click Next

Verify “Installation Summary” Screen and click next


Once the WLS installation is done. Uncheck the option “Quick start” and Click “Done”.

Important: You need to apply Patch WDJ7 to the WLS home before Installing/Upgrading the Grid control. Refer to Note 1072763.1 for instructions on how to apply online/offline patch to WLS.

Apply Patch WDJ7

Download WDJ7 patch from oracle support. https://support.oracle.com/ and follow the instructions below to apply the patch
Unzip and copy the file to /utils/bsu/cache_dir/ directory

Install Oracle Database 11.2

In this step we will install 11.2.0.2.0 database which will host the Grid control repository. Download the database binaries from the OTN and install the binaries by referring oracle documentation.
Using dbca create a database and make sure following Initialization parameters as per oracle Grid control Grid Control 11.1.0.1.0 Requirements.
In the dbca interview de-select the EM creation option so you can avoid dropping SYSMAN prior to Grid installation.

[TABLE=4]

If a database already exists, deconfigure dbcontrol using following method. This step only requires if you have not just created a database using above method.

If DB Control SYSMAN schema is created in the database, as a part of the database install. User has to deconfigure it, else while doing the Grid control install it will prompt you to remove the dbconsole.
Run the following commands as database install user

• Set the ORACLE_HOME and ORACLE_SID environment variable:

  For example:-
  export ORACLE_HOME=/u01/app/guest/product/11.2.0/dbhome_1
  export ORACLE_SID=orcl

• Go to the location: /bin
  Run the following command as database install user ( in case of single instance database):

Note: Grid control requires 200Mb of space in undo tablespace.

Install Grid control 11.1.0.1.0

Download the Grid Control software from OTN

• Go to the Software download location and invoke the ./runInstaller


Note:
• (Optional) On the My Oracle Support Details screen, uncheck the option : I wish to receive security updates vis My Oracle support
• It will ask you for a confirmation; click Yes and then Click Next

• On the Check for Updates screen



• (Optional) On the Check for Updates screen, select one of the following sources from where the software updates can be automatically downloaded and installed while the installation of Enterprise Manager Grid Control is in progress. Select Skip Software Updates and click Next

• On the Select Installation Type screen, select install a new Enterprise Manager system.



• On the Select Installation Type screen, select install a new Enterprise Manager system.



• If Enterprise Manager Grid Control is the first Oracle product you are installing on the host that is running on UNIX operating system, then the Oracle Inventory screen appears Otherwise, the Check Prerequisites screen appears.



• On the Specify Install Locations screen, provide the information required for installing the core components of Enterprise Manager Grid Control and storing the configuration files.


• For Oracle Middleware Home Location, validate and accept the default location or select another location that has write permission. This is where the Oracle home of Oracle Management Service is created: /opt/app/oracle//Middleware
• For OMS Instance Base Location, validate and accept the default location or select another location that has write permission. This is where the configuration files of Oracle Management Service will be stored. By default, this location is under the parent directory of the Oracle Middleware Home. For example, if the Oracle Middleware Home /Oracle/Middleware, then the Oracle Management Service Instance home is /opt/app/oracle/Middleware/oms11g

• On the Create WebLogic Server Domain screen, specify the WebLogic Domain Name, the WebLogic credentials, and the Node Manager password. By default, the WebLogic Domain name is GCDomain, and the Node Manager name is node manager. You can modify the WebLogic Domain name, but not the Node Manager name. The installer uses this information for creating Oracle WebLogic Domain and other associated components such as the admin server, the managed server, and the node manager. A Node Manager enables you to start, shut down, or restart an Oracle WebLogic Server instance remotely, and is recommended for applications with high availability requirements.



• On the Connect to Oracle Database screen, specify the fully-qualified name of the host where the existing database resides, the listener port and its service name or system ID (SID), and the SYS user password. The Installer uses this information to connect to the existing, certified Oracle Database where the Management Repository can be configured



• On the Configure Oracle Management Repository screen, do the following

• For SYSMAN Password, specify a password for creating the SYSMAN user account. The SYSMAN user account is used for creating the SYSMAN schema, which holds most of the relational data used in managing Enterprise Manager Grid Control. SYSMAN is also the super administrator for Enterprise Manager Grid Control. Ensure that your password contains at least 8 characters without any spaces, begins with a letter, and includes at least one numeric value, one lowercase letter, and one uppercase letter.
• For Management Tablespace, specify the full path to the location where the data file for management tablespace (mgmt.dbf) can be stored. The installer uses this information for storing data about the monitored targets, their metrics, and so on. Ensure that the specified path leads up to the file name. For example: If the database is on a file system, then the path must look like /scratch/db11g/oradata/mgmt.dbf.



• On the Secure Oracle Management Service screen provide the registration password



• On the Customize Ports screen, customize the ports to be used for various components, and click Next.



• On the Review screen, review the details and click on Install to start the installation



• Now you can see the install progress



• At the end of the install run a allroot.sh script



[root@htrdbl02 ~]# /opt/app/oracle/Middleware/WebLogic/oms11g/allroot.sh

Starting to execute allroot.sh ………

Starting to execute /opt/app/oracle/Middleware/WebLogic/oms11g/root.sh ……
Running Oracle 11g root.sh script…

The following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME= /opt/app/oracle/Middleware/WebLogic/oms11g

Enter the full pathname of the local bin directory: [/usr/local/bin]:
The file “dbhome” already exists in /usr/local/bin. Overwrite it? (y/n)
[n]:
The file “oraenv” already exists in /usr/local/bin. Overwrite it? (y/n)
[n]:
The file “coraenv” already exists in /usr/local/bin. Overwrite it? (y/n)
[n]:

Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root.sh script.
Now product-specific root actions will be performed.
Adding entry to /etc/oratab file…
Finished execution of /opt/app/oracle/Middleware/WebLogic/oms11g/root.sh ……

Starting to execute /opt/app/oracle/Middleware/WebLogic/agent11g/root.sh ……
Running Oracle 11g root.sh script…

The following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME= /opt/app/oracle/Middleware/WebLogic/agent11g

Enter the full pathname of the local bin directory: [/usr/local/bin]:
The file “dbhome” already exists in /usr/local/bin. Overwrite it? (y/n)
[n]:
The file “oraenv” already exists in /usr/local/bin. Overwrite it? (y/n)
[n]:
The file “coraenv” already exists in /usr/local/bin. Overwrite it? (y/n)
[n]:

Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root.sh script.
Now product-specific root actions will be performed.
Finished product-specific root actions.
Adding entry to /etc/oratab file…
Finished execution of /opt/app/oracle/Middleware/WebLogic/agent11g/root.sh ……

• Now it will start the install configuration



• Finally “Finish” Screen appears with URL information

How to verify the installation

Now that we have finished installing WLS/OMS and Agent, It is time to verify how it is working. First thing probably to do commands to see it is up and running.

• Verify OMS status

Run the following command at the shell.

$ emctl status oms
Oracle Enterprise Manager 11g Release 1 Grid Control
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
WebTier is Up
Oracle Management Server is Up

$ emctl stop oms
Oracle Enterprise Manager 11g Release 1 Grid Control
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Stopping WebTier…
WebTier Successfully Stopped
Stopping Oracle Management Server…
Oracle Management Server Successfully Stopped
Oracle Management Server is Down

$ emctl start oms
Oracle Enterprise Manager 11g Release 1 Grid Control
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Starting WebTier…
WebTier Successfully Started
Starting Oracle Management Server…
Oracle Management Server Successfully Started
Oracle Management Server is Up

Now you can login to the Enterprise Manager Grid Control URL: https://xx.xx.xx.xxx:7799/em



Enter system/password or sysman/password.

I am going to discuss how to deploy agent in another Post.