Running the TLOG Processor sample

This topic explains how to run test messages in the TLOG Processor v1.0 and v2.2.1 sample message flows.

Run the TLOG Processor ARTS sample
Run the TLOG Processor TRANSFORM sample
Run the TLOG Processor RETEK sample
Run the TLOG Processor MONITOR sample
Information about migration from IA62 and IA64 SupportPacs

To run the samples, you must put messages on the input queues, and get messages from the output queues. You can use the Dequeue section of the Test Client to retrieve the messages from the output queues. If the message is not on the output queue you expect, change the name of the output queue to the name of the failure queue.

If you encounter any problems when you run the sample, see Resolving problems when running samples in the IBM Integration Bus documentation.

Use the following instructions to run the samples:

Running the TLOG ARTS sample

Remove the TLOG RETEK and TLOG TRANSFORM message flows if you have already deployed them.
Deploy the TLOG ARTS message flows if they are not already deployed.
1. Right-click TLogV221_ARTS.bar in the ETTP_EXAMPLE, or TLogV1_ARTS.bar in the ETTP_EXAMPLE_V1 Integration project, click Deploy File.
2. Select the TLogV221 or TLogV1 integration server under the IB9NODE integration node.
Put one of the following input messages onto the input queue:
1. In the ETTP_EXAMPLE, or ETTP_EXAMPLE_V1 Integration project, double-click one of the following .mbtest files to open the file in the Test Client. To run the flows with POSLog v2.2.1 or POSLog v2.1.2 messages, use the .mbtest files with the postfix 221xml for POSLog v2.2.1, or 212xml for POSLog v2.1.2.
  - ACE_mime_poslogxml.mbtest
  - ACE_mime_tlograw.mbtest
  - ACE_mime_tlogxml.mbtest
  - ACE_poslogxml.mbtest
  - ACE_tlograw.mbtest
  - ACE_tlogxml.mbtest
  - GSA_mime_poslogxml.mbtest
  - GSA_mime_tlograw.mbtest
  - GSA_mime_tlogxml.mbtest
  - GSA_poslogxml.mbtest
  - GSA_tlograw.mbtest
  - GSA_tlogxml.mbtest
  - SA_mime_poslogxml.mbtest
  - SA_mime_tlograw.mbtest
  - SA_mime_tlogxml.mbtest
  - SA_poslogxml.mbtest
  - SA_tlograw.mbtest
  - SA_tlogxml.mbtest
2. In the Test Client, click Send Message. The message in the .mbtest file is written to the queue.
If the same input message has already been processed by the ARTS message flow, clean and prepopulate the ARTS database before putting the message to the queue again. To clean the ARTS database, run the following script in a DB2 console window: ClearTLOG_ARTSTables.bat/sh, which is available in the ETTP_EXAMPLE/samples_utilities/qsender/scripts, or ETTP_EXAMPLE_V1/samples_utilities/qsender/scripts directory. To prepopulate the ARTS database, run the following script in a DB2 console window: prepopulate_win.bat.bat or, on UNIX, prepopulate_aix, which are available in the ETTP_EXAMPLE/samples_utilities/qsender/scripts, or ETTP_EXAMPLE_V1/samples_utilities/qsender/scripts directory.

If the samples with TLog Raw input are being tested on a UNIX machine, use the input message files (*.txt) available under the ETTP_EXAMPLE/samples_utilities/input_message_files/unix directory.
Get the transformed message from the ARTS_EXAMPLE_POSLOGXML_OUT queue by using Dequeue:
1. In the Test Client, click Dequeue with the queue: ARTS_EXAMPLE_POSLOGXML_OUT or ARTS_EXAMPLE_INVALID_OUT.
2. Click Get Message to read a message from the ARTS_EXAMPLE_POSLOGXML_OUT queue.
3. If you want to make a copy of the output message:
  1. Under Detailed Properties, ensure that Source is selected.
  2. Right-click the contents of the message in the Source pane, click Select All.
  3. Right-click the contents of the message in the Source pane, click Copy to make a copy of the message.
If the ARTS_EXAMPLE_POSLOGXML_OUT queue has no message in it, the message might be in the input queue, the EXCEPTION_TRANSFORM or EXCEPTION_ARTS failure queues, or one of the system queues.

