To install a standalone Management Agent, use the Add Host Targets Wizard that is accessible from within the Enterprise Manager console, or use EM CLI. The Add Host Targets Wizard is an application that offers GUI-rich, interactive screens. Oracle recommends that you use this wizard, or EM CLI, for the mass-deployment of Management Agents. For more information about the Add Host Targets Wizard, see What Is an Add Host Target Wizard? in the Oracle Enterprise Manager Advanced Installation and Configuration Guide.

When you install a standalone Management Agent on a host, you will see the following default contents in the agent base directory:

<agent_base_directory>
    |_____agent_24.1.0.0.0
          |_____sbin
          |_____OPatch
          |_____agent.rsp
          |_____bin
          |_____cfgtoollogs
          |_____config
          |_____install
          |_____instalclient
          |_____.
          |_____.
    |_____agent_inst
          |_____.
    |_____agentInstall.rsp
    |_____agentimage.properties

To install a standalone Management Agent on a host, the Management Agent software for the host platform must be downloaded and applied using Self Update.

This section describes how to download and apply the Management Agent software for different platforms using Self Update. In particular, it contains the following:

• Acquiring the Management Agent Software in Online Mode

• Acquiring the Management Agent Software in Offline Mode

This section describes the actions involved in installing standalone Management Agents. It consists of the following:

• Installing Standalone Management Agents Using Add Host Targets Wizard

• Format of the Host List File

• Installing Standalone Management Agents Using EM CLI

• Supported Additional Parameters for Installing Standalone Management Agents Using Add Host Targets Wizard or EM CLI

1. Verify the installation on the Add Host Status page, or using the get_add_host_status EM CLI verb. Review the progress made on each of the phases of the deployment operation — Initialization, Remote Prerequisite Check, and Agent Deployment.

   In the Add Host Targets Wizard, after you click Deploy Agent to install one or more Management Agents, you are automatically taken to the Add Host Status page.

   For information on using the get_add_host_status EM CLI verb, see Installing Standalone Management Agents Using EM CLI.

2. If required, manually verify the installation:
   1. Navigate to the Management Agent home and run the following command to see a message that confirms that the Management Agent is up and running:

      $<AGENT_INSTANCE_HOME>/bin/emctl status agent

   2. Navigate to the Management Agent home and run the following command to see a message that confirms that EMD upload completed successfully:

      $<AGENT_INSTANCE_HOME>/bin/emctl upload agent

   3. From the Setup menu, select Manage the Manager, then select Agents. Verify that the Management Agent you installed is up and running.
3. Verify whether all the plug-ins listed in $<AGENT_HOME>/sysman/install/plugins.txt were installed successfully. To do so, run the following command:

   $<AGENT_INSTANCE_HOME>/bin/emctl listplugins agent -type all

4. If you have restrictive Privilege Delegation Provider (PDP) configuration settings, enter the location of nmosudo in your PDP configuration file.

   Enterprise Manager supports PDPs such as SUDO and PowerBroker that enable administrators to restrict certain users from running certain commands.

   In Enterprise Manager 24ai, nmosudo is located in the sbin directory that is in the agent home. For example, <AGENT_HOME>/sbin/nmosudo.

   Therefore, when you install a 24ai Management Agent, you must modify your PDP configuration file to update the new location of nmosudo.

   For example, if you use SUDO as your PDP, the configuration file for SUDO is typically /etc/sudoers. In this file, update the following entry with the new location to nmosudo.

   sudouser ALL : oracle /eminstall/basedir/sbin/nmosudo *

5. (Only for UNIX Operating Systems) If you had ignored the prerequisite check warning about not having root privileges, SUDO/PBRUN binaries, or SUDO/PBRUN privileges, then manually run the following scripts as a root user from each of the hosts where the installation was done. If you do not have SUDO/PBRUN privileges, then request your Administrator who has the privileges to run these scripts.

   • If this is the first Oracle product you just installed on the host, then run the orainstRoot.sh script from the inventory location specified in the oraInst.loc file that is available in the Management Agent home.

     For example, if the inventory location specified in the oraInst.loc file is $HOME/oraInventory, then run the following command:

     $HOME/oraInventory/orainstRoot.sh

   • Run the root.sh script from the Management Agent home:

     $<AGENT_HOME>/root.sh

6. If you had ignored a prerequisite check warning about wrong time zone settings, run the following command and follow the steps it displays:

   $<AGENT_INSTANCE_HOME>/bin/emctl resetTZ agent

7. By default, the host and the Management Agent get automatically added to the Enterprise Manager console for monitoring. None of the targets running on that host get automatically discovered and monitored.

   To monitor the other targets, you need to add them to Enterprise Manager either using the Auto Discovery Results page, the Add Targets Manually page, or the discovery wizards offered for the targets you want to monitor.

   For information about discovering targets in Enterprise Manager, refer to Overview of Discovering and Adding Targetsin the Oracle Enterprise Manager Administrator's Guide.

8. If you install a Management Agent on a host that resides in Oracle Cloud Infrastructure (OCI), the steps described above also apply to it.

   • Make sure the agent shows as up on the Enterprise Manager All Targets page.

   • Confirm Privilege Delegation is set for the agent on Enterprise Manager: Open Enterprise Manager Console and navigate to Setup > Security and click on Privilege Delegation.

   Once the Management Agent installation is completed, you can proceed with discovering targets. For information about discovering targets in Enterprise Manager, refer to Overview of Discovering and Adding Targets in the Oracle Enterprise Manager Administrator's Guide.

An Agent Gold Image represents the ideal state of a Management Agent in a data center, having customized configurations of the desired versions of the Management Agent software, the desired versions of the monitoring plug-ins, and the desired patches.

You can create an Agent Gold Image, using either of the following methods:

• Creating an Agent Gold Image Using Gold Agent Images Home Page

• Creating an Agent Gold Image Using EM CLI

1. From the Setup menu, select Manage the Manager, then select Gold Agent Images.
2. Click the name of the required Agent Gold Image.
3. Click Manage Image Versions and Subscriptions.
4. Select the Versions and Drafts tab, then from the Actions menu, select Create.
5. Specify an image version name, and a description for the image version, if required.

   When you create an image version and update a Management Agent with it, Enterprise Manager uses the image version name you provide here to create a subdirectory in the agent base directory for the Management Agent being updated.

   For example, if the agent base directory of the Management Agent being updated is /u01/software/em24/agentbasedir, and the agent home is /u01/software/em24/agentbasedir/agent_24.1.0.0.0, and if you provide OPB_BP1 as the image version name, then when you update the Management Agent with the image version, a new subdirectory /u01/software/em24/agentbasedir/GoldImage_OPB_BP1/agent_24.1.0.0.0 is created. The word limit for the image version name is 20 characters.

6. If you want to create the gold image version using a source Management Agent, for Create image by, select Selecting a source agent, then specify the source Management Agent that you want to use. In this case, you can also specify the following:

   • Work Directory: The working directory that must be used to create the Agent Gold Image. The default working directory is $AGENT_INSTANCE_HOME/install. Ensure that you have minimum 750MB space in this location.

   • Configuration Properties: The Management Agent configuration properties separated by ";" that must be captured while creating the Agent Gold Image. The names of these properties can be found in the $AGENT_INSTANCE_HOME/sysman/config/emd.properties file.

   • Exclude Files: The list of files that you want to exclude from the Agent Base Directory of the source agent while creating the Agent Gold Image. Ensure that you provide the complete file path. If there are two or more files, then separated them by a semicolon (;).

   However, if you want to create the gold image version by importing an existing gold image version, for Create image by, select Importing an image, then specify the location of the gold image version that you want to import. In order to be able to import an image, the image should already be staged. If you have not already staged the image for this purpose, see Managing the Lifecycle of an Agent Gold Image in the Oracle Enterprise Manager Advanced Installation and Configuration Guide.

7. Click OK.

   A job that creates the Agent Gold Image version is submitted to the Enterprise Manager job system. You can view the status of this job on the Gold Agent Image Activities page, in the Image Activities tab.

