Setting up the TLOG Processor v2.2.1 sample

You can configure and run the samples in one of two ways. You can use the configured BAR files, or you can configure the message flows and then deploy them. The following steps show both of the alternatives.

On Windows: DB2 scripts and batch files must be run from the DB2 console window on Windows.

On UNIX: You must have the necessary permissions to perform DB2 commands.

Use the configured BAR files

1. Configure the XSL path:
   • On Windows:
     1. Import, or import and deploy the samples.
     2. Copy the contents of the <Toolkit_Workspace> \ETTP_EXAMPLE\XSLT\POSLogV2.1 directory containing the XSLs that are required by the TLOG message flows to C:\Documents and Settings\All Users\Application Data\IBM\MQSI\XSL\external directory
   • On UNIX:
     1. Import the samples.
     2. Copy the contents of the <Toolkit_Workspace>\ETTP_EXAMPLE\XSLT\POSLogV2.1 directory containing the XSLs that are required by the TLOG message flows to /var/mqsi/XSL
     3. Manually deploy the BAR files, use the BAR files that are provided for the UNIX operating systems.
2. Create the queues that are required by the message flows:
   • On Windows (This step is not required if you have used the import and deploy option for the samples):
     • Run the batch file <Toolkit_Workspace>\ETTP_EXAMPLE\samples_utilities\qsender\scripts\BuildETTPSampleQueues_win.bat
   • On UNIX:
     • Run the script <Toolkit_Workspace>\ETTP_EXAMPLE\samples_utilities\qsender\scripts\BuildETTPSampleQueues_unix.sh
3. Create the Monitor and ARTS databases that are required by the message flows:
   • On Windows:
     1. Run the batch file <Toolkit_Workspace>\ETTP_EXAMPLE\samples_utilities\monitor\ddl\setuptlogmondb_win.bat
     2. Run the batch file <Toolkit_Workspace>\ETTP_EXAMPLE\samples_utilities\tlog_arts\ddl\setuptlogartsdb_win.bat
     3. Add two system data source names (DSNs), one named TLOGMON for the TLOGMON database and one named TLOGARTS for the TLOGARTS database, to the ODBC Data Source Administrator.
   • On UNIX:
     1. Run the script <Toolkit_Workspace>\ETTP_EXAMPLE\samples_utilities\monitor\ddl\setuptlogmondb_unix.sh
     2. Run the script <Toolkit_Workspace>\ETTP_EXAMPLE\samples_utilities\tlog_arts\ddl\setuptlogartsdb_unix.sh
     3. Add two data source names (DSNs), one named TLOGMON for the TLOGMON database and one named TLOGARTS for the TLOGARTS database, to the odbc.ini file.

   For more information about creating DSNs, see Enabling ODBC connections to the databases in the IBM Integration Bus documentation.

4. Configure the integration node with the user identifier and password to use when accessing the database:

   Use the mqsisetdbparms command to specify a user identifier and password for the integration node to use with the two data source names TLOGMON and TLOGARTS. This user identifier must be the same user identifier that you used when you created the database in the previous step.

   1. Open a command console window in which you can run IBM Integration commands. Enter the following command to specify the user identifier and password.

      mqsisetdbparms IB9NODE -n TLOGMON -u <user ID> -p <password>
      mqsisetdbparms IB9NODE -n TLOGARTS -u <user ID> -p <password>

   2. Enter the following command to reload the integration server.

      mqsireload IB9NODE -e TLogV221

5. Deploy the BAR files:
   • On Windows:
     • Manually deploy the message flow BAR file that is provided for Windows if it is not already deployed. The TLOG ARTS message flows are deployed by default.
   • On UNIX:
     • Manually deploy the message flow BAR file that is provided for UNIX operating systems.
   • On z/OS:
     • Create the message flow BAR file and deploy it manually.

Configure and deploy the message flows

