MQSeries Workflow
People administration

Version 1.0

December, 2001

Chris Arnold
IBM United Kingdom
Hursley Park
Winchester
England

arnoldc@uk.ibm.com

Property of IBM

 

Take Note!

Before using this report be sure to read the general information under "Notices".

First Edition, December 2001

This edition applies to Version 1.0 of MQSeries Workflow - People administration and to all subsequent releases and modifications unless otherwise indicated in new editions.

© Copyright International Business Machines Corporation 2001. All rights reserved. Note to US Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule contract with IBM Corp.

Table of Contents

Notices. iv

Trademarks and service marks. iv

Summary of Amendments. v

Preface. vi

Chapter 1. Introduction. 1

Scenario content 1

Chapter 2. Installation and running instructions. 3

Prerequisites. 3

Installation. 3

Running the Scenario. 3

Process Documentation. 3

Uninstall 3

Notices

The following paragraph does not apply in any country where such provisions are inconsistent with local law.

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore this statement may not apply to you.

References in this publication to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates.

Any reference to an IBM licensed program or other IBM product in this publication is not intended to state or imply that only IBM's program or other product may be used.  Any functionally equivalent program that does not infringe any of the intellectual property rights may be used instead of the IBM product.

Evaluation and verification of operation in conjunction with other products, except those expressly designated by IBM, is the user's responsibility.

IBM may have patents or pending patent applications covering subject matter in this document.  The furnishing of this document does not give you any license to these patents.  You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, 500 Columbus Avenue, Thornwood, New York 10594, USA.

The information contained in this document has not be submitted to any formal IBM test and is distributed AS-IS.  The use of the information or the implementation of any of these techniques is a customer responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment.  While each item has been reviewed by IBM for accuracy in a specific situation, there is no guarantee that the same or similar results will be obtained elsewhere.  Customers attempting to adapt these techniques to their own environments do so at their own risk.

Trademarks and service marks

The following terms, used in this publication, are trademarks of the IBM Corporation in the United States or other countries or both:

Ÿ         IBM

Ÿ         MQSeries

Ÿ         MQSeries Integrator

Ÿ         MQSeries Workflow

Ÿ         MQSI

Ÿ         MQWF

The following terms are trademarks of other companies:

·         Windows NT, Windows 2000                 Microsoft Corporation

Summary of Amendments

Date

Changes

December 2001

Initial release

 

 

 

Preface

This SupportPac provides a sample of how a process could be created to control the operations of MQSeries Workflow. It is not intended that the process contained in the SupportPac to be used within a production system. It would require further modification and the addition of activities to handle the different requirements of your own environment. 


Chapter 1. Introduction

IBM’s MQSeries Workflow (MQWF) provides a powerful tool to the challenge of managing processes. The processes normally associated with MQWF are those used to run the business.  When defining the architecture it is apparent that other process exists in and around the business process.  These are internal processes to an organization for example to manage people.  Even with the introduction of LDAP (Lightweight Directory Access Protocol) when staff members join a company there will be several systems, applications and security systems that require notification, updating and authorizations.  This SupportPac shows how MQSeries Workflow can be used to add a new person to the MQWF database. This process can be expanded to include several database updates.

Scenario content

The SupportPac includes an MQSeries Workflow process that consists of activities to update a basic staff definition:

·         To run a batch job to create basic FDL using UserId and user name 

·         To run the MQWF tool to import FDL

·         To run notepad to view the log.

·         To clean up the work files

·         To check a UserID is valid 

To complete the UserID validation, a Java program has also been included.

The Customer Scenario contains the following files.  (Substitute subsequent occurrences of <MQWFDir> with the MQSeries Workflow root directory of your installation).

Object

Install Directory
(The Install directory of MQSeries Workflow. <MQWFDir> This precedes all the subdirectories structures below)

Description

wo02.pdf

\SCENARIO\PeopleAdmin\DOC

SupportPac User Guide in Adobe PDF format

GoCheckUser.java

\SCENARIO\PeopleAdmin\Programs\Java

The Java application logons on to workflow to check to see if a user exists.

GoCheckUser.class

\SCENARIO\PeopleAdmin\Programs\Java

The java class.

Icon217.ico
Icon234.ico
Icon236.ico
ICON30.ICO
ICON32.ICO
ICON48.ICO

\SCENARIO\PeopleAdmin\images

The icons used in the process model. These need to be copied to <MQWFDir>\bin\INCOINST

DelFile.bat

\SCENARIO\PeopleAdmin\Programs

The batch script that will delete the work files produced by each workflow instance.

TheCreateUser.bat

\SCENARIO\PeopleAdmin\Programs

The batch script produces FDL to create a new user. Note the password defaults to “password”.

TheNewUser.bat

\SCENARIO\PeopleAdmin\Programs

This batch script runs the program FMCIBIE.  It contains the ADMIN password.  This will need to be updated if the default is not used.  If the password is left off then the password will be requested every time the activity runs.

AddUseri.htm

\SCENARIO\PeopleAdmin\FDL

\SCENARIO\PeopleAdmin\FDL\AddUseri

Process documentation.

AddUseri.fdl

\SCENARIO\PeopleAdmin\FDL

The process Flow Definition Language for the “Add User” process.

 

Chapter 2. Installation and running instructions

Prerequisites

·         MQSeries Workflow 3.3 Service Pack 1 or higher

·         Java 2 Standard Edition 1.3 (JRE or JVM in the system environment classpath)

Installation

The Customer Scenario must be unzipped in the directory of MQSeries Workflow. Replace all the occurrences of <MQWFDir> with the MQSeries Workflow Installation directory. All the occurrences of  <MQWFDir> in the FDL at <MQWFDir>\scenario\PeopleAdmin\FDL\AddUseri.fdl must be updated. 

In the installation instructions, it is assumed a Microsoft Windows NT/2000 installation is used with default settings for MQSeries Workflow Configuration “FMC”, MQWF system “FMCSYS” and MQWF group “FMCGRP” and queue manager FMCQM.  If you do not have a default installation, you must modify the FDL at <MQWFDir>\scenario\PeopleAdmin\FDL\AddUseri.fdl.

Also, if you have the JVM installed (rather than the JRE) you may have to change the “JRE” command to “Java” in the definition of the program within the FDL: as follows:

Replace

WINNT EXE PATH_AND_FILENAME "jre.exe"

with

WINNT EXE PATH_AND_FILENAME "java.exe"

Once the FDL has been changed it can be import into the runtime of the MQSeries Workflow system. You can also import and then view the process using the Buildtime tool.  You can use the following command from a command window to import the FDL file:

fmcibie -uADMIN -ppassword -o -t -i <MQWFDir>\scenario\PeopleAdmin\FDL\AddUseri.fdl

Running the Scenario

The standard client must be used to run the scenario. Log on to the MQSeries Workflow system using the client and the MQSeries Workflow UserId of Auto.  The Program Execution Agent “PEA” must be running for the UserId of Auto for the scenario to work.  The process can be started from the standard client or the Web client.  Once the process has started you can follow the execution of each activity using the monitor.

Once the user has been added successful use the default password of “password” to logon.

Process Documentation

The process documentation is held in the HTML document:

<MQWFDir>\scenario\PeopleAdmin\FDL\AddUseri.htm

The link to the process documentation. adduseri.htm

Uninstall

There three steps to uninstall the Customer Scenario:

1.       Delete the template from runtime. Use the Standard Client.

2.       Delete the directory <MQWFDir>\scenario\PeopleAdmin\

3.       Delete the process from Buildtime if imported.

 

 

 

 

 

 

 

 

 

 

 

 

 

End of Document