Installing Single Robot using RPM and Answer file on Linux environment
Article ID: 9924
Updated On:
Products
Issue/Introduction
Third-party distribution mechanisms (yum, rpm, etc) can be used as long as it can:
-
Copy a native robot installer to a remote system. 32-bit and 64-bit installers for Windows, Linux, Ubuntu, SUSE, Debian, Solaris, and AIX are available on your primary hub.
-
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.
Environment
- Any Linux platform supported by UIM robot (RHEL, CentOS, Debian, and Ubuntu).
Cause
- installation options
Resolution
1. Copy the appropriate Linux installer to /opt on the target system, e.g., nimsoft-robot-*
for example, nimsoft-robot.x86_64.rpm
2. Create an answer file without spaces between the key-value pairs.
domain=<domain name>
hub=<Hub Name>
hubip=<Hub IP>
robotip=<Robot IP> (optional)
hubrobotname=<Hub robot Name>
hubport=48002
3. Run the rpm using the following command
a. On Red Hat, SUSE, or CentOS, execute the following command, where <arch> is i386 or amd64:
rpm -ivh nimsoft-robot.<arch>.rpm
b. 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.
a. Go to /opt/nimsoft/install directory.
cd /opt/nimsoft/install
b. Edit the RobotConfigurer.sh file for the installation.
#build up the temp file
$SED "s/~${key}$/${val}/" $PREFIX/nimsoft/robot/robot.cfg > $PREFIX/nimsoft/robot/robot.cfg.temp
$SED -i "s/~${key}$/${val}/" $PREFIX/nimsoft/robot/robot.cfg
#move the changes
mv ${PREFIX}/nimsoft/robot/robot.cfg.temp ${PREFIX}/nimsoft/robot/robot.cfg
c. Run the script using ./RobotConfigurer.sh.
5. Verify the robot.cfg under /opt/nimsoft/robot directory as to whether the values mentioned in your answer file updated in the robot.cfg or not. If they were not updated, then there is some problem in updating the cfg file. So you can open a case with the Support team.
6. 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:
initctl start nimbus
Feedback
