nms-robot-vars.cfg - silent install best practices

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

I am having inconsistent results when trying to apply robot settings with the nms-robot-vars.cfg after a native rpm installation of a robot.

What are the best practices for the file and its use?

Environment

• Any robot version

Cause

• Guidance

Resolution

The following will apply:

• The nms-robot-vars.cfg will have to have a carriage return after the last data line

• The ./RobotConfigurer.sh can only be run one time after the rpm installation
  Running successive times will not perform updates

• The parameter-> origin=
  is placed in the spooler.cfg file not in the robot.cfg file

• Do NOT include any spaces between the parameter and the value in the file. For example, domain=Mydomain

• <!-- EMPTY_LINE --> <!-- Leave an empty line at the end of the file -->

Example answer file with required fields:

domain=<UIM_domain_to_which_the_robot_will_belong>
hub=<name_of_parent_hub>
hubip=<parent_hub_IP_address>
hubrobotname=<parent_hub_local_robot>
hubport=<parent_hub_port_number>

Different example using other parameters:

Additional Information

Deploy Robots in Bulk with a Third-Party Tool and Native Installers

Bulk Deployment with an XML File

RobotConfigurer.sh script is not changing robot.cfg after changing the answer file