Use case UC003 - Self checkout boxes (Pecuron) status data transfer
to a central Pecuron managment software
A Self Checkout Box will be sending status data as a JMS message to the
System. The System must watch the appropriate message queue and transfer
the incoming message to the head office Backbone Service Bus. At the beginning
and end of the processing the System must be generate events containing
information about the transaction status.
The picture below shows this use case in detail. JKHLE has taken care from
the beginning that with introduction of these new Self Checkout Devices
a near real-time and messaging based approach for data transfer is being
Use case UC003
The example is of a transfer of a status message from such a Self Checkout
(Pecuron) Device to the PBOA (Pecuron Back Office Application) that resides
centrally on an application server cluster for all retail stores of JKHLE.
See the message below for simulation of the application with an embedded
micro broker JMS Client on a Pecuron Device. For testing purposes you could
put this (text) message in the appropriate micro broker queue with HermesJMS.
In the real scenario this is a message a Pecuron sends to the head office
to indicate it is "ready for service".
For routing purposes you need to define one in-queue for each Pecuron device.
A Pecuron doesn't send any JMS custom header properties about his identity
and so far the identity must be defined as parameter for a dedicated Resource
Adapter / in-queue pair. Find below the in-queue definition for our example.
The Resource Adapter definition looks like following.
Finally there's the Flow definition as listed below.
You should take care to ensure there is an exact match of the topic definition
for the Resource Adapter definition (Resource Monitor acts as publisher)
and Flow definition (Application Control Service acts as subscriber and
starts the Flow).
Putting a test message into the queue XPDinteg_SelfCheckoutInQ
finally trigger the Flow that reads the message from this queue and puts
it into XPDinteg_ResOutQ
. It is necessary to generate JMS custom
header properties for further routing mechanisms at the Backbone Service
Bus. The parameters for the second Activity have the following meaning.
- adds the standard JMS custom header properties
that are required for further processing at central side
- adds a JMS custom property for ResourceType
- adds a JMS custom property for PecuronId (ID of the Pecuron
See the output in Lotus Expeditor integrator console window when the use
case was executed successfully below.
Console output UC003
Find below some excerpts from a PoT performed for JKHLE, including Pecuron
Device Application (PAPP) with micro broker JMS Client, Lotus Expeditor
integrator, WebSphere Message Broker (WMQ) and Pecuron Back Office Application
(PBOA). This one uses the use case UC003 for status information from Pecuron
to PBOA while it also implements a use case for messages from PBOA to Pecuron
that is not described here.
Operational considerations UC003
PBOA screen before receiving PAPP status message - the red dot means that
the Pecuron is not available for customer transactions
PBOA screen after receiving PAPP status message - the green dot means that
the Pecuron is ready for customer transactions