AutoSys instance addition on patched RHEL 8x, 9.x, 10.x environments

Products

• Autosys Workload Automation

Issue/Introduction

 This article confirms the behavior of the AutoSys installer when adding a new instance to a machine that already runs a higher version or patch level than the installation media.

Problem: 
When adding a new client instance using the "Add Instance" function from base installation media (e.g., an R12.1.00 ISO), there is a concern that the installer may abort or overwrite existing binaries if the machine has already been patched to a higher level (e.g., R12.1 Cum2).

Environment

• Product: AutoSys Workload Automation 12.x, 24.x
• Operating System: Red Hat Enterprise Linux (RHEL) 8.x, 9.x, 10.x

Cause

The AutoSys installer "Add Instance" function is safe to use on environments already patched beyond the level of the media.

1. The "Add Instance" function only creates the configuration environment (e.g., /etc/auto.profile, environment variables, and instance-specific config files).
2. The process connects the new instance to the program files already present on the machine.
3. Existing program files (binaries/libraries) at the higher patch level are not altered or downgraded by the installer.
4. The new instance operates immediately at the current version/patch level of the host.

Note: 
Manually copying an existing instance's files and using "find and replace" is not a supported method.
This leaves the installation records inconsistent and causes failures during future upgrades or patching.
Use the standard installer "Add Instance" procedure.

Resolution

Maintain AutoSys: Add an Instance