IBM MQSeries Workflow SupportPac WA07
Web Services Process Management Toolkit
Version 1 Release 2
Installation and Set-up
Installation Prerequisites
To use the Web Services Process Management Toolkit you need:
To model and execute a business process you need as a minimum requirement:
- MQSeries Workflow Version 3.3 Server
- MQSeries Workflow Version 3.3 Runtime Client or Web Client to run the sample scenario process, which is part of the MQSeries Workflow CD (optional).
Common installation steps
- Unzip the SupportPac files
The base SupportPac file is wa07.zip. Unzip this file into the installation
directory of MQSeries Workflow, for example \fmcwinnt or /usr/lpp/fmc.
This will create the necessary files and sub-directories in the smp directory
of your MQSeries Workflow installation.
- Configure the operating system
Set the environment variable WSPMTK_HOME to the directory where you installed
the package. On Windows NT/2000, this is, for example:
set WSPMTK_HOME=c:\fmcwinnt\smp\wspmtk
- Adapt the file bin\env.bat
In the file bin\env.bat set the environment variables according to your system
Note: The file env.bat is used by other batch files to set the correct
classpath.
- Create an MQSeries Workflow user with the same user ID with which you are logged
on.
Adapt the file person.fdl, which is located in the bin directory, and import it into the MQSeries Workflow system by executing the following command:
wfimport person.fdl
Note: When you set up the samples, an appropriate user ID is created.
Setting up the Generic Service Provider
To set up the generic service provider, you have to deploy it first to make it known by your
Websphere application server. The CreditRequest sample provided with this support pack
contains a CreditRequest.ear (to find under wspmtk\sample\CreditRequest) file. This file contains all neccessary files to setup the generic web service provider, a soap server with the already registerd CreditRequest sample.
After you have deployed the CreditRequest.ear file into the Webshpere application server, you have a new Enterprise Application which you must start. When the new application is started, the generic web service provider is ready to handle client requests.
Within the samples, the generic service provider uses the following MQSeries queue: WEBSERVICE at queue manager: FMCQM which is the default queue manager when installing MQSeries Workflow.
To create the queue, you can use the MQSeries Explorer or the runmqsc utility. To create a queue with the runmqsc utility, enter the following command:
Runmqsc FMCQM
DEFINE QLOCAL(WEBSERVICE) DESCR('Local queue for generic
service provider')
Setting up the Web Services User-defined Program Execution Server (UPES)
To set up the classpath and to run the Web Services UPES, use the WebServicesUPES.bat file that is located in the \bin directory.
Note: The WebServicesUPES.bat file also sets the classpath to the sample package.
The complete syntax of the WebServicesUPES is:
java com.ibm.workflow.soap.upes.WebServicesUPES [-h][-?] [numberOfThreads][QueueManagerName
[RequestQueue [ResponseQueue]]]
Within the samples, the Web Services UPES uses the following MQSeries queue:
WSUPES at queue manager: FMCQM which is the default queue manager when installing
MQSeries Workflow.
To create the queue, you can use the MQSeries Explorer or the runmqsc utility.
To create a queue with the runmqsc utility enter the following command:
Runmqsc FMCQM
DEFINE QLOCAL(WSUPES) DESCR('Local queue for Web Services
UPES')
For error handling, the Web Services UPES in addition uses a queue named ERROR at t queue manager: FMCQM which is the default queue manager when installing MQSeries Workflow.
To create the queue, you can use the MQSeries Explorer or the runmqsc utility.
To create a queue with the runmqsc utility enter the following command:
Runmqsc FMCQM
DEFINE QLOCAL(ERROR) DESCR('Local error queue used by Web Services UPES')
If you want to start the Web Services UPES automatically
using MQSeries triggering, perform the following steps:
- Open the MQSeries Explorer
- Open the Object Tree to Console Root\IBM MQSeries\Queue
Managers\<QMNAME>\Advanced\Process Definitions where <QMNAME>
is the name of your queue manager (default: FMCQM)
- Right-click 'Process Definitions' and select
'New\Process Definition'
- Enter the following values (leave unspecified
fields empty):
- Process Definition Name: WEBSERVICE.UPES
- Description: Web Services UPES
- Application Type: Windows NT
- Application Identifier: %WSPMTK_HOME%\bin\
WebServicesUPES.bat
- Click OK
- Open the Object Tree to Console Root\IBM MQSeries\Queue
Managers\<QMNAME>\Queues
- Right-click the WSUPES Queue
- Select the 'Triggering' Tab
- Enter the following values (leave unspecified
fields empty):
- Trigger Control: On
- Trigger Type: First
- Trigger Depth: 1
- Trigger Message Priority: 0
- Initiation Queue Name: FMCTRIGGER
- Process Name: WEBSERVICE.UPES
- Make sure the batch file %WSPMTK_HOME%\bin\
WebServicesUPES.bat reflects your environment
Next time a message arrives
in the UPES queue, the UPES will be started automatically.