Upgrading Applications Manager

When you upgrade an Automation Engine and its Local Agent, you must also upgrade all Remote Agents controlled by that Automation Engine to ensure that the Automation Engine and all its Agents are the same version.
To upgrade a UNIX or Windows Automation Engine, you run the
Applications Manager
installation script. The script upgrades the Automation Engine and its Local Agent to a new version of
Applications Manager
. If you are upgrading a host with multiple Agents, the
Applications Manager
communication processes (
aw*
) will not be replaced unless they are assigned write access.
To upgrade a Remote Agent, you run the Remote Agent install script
awagentinstall
. The script upgrades your Remote Agent to a new version of
Applications Manager
.
Rule-Based Optimization
Applications Manager
is designed to take advantage of rule-based optimization. It is recommended the database be started using rule-based optimization to enhance the performance of
Applications Manager
. In high load scenarios, the database must run in rule-based mode.
Changes in Behavior
Changes in behavior are described in the .
Default Objects Overwritten
If you have modified any of the
Applications Manager
default objects or scripts, they will be overwritten during the upgrade. For example, you may have modified a Program Type, or modified a Program Type script in the
exec
directory.
If you modified a default object, you will need to redefine it after the upgrade. Long term, you should consider creating unique Program Types that will not be overwritten.
If you modified a script, you can copy the script to a different directory, run the upgrade, then copy the script back to the original directory. As with the default objects, you should consider creating uniquely named scripts that will not be overwritten.