Oracle® Enterprise Manager Grid Control Advanced Installation and Configuration Guide 11g Release 1 (11.1.0.1.0) Part Number E16847-10 |
|
|
PDF · Mobi · ePub |
This appendix describes what property files and the command locations within them you need to validate before installing Oracle Management Agent (Management Agent). In particular, this appendix covers the following:
Every time you install a Management Agent, the property files mentioned in the platformInfo.properties
file are loaded with default locations for commands that are required for successful running of certain Application Programming Interfaces (APIs). For example, the ping
executable. This section describes such property files. In particular, this section covers the following:
Table E-1 describes the property files loaded from the platformInfo.properties
file.
Table E-1 Property Files Loaded from platformInfo.properties File
Loading Order | Property File Name | Type | Description |
---|---|---|---|
1 |
Generic |
Contains arguments that need to be passed every time the commands listed in this file are run. |
|
2 |
Generic |
Contains paths for all the commands that need to be run, regardless of the platform. |
|
3 |
|
Platform-Specific |
Contains commands that need to be run for that platform. For example, On Microsoft Windows, the path to the Cygwin binaries is hardcoded in the |
4 |
Generic |
Contains variables that are used to specify the command paths. You must uncomment the variables that you want to use and specify appropriate values. |
Keep in mind the following points:
The property files mentioned in the platformInfo.properties
file are loaded one-by-one in ascending order. This means that command locations you specify in the last file that is loaded will override the values you specified for the same key in the previously loaded property file.
For example, spaths.properties
is loaded before ssPaths.properties
. So if the default location for the ping executable in sPaths.properties
file is usr/bin/ping
, and if location for the same executable in the ssPaths.properties file as usr/sbin/ping
, then the value in the latter file takes precedence over the former file.
If you want to include other command variables, then you can do one of the following:
Specify the additional command variables in sPaths.properties
, ssPaths_<platform>.properties
, or userPaths.properties
.
Create a new property file with additional command variables. Then, mention the name of this new property file in platforminfo.properties
.
Table E-2 describes the other property files that are loaded.
Table E-2 Other Property Files Loaded
Property File Name | Type | Description |
---|---|---|
|
Generic |
Contains properties that help you control the activity and performance of the application. For example, these:
|
|
Generic |
If there are error messages displayed in the error stream that you know can be ignored in the setup, then you can update these messages in the Generally, if the error stream contains data when you run any command, then it is assumed that the command failed, however, the data in the error stream may not always correspond to the error. So, to ignore such error messages, you must add these messages (including the banner) to the For example, when you run Administrator. It usually boils down to these two things:#1) Respect the privacy of others.#2) Think before you type.Password: This essentially is just a warning to the user and does not constitute the failure of the executed command. |
Note:
The data format for these files mandates only one property per line. You must specify the property values in the format:variable=value
.The default command locations specified in the property files can vary between hosts and platforms. Therefore, it is important to verify the command locations before you install a Management Agent.
This section describes what property files and command locations within them you need to validate before you install a Management Agent. In particular, this section covers the following:
In the property files present in the <OMS_INSTANCE_HOME>/sysman/prov/resources/
location, validate the command locations (on the OMS host) for the following variables:
SH_PATH
SSH_ARGS
SSH_KEYGEN_PATH
SSH_PATH
SCP_ARGS
SCP_PATH
UNZIP_ARGS
UNZIP_PATH
TAR_PATH
Instead of manually reviewing each of the property files, you can run the following command from the OMS instance home to automatically list the variables that are not found in the default locations.
$<OMS_INSTANCE_HOME>/sysman/prov/resources/scripts/validatePaths -dirloc oms/sysman/prov/resources/
Note:
Before running the command, set the environment variableJARS_LOC
to the following location of the OMS home where OraInstallar.jar
and remoteinterfaces.jar
are present:
$<ORACLE_HOME>/sysman/prov/agentpush/jlib
In the property files present in the <OMS_INSTANCE_HOME>/sysman/prov/resources/
location, validate the command locations (on the destination host) for the following variables:
SH_PATH
SH_ARGS
SCP_PATH
SCP_ARGS
SUDO_PATH
SSH_HOST_KEY_LOC
ZIP_PATH
TAR_PATH