Skip Headers
Oracle® Enterprise Manager Grid Control Advanced Installation and Configuration Guide
11g Release 1 (11.1.0.1.0)

E16847-15
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

J Understanding Optional Arguments Run with ConfigureGC.pl Script

When you adopt the Installing Software Only and Configuring Later approach to install Enterprise Manager Grid Control or an additional Oracle Management Service (OMS), after installing the software binaries, to configure the product, you run the ConfigureGC.pl script.

The following are the optional arguments that can be passed with the ConfigureGC.pl script:

-noaddoncheck

While invoking the ConfigureGC.pl script, by default, some optional Configuration Assistants are run, including Verify Addons Installed. If you want to avoid running this Configuration Assistant for verifying the add-ons, then invoke the ConfigureGC.pl script with the -noaddoncheck argument.

For example,

$<ORACLE_HOME>/perl/bin/perl <ORACLE_HOME>/sysman/install/ConfigureGC.pl -noaddoncheck

ADDON_RESPONSE_FILE

If you want to specify some information about add-ons, then edit the following file, which is available in the Oracle home of the OMS, and pass it with the ConfigureGC.pl script.

<ORACLE_HOME>/sysman/addons/addon.rsp.template

For example,

$<ORACLE_HOME>/perl/bin/perl <ORACLE_HOME>/sysman/install/ConfigureGC.pl ADDON_RESPONSE_FILE=<AbsolutePathToResponseFile>

OMS_RESPONSE_FILE

To install the software binaries, you either invoke the Enterprise Manager Grid Control Installation Wizard and specify the required details, or use a response file that captures the required details.

However, if you want to overwrite the information that you provided in the installer or in a response file, then create a new response file with the updated information and pass it with the ConfigureGC.pl script.

For example,

$<ORACLE_HOME>/perl/bin/perl <ORACLE_HOME>/sysman/install/ConfigureGC.pl OMS_RESPONSE_FILE=<absolute_path_to_response_file>

Table J-1 and Table J-2 show the parameters you can pass in this response file to overwrite the information you provided while installing a complete Enterprise Manager system and additional OMS, respectively.

Table J-1 Parameters Recognized by ConfigureGC.pl Script While Configuring Enterprise Manager System

Parameter Description

ORACLE_INSTANCE_HOME_LOCATION

Specify the directory where the configuration files of OMS can be created.

By default, this location is under the parent directory of the Oracle Middleware Home. For example, if the Oracle Middleware Home is /u01/app/Oracle/Middleware, then the OMS Instance Base is /u01/app/Oracle/gc_inst.

For more information about this location, see What Is Oracle Management Service Instance Base Location?.

WLS_ADMIN_SERVER_USERNAME

Specify the default user name that will be used as the administrative user for the WebLogic Domain. By default, the user name is weblogic.

WLS_ADMIN_SERVER_PASSWORD

Specify the password for the WebLogic user account.

WLS_ADMIN_SERVER_CONFIRM_PASSWORD

Confirm the password for the WebLogic user account.

NODE_MANAGER_PASSWORD

Specify the node manager password.

NODE_MANAGER_CONFIRM_PASSWORD

Confirm the node manager password.

DATABASE_HOSTNAME

Specify the fully-qualified name of the host where the existing database resides. For example, db.host.com.

LISTENER_PORT

Specify the listener port to connect to the existing database.

SERVICENAME_OR_SID

Specify the Service name or the System ID (SID) of the existing database.

SYS_PASSWORD

Specify the SYS user account's password.

CONNECT_STRING

Specify the details of the database to which you want to connect. For example, if you are connecting to an Oracle RAC Database, and if you have specified the virtual IP address of one of its nodes, then specify details of the other nodes using this parameter.

Syntax:

(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=<HOSTNAME>)(PORT=<PORT>)))(CONNECT_DATA=(SID=<SID>)))

Example:

(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=stajs11.us.oracle.com)(PORT=1521)))(CONNECT_DATA=(SID=opg44)))

MANAGEMENT_TABLESPACE_LOCATION

Specify the full path to the location where the data file for management tablespace (mgmt.dbf) can be stored. Ensure that the specified path leads up to the file name.

For example:

  • If the database is on a file system, then the path must look like /u01/oracle/prod/oradata/mgmt.dbf

  • If the database is on Automatic Storage Management (ASM), then the path must look like +<disk_group1>/prod/oradata/mgmt.dbf, where disk_group1 is a diskgroup created on ASM and prod is the Service ID (SID).

  • If the database is on a raw device, then the path must look like </dev/raw1>/prod/oradata/mgmt.dbf, where /dev/raw1 is the raw device and prod is the SID.

Enterprise Manager Grid Control requires this data file to store information about the monitored targets, their metrics, and so on. Essentially, everything else other than configuration data, software library data, and audit data.

CONFIGURATION_DATA_TABLESPACE_LOCATION

Specify the full path to the location where the data file for configuration data tablespace (mgmt_ecm_depot1.dbf) can be stored. Ensure that the specified path leads up to the file name.

For example, /home/john/oradata/mgmt_ecm_depot1.dbf

Enterprise Manager Grid Control requires this data file to store configuration information collected from the monitored targets.