1. Sign in to EM CLI from the /bin directory present within the Oracle home:

   $<ORACLE_HOME>/bin/emcli login -username=<user_name>

   Once you run this command, EM CLI will prompt you for a password. Enter the password for the user name you specified.

2. Synchronize EM CLI:

   $<ORACLE_HOME>/bin/emcli sync

3. Run the create_gold_agent_image verb to create an Agent Gold Image using the specified source Management Agent or by importing an already created image from another Enterprise Management System:

   <ORACLE_HOME>/bin/emcli create_gold_agent_image
           -image_name="gold_image_name"
           -version_name="gold_image_version_name"
           -source_agent|-import_location="source_agent|import_location"
           [-gold_image_description="gold_image_description"]
           [-working_directory="working_directory_location"]
           [-config_properties= "agent_configuration_properties"]
           [-exclude_files= "list_of_files_directories_to_exclude"]

   Note that the parameters mentioned in [ ] are optional.

   Table 6-3 lists and describes the parameters supported for creating an Agent Gold Image version using EM CLI.

   Table 6-3 Supported Parameters for Creating an Agent Gold Image Version

   Parameter	Description
   -image_name	Agent Gold Image name to which the created Agent Gold Image must be added.
   -version_name	Version name of the Agent Gold Image. When you create an image version and update a Management Agent with it, Enterprise Manager uses the image version name you provide here to create a subdirectory in the agent base directory for the Management Agent being updated. For example, if the agent base directory of the Management Agent being updated is /u01/software/em24/agentbasedir, and the agent home is /u01/software/em24/agentbasedir/agent_24.1.0.0.0, and if you provide OPB_BP1 as the image version name, then when you update the Management Agent with the image version, a new subdirectory /u01/software/em24/agentbasedir/GoldImage_OPB_BP1/agent_24.1.0.0.0 is created. The word limit for the image version name is 20 characters.
   -source_agent	Management Agent to be used as the source to create the Agent Gold Image. To view a list of the Management Agents that can be used as a source to create a gold image, run emcli get_targets -target="oracle_emd".
   -import_location	Location where the Agent Gold Image is staged for creating the gold agent image version. This location is accessible from all the OMS instances.
   -gold_image_description	Description of the Agent Gold Image.
   -working_directory	Working directory to be used to create the Agent Gold Image. The default working directory is $AGENT_INSTANCE_HOME/install. Minimum free space required is 1 GB.
   -config_properties	Management Agent configuration properties separated by \";\" that must be captured while creating the Agent Gold Image. For example, MaxThread;GracefulShutdown.
   -exclude_files	List of files or directories separated by \";\" that must be excluded from the gold agent image version. For example, agent_24.1.0.0.0/cfgtoollogs/agentDeploy;agent_24.1.0.0.0/oui. Ensure that you provide only the relative path to the files and directories and not the absolute path.

   Examples:

   • The following example creates an Agent Gold Image OPC_AGI_DB_JUL_13, using example.com:3872 as the source Management Agent, and adds the gold image version to the gold image OPC_DB_MONITORING:

     <ORACLE_HOME>/bin/emcli create_gold_agent_image -source_agent=example.com:3872 -version_name=OPC_AGI_DB_JUL_13 -image_name=OPC_DB_MONITORING

   • The following example creates an Agent Gold Image OPC_AGI_DB_JUL_13, using example.com:3872 as the source Management Agent, /tmp as the working directory, and adds the gold image version to the gold image OPC_DB_MONITORING:

     <ORACLE_HOME>/bin/emcli create_gold_agent_image -source_agent=example.com:3872 -version_name=OPC_AGI_DB_JUL_13 -image_name=OPC_DB_MONITORING -working_directory=/tmp

   • The following example creates an Agent Gold Image OPC_AGI_DB_JUL_13 using gold image software staged at import location /abc/stage:

     <ORACLE_HOME>/bin/emcli create_gold_agent_image -import_location=/abc/stage -version_name=OPC_AGI_DB_JUL_13 -image_name=OPC_DB_MONITORING