Running the TLOG TRANSFORM sample

Remove the TLOG RETEK and TLOG ARTS message flows if you have already deployed them.
Deploy the TLOG TRANSFORM message flows if they are not already deployed:
1. Right-click TLogV221_TRANSFORM.bar in the ETTP_EXAMPLE or ETTP_EXAMPLE_V1 Integration project, click Deploy File.
2. Select the TLogV221 or TLogV1 integration server under the IB9NODE integration node.
Put one of the following input messages on the input queue:
1. In the ETTP_EXAMPLE or ETTP_EXAMPLE_V1 Integration project, double-click one of the following .mbtest files to open the file in the Test Client. To run the flows with POSLog v2.2.1 or POSLog v2.1.2 messages, use the .mbtest files with the postfix 221xml for POSLog v2.2.1, or 212xml for POSLog v2.1.2.
  - ACE_mime_poslogxml.mbtest
  - ACE_mime_tlograw.mbtest
  - ACE_mime_tlogxml.mbtest
  - ACE_poslogxml.mbtest
  - ACE_tlograw.mbtest
  - ACE_tlogxml.mbtest
  - GSA_mime_poslogxml.mbtest
  - GSA_mime_tlograw.mbtest
  - GSA_mime_tlogxml.mbtest
  - GSA_poslogxml.mbtest
  - GSA_tlograw.mbtest
  - GSA_tlogxml.mbtest
  - SA_mime_poslogxml.mbtest
  - SA_mime_tlograw.mbtest
  - SA_mime_tlogxml.mbtest
  - SA_poslogxml.mbtest
  - SA_tlograw.mbtest
  - SA_tlogxml.mbtest
2. In the Test Client, click Send Message. The message in the .mbtest file is written to the queue.
If the samples with TLog Raw input are being tested on a UNIX machine, use the input message files (*.txt) available under the ETTP_EXAMPLE/samples_utilities/input_message_files/unix directory.
Get the transformed message from the TRANSFORM_EXAMPLE_POSLOGXML_OUT queue by using Dequeue:
1. In the Test Client, click Dequeue with the queue: TRANSFORM_EXAMPLE_POSLOGXML_OUT.
2. Click Get Message to read a message from the TRANSFORM_EXAMPLE_POSLOGXML_OUT queue.
3. If you want to make a copy of the output message:
  1. Under Detailed Properties, ensure that Source is selected.
  2. Right-click the contents of the message in the Source pane, click Select All.
  3. Right-click the contents of the message in the Source pane, click Copy to make a copy of the message.
If the TRANSFORM_EXAMPLE_POSLOGXML_OUT queue has no message in it, the message might be in the input queue, the EXCEPTION_PRE_TRANSFORM or EXCEPTION_TRANSFORM failure queues, or one of the system queues.

Running the TLOG RETEK sample

Remove the TLOG TRANSFORM and TLOG ARTS message flows if you have already deployed them.
Deploy the TLOG RETEK message flows if they are not already deployed:
1. Right-click TLogV221_TRANSFORM.bar in the ETTP_EXAMPLE or ETTP_EXAMPLE_V1 Integration project, click Deploy File.
2. Select the TLogV221 or TLogV1 integration server under the IB9NODE integration node.
Put one of the following input messages on the input queue:
1. In the ETTP_EXAMPLE or ETTP_EXAMPLE_V1 Integration project, double-click one of the .mbtest files to open the file in the Test Client. To run the flows with POSLog v2.2.1 or POSLog v2.1.2 messages, use the .mbtest files with the postfix 221xml for POSLog v2.2.1, or 212xml for POSLog v2.1.2.
  - ACE_mime_poslogxml.mbtest
  - ACE_mime_tlograw.mbtest
  - ACE_mime_tlogxml.mbtest
  - ACE_poslogxml.mbtest
  - ACE_tlograw.mbtest
  - ACE_tlogxml.mbtest
  - GSA_mime_poslogxml.mbtest
  - GSA_mime_tlograw.mbtest
  - GSA_mime_tlogxml.mbtest
  - GSA_poslogxml.mbtest
  - GSA_tlograw.mbtest
  - GSA_tlogxml.mbtest
  - SA_mime_poslogxml.mbtest
  - SA_mime_tlograw.mbtest
  - SA_mime_tlogxml.mbtest
  - SA_poslogxml.mbtest
  - SA_tlograw.mbtest
  - SA_tlogxml.mbtest
