Use MFT with a remote database

We can use the Managed File Transfer logger to communicate with a database on a remote system.

If we have a database installed on a different machine from the machine Managed File Transfer is installed on, complete the following steps. The steps apply to both Db2® and Oracle unless stated otherwise.

Procedure

1. Install a database client on the system that we have installed Managed File Transfer on.
2. Add your remote database server to your local database client configuration. This configuration update is needed for Managed File Transfer and IBM MQ to correctly access the database.
3. Specify the new properties in the logger.properties file to connect to the database using the credentials file: wmfte.database.credentials.file. Note: Earlier versions of Managed File Transfer used the properties wmqfte.oracle.user or wmqfte.database.user, and wmqfte.oracle.password or wmqfte.database.password. These properties are now deprecated. Use wmfte.database.credentials.file instead.
4. Oracle only: To allow a remote connection to the database, change the XAResourceManager stanza in the coordination queue manager's qm.ini file to the following (ensuring you change the database name, user name and user password to match your own information): Oracle_XA+Acc=P/ftelog/qgw783jhT+SesTm=35+DB=FTEAUDIT1+SqlNet=FTEAUDIT1+threads=false, the change is highlighted in bold.
5. Oracle only: Specify a host and port in the logger.properties file, using the wmqfte.oracle.host and wmqfte.oracle.port properties. The default values for the host and port allow you to work with a local database client so if we have previously worked with a local database, you might not have set these values.