1. From the Setup menu, select Manage the Manager, then select Gold Agent Images.
2. Click the name of the required Agent Gold Image.
3. Click Manage Image Versions and Subscriptions.
4. Select the Versions and Drafts tab. Select the gold image version that you want to set as the current version, then click Set Current Version.

   A job that promotes the Agent Gold Image draft version to the current version is submitted to the Enterprise Manager job system. You can view the status of this job on the Gold Agent Image Activities page, in the Image Activities tab.

1. Sign in to EM CLI from the /bin directory present within the Oracle home:

   $<ORACLE_HOME>/bin/emcli login -username=<user_name>
   

   Once you run this command, EM CLI will prompt you for a password. Enter the password for the user name you specified.

2. Synchronize EM CLI:

   $<ORACLE_HOME>/bin/emcli sync
   

3. Run the promote_gold_agent_image verb to promote the Agent Gold Image version to the Current maturity level:

   <ORACLE_HOME>/bin/emcli promote_gold_agent_image -version_name="gold_image_version_name" -maturity="Current/Restricted/Draft"

   The -version_name parameter defines the Agent Gold Image version name that you want to promote.

   The -maturity parameter defines the gold image maturity level.

   For example, to promote the Agent Gold Image OPC_AGI_DB_JUL_13 to the Current maturity level, run the following:

   <ORACLE_HOME>/bin/emcli promote_gold_agent_image -version_name=OPC_AGI_DB_JUL_13 -maturity=Current

1. Sign in to EM CLI from the /bin directory present within the Oracle home:

   $<ORACLE_HOME>/bin/emcli login -username=<user_name>

   Once you run this command, EM CLI will prompt you for a password. Enter the password for the user name you specified.

2. Synchronize EM CLI:

   $<ORACLE_HOME>/bin/emcli sync

3. Run the get_targets verb to obtain the list of unmanaged hosts:

   emcli get_targets -unmanaged -targets="%:host" -format=name:script

   Make a note of the unmanaged hosts on which you want to install a Management Agent.

   To view more information on the syntax and the usage of the get_targets verb, run the following command:

   $<ORACLE_HOME>/bin/emcli help get_targets

4. Run the list_add_host_platforms verb to obtain a list of the platforms for which the Management Agent software is available in Software Library:

   $<ORACLE_HOME>/bin/emcli list_add_host_platforms 
                         [-all] 
                         [-noheader] 
                         [-script | -format]
   

   Note that the parameters mentioned in [ ] are optional.

   For example, $<ORACLE_HOME>/bin/emcli list_add_host_platforms -all

   Figure 6-2 displays the output of this command.

   Figure 6-4 Output of list_add_host_platforms -all

   
   

   

   
   

   If the Management Agent software for a platform on which you want to install a Management Agent is not available, download and apply it using Self Update. For information on how to download and apply the Management Agent software for a platform, see Meeting the Management Agent Software Prerequisites for Installing Standalone Management Agents Using Add Host Targets Wizard or EM CLI.

   To view more information on the syntax and the usage of the list_add_host_platforms verb, run the following command:

   $<ORACLE_HOME>/bin/emcli help list_add_host_platforms

5. If you want to deploy Management Agents on the selected hosts in a rolling manner, such that the deployment proceeds continuously from one deployment phase to another, ignoring the failed hosts in each deployment phase, specify the following in the <ORACLE_HOME>/sysman/prov/agentpush/agentpush.properties file:

   oracle.sysman.prov.agentpush.continueIgnoringFailedHost=true

   For more information about this deployment method, see Before You Begin Installing Standalone Management Agents Using Add Host Targets Wizard or EM CLI.