2. In the Test Client, click Send Message. The message in the .mbtest file is written to the queue.
If the samples with TLog Raw input are being tested on UNIX machine, use the input message files (*.txt) available under ETTP_EXAMPLE/samples_utilities/input_message_files/unix directory.
Get the transformed message from the RETEK_EXAMPLE_OUT queue by using Dequeue:
1. In the Test Client, click Dequeue with the queue: RETEK_EXAMPLE_OUT.
2. Click Get Message to read a message from the RETEK_EXAMPLE_OUT queue.
3. If you want to make a copy of the output message:
  1. Under Detailed Properties, ensure that Source is selected.
  2. Right-click the contents of the message in the Source pane, click Select All.
  3. Right-click the contents of the message in the Source pane, click Copy to make a copy of the message.
  If the RETEK_EXAMPLE_OUT queue has no message in it, the message might be in the input queue, the EXCEPTION_PRE_TRANSFORM, EXCEPTION_TRANSFORM, or EXCEPTION_RETEK failure queues, or one of the system queues.

Running the TLOG MONITOR sample

Remove the TLOG RETEK and TLOG TRANSFORM message flows if you have already deployed them.
Connect the Monitor subflow to the TLOG ARTS flow in the TLOG_ARTS_EXAMPLE__ACE, TLOG_ARTS_EXAMPLE__GSA, and TLOG_ARTS_EXAMPLE__SA message flows:
1. Connect the Out terminal of the ARTS_EXAMPLE_POSLOGXML_OUT node to the In terminal of the POSLOG Monitor TryCatch node.
2. Connect the Out terminal of the Invalid Message Trace node to the In terminal of the INVALID Monitor TryCatch node.
3. Connect the Out terminal of the Non-Standard Message Trace node to the In terminal of the Non-Standard Monitor TryCatch node.
Rebuild the TLogV221_ARTS BAR file:
1. Double-click TLogV221_ARTS.bar.
2. Click the Build icon. Save the BAR file.
Deploy the TLOG ARTS message flows if they are not already deployed.
1. Right-click the TLogV221_ARTS.bar in the ETTP_EXAMPLE or TLogV1_ARTS.bar in the ETTP_EXAMPLE_V1 Integration project, click Deploy File.
2. Select the TLogV221 or TLogV1 integration server under the IB9NODE integration node.
Put one of the following input messages on the input queue:
1. In the ETTP_EXAMPLE or ETTP_EXAMPLE_V1 Integration project, double-click the ACE_Monitor_valid.mbtest file to open the file in the Test Client.
2. In the Test Client, click Send Message. The message in the .mbtest file is written to the queue.
Follow the steps specified in the readme_analytics_plotter.txt file, which is available in the ETTP_EXAMPLE/samples_utilities/monitor/analytics_plotter or ETTP_EXAMPLE_V1/samples_utilities/monitor/analytics_plotter directory.
If the ARTS_EXAMPLE_POSLOGXML_OUT queue has no message in it, the message might be in the input queue, the EXCEPTION_TRANSFORM, EXCEPTION_ARTS, or EXCEPTION_MONITOR failure queues, or one of the system queues.

Information about migration from the IA62 and IA64 SupportPacs

This information applies to both the POSLog v1.0 and PosLog v2.2.1 samples.

If the TLOG XML input message has a <Terminal> element instead of a <TerminalNumber> element under TransactionRecord00, change the Message format property of the SAMPLE_ACE_TLOGXML_IN, SAMPLE_SA_TLOGXML_IN, and SAMPLE_GSA_TLOGXML_IN nodes to TLOGXML_IA62.

If the TLOG XML MIME input message has a <Terminal> element instead of a <TerminalNumber> element under TransactionRecord00 in the com.ibm.broker.tlog.constants.TLogConstants.java file, change the following line from public static final String TLOGXML="TLOGXML" to public static final String TLOGXML="TLOGXML_IA62".

Back to sample home