You can migrate from the stand-alone database logger to
the JEE database logger. You 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 JEE database logger. Back up your
database before migration. Before you restart the database logger,
update the database schema to store the new information produced by the
current version of WebSphere® MQ
File Transfer Edition.
Procedure
- 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 database logger has processed all of the messages on
its subscription. By default, this subscription is called SYSTEM.FTE.DATABASELOGGER.AUTO.
- Stop the database logger using the fteStopDatabaseLogger command.
- Back up the database using the tools supplied
with the database software.
- Delete the subscription belonging to the stand-alone database
logger. By default, this subscription is called SYSTEM.FTE.DATABASELOGGER.AUTO.
- If your database schema is at an earlier version,
you must migrate the schema to each subsequent level in order. For
example, if your database schema is at V7.0.1 and you are migrating
to V7.0.4, you 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 you must
migrate through:
If your database is DB2® on z/OS® and you are migrating between
the V7.0.2 and V7.0.3 schemas or between the V7.0.3 and V7.0.4 schemas,
you must 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.
If your database is Db2 on Windows, Linux or UNIX,
you are migrating between the V7.0.2 and V7.0.3 schemas, and you created
your database with a page size of less than 8K; you must increase
the page size of the database before migrating to the new version
of the database schema. For more information, see Increasing the page size of the log database on Db2 on Windows, UNIX or Linux.
If your database is
not Db2 or you created your
database with a page size of more than 8K, you can migrate the schema
in the same way as for other versions, by completing the steps below.
- If you are migrating between database tables in any other
circumstances complete the following steps:
- 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 install_directory/tools/sql directory
of the Remote Tools and Documentation installation.
- If you have made modifications to the initial schema, review the
migration file to ensure that the file will be compatible with your
modified database.
- Run the SQL file against your database.
- Install the JEE database logger EAR file as part of the
Remote Tools and Documentation installation. For more information,
see Installing IBM WebSphere MQ File Transfer Edition Remote Tools and Documentation using the graphical installer.
- Deploy the JEE database logger. For more information, see Installing the WebSphere MQ File Transfer Edition JEE database logger.
- 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.