Skip to main content

Upgrade

What is it?​

The upgrade procedure replaces the XP2 Connector scripts with a newer version while preserving all configuration files. You must back up configuration files before extracting the new distribution to avoid overwriting customized settings.

  • Perform this upgrade when a new version of the XP2 Connector distribution is released
  • Use this procedure to replace scripts only — configuration files are backed up and restored separately

Upgrade steps​

To upgrade the XP2 Connector, complete the following steps:

  1. FTP the distribution file to /ops/bin in binary.
  2. Log in to the machine as root.
  3. Change to the /ops/bin directory by entering:
cd /ops/bin
  1. Copy all configuration (INI) files to the /tmp directory. The configuration files consist of: 
cp MSGIN.ini /tmp
cp SMAFetchControlNumber.ini /tmp
cp autoreply.ini /tmp
cp run_xp_job.ini /tmp
  1. Untar the distribution file in the /ops/bin directory:
tar -xvf XP2Applications-<version>.tar
  1. Move the configuration files back into /ops/bin to restore the configuration:
mv /tmp/MSGIN.ini /ops/bin
mv /tmp/SMAFetchControlNumber.ini /ops/bin
mv /tmp/autoreply.ini /ops/bin
mv /tmp/run_xp_job.ini /ops/bin
  1. Confirm the scripts are in the directory the SMAXPSetup global property points to. If the property is /ops/bin/CreateXPEnvForPerl.ksh, that file must exist at that path after the upgrade.
Check the scripts landed where you expect

If the scripts are not where SMAXPSetup points, OpCon jobs keep running the previous version and the upgrade appears to have succeeded while changing nothing.