How do I use request.cfg file when doing automatic installation of probe packages?
CA UIM 8.2 or higher
distsrv, robot, and ADE package versions which are included in the CA UIM Server 8.2 distribution.
request.cfg file is used for automatic installation of probe packages and monitoring configuration.
To use request.cfg you create a simple text file called ?request.cfg? and place it in the Nimsoft directory 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 it has access to a local distsrv probe)
request.cfg also supports auto-(re)initialization by adding the key ?? 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) and install the Nimsoft Robot afterwards.
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 mistake in the file) - 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.
Is it possible to specify the path to distsrv in request.cfg ?
Yes, for controller (robot) version 5.00 or higher please use:
distsrv = /domain/hub/robot/distsrv
Can I use request.cfg to deploy a super package to apply changes to multiple probes?
Yes, the request.cfg can also deploy a super package during its operations as well - just specify its name in the request.cfg.
As of CA UIM 8.20 or higher:
The following comments pertain to support for request.cfg deployment with robot v7.70 and higher...
Upon startup, the robot/controller looks for request.cfg, a user-created text file that enables automatic deployment of the probes specified in that file to the robot. Previously, these requests could only be facilitated by distsrv, which still handles them by default.
To have a v7.70 robot direct the requests to ADE, use the Raw Configure utility to add the deploy_addr parameter to the robot.cfg, and specify the UIM Nimsoft address of the ADE probe:
See also CA UIM 8.2 Release Notes for more information:
Here is another link that you may find useful regarding use of ADE which can still be used in CA UIM version 8.2.
Other related information on request.cfg and ADE usage can be searched and found in the CA Community/Experts Forum at this link:
keywords: request cfg request.cfg file silent install installation ADE distsrv how auto automatic