JVM_DIAGNOSTICS_TABLESPACE_LOCATION

Specify the full path to a location where the data file for JVM diagnostics data tablespace (mgmt_ad4j.dbf) can be stored. Ensure that the specified path leads up to the file name. Enterprise Manager Grid Control requires this data file to store JVM-related monitoring data.

For example, /home/john/oradata/mgmt_ad4j.dbf

LOCK_ORACLE_MANAGMENT_SERVICE

OMS always runs in a secure mode, and can further have a locked or an unlocked state. In an unlocked state, the Management Agents that are secure and the Management Agents that are not unsecure communicate with the OMS using HTTPS and HTTP protocols, respectively. However, in a locked state, only secure Management Agents communicate with OMS using HTTPS protocol.

  • Specify TRUE if you want to lock the OMS running in a secure mode and further enhance the security of communication between the OMS and the Management Agents.

  • Specify FALSE if you do NOT want to further enhance the security of communication between the OMS and the Management Agent.

SYSMAN_PASSWORD

Specify a password for creating a SYSMAN user account. This password is used to create the SYSMAN user, which is the primary owner of the Management Repository schema.

SYSMAN_CONFIRM_PASSWORD

Confirm the password for creating a SYSMAN user account.

ALLOW_ONLY_SECURE_ACCESS_TO_CONSOLE

By default, you can use either HTTP or HTTPS protocol to access the Enterprise Manager Grid Control console.

  • Specify TRUE if you want to secure the access and allow users to access the console only using HTTPS protocol.

  • Specify FALSE if you do NOT want to secure the access and do NOT want to allow users to access the console only using HTTPS protocol.

AGENT_REGISTRATION_PASSWORD

To secure the communication between the OMS and the Management Agents, specify a password. Note that you have to provide the same registration password for securing your Management Agents.

AGENT_REGISTRATION_CONFIRM_PASSWORD

Confirm the agent registration password.

START_OMS

Specify TRUE if you want the OMS to start automatically after installation. Specify FALSE if you do NOT want it to start automatically.

SHARED_RECEIVE_DIRECTORY_LOCATION

Specify the full path to a location where you want to configure the shared file system loader.

A shared file system loader is typically required when you are planning to have multiple OMSes, so that a common location is maintained to store all the metric data files uploaded by the Management Agents.

If you configure the central directory now, then all subsequent additional OMS installations, which connect to the same Oracle Database, will automatically be mapped to this central directory.


Table J-2 Parameters Recognized by ConfigureGC.pl Script While Configuring an Additional OMS

Parameter Description

ORACLE_INSTANCE_HOME_LOCATION

Specify the directory where the configuration files of OMS can be created.

By default, this location is under the parent directory of the Oracle Middleware Home. For example, if the Oracle Middleware Home is /u01/app/Oracle/Middleware, then the OMS Instance Base is /u01/app/Oracle/gc_inst.

For more information about this location, see What Is Oracle Management Service Instance Base Location?.

ADMIN_SERVER_HOSTNAME

Specify the name of the host where the Admin Server is running. Admin Server is the server that was created when you installed the first Oracle Management Service 11g Release 1.

ADMIN_SERVER_PORT

Specify the port on which the Admin Server is running.

DATABASE_HOSTNAME

Specify the fully-qualified name of the host where the existing database resides. For example, db.host.com.

LISTENER_PORT

Specify the listener port to connect to the existing database.

SERVICENAME_OR_SID

Specify the System ID (SID) of the existing database.

SYSMAN_PASSWORD

Specify the SYSMAN user account's password.

CONNECT_STRING

Specify the details of the database to which you want to connect.

Syntax:

(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=<HOSTNAME>)(PORT=<PORT>)))(CONNECT_DATA=(SID=<SID>)))

Example:

(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=stajs11.us.oracle.com)(PORT=1521)))(CONNECT_DATA=(SID=opg44)))

AGENT_REGISTRATION_PASSWORD

To secure the communication between the OMS and the Management Agents, specify a password. Note that you have to provide the same registration password for securing your Management Agents.

AGENT_REGISTRATION_CONFIRM_PASSWORD

Confirm the agent registration password.

LOCK_ORACLE_MANAGMENT_SERVICE

OMS always runs in a secure mode, and can further have a locked or an unlocked state. In an unlocked state, the Management Agents that are secure and the Management Agents that are not unsecure communicate with the OMS using HTTPS and HTTP protocols, respectively. However, in a locked state, only secure Management Agents communicate with OMS using HTTPS protocol.

  • Specify TRUE if you want to lock the OMS running in a secure mode and further enhance the security of communication between the OMS and the Management Agents.

  • Specify FALSE if you do NOT want to further enhance the security of communication between the OMS and the Management Agent.

ALLOW_ONLY_SECURE_ACCESS_TO_CONSOLE

By default, you can use either HTTP or HTTPS protocol to access the Enterprise Manager Grid Control console.

  • Specify TRUE if you want to secure the access and allow users to access the console only using HTTPS protocol.

  • Specify FALSE if you do NOT want to secure the access and allow users to access the console only using HTTPS protocol.

START_OMS

Specify TRUE if you want the OMS to start automatically after installation. Specify FALSE if you do NOT want it to start automatically.