11 Deploying Management Agent in Silent Mode

Enterprise Manager Grid Control (Grid Control) supports silent installations in which you can install the Grid Control components such as Management Agent without going through an interview phase (displaying pages or responding to questions). In silent installations, a response file provides the necessary installation information, typically answered by you, using stored values.

This chapter provides instructions to install Management Agent in silent mode. In particular, it covers the following:

Available Response Files
Running Response Files
Silent Installation Process
Using Silent Mode to Install Additional Management Agent

Note:

You do not need to set the DISPLAY environment variable for silent installations using Oracle Universal Installer.

Available Response Files

The response file available for installing Management Agent in silent mode is additional_agent.rsp. You may fine this response files on the installation DVD-ROM at <DVD>/response.

Running Response Files

Run the response files in the following way:

For UNIX Platforms

Instantiate the appropriate response file and run it as shown in the following way:
```
./runInstaller -silent -responseFile=<absolute path of the response file> -waitforcompletion
```
For Microsoft Windows Platforms

Instantiate the appropriate response file and run it as shown in the following way:
```
./setup.exe -silent -responseFile <absolute path of the response file>
```

Silent Installation Process

The silent installation on a UNIX environment can bee seen as a three-step process:

noconfig: In the first step, you must execute the -noconfig option. This will copy all the bits into the corresponding Oracle homes.
allroot.sh/orainstRoot.sh: After the bits are copied, the installer will prompt you to run the allroot.sh script (and orainstRoot.sh) or root.sh script (depending on the installation type).
- Run the orainstRoot.sh script if this is the first Oracle product installation on your host.
- Run the allroot.sh script from the first Oracle home that was created during installation.
runconfig.sh: You must pass this command to run the configuration assistants.

For an additional Management Agent installation, run:
```
<AGENT_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<Agent Home> MODE=perform ACTION=configure
```

Note:

If you want to use the -noconfig option during the silent installation, you must execute the runconfig.sh command at the end of the installation in order to run the configuration assistants.

Note:

If the Management Agent does not start up automatically when you restart the host, then do the following:

Open the agentstup file from the Oracle home of the Management Agent:

$ORACLE_HOME/install/unix/scripts/agentstup
Edit the file to replace executingUser=$USER with executingUser=`id -un`. Then, save and exit the file.
Run the root.sh script from the Oracle home of the Management Agent:

$<ORACLE_HOME>/root.sh
Restart the Management Agent by running the following command from the Oracle home of the Management Agent:

$<ORACLE_HOME>/bin/emctl start agent

This is a one-time action to be taken. Step (1) to Step (3) will ensure that the Management Agent starts up automatically every time you restart the host in the future.

Caution:

When you are using the -noconfig option in your installation, ensure you also pass -silent to invoke the installer. The -noconfig option must be executed only during silent installations.

Using Silent Mode to Install Additional Management Agent

To perform a silent installation of this type:

Copy the <DVD>/response/additional_agent.rsp file to a location on your local host.

Modify the following entries in the response file.

Table 11-1 Parameters to Modify in additional_agent.rsp File

Parameter	Description
FROM_LOCATION	Specify the complete path to the products.xml file. For example, FROM_LOCATION = "../oms/Disk1/stage/products.xml".
BASEDIR	Specify the directory where the ORACLE_HOME directories must be created. For example, on Microsoft Windows, BASEDIR = "C:\OHOME1", and on Linux, BASEDIR = "/scratch/OracleHomes".
INSTALLATION_NAME	Specify the name to be used for creating the Oracle home directories. For example, INSTALLATION_NAME = "OHOME1".
sl_OMSConnectInfo	SSpecify the host name and port of the OMS. The values must be in the form {"HostName","Port"}. For example, sl_OMSConnectInfo={"oms.xyz.com", "4881"}.
CLUSTER_NODES	If you deployed the agent to a cluster, then specify the nodes of that cluster. Separate the nodes by a comma, Do NOT include spaces between the comma-separated node list. For example, "CLUSTER_NODES={node1,node2,node3}".

Invoke the runInstaller (setup.exe on Microsoft Windows) by executing:

<DVD>/<runInstaller or setup.exe> -silent -responseFile <location>/additional_agent.rsp

The following message on the root.sh scripts is displayed (for UNIX only):

WARNING: A new inventory has been created in this session. However, it has not yet been registered as the central inventory of this system.To register the new inventory please run the script '<User's Home Dir>/oraInventory/orainstRoot.sh' with root privileges.If you do not register the inventory, you may not be able to update or patch the products you installed.The following configuration scripts need to be executed as the root user.#!/bin/sh#Root script to run<User's Home Dir>/oraInventory/orainstRoot.sh<Install Location>/agent10g/root.shTo execute the configuration scripts:    1. Open a terminal window    2. Log in as root    3. Run the scripts    4. Return to this window and click OK to continue

Note:

If the Management Agent does not start up automatically when you restart the host, then do the following:

Open the agentstup file from the Oracle home of the Management Agent:

$ORACLE_HOME/install/unix/scripts/agentstup
Edit the file to replace executingUser=$USER with executingUser=`id -un`. Then, save and exit the file.
Run the root.sh script from the Oracle home of the Management Agent:

$<ORACLE_HOME>/root.sh
Restart the Management Agent by running the following command from the Oracle home of the Management Agent:

$<ORACLE_HOME>/bin/emctl start agent

This is a one-time action to be taken. Step (1) to Step (3) will ensure that the Management Agent starts up automatically every time you restart the host in the future.

Caution:

The agent you are installing is not secure by default. To secure the agent, run the following command. However, note that even after securing the Management Agent, some data might still be transferred over the network without being encrypted.

AGE<NT_HOME>/bin/emctl secure agent

Setting Up Proxy Configuration for the Management Agent

There are two ways to specify proxy information for a Management Agent:

Specify values for s_proxyHost and s_proxyPort using a response file when performing a silent installation using Oracle Universal Installer.

Specify values directly through the command-line option when invoking Oracle Universal Installer. For example:

<runInstaller or setup.exe> oracle.sysman.top.agent:s_proxyHost="<value>" oracle.sysman.top.agent:s_proxyPort="<value>"