OEM configuration steps in Oracle 12c

oracle 12c oem installation and oracle enterprise manager 12c installation guide and oracle enterprise manager 12c new features
MattGates Profile Pic
MattGates,United States,Professional
Published Date:02-08-2017
Your Website URL(Optional)
Comment
Installation of OEM 12c In this chapter we will cover: f Installing Enterprise Manager System with Simple configuration option f Installing Enterprise Manager System with Advanced cong fi uration option f Understanding Advanced Installer options f Installing Oracle Management Agent using the RPM file f Installing Oracle Management Agent using the agentDeploy.sh script Introduction The objective of this chapter is to outline the actual installation steps of OEM 12c and its agents, using various options of OEM 12c. All of these recipes have been developed to work on a server running Oracle Enterprise Linux 5u3 and Oracle Enterprise Manager Cloud Control 12c Version 12.1.0.1.0. Installing Enterprise Manager System with Simple configuration option There are two installation options for Enterprise Manager: f Simple f Advanced The Simple installation option is a quick and easy method to install OEM 12c, typically with the default options chosen by the installer. aInstallation of OEM 12c With the Advanced installation option, you can choose custom options as per your specific requirements. The following recipe describes installing OEM with the Simple configuration option. Getting ready Before you start, ensure that the server is connected to the network, and an SSH or a telnet client is available. Also, make sure that you have access to the Unix server as a root user or as a privileged user. OEM 12c Release 1 software can be downloaded fromhttps://edelivery.oracle.com/. The following files are available for download: V30905-01.zip V30906-01.zip V30907-01.zip Alternatively the latest version of this software can be downloaded from http://www. . oracle.com/technetwork/oem/grid-control/downloads/index.html How to do it... To install OEM 12c with the Simple cong fi uration option, perform the following steps: 1. Change the user ownership of the software location and then extract the OEM 12c software as the root user. chown -R oraoem:oinstall /u01/software su oraoem cd /u01/software unzip V30905-01.zip unzip V30906-01.zip unzip V30907-01.zip 2. Create aMiddleware directory as a root user, with the owner asoraoem and the group asoinstall. mkdir -p /u01/app/Middleware chown -R oraoem:oinstall /u01/app/Middleware 42 aChapter 2 3. Start the installation using therunInstaller command as useroraoem. Please note that free space on the/tmp mountpoint on the server must be greater than 400 MB. If adequate space is not available in/tmp, then specify theTEMP environment variable to use a location where at least 400 MB is available. cd /u01/software TEMP=/u01/tmp export TEMP ./runInstaller Starting Oracle Universal Installer... Checking Temp space: must be greater than 400 MB. Actual 32194 MB Passed Checking swap space: must be greater than 150 MB. Actual 3320 MB Passed Checking monitor: must be configured to display at least 256 colors. Actual 16777216 Passed Preparing to launch Oracle Universal Installer from /u01/tmp/ OraInstall2012-03-27_12-14-10AM. Please wait . 4. Deselect the I wish to receive security updates via My Oracle Support checkbox and then click on Next. 43 aInstallation of OEM 12c 5. Select Skip and then click on Next. 6. Click on Next. 44 aChapter 2 7. Select the Create a New Enterprise Manager System option and then select Simple. Enter the Middleware Home Location path. In this example, the middleware home is specified as /u01/app/Middleware. Now click on Next. 8. Enter an administrator password, which will be used as a common password for OEM 12c configuration. Enter the details in the Database Host Name field of the OEM 12 c repository database, along with Port, Service/SID, and SYS Password and then click on Next. 9. The automatic stats gathering job must be disabled. 45 aInstallation of OEM 12c 10. Click on Yes so that the installer takes care of the installation. 11. Review the installation path of the binaries. 12. Click on Install. 13. Theroot.sh command needs to be run on a different telnet window. 46 aChapter 2 14. Open a new terminal and connect it as root. . /u01/app/Middleware/oms/allroot.sh 15. Click on OK. 16. Review the information on the screen and then click on Close to complete the OEM 12c installation. 47 aInstallation of OEM 12c 17. Click on the OEM 12c URL and ensure that the URL is accessible. How it works... The preceding commands provide details about changing the owner of the software, creating a middleware directory, and the execution of the steps to install the OEM 12c system using the Simple configuration option. OEM 12 c is used to manage and maintain various Oracle databases and Fusion Middleware. There's more... The preceding commands will vary depending on the operating system being used. This is valid for Oracle Enterprise Linux. Installing Enterprise Manager System with Advanced configuration option In the Advanced installation option, the user can choose custom options as per their specific business requirements. The following recipe describes how to install OEM with the Advanced configuration option. 48 aChapter 2 Getting ready The OEM 12c Release 1 software can be downloaded from https://edelivery.oracle.com/. Alternatively the software can be downloaded athttp://www.oracle.com/ technetwork/oem/grid-control/downloads/index.html. How to do it... To install OEM 12c with the Advanced configuration option, perform the following steps: 1. Perform steps 1 to 6 of the preceding recipe Installing Enterprise Manager System with Simple configuration option . 2. Select the Create a new Enterprise Manager System option and then select Advanced. Enter the Middleware Home Location path. In this example, the middleware home location is specified as /u01/app/Middleware. 3. Click on Next. 49 aInstallation of OEM 12c 4. Select the optional plugins as per your business requirements. 5. Click on Next. 6. On the WebLogic Server Configuration Details screen, enter the credentials for the WebLogic User Name field and the required credentials for the Node Manager User Name field, and validate the path in the Oracle Management Service Instance Base Location field. 50 aChapter 2 7. Click on Next. 8. Enter the details of the OEM 12c repository database , and also specify the Database Host Name, Port, SID, and SYS Password, and then click on Next. 9. The automatic stats gathering job must be disabled. Click on Yes so that the installer takes care of this. 51 aInstallation of OEM 12c 10. Set the password (a note of these) and then click on Next. 11. On this screen, the user can amend the port number. In case the default port number is already in use by another application running on the server, then the user can select a new available port. The port must be greater than 1024 and less than 65535. In this example, default ports have been selected. 12. Click on Next. 13. Review the installation path of the binaries and then click on Install. 52 aChapter 2 14. Click on Next. 15. Open a new PuTTY terminal and execute the script as a root user, and then click on OK. 16. Review the information on the Installation Progress Details screen. 17. Click on Close to complete the OEM 12c installation. 53 aInstallation of OEM 12c How it works... This recipe provides details about changing the owner of the software, creating a middleware directory, and execution of the steps required to install the OEM 12c system using the Advanced configuration option. OEM 12 c is used to manage and maintain various Oracle databases and Fusion middleware. There's more... The preceding commands will vary depending on the operating system being used. The commands used above are valid for Oracle Enterprise Linux. Understanding Advanced Installer options The following recipe describes the various options available during the OEM installation process. This is primarily to address user specific-customizations. Getting ready Connect to the OEM server as the same user as the one used for the installation of OEM 12c. How to do it... 1. Change the WebLogic Domain Name. During OEM 12c installation, the installer creates a default domain name of GCDomain. To change the domain name during the installation use theWLS_ DOMAIN_NAME command line argument, as shown below: cd /u01/software TEMP=/u01/tmp export TEMP ./runInstaller WLS_DOMAIN_NAME=OEMDomain 2. Change the Provisioning Advisor Framework (PAF) staging directory. A Provisioning Advisor Framework (PAF) staging directory is created by default (/tmp) for copying the software library entities related to the deployment procedures. This location is used only for provisioning activities—entities are copied for the deployment procedure and then deleted once the deployment procedure ends. 54 aChapter 2 If you want to override this location and use a custom location then that installer need to invoke theEM_STAGE_DIR option, as shown below: cd /u01/software mkdir /spare/paf12c ./runInstaller EM_STAGE_DIR=/spare/paf12c 3. Install the additional plugins. The OEM 12c installation has various plugins that need to be installed for integration with other products, for example Oracle GoldenGate. 4. Download the required plugins from the OTN website at: http://www.oracle.com/technetwork/oem/grid-control/downloads/ index.html 5. Transfer the required plugin files to any staging directory on the server. The following command can be used to provide the plugin location during the OEM 12c installation. cd /u01/software ./runInstaller -pluginLocation /u01/software/ The plugin page will display additional plugins apart from the plugin specified in the custom location. Now the user can choose the plugins under the Advanced installation option, and complete the installation. 6. Use the optionsSTART_OMS andb_startAgent. OMS and the Management Agent start automatically upon successful installation. If we do not want to start OMS or Management Agent then we can achieve that by invoking therunInstaller command with theSTART_OMS option and the b_startAgent option. The value can be set toTRUE orFALSE depending on the control we need to achieve. ‰ To prevent the automatic start of OMS after installation, use the following command: ./runInstaller START_OMS=FALSE b_startAgent=TRUE ‰ To prevent the automatic start of Management Agent, use the following command: ./runInstaller START_OMS=TRUE b_startAgent=FALSE 55 aInstallation of OEM 12c 7. Configure the OEM with a different hostname other than the physical host. OEM is configured with a different hostname other than the physical host. The following command explains how to invoke OEM installed using a different hostname other than the physical host typically specified in /etc/hosts. The hostname should not contain any underscores. ./runInstaller ORACLE_HOSTNAME=servername.com How it works... This recipe describes various Advanced installation options. This way users can create a customized Cloud Control WebLogic domain, install custom plugins as per your business requirements, configure automatic start/stop of OMS and Management Agent, and specify a different hostname other than the physical server. There's more... This recipe will vary depending on the operating system being used. The examples used here are valid for Oracle Enterprise Linux. Installing Oracle Management Agent using the RPM file Oracle Management Agent (Management Agent) is one of the core components of Enterprise Manager Cloud Control and enables you to convert an unmanaged host to a managed host in the Enterprise Manager System. The Management Agent works in conjunction with the plugins to monitor the targets running on a managed host. This recipe describes the installation of Oracle Management Agent using the RPM file. Getting ready Installing a Management Agent by using its.rpm file is primarily a silent way of installing a Management Agent. Make sure that you have access to the Unix server as a root user or as a privileged user. 56 aChapter 2 How to do it... 1. Check the existence of the/usr/lib/oracle directory, and create it if it does not exist already. ls -lrt /usr/lib/oracle ls: /usr/lib/oracle: No such file or directory mkdir /usr/lib/oracle chmod 777 /usr/lib/oracle 2. Verify the existence of the rpm build package and install it on the OMS host, if required. rpm -qa rpm-build yum install rpm-build 3. Connect to the OMS host as an OEM 12c installation owner and log in to OEM by using theemcli command. export OMS_HOME=/u01/app/Middleware/oms OMS_HOME/bin/emcli login -username=sysman -password=xxxxxxxx Login successful 4. Synchronizeemcli. OMS_HOME/bin/emcli sync Synchronized successfully 5. Identify the platforms for which the Management Agent software is available on the OMS host. OMS_HOME/bin/emcli get_supported_platforms Getting list of platforms ... Check the logs at /u01/app/Middleware/oms/bin/agent.log About to access self-update code path to retrieve the platforms list.. Getting Platforms list ... - Version = 12.1.0.1.0 Platform = Linux x86-64 - Platforms list displayed successfully. 57 aInstallation of OEM 12c 6. Download the.rpm file of the Management Agent from the Oracle software library to a temporary directory on the OMS host. OMS_HOME/oms/bin/emcli get_agentimage_rpm -destination=/u01/ software -platform=""Linux x86-64"" -version=12.1.0.1.0 Platform:Linux x86-64 Destination:/u01/software Checking for disk space requirements... === Partition Detail === Space free : 17 GB Space required : 1 GB RPM creation in progress ... Check the logs at /u01/software/get_agentimage_rpm_2012-04-11_17- 18-26-PM.log Copying agent image from software library to /u01/software Setting property ORACLE_HOME to:/u01/app/Middleware/oms calling pulloneoffs with arguments:/u01/app/Middleware/oms/ u01/app/Middleware/oms/sysman/agent/12.1.0.1.0_AgentCore_226. zip12.1.0.1.0Linux x86-64/u01/softwaretrue Agent Image copied successfully... Creation of RPM started... RPM creation successful. Agent image to rpm conversion completed successfully Now we have the.rpm file oracle-agt-12.1.0.1.0-1.0.x86_64.rpm available at/u01/software. Copy the newly-created agent RPM file to the relevant target to install the OEM 12c Cloud Control Management Agent. Connect to the target server as a privileged user and start the installation. 7. Create a user for the OEM 12c Management Agent installation. Ideally it should be the same as the OEM 12c installation user on the OMS server. In this example, oraoem is used as the Unix user. 8. Create the home directory for the Management Agent installation. mkdir -p /dboracle/product/agent12c 9. Enter the OMS server host domain name in the/etc/hosts file. 58 aChapter 2 10. Run the.rpm file as a root user to install the Management Agent. rpm -ivh /scratch/oracle-agt-12.1.0.1.0-1.0.x86_64.rpm Preparing... 100% Running the prereq 1:oracle-agt 100% Follow these steps to complete the Management Agent rpm installation: 1. Edit the properties file/usr/lib/oracle/agent/agent.properties and enter the correct values. 2. Execute the/etc/init.d/config.pl command. 11. Edit theagent.properties file to provide the OMS host and target server details. - s_OMSHost:String OMS host info required to connect to OMS s_OMSPort:String OMS port info required to connect to OMS AGENT_REGISTRATION_PASSWORD:String Agent Registration Password needed to establish a secure connection to the OMS. - s_OMSHost=agent_servername.domainname.com s_OMSPort=7799 AGENT_REGISTRATION_PASSWORD=xxxxxxxx - agentUserName:String User name with which the agent should be installed. agentUserGroup:String Group to which the agent user belogs. - agentUserName=oraoem agentUserGroup=oinstall 59 aInstallation of OEM 12c - OraInvLoc:String Absolute path of the inventory location where the agent user has write permissions. Example : OraInvLoc=/usr/lib/oraInventory - OraInvLoc=OraInvLoc - BASEDIR:String Location of the agent base directory. Example: BASEDIR=/tmp/agentNG - BASEDIR=/dboracle/product/agent12c - ORACLE_HOSTNAME:String Virtual hostname where the agent is deployed. Example: ORACLE_HOSTNAME=hostname.domain - ORACLE_HOSTNAME=ORACLE_HOSTNAME 12. Execute the/etc/init.d/config.pl script to complete the Management Agent installation. . /etc/init.d/config.pl …. Agent Configuration completed successfully The following configuration scripts need to be executed as the ""root"" user. /bin/sh Root script to run /dboracle/product/agent12c/core/12.1.0.1.0/root.sh To execute the configuration scripts: 1. Open a terminal window 2. Log in as ""root"" 3. Run the scripts 60 a