Working with a remote database

You can use the WebSphere® MQ File Transfer Edition database 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 File Transfer Edition 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 you have installed WebSphere MQ File Transfer Edition on.
  2. Add your remote database server to your local database client configuration. This configuration update is needed for WebSphere MQ File Transfer Edition and WebSphere MQ to correctly access the database.
  3. 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. For more information about this stanza, see Configuring transaction support.
  4. Oracle only: Specify a host and port in the databaselogger.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.

Task Task

Feedback

Timestamp icon Last updated: Tuesday, 30 January 2018
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/dl_db_remote.htm