You can use the WebSphere® MQ Managed File Transfer logger
to communicate with a database on a remote system.
About this task
If you have a database installed on a different machine from
the machine WebSphere MQ Managed File Transfer is installed
on, complete the following steps. The steps apply to both DB2® and Oracle unless stated otherwise.
Procedure
- Install a database client on the system that you have installed WebSphere MQ Managed File Transfer on.
- Add your remote database server to your local database
client configuration. This configuration update is needed for WebSphere MQ Managed File Transfer and IBM® WebSphere MQ to correctly access the database.
- 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 WebSphere MQ 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.
- 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.
- 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 you have previously worked with a local
database, you might not have set these values.