+

Search Tips | Advanced Search

Migrating an FTE V7.0 database logger to MQ V7.5 or later

Use the fteMigrateLogger command to migrate a stand-alone WebSphere MQ File Transfer Edition Version 7.0 database logger to IBM WebSphere MQ Version 7.5, or later. If we have configured the database logger as a Windows service, we must complete extra migration steps.


Before starting

Identify instances of the stand-alone database logger. We must update database logger instances before other parts of the Managed File Transfer network so that these instances can correctly process the latest versions of the transfer log messages they receive.


About this task

To migrate directly to Version 7.5, or later, first stop the logger and then migrate this installation to the required version. When this migration is complete, use the fteMigrateLogger: migrate an FTE V7.0 database logger to MQ V7.5 or later command to migrate the database logger configuration to required version of IBM MQ.

If the queue manager is WebSphere MQ File Transfer Edition Version 7.0.1, Fix Pack 6 or later, we can alternatively perform a side-by-side migration by using multiple installations as detailed in the following steps. If we do not wish to perform a side-by-side migration, instead migrate the queue manager and logger using the steps as described above.

If the database logger is connected to an WebSphere MQ File Transfer Edition Version 7.0.1, Fix Pack 5 or earlier queue manager, we must first either migrate this installation to WebSphere MQ File Transfer Edition Version 7.0.1, Fix Pack 6, to permit a side-by-side migration, or we must migrate this installation directly to IBM WebSphere MQ Version 7.5, or later, and additionally select the File Transfer components.

If the database logger is configured as a Windows service we must run the fteMigrateLogger command with the -f parameter. For more information, see fteMigrateLogger: migrate an FTE V7.0 database logger to MQ V7.5 or later.


Procedure

  1. Install IBM WebSphere MQ Version 7.5, or later, alongside the existing WebSphere MQ File Transfer Edition Version 7.0 installation, selecting the MQ Server and Managed File Transfer Service components.
  2. Stop the WebSphere MQ File Transfer Edition Version 7.0 database logger.
  3. Move the queue manager to the IBM WebSphere MQ Version 7.5, or later installation.
  4. Use the fteMigrateLogger command to migrate the database logger configuration from the WebSphere MQ File Transfer Edition Version 7.0 installation to the IBM WebSphere MQ Version 7.5, or later database logger.
  5. Create the tables needed for the database logger to start by running the sql scripts in MQ_INSTALLATION_PATH/mqft/sql. There is one script for each increase in product level, run all that are appropriate in order. We must run the upgrade sql scripts in version order, starting with their current level of IBM WebSphere MQ File Transfer Edition or Managed File Transfer. The available scripts, where *** can be Db2, Oracle, or z/OS, are as follows:

    • ftelog_tables_***_701-702.sql
    • ftelog_tables_***_702-703.sql
    • ftelog_tables_***_703-704.sql
    • ftelog_tables_***_704-750.sql
    • ftelog_tables_***_750-7502.sql
    • ftelog_tables_***_7502-800.sql

    For example, if we are using WebSphere MQ File Transfer Edition Version 7.0.3 and are migrating to IBM MQ Version 8.0.0.0, run 703-704, 704-750, 750-7502, and 7502-800.Note: On z/OS, we can go directly from 704 to 800, using ftelog_tables_zos_704-800.sql The scripts up to ftelog_tables_***_704-750.sql are included in IBM MQ Version 8.0.0.0, and are located in the MQ_INSTALL ATION_PATH/mqft/sql directory. Upgrades beyond 750 were not shipped with IBM MQ Version 8.0.0.0; if they are not present in the directory, we can download them from the link specified in APAR IT01841.

  6. Optional: If the WebSphere MQ File Transfer Edition Version 7.0 database logger was configured as a Windows service, complete the following steps:
    1. Reconfigure the database logger so that it is no longer a Windows service using the fteModifyDatabaseLogger command.
    2. Reconfigure the Managed File Transfer Version 7.5, or later logger so that it is a Windows service using the fteModifyLogger command.

  7. Start the Managed File Transfer Version 7.5, or later database logger.


Results

The database logger has now been migrated from WebSphere MQ File Transfer Edition Version 7.0 to IBM WebSphere MQ Version 7.5, or later. Parent topic: Migrating IBM MQ Managed File Transfer

Last updated: 2020-10-04