1. Configure the XSL path:
   • On Windows:
     1. Import the samples.
     2. Set the XSL path in the StyleSheetDirectory property of the Transformation subflow in all of the message flows to <Toolkit_Workspace>\ETTP_EXAMPLE\XSLT
     3. Prefix the existing stylesheet name in the StylesheetName property of the Transformation subflow in all of the message flows with POSLogV2.1\
   • On UNIX:
     1. Import the samples.
     2. Set the XSL path in the StyleSheetDirectory property of the Transformation subflow in all of the message flows to <Toolkit_Workspace>/ETTP_EXAMPLE/XSLT
     3. Prefix the existing stylesheet name in the StylesheetName property of the Transformation subflow in all of the message flows with POSLogV2.1/
   • On z/OS:
     1. Import the samples.
     2. Transfer the XSLs to z/OS in binary mode by using FTP.
     3. Set the XSL path in the StyleSheetDirectory property of the Transformation subflow in all the message flows to the XSL path.
2. Configure the log path:
   • On Windows:
     • All of the message flows have the log paths already set for Windows by default.
   • On UNIX:
     • Set the logpath in all of the message flows to /var/mqsi/Common/log
   • On z/OS:
     • Set the logpath in all of the message flows to <Integration_Bus_Install_Directory>/output
3. Save the message flows.
4. Rebuild the BAR files for Windows and UNIX, create new BAR files for z/OS.
5. Create the queues that are required by the message flows:
   • On Windows:
     • Run the batch file <Toolkit_Workspace>\ETTP_EXAMPLE\samples_utilities\qsender\scripts\BuildETTPSampleQueues_win.bat
   • On UNIX:
     • Run the script <Toolkit_Workspace>\ETTP_EXAMPLE\samples_utilities\qsender\scripts\BuildETTPSampleQueues_unix.sh
6. Create the Monitor and ARTS databases that are required by the message flows:
   • On Windows:
     1. Run the batch file <Toolkit_Workspace>\ETTP_EXAMPLE\samples_utilities\monitor\ddl\setuptlogmondb_win.bat
     2. Run the batch file <Toolkit_Workspace>\ETTP_EXAMPLE\samples_utilities\tlog_arts\ddl\setuptlogartsdb_win.bat
     3. Add two system DSNs, one named TLOGMON for the TLOGMON database and one named TLOGARTS for the TLOGARTS database, in the ODBC Data Source Administrator.
   • On UNIX:
     1. Run the script <Toolkit_Workspace>\ETTP_EXAMPLE\samples_utilities\monitor\ddl\setuptlogmondb_unix.sh
     2. Run the script <Toolkit_Workspace>\ETTP_EXAMPLE\samples_utilities\tlog_arts\ddl\setuptlogartsdb_unix.sh
     3. Add two DSNs, one named TLOGMON for the TLOGMON database and one named TLOGARTS for the TLOGARTS database, in the odbc.ini file.
   • On z/OS:
     1. Transfer the following scripts in binary mode by using FTP:
        • <Toolkit_Workspace>\ETTP_EXAMPLE\samples_utilities\monitor\ddl\setuptlogmondb_zos.sql
        • <Toolkit_Workspace>\ETTP_EXAMPLE\samples_utilities\tlog_arts\ddl\setuptlogartsdb_zos.sql
     2. Run the script <Toolkit_Workspace>\ETTP_EXAMPLE\samples_utilities\monitor\ddl\setuptlogmondb_zos.sql
     3. Run the script <Toolkit_Workspace>\ETTP_EXAMPLE\samples_utilities\tlog_arts\ddl\setuptlogartsdb_zos.sql

   For more information about creating DSNs, see Enabling ODBC connections to the databases in the IBM Integration Bus documentation.

7. Configure the integration node with the user identifier and password to use when accessing the database:

   Use the mqsisetdbparms command to specify a user identifier and password for the integration node to use with the two data source names TLOGMON and TLOGARTS. This user identifier must be the same user identifier that you used when you created the database in the previous step.

   1. Open a command console window in which you can run IBM Integration commands. Enter the following command to specify the user identifier and password.

      mqsisetdbparms IB9NODE -n TLOGMON -u <user ID> -p <password>
      mqsisetdbparms IB9NODE -n TLOGARTS -u <user ID> -p <password>

   2. Enter the following command to reload the integration server.

      mqsireload IB9NODE -e TLogV221

8. Deploy the BAR files manually:
   • On Windows:
     • Manually deploy the message flow BAR file provided for Windows if it is not already deployed.
   • On UNIX:
     • Manually deploy the message flow BAR file that is provided for UNIX operating systems.
   • On z/OS:
     • Manually deploy the message flow BAR file.

Back to sample home