The request.cfg file is used for automatic installation of probe packages and monitoring configuration but there are no detailed instructions on what is required in this file.
CA UIM 8.2 or higher
distsrv, robot, and automated_deployment_engine package versions which are included in the CA UIM Server 8.2 and higher distribution.
To use request.cfg you create a simple text file called 'request.cfg' and place it in the Nimsoft directory of the robot to force the robot to pull specifically referenced probes or superpackages down when the Robot starts up. The general format is shown below.
packages = baseOS-silver, base-apache, custom-0815
Be sure that the hub managing the robot has access to a local distsrv probe.
request.cfg also supports auto-(re)initialization by adding the key following key and value to the file:
expect_ip_change = yes
When the robot starts up, it will look for a file called 'request.cfg' in the Nimsoft directory. The package requests are submitted to the distsrv probe, or ADE (Automatic Deployment Engine) probe if you are running 8.3 or higher, which then performs the installation.
Here is an example of the contents of a request.cfg file:
packages = cdm, processes, ntevl
To perform a complete installation of a Robot and a set of packages, you should prepare a request.cfg file and copy it to the intended Nimsoft installation directory (normally C:\Program Files (x86)\Nimsoft) then install the Nimsoft Robot.
Please also note that a script can start and stop a robot but a script cannot push the request.cfg as this is a built-in function of the robot. If the request.cfg is in the correct location (and has no mistakes in the file contents) - when the robot starts and the robot is in good working condition, it will recognize the existence of the request.cfg file and process it.