Preparing to install the Java EE database logger for MFT

Follow these instructions to prepare your Managed File Transfer environment before installing the Java EE database logger.

1. 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.
2. Create a database using the tools provided by your database. The database must have a table space 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.
3. Create the required database tables using your database's tools.

   On Multiplatforms, 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 for z/OS 9.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 for z/OS 9.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.
4. If you are using an Oracle database, add USE_SID_AS_SERVICE_listener_name=on to your listener.ora file, where listener_name is the name of the listener on your database server. Then restart the listener.
   This parameter specifies that the database connection treats the Oracle system identifier (SID) as the service name for the database. This parameter is required because the MFT database logger connects to Oracle databases only by using a SID but later Oracle databases (from version 12c) use a service name. For more information, see the documentation for your version of Oracle, for example Oracle Net Listener Parameters in the listener.ora File. If you do not modify the listener.ora file, you might see the following message when you run the logger:

   ORA-12505, TNS:listener does not currently know of SID given in connect descriptor

5. 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 the Java EE database logger for MFT.
6. Create a reject queue in IBM® MQ.
   Because the 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 fteCreateLogger command creates a reject queue. The default name for this reject queue is SYSTEM.FTE.LOG.RJCT.logger_name
7. Follow the instructions in the topic Configuring user access for the Java EE database logger for MFT.