Use the fteMigrateLogger command to migrate a stand-alone IBM® WebSphere® MQ File Transfer Edition 7.0 database logger to IBM WebSphere MQ 7.5, or later. If you have configured the database logger
as a Windows service, you must complete extra migration
steps.
Before you begin
Identify instances of the stand-alone database logger. You 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 IBM WebSphere MQ 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
command to migrate the database logger configuration to required version of IBM MQ.
If the queue manager is IBM WebSphere MQ File Transfer Edition 7.0.1 Fix Pack 6 or later,
you can alternatively perform a side-by-side migration by using multiple installations as detailed
in the following steps. If you 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 IBM WebSphere MQ File Transfer Edition 7.0.1 Fix Pack 5 or earlier queue manager, you must first either
migrate this installation to IBM WebSphere MQ File Transfer Edition 7.0.1 Fix Pack 6, to permit
a side-by-side migration, or you must migrate this installation directly to IBM WebSphere MQ 7.5, or later, and additionally select the File Transfer
components.
If the database logger is configured as a Windows
service you must run the fteMigrateLogger command with the
-f parameter. For more information, see fteMigrateLogger: migrate an FTE 7.0 database logger to MQ 7.5 or later.
Procedure
-
Install IBM WebSphere MQ 7.5, or later, alongside the
existing IBM WebSphere MQ File Transfer Edition 7.0 installation, selecting the MQ
Server and Managed File Transfer Service components.
-
Stop the IBM WebSphere MQ File Transfer Edition 7.0 database logger.
-
Move the queue manager to the IBM WebSphere MQ 7.5, or later
installation.
-
Use the fteMigrateLogger command
to migrate the database logger configuration from the IBM WebSphere MQ File Transfer Edition 7.0 installation to the IBM WebSphere MQ 7.5, or later database logger.
-
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.
You 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 you are using
IBM WebSphere MQ File Transfer Edition 7.0.3
and are migrating to
IBM MQ 8.0.0.0, run
703-704, 704-750, 750-7502, and 7502-800.
Note: On
z/OS, you 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 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 8.0.0.0; if
they are not present in the directory, you can download them from the link specified in
APAR
IT01841.
-
Optional: If the IBM WebSphere MQ File Transfer Edition 7.0 database logger was
configured as a Windows service, complete the following
steps:
-
Reconfigure the database logger so that it is no longer a Windows service using the fteModifyDatabaseLogger command.
-
Reconfigure the Managed File Transfer in
IBM WebSphere MQ 7.5 or later logger so that it is a Windows service using the fteModifyLogger command.
-
Start the Managed File Transfer in IBM WebSphere MQ 7.5 or later database logger.
Results
The database logger has now been migrated from IBM WebSphere MQ File Transfer Edition 7.0 to IBM WebSphere MQ 7.5, or later.