The CA AutoSys Workload Automation PeopleSoft Adapter version 2.1.0 installs into the AutoSys directory structure (executable files in $AUTOSYS/bin, configuration files in $AUTOUSER). With the upgrade from AutoSys 4.x to 11.x these directory structures change leaving a situation where concurrent use in the 4.x and 11.x environments becomes cumbersome to manage as well as complicating the uninstallation of the 4.x product once it is fully decommissioned.
This document describes the steps involved in moving the product out of the AutoSys directory structure making it available to both environments while protecting it from damage due to removal of the 4.x environment.
- No patch is required if the adapter is run in the AutoSys 11.0 environment, however a patch is required to make the adapter compatible with the 11.3.x environment. At the time this document was authored the patch for 11.3.x compatibility was not published and was available only through CA support. Please check with support for current patch availability/status.
- This document assumes that the adapter was installed and configured as documented in theUnicenter AutoSys Job Management Adapter for PeopleSoft User Guide 2.1.0 or theUnicenter AutoSys Job Management Adapter for PeopleSoft User Guide 2.1.0 R10 or the Unicenter AutoSys Job Management Adapter for PeopleSoft User Guide 2.1.0 R11. Custom implementations are not covered here and it is the responsibility of the customer to adapt these instructions as needed in the event of a non-standard installation.
- * For production systems we highly recommend that the customer test the function of the existing adapter at each step to verify that it is still functional!
- Make backup copies of the /etc/auto.profile, $AUTOSYS/bin directory and $AUTOUSER directory prior to making any changes.
- Create a new directory for the adapter's executable files and configuration files: We recommend creating the following directory under /opt/CA: ps_adapt_2.1.0. Set the ownership and permissions on the directory to match that of the current $AUTOSYS/bin and $AUTOUSER directories. In the event that the permissions do not match, set to whichever is the more permissive of the two. NOTE: If /opt/CA does not already exist then create
- Update the PATH statement in the /etc/auto.profile to include the directory created in step 1 (/opt/CA/ps_adapt_2.1.0 ) so that the executable files will be found without the need of specifying a fully qualified path in your job definitions. (both environments source this file)
- * Move the executable files auto_ps7 and adhoc_ps7 from the existing 4.x $AUTOSYS/bin directory to the /opt/CA/ps_adapt_2.1.0 directory. (please note the adhoc_ps7 is no longer supported, we have included it in this list in case some customers are still using it)
- * Move the configuration files: the adapter uses a unique configuration file for each PeopleSoft instance that it connects to. These configurations are referenced by environment variables set in the /etc/auto.profile.
- Move the *.cfg files from the existing 4.x $AUTOUSER directory to the /opt/CA/ps_adapt_2.1.0 directory.
- In the /etc/auto.profile there are variables set that point to the configuration files, these variables need to be edited in order to correctly indicate the new location of the files.
- * Move the .autorc file: The adapter has an additional file named .autorc in the existing 4.x $AUTOUSER directory. This file contains the peoplesoft user and encrypted password values in it.
- Move the .autorc file to the /opt/CA/ps_adapt_2.1.0 directory.
- The .autorc file is referenced by the variable AUTORC. Update the value of the AUTORC variable in the /etc/auto.profile or create it if it does not already exist.
- Copy the "psoft" directory: there is an additional directory named psoft (or PSOFT) the existing 4.x $AUTOUSER directory. Once the new agent/client is installed that directory and the file in it will need to be copied to the 11.x $AUTOUSER directory.