How can we configure the default robot install folder to be unique independent of how it is installed?

Products

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

Issue/Introduction

Is it possible to specify the installation path for the OC Inventory-> Robot Deployment?

Environment

• DX UIM 23.4 CU7

Cause

• Not supported

Resolution

In the Unified Infrastructure Management (UIM) Operator Console (OC), the automatic robot deployment feature does not allow you to specify a custom path; it always targets the default installation location (typically the C: drive on Windows)

There are a few other options available which allow you to specify the path for installing the robot.

1. Bulk robot deployment using the installdir <path> parameter

Bulk robot deployment with an XML file

Bulk/Third-party: Include this parameter in your nms-robot-vars.cfg or deployment command for consistent application. 

2. Deploying robots en masse

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

3. Command Line (use of command-line arguments to specify the path during installation.)

Windows Installation
For a customized install path on Windows, use the /DIR parameter with the executable: 

Command: nimsoft-robot-x64.exe /DIR="C:\custom\path\Nimsoft" /VERYSILENT /SUPPRESSMSGBOXES /NORESTART

Note: Quotation marks are required if the path contains any spaces.

Linux/Unix Installation
On Linux systems, use the --prefix argument during installation to define a unique path: 

Command: ./nimsoft-robot-x64.rpm --prefix=/opt/<custom_nimsoft>

Alternatively: When using the nimldr utility, it will prompt for the installation directory, allowing you to define a custom install path.

Additional Information

Key Considerations

---

Default Behavior: Without arguments, 64-bit Windows defaults to C:\Program Files\Nimsoft, and Linux defaults to /opt/nimsoft.

Active/Passive Clustering
For clustered environments, ensure the custom path is on a shared drive and that the installation is performed on both nodes.

Multiple Robots
To run multiple robots on one host in unique folders, you must create distinct robot.cfg files, unique robot names, and separate NimbusWatcherService instances for each. 

Standardizing Across Installations
To ensure consistency across various methods (manual, ADE), it is best to place the required installer (nimsoft-robot.exe) and a configuration file with the pre-defined /DIR in a central location, or use automation scripts to call the installer with the parameters