Skip Headers
Oracle® Enterprise Manager Grid Control Installation and Basic Configuration
10g Release 2 (10.2)

Part Number B16228-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

4 Performing Enterprise Manager Silent Installations

This chapter contains the following sections:

Performing Silent Installations

Enterprise Manager supports silent installations in which you can install components without displaying pages or responding to questions. In silent installations, a response file provides the necessary installation information, normally 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 shows the response files made available for each installation type. The response files are available on the installation DVD-ROM at:

<DVD>/Response

Instantiate the appropriate response file and execute it as shown below:

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

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:

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


Note:

If you are executing a silent installation with -noconfig option, the installer prompts you to execute allroot.sh at the end of the installation in order to run the configuration assistants. You must run root.sh from the first Oracle home that was created during the installation (typically the database Oracle home), and then execute runconfig.sh.

If you are performing a chain installation, the command to run the config assistants with encapsulated xml is:

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

See Appendix D, "Executing the runConfig Command Line Tool" for more information.



Caution:

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

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 by executing:

    <DVD>/runInstaller -silent -responseFile <location>/em_with_new_db.rsp
    
    

    The following message on the root.sh scripts is displayed:

    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
    
    

    IMPORTANT:

    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.

  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 by executing:

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

    The following message on the root.sh scripts is displayed:

    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 by executing:

    <DVD>/runInstaller -silent -responseFile <location>/additional_mgmt_service.rsp
    
    

    The following message on the root.sh scripts is displayed:

    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 by executing:

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

    The following message on the root.sh scripts is displayed:

    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, you must execute the following command from the agent Oracle home:
AGENT_HOME/bin/emctl secure agent <password>

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 set up a file with component names and desired port numbers. The installer uses the values from the file instead of the default port numbers.

This file is typically called the staticports.ini file, but you can rename it to anything that is appropriate. The AppendixG, "Formats for the Staticports.ini File" section describes the file format.

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

<DVD>/response/staticports.ini

When you start the installer, specify the appropriate parameter and the full path to the staticports.ini file on the command line. Make sure that you use the correct parameter for the installation type that you are using. If you use the incorrect parameter, the installer assigns default ports to all components.

For example, to install an additional Management Agent, in the DVD directory, type the following command at the command line:

/runInstaller -staticPortsIniFile <staticport.ini file name>

To invoke runInstaller with the staticports.ini option, execute the following command:

./runInstaller -staticPortsIniFile <staticport.ini file name>

This file is typically called the staticports.ini file, but you can rename it anything appropriate. The AppendixG, "Formats for the Staticports.ini File" of Appendix G, "Assigning Custom Ports", describes the file format.


See Also:

For more information on assigning custom port numbers for installation components, refer to the Oracle Application Server 10g Installation Guide for your operating system located at:
http://otn.oracle.com/documentation/appserver10g.html