Database logger configuration properties for WebSphere MQ File Transfer Edition
The database logger has a set of configuration properties. The table details the properties and their default values. Specify these properties in the databaselogger.properties file, which is in the config_directory/coordination_qmgr directory.
Property name | Description | Default value |
---|---|---|
wmqfte.max.transaction.messages | The maximum number of messages that is processed in a transaction before the transaction is committed. In circular logging mode, a queue manager has a fixed amount of space available for inflight data. Ensure you set this property with a sufficiently low value so that the available space does not run out. | 50 |
wmqfte.max.transaction.time | The maximum length of time in milliseconds that passes between transaction commits. | 5000 |
wmqfte.max.consecutive.reject | The maximum number of messages that can be rejected
consecutively (that is, without encountering a valid message). If this number is exceeded the database logger concludes that the problem is not with the messages themselves but with the configuration. For example, if you make an agent-name column in the database narrower than all of your agent names, all messages referring to agents are rejected. |
50 |
wmqfte.reject.queue.name | The name of a queue that the database logger puts messages to that the logger cannot handle. See Database logger error handling and rejection for details of which messages might be put onto this queue. | SYSTEM.FTE.DATABASELOGGER.REJECT |
wmqfte.command.queue.name | The name of a queue that the database logger reads command messages controlling its behavior from. | SYSTEM.FTE.DATABASELOGGER.COMMAND |
wmqfte.queue.manager | The queue manager that the database logger connects to (the queue manager must be on the same machine as the database logger). | No default value |
wmqfte.message.source.type | One of the following values:
|
automatic subscription |
wmqfte.message.source.name | If the message source type is administrative subscription or queue, the name of the subscription or queue to use. This property is ignored if the source type is automatic subscription. | No default value |
wmqfte.database.name | The name of the database containing the WebSphere MQ File Transfer Edition log tables. | No default value |
wmqfte.database.type | The database management system in use: DB2® or Oracle. Set this value to db2 or oracle. |
db2 |
wmqfte.database.schema | The database schema that contains the WebSphere MQ File Transfer Edition logging tables. In most cases the default value is appropriate, but you might need to specify an alternative value depending on your own site-specific database considerations. | FTELOG |
wmqfte.database.native.library.path | The path containing the native libraries needed by your chosen database driver (if any). For example, the Type 2 driver for Db2 on AIX® requires libraries from /opt/IBM/db2/V9.5/lib32/. As an alternative to this property, you can set the java.library.path system property using other methods. | No default value |
wmqfte.database.driver | The location of the JDBC driver classes for
the database. This is typically the path and file name of a JAR file.
For example, the Type 2 driver for Db2 on AIX requires the file /opt/IBM/db2/V9.5/java/db2jcc.jar.
On Windows specify the path
separator as a forward slash character (/) for example, C:/Program
Files/IBM/SQLLIB/java/db2jcc.jar. On z/OS®, you must reference all of
the following JAR files:
If your database driver consists of multiple JAR files (for example, Db2 V9.1 requires a driver JAR file and a license JAR file), include all of these JAR files in this property. Separate multiple file names using the classpath separator for your platform, that is, the semicolon character (;) on Windows and the colon character (:) on other platforms. |
No default value |
wmqfte.max.retry.interval | The maximum time, in seconds, between retries
when the database logger encounters a persistent error. Some error conditions (for example, loss of database connection) prevent the database logger continuing. When this type of condition occurs, the logger rolls back the current transaction, waits for a period, and then retries. The time that the logger waits is initially very short, so that transitory errors can be overcome quickly. However, each time the database logger retries, the time that it waits is increased. This prevents too much unnecessary work taking place when the error condition is longer-lasting, for example when a database is taken down for maintenance. Use this property to set a limit to the length of the wait, so that a retry occurs in a reasonable time of the error condition being resolved. |
600 |
wmqfte.database.user | The user that the database logger uses to connect to the database. | No default value |
wmqfte.database.password | The password that the database logger uses to connect to the database. | No default value |
wmqfte.oracle.port | The port that the database logger uses to connect to the Oracle instance. This port is also known as a TNS listener. | 1521 |
wmqfte.oracle.host | The host that the database logger uses to connect to the Oracle instance. | localhost |