6. Run the submit_add_host verb to submit the Add Host session and install Management Agents:

   $<ORACLE_HOME>/bin/emcli submit_add_host
           -host_names="List of host names."
           -platform="Platform id"
           -installation_base_directory="Installation base directory."
           -credential_name="Credential Name"
           [-credential_owner="Credential Owner"]
           [-instance_directory="Instance directory"]
           [-port="Agent port"]
           [-version_name="Gold Image Version Name"]
           [-image_name="Gold Image Name"]
           [-session_name="Deployment session name"]
           [-deployment_type="Type of agent deployment"]
           [-privilege_delegation_setting="Privilege delegation setting"]
           [-additional_parameters="parameter1 parameter2 ..."]
           [-source_agent="Source agent"]
           [-master_agent="Master agent"]
           [-input_file=properties_file:"Properties file"]
           [-predeploy_script="Predeploy script"]
           [-predeploy_script_on_oms]
           [-predeploy_script_run_as_root]
           [-preinstallation_script="Preinstallation script"]
           [-preinstallation_script_on_oms]
           [-preinstallation_script_run_as_root]
           [-postinstallation_script="Postinstallation script"]
           [-postinstallation_script_on_oms]
           [-postinstallation_script_run_as_root]
           [-configure_hybrid_cloud_agent]
           [-hybrid_cloud_gateway_agent="Hybrid Cloud Gateway Agent"]
           [-hybrid_cloud_gateway_proxy_port="Hybrid Cloud Gateway Proxy Port"]
           [-wait_for_completion]        

   Note that the parameters mentioned in [ ] are optional.

   Table 6-4 lists and describes the parameters supported for submitting an Add Host session which installs Management Agents on unmanaged hosts, thereby converting them to managed hosts.

   Table 6-4 Supported Parameters for Submitting an Add Host Session

   Parameter	Description
   -host_names	The names of the hosts where the agents need to be installed, separated by a semi colon.
   -platform	The ARU platform ID of the hosts where the agent need to be installed.
   -installation_base_directory	The directory where the Management Agent will be installed. Provide this parameter in double quotes if it is a MS-DOS/Windows style path.
   -credential_name	The named credential to be used for installing the Management Agent.
   -credential_owner	The owner of the named credential.
   -instance_directory	The instance directory of the Management Agent. Provide this parameter in double quotes if it is a MS-DOS/Windows style path.
   -port	The port through which the Management Agent should communicate with the OMS.
   -version_name	The Agent Gold Image name to be used for deployment. Run emcli list_gold_agent_images to view a list of Agent Gold Images.
   -session_name	The session name which uniquely identifies the Add Host session.
   -deployment_type	The type of Management Agent deployment. You can install a Shared Agent and clone a Management Agent by specifying the -deployment_type option with the submit_add_host verb. To install a Shared Agent, specify -deployment_type=SHARED. To clone a Management Agent, specify -deployment_type=CLONE. By default, the -deployment_type option is set to FRESH, so if this option is not specified, a fresh Management Agent is installed on the selected host.
   -privilege_delegation_setting	The privilege delegation setting for installing an Management Agent and running the root script.
   -additional_parameters	Additional parameters for installing a Management Agent.
   -source_agent	The source Management Agent for installing a cloned Management Agent.
   -master_agent	The master Management Agent for installing a shared Management Agent.
   -input_file	The properties file containing the Management Agent installation inputs.
   -preinstallation_script	The script that you want to run before installing the Management Agent. Provide this parameter in double quotes if it is a MS-DOS/Windows style path.
   -preinstallation_script_on_oms	Indicates that the preinstallation script resides on the OMS host.
   -preinstallation_script_run_as_root	Runs the preinstallation script as the root user.
   -postinstallation_script	The script you want to run after installing the Management Agent. Provide this parameter in double quotes if it is a MS-DOS/Windows style path.
   -postinstallation_script_on_oms	Indicates that the postinstallation script resides on the OMS host.
   -postinstallation_script_run_as_root	Runs the postinstallation script as the root user.
   -configure_hybrid_cloud_agent	Enables you to deploy a management agent on a hybrid cloud.
   -hybrid_cloud_gateway_agent	The Management Agent that provides a communication channel between the Oracle Public Cloud virtual hosts and the OMS deployed in your private network.
   -hybrid_cloud_gateway_proxy_port	The port on which the Hybrid Cloud Agent can communicate with the Hybrid Cloud Gateway Proxy.
   -wait_for_completion	Runs the Add Host operation synchronously.

   Examples:

   • To submit an Add Host session on the host example.com, having platform ID 226, with /opt/agent as the installation base directory, using the named credential oracle and privilege delegation setting /usr/bin/sudo -u %RUNAS% %COMMAND%, run the following command:

     $<ORACLE_HOME>/bin/emcli submit_add_host -host_names=example.com -platform=226 -installation_base_directory=/opt/agent -credential_name=oracle -privilege_delegation_setting="/usr/bin/sudo -u %RUNAS% %COMMAND%"

   • To submit an Add Host session on the host example2.com, having platform ID 233, with C:\agent as the installation base directory, using the named credential oracle, run the following command:

     $<ORACLE_HOME>/bin/emcli submit_add_host -host_names=example2.com -platform=233 -installation_base_directory="C:\agent" -credential_name=oracle

   • To submit an Add Host session using the inputs provided in the properties file /opt/inputs.txt, run the following command:

     $<ORACLE_HOME>/bin/emcli submit_add_host -input_file=properties_file:/opt/inputs.txt

   • To submit an Add Host session of type CLONE, on the host example.com, having platform ID 226, with /opt/agent as the installation base directory, example1.com:3872 as the source agent, using the named credential oracle, run the following command:

     $<ORACLE_HOME>/bin/emcli submit_add_host -host_names=example.com -platform=226 -installation_base_directory=/opt/agent -credential_name=oracle -deployment_type=CLONE -source_agent=example1.com:3872

   • To submit an Add Host session of type SHARED, on the host example.com, having platform ID 226, with /opt/agent/agent_inst as the instance directory, example1.com:3872 as the master agent, using the named credential oracle, run the following command:

     $<ORACLE_HOME>/bin/emcli submit_add_host -host_names=example.com -platform=226 -instance_directory=/opt/agent/agent_inst -credential_name=oracle -deployment_type=SHARED -master_agent=example1.com:3872

   To view more information on the syntax and the usage of the submit_add_host verb, run the following command:

   $<ORACLE_HOME>/bin/emcli help submit_add_host

