Skip Headers
Oracle® Enterprise Manager Cloud Control Basic Installation Guide
12c Release 1 (12.1.0.1)
E22624-12
  Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
 
Next
Next
 

B Validating Command Locations

This chapter describes what property files and the command locations within them you need to validate before installing a standalone Oracle Management Agent (Management Agent). In particular, this chapter covers the following:

Overview of Property Files

Every time you install a Management Agent, the property files mentioned in the platformInfo.properties file are loaded with default locations to commands that are required for successfully running certain Application Programming Interfaces (APIs). For example, the ping executable. This section describes such property files. In particular, this section covers the following:

Property Files Loaded from platformInfo.properties File

Table B-1 describes the property files loaded from the platformInfo.properties file.

Table B-1 Property Files Loaded from platformInfo.properties File

Loading Order Property File Name Type Description

1

Paths.properties

Generic

Contains arguments that need to be passed every time the commands listed in this file are run.

2

sPaths.properties

Generic

Contains paths for all the commands that need to be run, regardless of the operating system.

3

ssPaths_<platform>.properties

Operating System-Specific

Contains commands that need to be run for a particular operating system. For example, ssPaths_linux_zseries64.properties.

On Microsoft Windows, the path to the Cygwin binaries is hardcoded in the ssPaths_msplats.properties file. If you install Cygwin in a location other than c:\cygwin (default location), it can cause the Management Agent installation to fail. To resolve this issue, you must either install Cygwin in the default directory (c:\cygwin), or update this properties file with the correct path to the Cygwin binaries.

4

userPaths.properties

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

Other Property Files Loaded

Table B-2 describes the other property files that are loaded.

Table B-2 Other Property Files Loaded

Property File Name Type Description

system.properties

Generic

Contains properties that help you control the activity and performance of the application. For example, these:

  • oracle.system.prov.threadpoolsize

    Number of threads that get created in the application and work in parallel to run the commands on the destination hosts. The default threadpool size value that is set is 32. You can specify an appropriate value for the threadpool size in this property.

  • oracle.sysman.prov.threadpoolmaxsize

    Number of threads that can increase dynamically depending on the workload. The default value used in the application is 256. You can specify an appropriate maximum value for the threadpool size in this property.

ignoreMessages.txt

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 ignoreMessages.txt file.

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 the messages (including the banner) to the ignoreMessages.txt file.

For example, when you run /usr/local/bin/sudo on a remote host, it writes the following messages on to the error stream. Error messages of this kind can be added to the ignoreMessages.txt file.

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

Validating Command Locations

The default command locations specified in the property files can vary between hosts and operating systems. Therefore, it is important to verify the command locations before you install a Management Agent.

To validate the command locations, follow these steps:

  1. Access the platformInfo.properties file from the following location of the OMS home, and make note of the property files you need to validate for your platform:

    $<OMS_HOME>/oui/prov/resources

  2. Access each of the property files you noted in Step (1), and verify that the command locations mentioned for the following variables map to valid locations on the OMS host:

    • SSH_PATH

    • SCP_PATH

    • SH_PATH

    • PING_PATH

  3. Access each of the property files you noted in Step (1), and verify that the command locations mentioned for the following variables also map to valid locations on the destination host:

    • SCP_PATH

    • SH_PATH

    • SSH_PATH

    • CHMOD_PATH

    • MKDIR_PATH

    • RM_PATH