Migrating from the stand-alone database logger to the Java EE database logger for MFT

We can migrate from the stand-alone database logger to the Java EE database logger. We must stop the stand-alone database logger and install the JEE database logger. To avoid losing or duplicating log entries you must stop messages being published to the SYSTEM.FTE topic before stopping the stand-alone database logger, and restart it after you have installed the Java EE database logger. Back up your database before migration.



Procedure

  1. Before stopping the database, run the following MQSC command against your coordination queue manager: ALTER QM PSMODE(COMPAT) This stops messages being published to the SYSTEM.FTE/Log topic. Wait until the logger has processed all of the messages on its subscription. By default, this subscription is called SYSTEM.FTE.LOGGER.AUTO.
  2. Stop the database logger using the fteStopLogger command.
  3. Back up the database using the tools supplied with the database software.
  4. Delete the subscription belonging to the stand-alone database logger. By default, this subscription is called SYSTEM.FTE.LOGGER.AUTO.
  5. If your database schema is at an earlier version, we must migrate the schema to each subsequent level in order. For example, if your database schema is at V7.0.1 and we are migrating to V7.0.4, we must migrate your schema from V7.0.1 to V7.0.2, then from V7.0.2 to V7.0.3, and then from V7.0.3 to V7.0.4. Migrate your database schema from version old to version new, where old and new are variables that describe a schema version, by performing the one of the following actions for each version of the schema that we must migrate through:

    • If your database is Db2 on z/OS and we are migrating between the V7.0.2 and V7.0.3 schemas or between the V7.0.3 and V7.0.4 schemas, create a new database schema and copy your existing data into it. For more information, see Migrating the database tables on Db2 on z/OS to MQ V8.0 or later.

    • If your database is not Db2 or you created your database with a page size of more than 8K, we can migrate the schema in the same way as for other versions, by completing the following steps.

    • If we are migrating between database tables in any other circumstances complete the following steps:
      1. Choose the file that is appropriate to your database platform and has a name that includes the string old-new. This file is located in the MQ_INSTALLATION_PATH/mqft/sql directory of the Remote Tools and Documentation installation.
      2. If we have made modifications to the initial schema, review the migration file to ensure that the file will be compatible with your modified database.
      3. Run the SQL file against your database.

  6. Install the Java EE database logger EAR file.
  7. Deploy the Java EE database logger. For more information, see Installing the Java EE database logger for MFT.
  8. Run the following MQSC command against your coordination queue manager: ALTER QMGR PSMODE(ENABLED) This enables publishing of messages to the SYSTEM.FTE/Log topic.


Results

Parent topic: Configure an MFT logger