Skip Headers
Oracle® Enterprise Manager Cloud Control Advanced Installation and Configuration Guide
12c Release 4 (12.1.0.4)

E24089-33
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

9 Installing the Oracle Management Agent Software Now and Configuring It Later

This chapter explains how you can install only the software binaries of Oracle Management Agent (Management Agent) at one point and configure the installation at a later stage. In particular, this chapter covers the following:

9.1 Overview

You can choose to install only the software binaries of the Management Agent at one point and configure it at a later stage to work with the associated Oracle Management Service (OMS). This approach enables you to divide the installation process into two phases, mainly the installation phase and the configuration phase.

During the installation phase, you invoke the agentDeploy.sh script passing the -softwareOnly argument to copy the software binaries and create an Oracle home for the Management Agent. During the configuration phase, you invoke the same script passing -configOnly to configure the software binaries.

Understandably, the installation phase takes much lesser time compared to the configuration phase because the installation phase involves only copying of binaries. This helps you plan your installation according to the time and priorities you have.

Note:

This installation type is available only in silent mode.

Note:

If you want to repoint your existing Management Agents to a new Oracle Management Service (OMS), then you must first deinstall those Management Agents and plug-ins, and then redeploy those Management Agents and plug-ins using the new OMS. This is typically done when you want to move from an Enterprise Manager Cloud Control system in a test environment to an Enterprise Manager Cloud Control system in a production environment.

When you repoint your existing Management Agents to a new OMS, you cannot move the targets monitored by the Management Agents, the target history, and the Management Agent history. The monitored targets and the history data is lost.

9.2 Before You Begin

Before you begin installing a Management Agent, review the points outlined in Section 6.2.

9.3 Prerequisites

Before installing the Management Agent, ensure that you meet the prerequisites described in Section 6.3.

9.4 Installation Procedure

To install only the software binaries of a Management Agent in silent mode, follow one of the procedures mentioned in Section 6.4.2. While invoking the deployment script, ensure that you pass the -softwareOnly option:

<Software_Extracted_Location>/agentDeploy.sh AGENT_BASE_DIR=<absolute_path_to_agentbasedir> RESPONSE_FILE=<absolute_path_to_responsefile> -softwareOnly

For example, /tmp/agtImg/agentDeploy.sh AGENT_BASE_DIR=/scratch/agent12c RESPONSE_FILE=/tmp/agtImg/agent.rsp -softwareOnly

If the Management Agent is installed successfully, a message mentioning so is displayed on the command line.

Note:

Do not pass the option -forceConfigure.

9.5 Configuration Procedure

To configure the software binaries of a Management Agent in silent mode, invoke the deployment script with the following options from the Management Agent home:

$<AGENT_HOME>/sysman/install/agentDeploy.sh AGENT_BASE_DIR=<absolute_path_to_agentbasedir> RESPONSE_FILE=<absolute_path_to_responsefile> -configOnly

For example, $<AGENT_HOME>/sysman/install/agentDeploy.sh AGENT_BASE_DIR=/scratch/agent12c RESPONSE_FILE=/tmp/agtImg/agent.rsp -configOnly

If the Management Agent is installed successfully, a message mentioning so is displayed on the command line.

Note:

  • The response file you pass here is the same response file you passed in Section 9.4.

  • Do not pass the option -forceConfigure.

9.6 After You Install

After you install the Management Agent, follow the steps outlined in Section 6.5.