Upgrade from Service Pack 11.6.01 to 11.6.02
This article describes how you can upgrade from Service Pack 11.6.01 to Service Pack 11.6.02.
This article describes how you can upgrade
CA XCOM Data Transport for Windowsfrom Service Pack 11.6.01 to Service Pack 11.6.02.
Review the Considerations
Consider the following information before you upgrade to Service Pack 11.6.02:
- You can rollback the upgrade manuallyonly. No automatic rollback exists.
- You can upgradeCA XCOM Data Transport for Windows11.6.01 64-bit to CA XCOM Data Transport for Windows 11.6.02 64-bit only, but you cannot upgrade from 11.6.01 32-bit to 11.6.02 64-bit.Service Pack 11.6.02 does not support 32-bit.
- TheCA XCOM Data Transport for WindowsService Pack installer acts as both a new and upgrade installer. If the Installer does not find any installed XCOM instance on your computer, the installer acts as a new installer. If the installer finds a Release 11.6 XCOM instance, the installer acts an upgrade installer.
- You can upgrade in either GUI mode or silent mode:
- To upgrade in GUI mode, follow the instructions on this page.
- To upgrade in silent mode, follow the instructions on Install or Upgrade in Silent Mode.
Understand the Process
When you run the installation program to upgrade the product, it performs the following tasks:
- Performs pre-installation checks to verify the following criteria:
- The user who invokes the installer has admin permissions.
- NoCA XCOM Data Transport for Windowsprocesses are running.
- The currently installed product version is a candidate for the upgrade process.
- Backs up the following information from the existing product environment:
- XCOM_HOME directory
- Registry Keys
- Installs the following entities:
- CA XCOM Data Transport for Windowsbinary files and services
- CAPKI software
- Restore the existingCA XCOM Data Transport for Windowsuser customized settings:
- User customized configuration files, including configssl.cnf, history.inserts, log4j.properties, StandAloneGUIParameters.xml, xcom.cnf, xcom.glb, xcom.ses, xcom.tid, xcom.log, xcomlp, xcomntfy, and exit scripts
- User customized configuration folders, including ssl, tmp, preferences, trace, and convtab
- registry settings
- Copies the user specified JDBC driver jar files to the XCOM_HOME/lib directory
- Removes the existing CAPKI software.
- Performs configuration file migration where the key value pair are compared and merged in configuration files like xcom.glb, xcom.cnf and configssl.cnf.
- Migrates the Transfer Queue records from Service Pack 11.6.01 to the appropriate Service Pack.
- Performs post-installation tasks.
History schema for Service Pack 11.6.02 remains same as Service Pack 11.6.01.
Perform the Pre-Upgrade Tasks
Before you upgrade, complete the following tasks:
- Coordinate with users for the best time to perform the upgrade.
- Verify that no active transfers are running.
- Stop all CA XCOM Data Transport applications.
- Stop the XCOM Scheduler service.
To upgrade from Service Pack 11.6.01, follow these steps:
- Right-click XCOM.exe and select Run as Administrator.
- Follow the directions on the installation panels, and click Next to proceed through the installation process. Click Cancel to exit at any time. Confirm or supply the following information at the prompts:
- License agreement
- Decision to upgrade
- Components to upgrade
- Backup directory
- If TRUST_DATABASE_TYPE= MySQL/DB2, consent for upgrading the trusted database drivers:
- For MySQL, the JDBC Driver Path for the MySQL connector jar files
- For DB2, the JDBC Driver Path and JDBC Driver License for the DB2 JDBC connector jar files
- Provide consent for upgrading History DB schema
- Verify the details on the Pre-Installation (pre-upgrade) Summary panel and click Install.
- Note whether any messages appear about failed upgrade tasks. You can research these messages later in the upgrade log files, which are described later on this page.
- When the upgrade is completed, click Done.
Perform the Post-Upgrade Tasks
The post-installation tasks are:
- (Optional) If you have not already done so, set the PATH variable to include the directory whereCA XCOM Data Transport for Windowsis installed.
- Before you use the product, start the XCOMD CA XCOM Scheduler service.
- If you have not already done so, create the CA XCOM batch interactive group for running jobs or scripts.
- (If applicable) If you used XcomAPI and XcomQAPI from a previous release ofCA XCOM Data Transport for Windowsto build custom applications, perform the following tasksbeforeyou use them with Service Pack:
- Recompile your applications with the Visual Studio 2013 compiler.
- Link them with the new versions of xcomapitcp.lib/xcomapisna.lib from Service Pack.
Review the Log Files
The upgrade log files are:
- %temp%\xcominstaller.log – warnings, error messages, and exit codes that occurred during the installation.
- %XCOM_HOME%\Uninstaller\Logs\*install*.log – the sequence of actions that the installer performed
- %temp%\capki_install.log – CAPKI installation log file