Follow these instructions to prepare your environment before
installing the JEE database logger.
About this task
For more information about the JEE database logger, see the
topic
Configuring a WebSphere MQ File Transfer Edition logger.
Procedure
- Install your database software using the
documentation for your database. If JDBC support is an
optional component for your database, you must install this component.
- Create a database using the tools provided by your database. The database must have a
tablespace and bufferpool page size of at least 8K. The default schema name is FTELOG. If you use a schema name other than FTELOG, you must edit
the provided SQL file appropriate to your database, ftelog_tables_db2.sql or
ftelog_tables_oracle.sql, to reflect this before proceeding to the next step.
For more information, see wmqfte.database.schema in
- Create the required database tables using your database's tools. On distributed platforms, the files ftelog_tables_db2.sql and
ftelog_tables_oracle.sql contain SQL commands that you can run to create the
tables.
On z/OS®, the file that you need to run
depends on the version of DB2® for z/OS that you are using:
- For Db2
z/OS V9.0 and earlier, run the file
ftelog_tables_zos.sql to create the tables. This file creates the tables using
an INTEGER data type for fields which denote the sizes of files that are transferred and the table
ID associated with each transfer.
- For Db2
z/OS V9.1 and later, run the file
ftelog_tables_zos_bigint.sql to create the tables. This file creates the tables
using a BIGINT data type for fields which denote the sizes of files that are transferred and the
table ID associated with each transfer.
- If you have changed the schema name from FTELOG, you must
change the schema name in the EAR file. For more information, see Changing the schema name in your Java Platform, Enterprise Edition database logger.
- Create a reject queue in WebSphere® MQ. Because the database
logger never discards log messages, if the logger encounters a message
that it cannot handle, it places the message on the reject queue for
examination and possible reprocessing. Do not use the queue manager's
dead letter queue for this purpose, because rejected messages do not
have a DLH header and because rejected messages must not be combined
with messages put to the dead letter queue for other reasons. The
default name for the reject queue is SYSTEM.FTE.DATABASELOGGER.REJECT.
The reject and command queues are defined in the MQSC file generated
by the fteSetupCoordination command in WebSphere MQ
File Transfer Edition Version 7.0.1 or later.
If you defined your coordination queue manager configuration using
an earlier version, you create this queue manually.
- Follow the instructions in the topic Configuring user access for the JEE
database logger.
What to do next
Now you can install the JEE database logger in a JEE-compliant
application server. Use the instructions in the following topics,
based on the application server you are using: