4 Enterprise Manager Silent Installations

This chapter contains the following sections:

• Performing Silent Installations

• Assigning Custom Ports (Static Ports Feature)

Performing Silent Installations

Enterprise Manager supports silent installations in which you can install the Enterprise Manager Grid Control components (Management Service, additional Management Service, or 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 the user, using stored values.

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

Table 4-1, "Available Response Files for Silent Installation" shows the response files made available for each installation type. The response files are available on the installation DVD-ROM at:

<DVD>/response

Executing the Response File on UNIX

Instantiate the appropriate response file and execute it as shown in the following code excerpt:

./runInstaller -silent -responseFile=<absolute path of the response file> -waitforcompletion

Executing the Response File on Microsoft Windows

Instantiate the appropriate response file and execute it as shown in the following code excerpt:

./setup.exe -silent -responseFile <absolute path of the response file>

Table 4-1 Available Response Files for Silent Installation

Installation Option	Response File
Enterprise Manager 10g Grid Control Using a New Database	em_with_new_db.rsp
Enterprise Manager 10g Grid Control Using an Existing Database	em_using_existing_db.rsp
Additional Management Service	additional_mgmt_service.rsp
Additional Management Agent	additional_agent.rsp

See Also: Chapter 6, " Deploying the Management Agent" for more information on performing silent installations of Management Agents using the agentDownload script.

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

1. noconfig: In the first step, you must execute the -noconfig option. This will copy all the bits into the corresponding Oracle homes.

2. allroot.sh: After the bits have been copied, the installer will prompt you to run the allroot.sh (and orainstRoot.sh) or root.sh script (depending on the the installation type. This is required to run the configuration scripts. You must run allroot.sh from the first Oracle home that was created during the installation (typically the database Oracle home).

3. runconfig.sh: You must pass this command to execute the configuration assistants.

   For an Enterprise Manager installation using a new database, execute:

   <DB_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<database home path> ACTION=configure MODE=perform COMPONENT_XML={encap_emseed.1_0_0_0_0.xml}
   
   

   For an Enterprise Manager installation using an existing database, execute:

   <OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<OMS Home> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}
   
   

   For an additional Management Service installation, execute:

   <OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<OMS Home> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}
   
   

   For an additional Management Agent installation, execute:

   <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.

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.

Executing the Response File on Microsoft Windows

On Windows, you can perform an end-to-end silent installation by executing the following command:

./setup.exe -silent -responseFile <absolute path of the response file>

See Table 4-1 for a list of available response files for silent installations.

Silent Installation of Enterprise Manager Using a New Database

To perform a silent installation of this type:

1. Copy the <DVD>/response/em_with_new_db.rsp file to a location on the local machine and modify the Value Unspecified entries accordingly.

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

   <DVD>/<runInstaller or setup.exe> -silent -responseFile <location>/em_with_new_db.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>/db10g/allroot.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
   
   

   
   

   Caution: If this is the first time an Oracle product is being installed on the machine, the database listener targets will not be discovered, as the root.sh scripts have not been executed.

   
   

3. After the installation is complete, you must execute orainstRoot.sh and allroot.sh scripts as root (UNIX only).

4. To discover the Enterprise Manager targets, you can execute <Install Location>/agent10g/bin/agentca, or discover the targets from the Enterprise Manager console. See AppendixA, "Invoking the Agent Configuration Assistant in Standalone Mode" for more information on executing the Agent Configuration Assistant in standalone mode.

Silent Installation of Enterprise Manager Using an Existing Database

To perform a silent installation of this type:

1. Copy the <DVD>/response/em_using_existing_db.rsp file to a location on the local machine and modify the Value Unspecified entries accordingly.

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

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

   The following message on the root.sh scripts appears (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>/oms10g/allroot.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
   

Silent Installation of an Additional Management Service

To perform a silent installation of this type:

1. Copy the <DVD>/response/additional_mgmt_service.rsp file to a location on the local machine and modify the Value Unspecified entries accordingly.

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

   <DVD>/<runInstaller or setup.exe> -silent -responseFile <location>/additional_mgmt_service.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>/oms10g/allroot.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
   

Silent Installation of an Additional Management Agent

To perform a silent installation of this type:

1. Copy the <DVD>/response/additional_agent.rsp file to a location on the local machine and modify the Value Unspecified entries accordingly.

2. 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
   
   

Caution: The agent you are installing is not secure by default. To secure the agent, execute the following command: 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>"
  

Assigning Custom Ports (Static Ports Feature)

You can specify custom port numbers for components instead of having the installer assign default port numbers. This feature is called the static ports feature. To use static ports, you must set up a file with component names and the appropriate port numbers. The installer uses the values from the file instead of the default port numbers.

The staticports.ini file is available on the installation DVD-ROM at:

<DVD>/response/staticports.ini

To invoke runInstaller (setup.exe on Microsoft Windows) with the staticports.ini option, execute the following command:

./<runInstaller or setup.exe> -staticPortsIniFile <location>/staticport.ini

This file is called the staticports.ini file. Chapter4, "Formats for the Staticports.ini File" describes the file format.

See Also: Oracle Application Server 10g Installation Guide (for your operating system) for more information on assigning custom port numbers for installation components at: http://otn.oracle.com/documentation/appserver10g.html

Edit the local copy (the file on the hard disk) to include the required port numbers.

You do not need to specify port numbers for all components in the staticports.ini file. If a component is not listed in the file, the installer uses the default port number for that component.

When installation is complete, you can check the ORACLE_HOME/install/portlist.ini file to view the assigned ports.

Note: When choosing port numbers, consider the following: Port numbers cannot be greater than 65536. If you use a port number less than 1024 for a component, you must run the component as the root user. If you use a port number less than 1024 for a component, the installer cannot start up the component at the end of installation. You may need to configure the component first before you can start it up. See the appropriate component documentation for details.

The installer verifies that the ports specified in the file are available (free) by reading the Properties file in all the Oracle homes. If the installer detects that a specified port is not available, it displays an alert.

A port is considered to be free only if:

• There are no Oracle products assigned to that port.

• There are no processes running on that port.

The installer does not assign a port that is not available. To fix this:

1. Edit the staticports.ini file to specify a different port.

2. Click Retry. The installer rereads thestaticports.ini file and verifies the entries in the file again.

Note: The staticports.ini file uses the same format as the ORACLE_HOME/install/portlist.ini file, which is created after an Oracle Application Server installation. If you have installed Oracle Application Server and you want to use the same port numbers in another installation, you can use the portlist.ini file from the first installation as the staticports.ini file for subsequent installations.

Edit the local copy (the file on the hard disk) to include the appropriate port numbers.

Formats for the Staticports.ini File

The staticports.ini file has the following format. Replace port num with the port number that you want to use for the component.

# Enterprise Manager#Enterprise Manager Central Agent Port=port_num#Enterprise Manager Central Console Port=port_num#Enterprise Manager Central Console Secure Port=port_num# J2EE and Web Cache#Oracle HTTP Server Listen port=port_num#Oracle HTTP Server Listen (SSL) port=port_num#Oracle HTTP Server Diagnostic port=port_num#Web Cache HTTP Listen port=port_num#Web Cache HTTP Listen (SSL) port=port_num#Web Cache Administration port=port_num#Web Cache Invalidation port=port_num#Web Cache Statistics port=port_num#Oracle Notification Server Request port=port_num#Oracle Notification Server Local port=port_num#Oracle Notification Server Remote port=port_num#Application Server Control port=port_num#Application Server Control RMI port=port_num#Oracle Management Agent port=port_num#Log Loader port=port_num

Note: After having specified appropriate port values, ensure you remove the comment (#) for those properties before saving the file. The values are not considered otherwise.

Error Conditions that Cause the Installer to Resort to Default Ports

Check your staticports.ini file carefully, because a mistake can cause the installer to use default ports without displaying any warning. Here are some things that you should check:

• If a port is already being used by a component or any other application, do not specify that port (used port) in the staticports.ini file.

  
  

  Note: If you specify a port that is already in use, the related configuration assistant will also fail.

  
  

• If you have specified the same port for more that one component, the installation will display an error after the prerequisite checks phase. You must rectify this error before proceeding with the installation.

• If you have syntax errors in the staticports.ini file (for example, if you omitted the equal (=) character for a line), the installer ignores the line. For the components specified on such lines, the installer assigns the default ports. The installer does not display a warning for lines with syntax errors.

• If you misspell a component name, the installer assigns the default port for the component. Names of components in the file are case-sensitive. The installer does not display a warning for lines with unrecognized names.

• If you specify a nonnumeric value for the port number, the installer ignores the line and assigns the default port number for the component. It does this without displaying any warning.

• If you misspell the parameter on the command line, the installer does not display a warning. It continues and assigns default ports to all components.

• If you specify a relative path to the staticports.ini file (for example, ./staticports.ini) on the command line, the installer does not find the file. The installer continues without displaying a warning and it assigns default ports to all components. You must specify a full path to the staticports.ini file.

• If the parameter you specify on the command line does not match the installation type that you are performing (for example, if you specify the parameter for the middle tier but you are installing the infrastructure), the installer does not give a warning. It continues and assigns default ports to all components.