In this section we describe the configuration of the different use cases step by step. The following picture gives an overview of four use cases.
Use cases overview
Use case UC001 - Article data transfer to store and print article labels
A message containing article data is being sent from Backbone Service Bus to the System. It must be recognized in terms of purpose, life time and destination where data should be delivered to. The message payload must be extracted and detached to a directory at the local file system of the Back Office Server. After delivery of the file a batch file must be executed. All parameters are provided in the message header of the incoming message. At the beginning and end of the processing in the system events must be generated containing information about the transaction status.
The picture below shows the Lotus Expeditor integrator components that are working for processing the transactional data. For better clarity components that provide monitoring events are excluded.
Use case UC001
It defines a file structure as following.
This is for printer data files to be stored and the batch file that should be executed. The batch file itself contains an echo command only to be able to see in the console window whether it has been executed.
If the batch file contains code that might stop batch execution for a longer time (for example, long running processes for data processing of user interaction) you should use a remote call of another batch process with the call command. Otherwise Lotus Expeditor integrator may hang.
The incoming JMS message is shown below, it can be loaded into WebSphere MQ queue XPDinteg.ReqOutQ100
with a JMS client that is able to load JMS messages into a message queue. For these purposes, we can use HermesJMS, an open source JMS browser. The configuration of HermesJMS is described in section 7.1 Using HermesJMS to work with WebSphere MQ and micro broker
The message must contain at least the parameters as shown above. Additional parameters can be added by an Inbound Resource Mapper. See the appropriate section in XPDinteg.xml
below (don't forget to copy this configuration file to C:\Program Files\IBM\Lotus\Integrator\config\new
once you've made any changes and check the console output whether the configuration update has been processed successfully).
In principle an incoming message from the Backbone Service Bus is being routed through the Dispatcher. The unique key for every message is defined by the parameter ResourceType
. This is being referenced within Resource Inbound Mapper to add further optional parameters. Afterward, the Dispatcher itself fires an event to the topic
at the EventAdmin Service. In our case this topic is
The appropriate Flow (it has do be defined and stored in C:\Program Files\IBM\Lotus\Integrator\flowdefs
directory) is triggered by an event on this topic as defined in Flow header. Find the Flow definition for use case UC001 below (Flow PutPriceUpdateFile.flow
The last activity in the Flow contains the name for the local script file that should be executed (for example, for calling the program for printing label data delivered by the file). Finally the output in the console window should look similar to the following :
Console output UC001