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

uim851
Install_robot_third_party_tool
CA UIM
does not support the use of native installers to perform robot upgrades. To upgrade your robots, you must use the
robot_update
package that is available in either the Admin Console or Infrastructure Manager Archive.
For first-time robot installations, the native robot installers are still supported.
If you already have a software deployment tool (such as
Yum
or
Altiris
), you can use it to deploy robots. Almost any third-party distribution mechanism can be used as long as it can:
  1. Copy a native robot installer to a remote system. 32-bit and 64-bit installers for Windows, Linux, Ubuntu, Debian, Solaris, and AIX are available on your primary hub. See the Support Compatibility Matrix for details on supported versions. 
  2. Copy an answer file that you have prepared. The native robot installers execute silently using the robot configuration values in the answer file. This file must follow the correct syntax and format.  
  3. Execute the steps for the appropriate installer.
You can install a single robot with an answer file.
  1. Copy the answer file and the appropriate installer to the target system.
  2. Manually execute the installation steps on the target system.
Preparing an Answer File
Your answer file must be a text file in the following syntax and format. Supply actual values for each parameter. Do not include spaces between the parameter and value. For example,
domain=
Mydomain
.
Name the answer file
nms-robot-vars.cfg
.
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
(optional fields)
Note the following information:
  • The 
    domain
    hub
    hubip
    hubrobotname
    , and
     hubport
    are required.
  • Optional parameters with no answer are valid. However, it is better to omit a parameter from the answer file than to include it with an empty value.
  • The default port for a hub is 48002.
  • We recommend preparing a simple answer file with only required fields during initial robot deployment. You can add optional fields later. Make bulk changes to the robot configuration using drag-and-drop in Infrastructure Manager.
  • Any robot attribute can be configured in the answer file with the format
    parameter=
    value
    . For a complete list of robot parameters, see Bulk Robot Deployment with an XML File.
Parameter
Definition
Example
domain
UIM domain
HOST_ABC_DOM
hub
Name of the parent hub of the robot
HOST_ABC_HUB
hubip
Hostname or IP address of the robot parent hub. This field is not required
10.0.0.10
hubrobotname
Name of the parent hub robot
HOST_ABC_ROBOT
hubport
Hub listening port
48002
robotip
(optional)
IP address of the target system
10.0.0.11
robotname
(optional)
Desired name for the robot. Default,
hostname
HOST_MNO
first_probe_port
(optional)
Port that is used by the first probe
48000
origin
(optional)
Desired origin value
HUBNAME
Deploying to Windows 
Your third-party deployment tool must perform the following actions.
  1. Copy the appropriate Windows installer to any folder on the target system:
    • nimsoft-robot-x64.exe
      (64-bit)
    • nimsoft-robot.exe
      (32-bit)
  2. Copy the
    nms-robot-vars.cfg
    answer file to the same folder.
  3. Install the robot by executing:
     <EXE_package>.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART
    The default install folder is
    C:\Program Files (x86)\Nimsoft
    for 32-bit systems, and
    C:\Program Files\Nimsoft
    for 64-bit systems. To specify the folder, append the following parameter to the command. Quotation marks are required.
     /DIR="c:\path\to\install"
    To specify the log file, append:
    /LOG="name_of_install_log.txt"
