Know How : IBM Integration Bus V9 Retail Pack: TLog to POSLog pattern –Web monitoring
katagall 270001E8SV Visits (2041)
In this blog, I would like to give a brief explanation of TLog to POSLog pattern offered in Retail Pack V1.0 and then concentrate on Web monitoring facility available to monitor the sales data.
The Retail Pack V1.0 comes with a TLog to POSLog pattern that can integrate the in-store devices that generate transaction data and the back-end applications. The pattern offers following functionalities:
1. Transforms TLog data,that is in ACE TLog, TLog XML, POSLog, or MIME with SOAP attachments format, into POSLog v2.1 format.
2. Three choices of input transport are available – Queue, HTTP and File.
3. The POSLog data generated can be sent to a Queue, publish to a topic or write to File.
The pattern also has a feature to monitor the revenue over Web UI. The monitoring can be done at Store and POS level at interval of five minutes, one hour and over a week.
To enable web monitoring on the pattern instance, the option for monitoring should be enabled during pattern instance generation. Once the pattern is instantiated, along with the TLog to POSLog application, another application is generated for web monitoring purpose. This application is basically responsible for reading the monitoring events published by the TLog to POSLog flow and publishing them to the Web UI every 20 seconds.
After these applications are deployed to the integration node and the setup done for the pattern, which includes creating queues and subscriptions, the monitoring must be enabled on the broker with “mqs
A detailed explanation for setup can be found at the infocenter page:
The URI for web monitoring is http
On this page, the pattern instance name needs to be selected for which Web monitoring needs to be done.
The URI http
If the requirement is such that sales data for multiple stores needs to be monitored in a single pattern instance then the following steps can be followed:
Now the Web UI shows sales data graph for multiple stores.
The pattern comes with web monitoring facility for revenue, however any sales data in the POSLog message can be monitored by editing the XPATH expression in the Aggregator message flow of the Monitoring application.
Disclaimer: Each posting on this site is the view of its author and does not necessarily represent IBM’s positions, strategies or opinions. I do not guarantee correctness of the opinions or content or sample code presented here. Use it at your own risk.