7. Run the get_add_host_status verb to view the status of the created Add Host session:

   $<ORACLE_HOME>/bin/emcli get_add_host_status 
                         -session_name 
                         [-details] 
                         [-show_only_failed_hosts] 
                         [-host_name] 
                         [-noheader] 
                         [-script | -format]
   

   Note that the parameters mentioned in [ ] are optional.

   For example, $<ORACLE_HOME>/bin/emcli get_add_host_status -session_name=ADD_HOST_SYSMAN_operation

   This example displays the status of the ADD_HOST_SYSMAN_operation Add Host session.

   To view the detailed Management Agent deployment status of a particular host, run the get_add_host_status verb with the -host_name parameter. For example:

   $<ORACLE_HOME>/bin/emcli get_add_host_status -session_name=ADD_HOST_SYSMAN_operation -host_name=example.com

   This command also displays the location of the log file for the deployment of a Management Agent on the specified host. If the deployment failed, you can investigate the failure by reviewing the log files. One log file is generated per host.

   Figure 6-3 displays a sample output of the command.

   Figure 6-5 Output of emcli get_add_host_status

   
   

   

   
   

   Alternatively, to know where the Management Agent log files are located, see Overview of the Installation and Configuration Log Files in the Oracle Enterprise Manager Advanced Installation and Configuration Guide.

   Run the list_add_host_sessions verb to view the details or track the progress of all the Add Host sessions:

   $<ORACLE_HOME>/bin/emcli list_add_host_sessions 
                         [-host_name]
                         [-session_name]
                         [-match_all]
                         [-noheader] 
                         [-script | -format]
   

   For example, $<ORACLE_HOME>/bin/emcli list_add_host_sessions -host_name=example.com

   This example displays all the Add Host sessions that the host example.com was a part of.

   To view more information on the syntax and the usage of the get_add_host_status and the list_add_host_sessions verb, run the following commands:

   $<ORACLE_HOME>/bin/emcli help get_add_host_status
   $<ORACLE_HOME>/bin/emcli help list_add_host_sessions
   