After installation, the robot starts automatically.
Deploying to Linux
Use your third-party deployment tool to perform the following actions.
Note:
If you are not using root access, use either
sudo
<command>
or
su -c "
<command>
"
. You can also use
su
to get a root shell and execute the command.
  1. Copy the appropriate Linux installer to
    /opt
    on the target system:
    • nimsoft-robot-x64.rpm 
      64-bit SUSE, SLES, or RHEL
    • nimsoft-robot.rpm 
      32-bit SUSE, SLES, or RHEL
    • nimsoft-robot+debian_amd64.deb 
      64-bit Debian
    • nimsoft-robot+debian_i386.deb 
      32-bit Debian
    • nimsoft-robot+ubuntu_amd64.deb 
      64-bit Ubuntu (supports Ubuntu 14 and 16)
    • nimsoft-robot+ubuntu_i386.deb 
      32-bit Ubuntu
  2. Copy the
    nms-robot-vars.cfg
    answer file to
    /opt
    .
  3. Install the robot.
    • On Red Hat, SUSE, or CentOS, execute the following command, where 
      <arch>
       is
      i386
      or
      amd64
      :
      rpm -ivh nimsoft-robot.
      <arch>
      .rpm
      The default install directory is
      /opt/nimsoft
      . To specify the installation directory, execute the following command, where
      <directory>
      is the full path:
       rpm -ivh nimsoft-robot.<arch>.rpm --prefix=<
      directory>
      The rpm flags function as follows:
           -i    
      install the software package
           -v
         display a simple status line to show what is being installed (
      verbose
       mode)
           -h
        display fifty hash marks (#) to show the status as the install proceeds; when all fifty have displayed, installation is complete
    • On Debian or Ubuntu, execute the following command using
      sudo
      ,
      su -c
      , or as the root user. Specify
      <OS>
      as
      debian
      or
      ubuntu,
      and specify
      <arch>
      as
      i386
      or
      amd64
      .
      dpkg -i nimsoft-robot+
      <OS>
      _
      <arch>
      .deb
  4. Execute the
    RobotConfigurer.sh
    script to configure the robot when the installer exits.
    cd /opt/nimsoft/install bash RobotConfigurer.sh
  5. Perform these steps only if your controller version is 7.91 or earlier:
    1. This step is not required for Ubuntu 14. For Ubuntu 16, execute
      /opt/nimsoft/install/service-ctrl.sh enable
      to enable the robot service.
    2. The installation is complete. To start the robot, use one of the following commands:
      • For Red Hat, SUSE, CentOS, or Debian:
        /etc/init.d/nimbus start
      • For Ubuntu:
        /opt/nimsoft/bin/niminit start
  6. Perform this step only if your controller version is 7.93 or later.
    The installation is complete. To start the robot, use the following command for all platforms:
    /opt/nimsoft/bin/niminit start
Deploying to HP-UX
Use your third-party deployment tool to perform the following actions.
  1. Copy the appropriate installer to the
    /opt
    directory on the target system.
    • For HP-UX on PA RISC
      : nimsoft-robot-hppa
      -
      11.31.depot.gz
    • For HP-UX on Itanium:
      nimsoft-robot-ia64-11.31.depot.gz    
  1. Copy the
    nms-robot-vars.cfg
    answer file to
    /opt
    .
  2. Extract the
    .gz
    file. Execute the following command, where 
    <arch>
     is 
    hppa
     or 
    ia64
    :
    /usr/contrib/bin/gunzip /
    opt
    /nimsoft-robot-
    <arch>-
    11.31.depot.gz
  3. Execute the following command to install the robot.
    /usr/sbin/swinstall –s /
    opt
    /nimsoft-robot-
    <arch>
    -11.31.depot \*
  4. Execute the
    RobotConfigurer.sh
    script to configure the robot when the installer exits.
    cd /opt/nimsoft/install /bin/sh RobotConfigurer.sh
  5. The installation is complete. To start the robot, use the following command.
    /opt/nimsoft/bin/niminit start
To stop the robot or view the status, 
ssh
to the system, and execute the
niminit
command.
/opt/nimsoft/bin/niminit stop /opt/nimsoft/bin/niminit status
Deploying to Solaris
Note:
Beginning with robot version 7.95, if you create a new Solaris zone, a robot installed in the global zone is not automatically deployed to the new zone. To install a robot in a new, non-global zone, install the robot into the non-global zone using the same steps that you use to install the robot in the global zone.
Use your third-party deployment tool to perform the following actions.
Note:
If you are not using root access, use either
sudo
<command>
or
su -c "
<command>
"
. You can also use
su
to get a root shell and execute the command.
  1. Copy the appropriate Solaris installer to the
    /opt
    directory on the target system.
    • For Solaris 32-bit:
      nimsoft-robot-i386.gz
    • For Solaris 64-bit:
      nimsoft-robot-amd64.gz
    • For Solaris SPARC:
      nimsoft-robot-sparcv9.gz
  2. Copy the
    nms-robot-vars.cfg
    answer file to
    /opt
    .
  3. Execute the following commands to extract and install the robot. Replace
    <arch>
    with
    i386
    ,
    amd64
    , or
    sparcv9
    .
    gunzip -c nimsoft-robot-
    <arch>
    .gz 
    pkgadd -d /opt/nimsoft-robot-
    <arch>
  4. When the installer completes, execute the
    RobotConfigurer.sh
    script to configure the robot.
    cd /opt/nimsoft/install bash RobotConfigurer.sh
Installation is complete. To view status of the robot, ssh to the server, and execute:
ps -ef | grep nimbus
Deploying to AIX
The AIX robot is supported on 64-bit systems only. To determine whether the target kernel is 32-bit or 64-bit, execute:
getconf KERNEL_BITMODE
Use your third-party deployment tool to perform the following actions.
  1. Copy the AIX installer to the target system:
    nimsoft-robot.aix6.1.ppc64.rpm
  2. Copy the
    nms-robot-vars.cfg
    answer file to
    /opt
    .
  3. Execute the following command as the root user to install the robot to the default directory,
    /opt/nimsoft
    :
    rpm -ivh nimsoft-robot.aix6.1.ppc64.rpm
    To install the robot to a specific directory, execute the following command as root, where 
    <directory>
     is the full path:
    rpm -ivh nimsoft-robot.aix6.1.ppc64.rpm --prefix=
    <directory>
    The rpm flags function as follows:
         -i  
     install the software package
         -v   
    display a simple status line to show what is being installed (
    verbose
     mode)
         -h 
    display fifty hash marks (#) to show the status as the install proceeds; when all fifty have displayed, installation is complete
  4. To run the robot as a nonroot user account, take the following steps:
    Add the nonroot user to
    /etc/nimbus.conf
    :
    echo "NIMBUS_USR=<
    NonRootUser
    >" >> /etc/nimbus.conf
    Change the ownership of the /etc/nimbus.conf file, and the UIM installation to the nonroot user:
    chown <
    NonRootUser
    > /etc/nimbus.conf
    chown -R <
    NonRootUser
    > /
    UIMHOME
  5. Run the
    RobotConfigurer.sh
    script as root to configure the robot:
    cd /opt/nimsoft/install sh RobotConfigurer.sh
  6. Enable the Nimbus service as root:
    /opt/nimsoft/install/service-ctrl.sh enable
  7. Start the robot as root. If the robot is configured to run as a nonroot account, the processes are running as the nonroot user.
    /usr/bin/startsrc -s nimbus
Installation is complete. To stop the robot or view the status, execute:
/usr/bin/stopsrc –s nimbus
/usr/bin/lssrc –s nimbus