Migrate XCOM for Windows or UNIX/Linux Trusted Database to new server
search cancel

Migrate XCOM for Windows or UNIX/Linux Trusted Database to new server

book

Article ID: 410028

calendar_today

Updated On:

Products

XCOM Data Transport XCOM Data Transport - Linux PC XCOM Data Transport - Windows

Issue/Introduction

This article describes how to migrate an XCOM Trusted Database from a current Windows XCOM server to a new Windows XCOM server as part of a new XCOM installation/upgrade. For this example DB2 will be referenced but the same steps apply for any supported RDBMS for the XCOM Trusted Database.
The same steps also apply to XCOM for Unix/Linux.

Environment

XCOM™ Data Transport® for Windows
XCOM™ Data Transport® for UNIX/Linux

Resolution

  1. On the current Windows server back up the existing DB2 Trusted Database.

  2. On the new Windows server:
    • Install DB2 software according to XCOM for Windows 12.0 Address Software Requirements.
    • Restore the Trusted Database backup from the the current Windows Server.
    • Install XCOM for Windows 12.0 and its latest patch. Do not start the xcomd service.

  3. Follow the 12.0 Set Up Trusted Access steps except for "Create the Trusted Database and Tables" because the database is already there.
    That includes using a text editor to update the xcom.glb file with the required TRUST_ parameters for the new ODBC DSN. The current server ODBC DSN and xcom.glb file parameter values can be used for comparison.
    NOTES:
    • In the context of Trusted transfers, the combination of xcom.glb values SYSNAME and SYSID is treated as a unique identifier of the XCOM server which will be used to query Trusted Database by the XCOM GUI JDBC connection to view the data under "Remote System" and "Manage Users".
    • When data is added to either table XCOM_TRUSTED_SYS or XCOM_TRUSTED_USERS for each new row the SYSNAME & SYSID columns contain the values from the local XCOM server and the SYSTEM_NAME column contains the combined SYSNAME & SYSID values for each remote system that has been added.
    • When viewing the data the XCOM GUI is only reading data where SYSNAME and SYSID matches the values in the local xcom.glb file.
    • Thus when migrating a Trusted Database to a new XCOM server the values of both SYSNAME and SYSID must be the same. If this is not done no data will be visible in the GUI Trusted Transfer tab after all steps have been completed even though the Global Parameters tab for Trusted show a successful connections for JDBC and ODBC with the number of rows in both tables being > 0. 

  4. Manually run the command UPGRADETRUSTDB.EXE to upgrade the Trusted Database schema per the steps "Upgrade the Trusted Database Schema Manually" on the Upgrade from a Supported Release page.

  5. Start the xcomd service.

  6. Use the XCOM GUI to check the Trusted Database connection via the Global Parameters tab for Trusted. Then use the Trusted Transfer tab to check that the expected data is visible.

Additional Information

  1. If the current server is using local Windows accounts for XCOM Trusted transfers and the XCOM GUI option "Manage Users" shows values for DOMAIN which relate to the current server name (rather than being independent of the server i.e. Active Directory or Company Domain) then those values will need to be updated to the corresponding DOMAIN value for the new server.
    Those updates can either be done via the GUI or an SQL Query can be run to update the values of column USER_DOMAIN in Trusted Database table XCOM_TRUSTED_USERS.

  2. Doc. references:
    Use the GUI to Perform XCOM Functions
    Manage Trusted Transfer
Powered by Wolken Software