8. If the output of the get_add_host_status EM CLI verb mentions that a particular installation phase has failed or has a warning, do one of the following:

   • Fix the problem by reviewing the error description carefully, understanding its cause, and taking action as recommended by Oracle.

     • You can retry the deployment of Management Agents with the same installation details.

       To do so using EM CLI, use the retry_add_host verb, with the -retry_using_same_inputs option:

       $<ORACLE_HOME>/bin/emcli retry_add_host 
                             -session_name 
                             -retry_using_same_inputs 
                             [-wait_for_completion]
       

       Note that the parameters mentioned in [ ] are optional.

       For example, $<ORACLE_HOME>/bin/emcli retry_add_host -session_name='ADD_HOST_SYSMAN_operation2' -retry_using_same_inputs

     • You can retry the deployment of Management Agents with modified installation details.

       To do so using EM CLI, use the retry_add_host verb, with the -update_inputs_and_retry option:

       $<ORACLE_HOME>/bin/emcli retry_add_host 
               -session_name="session_name"
               -retry_using_same_inputs | -update_inputs_and_retry"
               [-host_names="Host names"]
               [-platform="Platform id"]
               [-installation_base_directory="Installation base directory"]
               [-credential_name="Credential Name"]
               [-credential_owner="Credential Owner"]
               [-instance_directory="Instance directory"]
               [-port="Agent port"]
               [-deployment_type="Type of agent deployment"]
               [-privilege_delegation_setting="Privilege delegation setting"]
               [-additional_parameters="parameter1 parameter2 ..."]
               [-source_agent="Source agent"]
               [-master_agent="Master agent"]
               [-preinstallation_script="Preinstallation script"]
               [-preinstallation_script_on_oms]
               [-preinstallation_script_run_as_root]
               [-postinstallation_script="Postinstallation script"]
               [-postinstallation_script_on_oms]
               [-postinstallation_script_run_as_root]
               [-configure_hybrid_cloud_agent]
               [-hybrid_cloud_gateway_agent="Hybrid Cloud Gateway Agent"]
               [-hybrid_cloud_gateway_proxy_port="Hybrid Cloud Gateway Proxy Port"]
               [-wait_for_completion]

       Note that the parameters mentioned in [ ] are optional.

       For example, $<ORACLE_HOME>/bin/emcli retry_add_host -session_name='ADD_HOST_SYSMAN_operation2' -update_inputs_and_retry -credential_name=oracle2

       This example retries the deployment of Management Agents for the ADD_HOST_SYSMAN_operation2 Add Host session, using the oracle2 named credential.

     To view more information on the syntax and the usage of the retry_add_host verb, run the following command:

     $<ORACLE_HOME>/bin/emcli help retry_add_host

   • Ignore the warning or failure, and continue with the session if you prefer.

     • You can choose to proceed with the deployment of Management Agents only on those remote hosts that have successfully cleared the checks, and you can ignore the ones that have Warning or Failed status.

       To do so using EM CLI, use the continue_add_host verb, with the -continue_ignoring_failed_hosts option:

       $<ORACLE_HOME>/bin/emcli continue_add_host 
                             -session_name
                             -continue_ignoring_failed_hosts
                             [-wait_for_completion]
       

       Note that the parameters mentioned in [ ] are optional.

       For example, $<ORACLE_HOME>/bin/emcli continue_add_host -session_name='ADD_HOST_SYSMAN_operation2' -continue_ignoring_failed_hosts

     • You can choose to proceed with the deployment of Management Agents on all the hosts, including the ones that have Warning or Failed status.

       Note that choosing this option will ignore the prerequisites in order to allow the Management Agent installation to proceed. If you want to proceed with this option, you must ensure that all the prerequisites are met through manual methods. The practice of ignoring prerequisite checks must be done only with the help of Oracle Support, or with a clear understanding of the impact of bypassing these checks.

       To do so using EM CLI, use the continue_add_host verb, with the -continue_all_hosts option:

       $<ORACLE_HOME>/bin/emcli continue_add_host 
                             -session_name
                             -continue_all_hosts
                             [-wait_for_completion]
       

       Note that the parameters mentioned in [ ] are optional.

       For example, $<ORACLE_HOME>/bin/emcli continue_add_host -session_name='ADD_HOST_SYSMAN_operation2' -continue_all_hosts

     To view more information on the syntax and the usage of the continue_add_host verb, run the following command:

     $<ORACLE_HOME>/bin/emcli help continue_add_host