is work in progress. Please check back soon for actual content.|Info
This section describes a "how-to" for an intial setup of Lotus
Expeditor integrator and the step-by-step configuration for the different
use cases described in section 6.2
. For further details
of use and administration please check Lotus Expeditor integrator UsersGuide.pdf
and AdministratorsGuide.pdf (contained in installation image).
Nevertheless Lotus Expeditor integrator is self contained it makes sense
only in combination with a Backbone Service Bus at the Head Office. For
testing purposes you need to setup a VMWare image with following software
- Microsoft Windows Server 2003 Standard
- Adober Acrobat Reader 8.1.2
- WebSphere MQ 220.127.116.11
of Lotus Expeditor integrator
All described installation steps are related to a Windows 2003 Server operating
system (U.S. english). For other operating systems and languages please
check Lotus Expeditor integrator Infocenter.
1. Detach the software into installation base directory,
2. Execute \desktop\install
the installation setup dialog.
3. Finally, you should have Lotus Expeditor integrator installed in C:\Program
Installation directory overview
At next you could execute XPDintegStart.bat
to verify your installation.
There will occur two command windows for initialization, than disappear
and a new one will show the OSGi console window.
Lotus Expeditor integrator first start
Congratulations! You've successfully installed Lotus Expeditor integrator
on your system. At next we'll step trough the basich configuration of connectivity
and the uses cases described in in section 6.2
to create a template
for mass rollout. Keep the command line window open for further investigation.
Please do NOT close the console window with "Close" button! It
will keep underlying JVM open and bring the system in an inconsistent status.
Type "exit" instead of in the console window if you want to stop
Lotus Expeditor integrator accordingly. If you should have closed console
window with "Close" button or system has been crashed you can
reset Lotus Expeditor integrator with C:\Program Files\IBM\Lotus\Integrator\XPDintegReset.bat.
The console window of Lotus Expeditor integrator is intended for testing
purposes only. In a production environment you'll run Lotus Expeditor integrator
as a service without console. Please check for further configuration of
this service the AdministratorsGuide.
If you're dealing with pure Lotus Expeditor integrator without a management
software like Lotus Expeditor Server or WebSphere Premises Server than
there's one file that contains all necessary configuration information
. You should
copy this file to a working location for further editing. If you've made
some changes you need to copy the changed file into C:\Program Files\IBM\Lotus\Integrator\config\new
directory. Lotus Expeditor integrator has a pre-configured Flow built-in
that monitors this directory for a file named XPDinteg.xml. If this file
occurs Lotus Expeditor integrator will pick up, validate and update his
configuration. Let's see how this looks like.
1. Copy the file to a working location. At this step, change nothing. We'll
keep the file for further work at this work location.
2. Take the file and copy it to C:\Program Files\IBM\Lotus\Integrator\config\new
Lotus Expeditor integrator update
The last two entries in console window show that Lotus Expeditor integrator
has successfully picked up the new file and updated his configuration.
The file in C:\Program Files\IBM\Lotus\Integrator\config
has been replaced by the new one too. Let's now start with the enterprise
connectivity configuration (to Backbone Service Bus).
Configure enterprise connectivity to the Head Office
At first, open the file XPDinteg.xml
that you have copied to the
work loaction with an appropriate XML editor. It could be of course Rational
Application Developer, even if this can also host Lotus Expeditor Toolkit
for development of custom Activities. Move to the following section
First of all, enter a value for location_id
this will be included in any transaction event for recognition of this
Lotus Expeditor integrator instance. For our example we've used the value
. Keep the file XPDinteg.xml
at work loaction open.
Now we'll configure WebSphere MQ for
as representation of Backbone Service Bus. For all WebSphere MQ related
tasks we've used WebSphere MQ Explorer. Once you have installed WebSphere
MQ you must create a default Queue Manager.
WebSphere MQ Queue Manager configuration
At next create the message queues as
shown in next picture. For a more detailed description of the queues check
WebSphere MQ Queue configuration
Now we'll add the configuration for
the micro broker bridge. Remove following section (marked bold) in XPDinteg.xml
at work location
At next move to following section
and replace the bold marked lines as
shown below (these lines have been copied from C:\Program Files\IBM\Lotus\Integrator\config\samples\Sample_XPDinteg.xml
and modified with the appropriate values matching the curretn system configuration)