IBM MQSeries Workflow Version 3.1 for Business Integration

Software Announcement
July 28, 1998
Announcement Letter Number: 298-270


Table of Contents:

(Corrected on October 27, 1998)

Under Passport Advantage Subscription, the part number for Software Advantage Upgrade Protection for FlowMark Version 2.3 servers was corrected.

At a Glance

This new version offers important enhancements in the areas of:

  • Business integration -- In the MQSeries family, IBM MQSeries Workflow Version 3.1 represents the workflow component. It ties together applications, people, tasks, and technology across and beyond organizations, linking disparate activities, systems, and applications across heterogeneous platforms.

  • Scalability and capacity -- IBM MQSeries Version 5 and IBM DB2 Universal Database Version 5, which are supplied with MQSeries Workflow Version 3.1, offer greatly enhanced scalability and capacity for FlowMark V2.3 customers. This is achieved by the exploitation of MQSeries and DB2 features as well as by an enhanced, scalable workflow runtime system architecture.

  • Windows 32-bit exploitation --
    • Buildtime and standard client on Windows NT and Windows 95
    • ActiveX controls development kit (modification level 1)
    • Prepared for Microsoft BackOffice server certification
  • Licensing terms -- New terms reflect use on a wide range of distributed server hardware configurations and different end user involvement in regard to the Internet.
-----------------------------------------
For ordering, contact:
  Your IBM representative, an IBM
  Business Partner, or IBM North America
  Sales Centers at
    800-IBM-CALL  Reference: YE010



Overview

With IBM MQSeries (R) Workflow Version 3.1 you can optimize the competitive capabilities of your organization. Customers using this technology in production have already been experiencing these key benefits:

  • Integration of business processes within and across enterprises
  • Integration of applications
  • Faster execution of business processes
  • Higher productivity through automation
  • Better service to customers at reduced costs
  • Improved quality of process execution
  • Enforcement of processes to achieve ISO 9000 compliance
IBM MQSeries Workflow Version 3.1 is a workflow management middleware offering that automates workflow between applications, and automates business processes involving people and applications to give organizations more control of their business activities. MQSeries Workflow helps you in daily business operations, planning, and management, to align and integrate resources and applications, to improve efficiency, and to gain higher market share. In addition, it enables the design of applications tailored to your business.

IBM MQSeries Workflow Version 3.1 is the next version of IBM FlowMark (R). IBM has developed this new version to provide a growth path to FlowMark Version 2.3 customers. With this version we are also renaming FlowMark to MQSeries Workflow.

IBM MQSeries Workflow Version 3.1 is a member of IBM's MQSeries family of offerings, which provide customers a portfolio of Business Integration software. It builds on the sound foundation of IBM MQSeries Version 5, IBM's industry-leading, messaging-oriented middleware. It enables integration across heterogeneous IT environments so that workflow tasks communicate securely and reliably over a wide range of platforms.

For data storage, IBM MQSeries Workflow Version 3.1 uses IBM DB2 (R) Universal Database Version 5, the relational database recognized worldwide, to expand capacity and scalability beyond previous limits.

Among the most notable new functions of MQSeries Workflow is full support for 32-bit Windows (TM) platforms: a server running on Windows NT (R), Buildtime and standard clients running on Windows NT or Windows 95, Workflow client APIs, and a rich set of development tools. It is prepared for Microsoft (TM) BackOffice certification.

New licensing terms bring a scalable pricing structure based on processor strength and a new user definition that accommodates Internet scenarios.



Intended Customers

IBM MQSeries Workflow may be beneficial to businesses in any industry, as well as to non-profit organizations.



Key Prerequisites

IBM MQSeries Workflow Version 3.1 operates on:

  • AIX (R), OS/2 (R), or Windows NT for the servers
  • AIX, OS/2, Windows NT, or Windows 95 for the client APIs
  • Windows NT or Windows 95 for the standard clients

------------------------------

This announcement is provided for your information only. For additional information, contact your IBM representative, call 800-IBM-4YOU, or visit the IBM home page at: http://www.ibm.com



DESCRIPTION



Planned Availability Dates

This program will be made available in three stages, and each stage will be associated with a new modification level. Each modification level will make available additional functions, features, and national language versions as outlined below:

Supported                       Modification
Features                           Level          Available

Buildtime on 0 July 31, 1998 Windows NT + 95; server on AIX, Windows NT; standard clients on Windows NT + Windows 95

All the above plus 1 October 30, 1998 OS/2 Runtime Support; Lotus Notes (R) client; ActiveX controls devlp. kit

All the above plus 2 December 31, 1998 additional APIs

Beta: November 30, 1998: Java (TM) API beans client downloadable from the Internet



Business Integration

Business Integration is about improving customer service, reducing cost, and avoiding wasted effort. It is about optimizing your business processes, applicable to any organization in any industry. It is about integrating your value chain across suppliers and customers, allowing you to act more readily, responsively, and effectively. It is about helping companies rapidly deploy and get better value from e-business and the uptake of the Web. It is about solving the information integration issues of mergers and acquisitions.

IBM's architected Business Integration with MQSeries initiative has three products: MQSeries for reliable interconnection over more than 25 platforms, MQIntegrator, to simplify message transformation, rules, and intelligent routing, and finally MQSeries Workflow, to leverage corporate effectiveness through optimized use of staff and computing resources. These products reduce the burden of IT shops, enabling them to be market driven and responsive to the rate of market change when addressing integration-related business issues. The products specialize in ease of deployment, reducing the cost of ownership and minimizing the user and IT skills required for integration.

Workflow and messaging are key to corporate responsiveness. Business activities instantly share customer and status information through an event-driven model triggered from the text or content of individual business transactions. These events are reliably automated to trigger further computing activity or may pass to staff through worklists and personal activity.



New Functions and Enhancements

Based on Message Queuing: IBM MQSeries Workflow Version 3.1 uses IBM MQSeries Version 5 as the underlying middleware for client/server communication, communication between server components, and server transaction commit coordination with DB2. The MQSeries Workflow program package includes the MQSeries code CD-ROMs for all platforms supported by MQSeries Workflow and a restricted license for use only in association with MQSeries Workflow.

Based on Relational Database: IBM MQSeries Workflow Version 3.1 stores Buildtime and Runtime data in a relational database. The MQSeries Workflow servers exploit the industrial strength, capacity, scalability, transaction, reliability, security, and administration functions built into DB2 UDB.

The MQSeries Workflow program package includes the DB2 UDB code CD-ROMs for all platforms supported by MQSeries Workflow and a restricted license to use IBM DB2 Universal Database Version 5 only in association with MQSeries Workflow.

Buildtime for Windows NT and 95: With MQSeries Workflow Buildtime, you define and document your business processes in a workflow model consisting of the following elements:

  • Processes comprised of several activities and subprocesses, together with a specification of their control and data flows

  • The definition and assignment of the workflow participants within an organization to activities and processes
    • The registration of programs to activities

    • The definition of data structures, for use with activities and program registrations
With MQSeries Workflow Buildtime, you can graphically depict the processes and their activities in a process model, and define all other pieces of the workflow model via a graphical user interface. In addition, Buildtime provides functions to define the properties of MQSeries Workflow servers and their network topology. MQSeries Workflow Buildtime operates on a personal computer running either Windows NT or Windows 95.

Buildtime uses its own database for modeling purposes. Access is implemented via Open Database Connectivity Support (ODBC). Either IBM DB2 Universal Database Version 5 or Microsoft JetEngine can be used. JetEngine is supplied together with the MQSeries Workflow program package.

The workflow data can be transferred via an export/import function into the Runtime database.

Workflow Servers: The MQSeries Workflow servers connect all clients, and control the execution of processes throughout your organization. A server consists of one or more components, such as administration server, execution server, scheduling server, or cleanup server. MQSeries Workflow servers have been designed for scalability including exploitation of multiprocessor architectures such as SMP and SP2 (R). Multiple execution servers can be started on a single server (hotpooling) or multiple servers (system group) sharing the same database; this will allow customers to connect more and more workflow clients to the same workflow Runtime database, sharing the same workflow definitions and running process instances.

Administration Utility: The Administration Utility allows the administrator to start and stop server components, query their status, view various system properties, monitor various events, and view their associated messages in an MQSeries Workflow system or system group.

Supported Platforms

                     Build        Client Client Admin PEA
                     time  Server  GUI    API    API
----------------------------------------------------------
IBM AIX                      x             x      x    x
----------------------------------------------------------
IBM OS/2                     x             x      x    x
----------------------------------------------------------
Microsoft Windows NT   x     x      x      x      x    x
----------------------------------------------------------
Microsoft Windows 95   x            x      x      x    x
----------------------------------------------------------
Lotus Notes on OS/2                 x      x
            on Win NT               x      x
            on Win 95               x      x
----------------------------------------------------------

Standard Client: Available on Windows NT and Windows 95, the MQSeries Workflow standard client provides a graphical user interface to manage processes and work items. The clients serve as the interface for the users and work together with the program execution agents to invoke applications that run under MQSeries Workflow control.

Client for Lotus Notes: The MQSeries Workflow Client for Lotus Notes is an interface to Lotus Notes, which relies on the Workflow client API. Through the MQSeries Workflow Client for Lotus Notes, you can use Notes (TM) as a corporate data repository and as the front-end work environment for MQSeries Workflow without further adaptation.

The MQSeries Workflow Client for Lotus Notes provides two primary enhancements:

  • It represents the Client on a Notes desktop.

  • It provides a transparent runtime interface with functions and APIs, it allows you to create a Notes environment, and it completely hides the fact that MQSeries Workflow is involved.
The MQSeries Workflow Client for Lotus Notes is available for Windows NT, Windows 95, and OS/2 (Hebrew is not supported on OS/2).

Program Execution Agent (PEA): An MQSeries Workflow Program Execution Agent enables the execution of client programs as defined for program activities.

Audit Trail: Audit trail data is stored in IBM DB2 Universal Database Version 5. DB2 tools can be used to query the audit trail.

Prepared for BackOffice Server Certification: IBM MQSeries Workflow Version 3.1 is prepared for Microsoft BackOffice Server certification, providing these features:

  • Ability to run the server as NT service (mod. level 0)

  • Support for SMS installation

  • Transport independence (as supported by IBM MQSeries Version 5)

  • Support for NT Unified Logon (mod. level 0)
To obtain the actual certification status, visit: Note: IBM MQSeries Version 5 and IBM DB2 Universal Database Version 5 already are Microsoft BackOffice certified.

Workflow Client Application Programming Interfaces: MQSeries Workflow client APIs allow for access to workflow server functions from program activity and workflow client implementations. The workflow client API is implemented in C, providing the base for additional program language bindings and FlowMark Version 2.3 compatibility APIs. As a result, a variety of programming languages is supported for the different platforms, including C, C++, VisualBasic, REXX, and LotusScript (R).

The MQSeries Workflow ActiveX Controls Development Kit provides higher-level programming interfaces to workflow client components implemented as ActiveX Controls. These Controls simplify the development of custom workflow clients.

Java Client as Beta Program: IBM will provide a Java client and related support services. This thin client solution consists of a Java-based gateway to MQSeries Workflow and a set of Java beans. These beans access the gateway using a CORBA or RMI infrastructure and run on Java Virtual Machine, for example on the IBM Network Station (TM).

As a precursor to the upcoming OMG Workflow Facility the Java client allows customers to embed workflow functionality into Internet applications. This Java client will be downloadable from the MQSeries Workflow Internet home page. For more details, visit:

New Licensing Terms: IBM MQSeries Workflow Version 3.1 implements a scalable and versatile pricing structure according to customer usage. It reflects use on a wide range of server machines as well as different end user involvement (for example an anonymous Internet user starting new processes versus employees processing work items assigned to them).

Three items make up the program license:

  1. The program package, carrying a fixed price.

  2. The servers, representing a scalable licensing structure following the one defined by IBM MQSeries Version 5. The customer pays capacity units (CUs) according to the strength and number of all the processors that execute the MQSeries Workflow servers.

  3. The registered users, representing all people who have the possibility to work directly or indirectly with MQSeries Workflow work items.



Migrating from FlowMark Version 2.3

The following approaches can be used:

  • Process models can be migrated from FlowMark V2.3 to IBM MQSeries Workflow Version 3.1 via FDL export from FlowMark V2.3 and import to Buildtime of MQSeries Workflow Version 3.1.

  • To work with IBM MQSeries Workflow Version 3.1, programs developed for FlowMark V2.3 need to be recompiled and relinked, provided that the compiler is still available on the affected operating environment. Some circumstances might require program modifications to cope with new or changed functions and concepts in MQSeries Workflow Version 3.1.
For customers who use FlowMark Version 2.3 in production and want to migrate to this new MQSeries Workflow Version 3.1, IBM and Business Partners offer upgrade services for a fee.



Services Support and Solutions Offerings

IBM is committed to working with industry vendors to define interfaces for higher-value functions, APIs, tools, and management functions for Business Integration. IBM will also provide partnering opportunities for Independent Software Vendors (ISVs) and System Integrators (SIs). For example, IBM will work with ISVs to provide complementary solutions, applications, tools, and system management and monitoring offerings. The Software Solutions Development Laboratory, Boeblingen, Germany is already working with partners to create and deliver solutions based on IBM MQSeries Workflow.

System Integrators will be able to assist customers with their implementation and integration.

IBM Global Services, as well as the Workflow Competence Centers, work jointly with Business Partners to provide all kinds of services to satisfy the MQSeries Workflow customers.

Workflow Competence Center Services: These centers provide you additional, customizable offerings for a fee:

Systems Assurance: Validates model design and system configuration against the following criteria:

  • Model logic, error check

  • Workload, performance, and capacity planning

  • Hardware and software topology
Workflow Development: Provides:
  • Assistance in designing your process model for MQSeries Workflow

  • Education in workflow and business process modeling
Installation Support: Installs and configures MQSeries Workflow and prerequisites in heterogeneous customer environments

Migration Support: Assists customers to upgrade from FlowMark to MQSeries Workflow:

  • Buildtime process models

  • Runtime-data process instances

  • Customer application migration
Generic Automatic Test Tool: Tests and tunes MQSeries Workflow applications, and evaluates their behavior. When writing application programs for the C APIs, this tool provides instant feedback, and helps developers in testing and training. A prototyping facility allows for rapid definition of API scenarios, load simulation on servers and clients, and easy performance measurements. This tool is available only as part of the development services.

Application Implementation: Offers development of customized programs requiring:

  • ActiveX exploitation

    To customize the standard client, and to build customer-based worklists and other process-related applications on Microsoft clients

  • Lotus Notes integration

    Customization of Lotus (R) Notes clients

  • Implementation of a Java Internet client

    To develop a Workflow Internet application using the Workflow Java beans APIs (customization and full support for a fee)



EuroReady

IBM MQSeries Workflow Version 3.1 has been tested and is EuroReady.



Year 2000

This product is Year 2000 ready. When used in accordance with its associated documentation, it is capable of correctly processing, providing, and/or receiving date data within and between the 20th and 21st centuries, provided all other products (for example, software, hardware, and firmware) used with the product properly exchange accurate date data with it.

The maintenance end date for this Year 2000 ready product is June 30, 2001.



PRODUCT POSITIONING



IBM MQSeries Family of Products for Business Integration

IBM MQSeries Workflow Version 3.1 is the next version of IBM FlowMark. With this version FlowMark is renamed to MQSeries Workflow.

IBM has announced a family of products based on IBM's industry-leading IBM MQSeries Version 5 messaging software to help companies address Business Integration issues quickly and economically, making them more agile, customer-oriented, and competitive as they face the increasing complexities of conducting business globally and electronically. This MQSeries family of products allows companies to maximize e-business opportunities by leveraging existing resources to improve speed-to-market and anticipate IT changes as their business changes.

IBM Business Integration consists of three modular offerings under the MQSeries brand which can be used together in any combination, modular or separately:

  • IBM MQSeries Version 5 for secure and reliable communication of application messages over a wide range of platforms.

  • MQSeries Integrator for transformation and routing of application messages. It is optimized for high-volume, in-storage transformation of messages. The initial offering is called MQIntegrator, which has MQSeries integrated with New Era of Networks, Inc. (NEON) transformation and rules engine.

  • IBM MQSeries Workflow for workflow automation between applications, and applications and people.
MQSeries Integrator intercepts MQ (TM) messages, transforming and routing the message contents based on information stored in a rules database.

MQSeries Workflow uses IBM MQSeries Version 5 messaging for the communication between the MQSeries Workflow clients and servers.

In addition:

  • MQSeries Workflow processes can be started by a custom MQSeries application program that listens to an MQSeries queue, initiates the MQSeries Workflow process container with message data, and starts the execution of the MQSeries Workflow process template.

  • You can develop MQSeries Workflow program activities that put and get the container data of MQSeries Workflow activities to and from an MQSeries message queue for communication to applications on additional platforms.
MQSeries Integrator can also be used in both scenarios as described above, in conjunction with MQSeries Workflow:
  • MQSeries Integrator can generate a message to start a process.

  • MQSeries Integrator can intercept the message generated by the custom MQSeries Workflow activity program and transform and/or re-route it to one or more target applications via MQSeries, as defined in the MQSeries Integrator rules database.

  • You can also use MQSeries Integrator as a rules database to transform the data in a container for MQSeries Workflow. One can create an MQSeries Workflow program activity that puts workflow container data into a queue, which can then be accessed by MQSeries Integrator and transformed as defined by the rules in the MQSeries Integrator database, and the resulting message then is put into a reply queue.



Document Management and IBM Enterprise Document Management Suite

Document routing is a key function associated with document management. Many workflow integration projects involve the integration of at least one document management system, such as IBM ImagePlus (R) VisualInfo (TM), via workflow process models into the overall business solution.

Document management products, such as IBM ImagePlus VisualInfo, typically include built-in, internal workflow for basic sequential document routing functions. MQSeries Workflow can be used together with ImagePlus VisualInfo, gaining more flexible and advanced routing capabilities. Also, additional applications are integrated into the overall business process managed by MQSeries Workflow.

IBM EDMSuite is a portfolio of Web-enabled products that include imaging, workflow, COLD (computer output to laser disk) archiving, collaborative document management, and Internet connection components. The workflow management component is MQSeries Workflow.

The IBM EDMSuite strategy opens the door to the wealth of digital documents stored in systems across your organization by leveraging the power of network computing. This information can give you a complete picture of customer relationships, integrate project information from across your organization, or provide immediate access to the wide range of information needed to be agile in a competitive environment. Access is provided through familiar Web browsers, Lotus Notes clients, and sophisticated production clients.

For more details, visit:



Business Analysis and Modeling Tools

Prior to the implementation of a workflow management (WFM) system, consultants and partners often use Business Analysis and Modeling tools to determine the particular business processes for automation and refinement. These tools typically concentrate on the functions needed for consulting purposes, leaving out the detailed definitions needed to run and execute a workflow.

Workflow management engines also offer workflow definition tools, to specify everything needed to automate a process. MQSeries Workflow Buildtime is such a tool, which allows for the specification of process models (activities, data container, control, and data flow), organization models ("staff"), program registration, and server definitions.

Business Analysis and Modeling tools can interface to MQSeries Workflow via published interfaces. You can import workflow definitions using the Flow Definition Language (FDL) into the MQSeries Workflow Buildtime and/or MQSeries Workflow server databases.

After execution of a process model during runtime, the MQSeries Workflow audit trail can be used to store workflow history data in a data warehouse and analyze what happened when the processes were executed. You can develop tools that analyze this workflow history data, to verify assumptions made during the modeling phase and optionally refine the process definition.

Several vendors have created Business Analysis and Modeling tools and programs that support FlowMark V2.3 FDL, for example Holosofx WorkflowBPR. Its Version 3.0 (5620-BHB) and Version 2.0 (5620-BHA) are available from Holosofx, marketed jointly with IBM.



Combining Production Workflow and Ad-Hoc Workflow

Workflow applications can be divided into the ad-hoc (and collaborative) workflow segment and the production (and administrative) workflow segment: ad-hoc workflows are often defined and changed on the spot (for example when defining a task force), and a specific workflow definition is executed only very few times; whereas production workflows are typically pre-defined once and then repeated many times as modeled.

In the ad-hoc market segment, customers often use either groupware systems such as Lotus Notes and Microsoft Exchange, or Web Browsers, to implement workflow solutions for the knowledge worker using collaboration databases and/or a scripting language such as LotusScript, VisualBasic, or HTML.

MQSeries Workflow is primarily an offering to the production workflow market segment, while also offering a lot of ad-hoc functionality such as online update to staff definitions and late binding of subprocesses, which both can immediately affect the flow of work to people in running processes.

MQSeries Workflow supports production workflows integrated into standard desktops:

  • The MQSeries Workflow client for Lotus Notes allows customers to use their Lotus Notes desktop to interface to MQSeries Workflow processes and work items.

  • Similar client desktop integration solutions have also been built by partners and customers, to support Microsoft Exchange (via ActiveX) and Web Browsers (via HTML/CGI or Java and the Workflow C++ APIs).
With the combination of MQSeries Workflow and Lotus Notes, IBM offers a complete workflow management solution covering all workflow application segments.



Workflow and Application Servers

Application servers, such as Component Broker, CICS (R), Lotus Domino (TM), and TXSeries, are focused on enabling the building, deploying, and managing of business applications (for example real time business data access and update) according to particular styles of application programming. The application designer typically has responsibility and control over the application and data design choices, but works within this programming style (model or environment). Application servers also provide capability for integrating applications and data, as long as the specific programming style (model) is used. Application designers have leveraged this integration capability and will continue to do so.

Business Integration with MQSeries is a complementary family of products to the application server offerings, focussing on the heterogeneous integration of application programs, information sources, and business processes. Business integration does this integration without imposing a programming style (model) to the end points being integrated.

MQSeries Workflow is concerned with automating business processes across disparate heterogeneous business systems, as well as human activity. The business process elements being automated are autonomous.

Automation logic elements (scripts, process models, and so forth) are themselves styles of business application programs with many of the same system design concerns (performance, availability, scale, life cycle, and so forth) as traditional business applications.

The workflow application designer has control over the logic of sequencing between business process steps, but not over the steps themselves.

  • Component Broker is in the process of enhancing its programming model to include workflow initiation and coordination. The workflow engine that Component Broker plans on leveraging is MQSeries Workflow.

  • Lotus Domino and Notes also provide workflow capability for homogeneous Domino and Notes environments. MQSeries Workflow can interface with this Lotus workflow capability, and assists in providing workflow automation across a heterogeneous environment.

  • MDp provides workflow capability to CICS-based application solutions such as ECC's Callflow. MQSeries Workflow can interface with this application workflow, and integrate it with other applications and additional platforms.

  • ActiveX and JavaBeans are popular component models, exploited by many application developers today. Such application components typically provide the interfaces needed for integration into a workflow client. MQSeries Workflow is well-suited to integrate application components via a workflow model, and supports the integration of ActiveX components with the ActiveX controls development kit.

  • ERP systems are packaged applications that promise many of the benefits of integrated workflow-based solutions. They also face many of the same problems solved by workflow management systems: most of them are still monolithic applications, and some ERP vendors have started efforts to decomponentize their system into pieces that can be released more independently, and they are providing tools to simplify the introduction time for their system. Some ERP systems internally use a workflow component.

  • MQSeries Workflow can provide workflow automation beyond ERP systems, integrating other applications within and across enterprises as needed to build additional business solutions. For this integration, MQSeries Workflow can interface with ERP systems through either of the following, dependent on the concrete scenarios and ERP modules to be supported:
    • The external interfaces of that ERP system's clients or servers and/or

    • The integration support provided for a particular ERP system by an MQSeries bridge and/or MQIntegrator Application Templates. For a list of ERP systems supported by MQSeries and MQIntegrator, refer to:
In general MQSeries Workflow enables integration of heterogeneous applications, information sources, and business processes via predefined workflow models.



Network Computing and e-business

The Internet is a huge opportunity for the development of new integrated solutions, and provides the ability to reach virtually everyone everywhere on the globe. Speed-to-market and quick reaction to market changes are key in this environment. The ability of MQSeries Workflow to integrate existing and new application components on distributed platforms into business solutions enables this needed flexibility for e-business solutions and allows you to update individual workflow application components or the process model gradually as the business demands.

The desktop interface exposed by these solutions is typically custom built, deploying the customer's Internet support technology of choice, such as communication protocols, ORB, development environments, and Internet standards such as HTML, CGI, Java, and XML. MQSeries Workflow supports the creation of such solutions via its Runtime API Libraries and its MQSeries Workflow Development Kit.

Customers already have successfully implemented such workflow-based solutions for the Internet, based on the FlowMark and MQSeries Workflow client APIs.



Standards

The definition of standards for workflow management systems is driven by the Workflow Management Coalition (WfMC). This is a group of companies whose aim is to develop specifications that allow different workflow management products to interoperate with each other. In addition, the WfMC supports related workflow specifications with appropriate standard bodies, such as OMG, as a base for wider deployment of workflow interfaces in the context of object-oriented and Internet-based development efforts. For more information visit:

MQSeries Workflow is designed according to the WfMC reference model. The referring APIs are available, based on this modular architecture.

As a sponsor of the WfMC, IBM also continues to be a major contributor to future standard development.

The WfMC also coordinates the SWAP workflow initiative announced by Netscape. SWAP is based on an IBM proposal for an OMG workflow standard (jFlow) and complements the workflow standards that IBM has been driving during the last couple of years.

IBM does support Netscape's initiative to define an HTTP/XML based workflow standard. SWAP together with jFlow will enable cooperation of workflow management systems across a broad variety of protocols used in the Internet today.



Systems Management

  • Workflow in production requires effective system management procedures to be in place, specifically for network monitoring, troubleshooting, and backup of workflow and application data.

    MQSeries Workflow provides command line system management interfaces, for example to start and stop the system via the MQSeries Workflow admin utility. It supports standard system management interfaces, for example as required for Microsoft BackOffice certification (runs as NT service and supports SMS installation).

    In addition, MQSeries and DB2 tools apply to manage the workflow software stack, together with tools that support the operating system, the network protocols, and the applications. For example, ADSTAR (R) Distributed Storage Manager (ADSM) is a solution for backup and archival of workflow data stored in MQSeries and DB2 UDB.

  • Customers also use MQSeries Workflow to automate systems management processes triggering Tivoli TME 10 (TM) activities, for example. Refer to Redbook ZZ81-0405, Integrating Change Management into Business Processes, for more details on possible solutions in this area, which include the automation of the ordering process for hardware and software in an organization, combined with automated software distribution via a systems management tool.



STATEMENT OF GENERAL DIRECTION

IBM intends to make available IBM MQSeries Workflow Version 3.1 servers to run in the following additional operating environments:

  • HP-UX
  • Sun Solaris
In addition IBM also intends to make available IBM MQSeries Workflow Version 3.1 for OS/390 (TM).

These Statements of Direction represent IBM's current intentions and objectives and are subject to change or withdrawal.

Trademarks

      NETWORK STATION, MQ, VisualInfo, and OS/390 are trademarks of
      International Business Machines Corporation in the United
      States or other countries or both.
      MQSeries, FlowMark, DB2, DB2 Universal Database, AIX, OS/2,
      SP2, ImagePlus, CICS, and ADSTAR are registered trademarks of
      International Business Machines Corporation in the United
      States or other countries or both.
      Windows and Microsoft are trademarks of Microsoft Corporation.
      Windows NT is a registered trademark of Microsoft Corporation.
      Java is a trademark of Sun Microsystems, Inc.
      TME 10 is a trademark of Tivoli Systems, Inc.  in the United
      States or other countries or both.
      Notes and Domino are trademarks of Lotus Development
      Corporation.
      Lotus Notes, LotusScript, and Lotus are registered trademarks
      of Lotus Development Corporation.
      Other company, product, and service names may be trademarks or
      service marks of others.



SUPPLEMENTAL INFORMATION



EDUCATION SUPPORT

The following education courses are available for customers and Business Partners:

Course Title

IBM MQSeries (R) Workflow Version 3.1:

    Basics: 1 day theory plus 1 day hands-on class
    Administration: 2-day class
    Modeling: 2-day class
    API Programming: 5-day class
Ask your IBM representative for details and enrollment. Visit this Web site for additional information: The appropriate curriculum will be updated, as necessary, to include the enhancements in this announcement.

Services designed to assist you in the installation and implementation of IBM MQSeries Workflow in your organization are also available.



PUBLICATIONS

No hardcopy publications are shipped with this program.

The following publications are available separately in U.S. English from Mechanicsburg after July 31, 1998. To order, contact your IBM representative:

Form
Number         Title

IBM MQSeries Workflow Version 3.1: GH12-6285 Concepts and Architecture (introduction) SH12-6286 Getting Started with Buildtime SH12-6287 Getting Started with Runtime SH12-6288 Installation Guide SH12-6289 Administration Guide SH12-6291 Programming Guide GH12-6357 List of Workstation Server Processor Groups



Displayable Softcopy Publications

These manuals are part of the basic machine-readable material and can be displayed with an HTML browser or with Adobe Acrobat Reader, respectively. The manuals are stored as HTML and PDF files on a CD-ROM dedicated to softcopy documentation, which is shipped together with the program CD-ROM. As the national language versions become available, this CD-ROM is refreshed accordingly.

The files can also be used with an HTML browser or with an Adobe Acrobat Reader, respectively, to create unmodified printed copies of these manuals. Terms and conditions for use of the machine-readable files are shipped with the files.



TECHNICAL INFORMATION



Specified Operating Environment

Buildtime Environment

  • A personal computer with Intel-based processor architecture is required (for example, Pentium (TM) 200 MHz).

  • Screen: Resolution 1024x768, recommended 17 inches (measured diagonally) or larger.

  • Microsoft (TM) Windows NT (R) Workstation V4.0 (Service Pack 3 required) or Windows (TM) 95, Service Pack 1 or OSR2 is required.

  • Buildtime database: IBM DB2 Universal Database (R) Enterprise Edition for Windows NT Version 5, or IBM DB2 Universal Database Personal Edition for Windows 95 Version 5, or Microsoft JetEngine (all databases are included in MQSeries Workflow Version 3.1). For DB2 (R) UDB, installation of FixPak WR09024 (April 1998) is required. Visit URL for DB2 FixPaks.
                  **** DB2 UDB ****           *** JetEngine ***
Operating         Main         Hard          Main         Hard
Environment       Memory       Disk          Memory       Disk

Windows 95 64 MB 1 GB 48 MB 700 MB Windows NT 96 MB 1 GB 64 MB 700 MB

Note: Make sure you have sufficient swap space.

Runtime Environments

General Recommendations

  • When setting up your servers, for performance and safety reasons keep data and log files on separate disks.

  • All specifications are valid for a two-tier configuration (database and server reside on the same system).

  • The number and size of process models and process instances residing in the runtime database, as well as the number of clients concurrently attached to the server, heavily influence the demand for main memory and hard disk space.

  • For systems not used for production (for example development/test/demo systems) less main memory may be sufficient.
Servers for AIX (R)
  • An RS/6000 (TM) single processor, or SMP, or SP2 (R) machine as supported by AIX is required. For a list of IBM machines visit URL:
  • Screen: A dedicated graphical display is not necessary. The system console is sufficient.
Operating           Main                Hard
Environment         Memory              Disk

RS/6000 256 MB 2 GB

Clients for AIX: A workstation capable of running the operating system.
  • Operating System: AIX Version 4.2.

  • IBM MQSeries for AIX Version 5 client (included). Installation of MQSeries CSD 02 is required. Visit URL for MQSeries CSDs.

  • For the development of programs using the MQSeries Workflow APIs, one of:
    • IBM CSet++ for AIX Version 3.1.4 (MQSeries Workflow client APIs for C and C++, FlowMark (R) 2.3 compatibility workflow client API for C++).

    • IBM C for AIX Version 3.0 (FlowMark 2.3 compatibility C language API).
Servers for OS/2 (R) (Available in Modification Level 1)
  • A personal computer supported by OS/2 with Intel-based processor architecture, for example Pentium 200 MHz, is required.
                           **** DB2 UDB ****
Operating                 Main           Hard
Environment               Memory         Disk

OS/2 Warp Server V4 128 MB 2 GB

  • Operating System: OS/2 Warp Server Version 4.

  • IBM MQSeries for OS/2 Version 5 (included). Installation of MQSeries CSD 02 is required. Visit URL for MQSeries CSDs.

  • DB2 Universal Database Enterprise Edition for OS/2 Version 5 (included). The DB2 FixPak level required will be announced at the availability date.
Clients for OS/2 (Available in Modification Level 1): A personal computer capable of running the operating system and at least 32 MB of main memory are recommended.
  • Operating System: OS/2 Warp Version 4.

  • IBM MQSeries for OS/2 Version 5 client (included). Installation of MQSeries CSD 02 is required. Visit URL for MQSeries CSDs.

  • For the development of programs using the MQSeries Workflow APIs, one of:
    • IBM VisualAge (R) C++ Version 3.0 (MQSeries Workflow client APIs for C and C++, FlowMark 2.3 compatibility workflow client API for C++, FlowMark 2.3 compatibility C language API).

    • IBM REXX (included in OS/2, FlowMark 2.3 compatibility REXX language API).
  • For the MQSeries Workflow Client for Lotus Notes (R):
    • Lotus Notes Release 4.5 (Hebrew is not supported).
Servers for Windows NT
  • A personal computer with Intel-based processor architecture, for example Pentium with 200 MHz, is required.
For test or demo purposes, an IBM ThinkPad (R) or portable Personal Computer is acceptable.
                           **** DB2 UDB ****
Operating                 Main           Hard
Environment               Memory         Disk

Windows NT 128 MB 2 GB

Clients for Windows NT: A personal computer with Intel-based processor architecture capable of running the operating system and 64 MB of main memory are recommended.
  • Operating System: Microsoft Windows NT Workstation V4.0; Service Pack 3 is required.

  • IBM MQSeries for Windows NT Version 5 client (included). Installation of MQSeries CSD 02 is required. Visit URL for MQSeries CSDs.

  • For the development of programs using the MQSeries Workflow APIs, one of:
    • Microsoft Visual C++ Version 5.0 (MQSeries Workflow client APIs for C and C++, FlowMark 2.3 compatibility workflow client API for C++, FlowMark 2.3 compatibility C language API).

    • IBM VisualAge C++ Version 3.5 (MQSeries Workflow client APIs for C and C++, FlowMark 2.3 compatibility C language API).

    • Microsoft VisualBasic Version 5.0 (FlowMark 2.3 compatibility VisualBasic language API).
  • For the development of programs using the MQSeries Workflow ActiveX Controls (not part of mod. level 0):
    • Microsoft VisualBasic Version 5.0.
  • For the MQSeries Workflow client for Lotus Notes (not part of mod. level 0):
    • Lotus Notes Release 4.5.
  • For an MQSeries Workflow standard client, no additional prerequisites are required.
Clients for Windows 95: A personal computer capable of running the operating system and 48 MB of main memory are recommended.
  • Operating System: Microsoft Windows 95; Service Pack 1 or OEM Service Release 2 is required.

  • IBM MQSeries for Windows 95 Version 5 client (included). Installation of MQSeries CSD 02 is required. Visit URL for MQSeries CSDs.

  • For the development of programs using the MQSeries Workflow APIs, one of:
    • Microsoft Visual C++ Version 5.0 (MQSeries Workflow client APIs for C and C++, FlowMark 2.3 compatible workflow client API for C++, FlowMark 2.3 compatibility C language API).

    • IBM VisualAge C++ Version 3.5 (MQSeries Workflow client APIs for C and C++, FlowMark 2.3 compatibility C language API).

    • Microsoft VisualBasic Version 5.0 (FlowMark 2.3 compatibility VisualBasic language API).
  • For the development of programs using the MQSeries Workflow ActiveX Controls (available in mod. level 1):
    • Microsoft VisualBasic Version 5.0.
  • For the MQSeries Workflow client for Lotus Notes (available in mod. level 1):
    • Lotus Notes Release 4.5.
  • For an MQSeries Workflow standard client, no additional prerequisites are required.
Compatibility: Process models created under FlowMark Version 2.3 can be imported to IBM MQSeries Workflow Version 3.1.

Applications developed under FlowMark Version 2.3 can be recompiled and relinked as long as IBM MQSeries Workflow Version 3.1 supports the programming languages affected.

Limitations: To plan for optimum performance and capacity and for possible limitations, contact your IBM representative or Business Partner for a systems assurance review with a Workflow Competence Center expert.

Performance Considerations: The performance of IBM MQSeries Workflow Version 3.1 depends heavily on the usage characteristics of the process models and organization definitions, the average and maximum size of worklists, the capacity and utilization of the MQSeries Workflow and database server machines, the speed and memory size of the server and client machines, and the transmission speed and load of the communication channels.

To increase the number of users sharing the same processes, consider the use of multiple servers sharing the same database.

Contact your IBM representative or Business Partner for a systems assurance review of your specific implementation of IBM MQSeries Workflow Version 3.1.



Planning Information

Installation and Maintenance: On all platforms, you can install IBM MQSeries Workflow Version 3.1 from the CD-ROM. Alternatively you can create installation diskettes for OS/2 and Windows NT from the CD-ROM.

Communication Protocols: The components of MQSeries Workflow communicate with each other via IBM MQSeries Version 5 and/or IBM DB2 Universal Database Version 5. IBM MQSeries Version 5 supports the following protocols:

  • TCP/IP (tested with MQSeries Workflow Version 3.1)
  • IPX
  • NetBIOS
  • SNA LU6.2
For the actual status visit URL: Customer Responsibilities: The customer is responsible to:
  1. Assign a knowledgeable systems administrator who has responsibility for planning, installing, maintaining, and administering an IBM MQSeries Workflow Version 3.1 installation in production.

  2. Implement the management procedures for an effective operation.

  3. Provide sufficient hardware resources if IBM MQSeries Workflow Version 3.1 is used in production.
Ask IBM or Business Partners to obtain assistance with customizable services offerings.

Installability: The customer must install IBM MQSeries Version 5 and IBM DB2 Universal Database Version 5 (the program code for both is available from the MQSeries Workflow program package) before IBM MQSeries Workflow Version 3.1 can be installed. Installation of these programs is not described in the MQSeries Workflow documentation. To prepare for their smooth installation, you should have handy their installation instructions or the latest release of their installation manuals in respect to the intended platform.

Packaging

Program Package: IBM MQSeries Workflow Version 3.1 is available as one family program package, containing all product components for all supported operating environments. It includes:

  • IPLA booklet and pointer sheet

  • One Proof of Entitlement for two MQSeries Workflow server Capacity Units

  • One Proof of Entitlement for one MQSeries Workflow Registered User

  • List of Workstation Server Processor Groups

  • Service Statement

  • License Information

  • Customer Registration Card

  • One CD-ROM containing the IBM MQSeries Workflow Version 3.1 program code for all national language versions supported

  • One CD-ROM containing the IBM MQSeries Workflow Version 3.1 softcopy documentation for all national language versions supported

  • Four CD-ROMs containing the IBM MQSeries Version 5 program code

  • Seven CD-ROMs containing the IBM DB2 Universal Database Version 5 program code



Security, Auditability, and Control

The security and auditability features are:

  • Access to MQSeries Workflow program and data files is protected via local operating system security mechanisms.

  • User authentication is provided by means of an IBM MQSeries Workflow user ID and password. Passwords are not transmitted over the line, neither at user logon nor when users change their passwords. No clear text password is stored in the MQSeries Workflow server databases.

    The following platform-specific options are also supported for logon:

    • Windows NT unified logon is supported, as required for Microsoft BackOffice certification.

    • The MQSeries Workflow client for Lotus Notes supports user authentication via Notes (TM) ID files and an automatic connection of that user to the workflow server.
  • DB2 security applies for access control to MQSeries Workflow databases.

  • MQSeries security applies for access control to MQSeries Workflow queues.

  • Users must be authorized via FDL and/or MQSeries Workflow Buildtime to access MQSeries Workflow resources, such as processes, and to administer the system.

  • Auditing is provided via operating system security logs and an MQSeries Workflow audit log.
The customer is responsible for evaluation, selection, and implementation of security features, administrative procedures, and appropriate controls in application systems and communication facilities.



ORDERING INFORMATION

To order, specify the program package and the appropriate number of capacity units and registered users.

All charges are one-time charges. The program package carries a fixed price. In addition there are two variable charge units:

  • Processor-based charges for all processors or machines running MQSeries Workflow servers and databases, and

  • Registered users



Processor Charges Definition

The price structure for servers depends on the strength and number of processors. These are assigned to tiers associated with a certain number of Capacity Units (CUs) as the means for charging. The higher the tier and the greater the number of processors, the more CUs are required. The customer must purchase CU Authorizations to use servers or databases of the program on each machine and machine upgrade. The program package includes two CU Authorizations; additional CU Authorizations must be purchased if the customer uses MQSeries Workflow servers or databases on machines that represent a greater number of Capacity Units.

MQSeries Workflow Workstation Server Processor Groups

.--------+----+----+----------------------------------------.
|        |Tier| CU |     Processors/Machines                |
|--------+----+----+----------------------------------------|
| Entry  | T1 |  2 | Intel Uniprocessor machines            |
|--------+----+----+----------------------------------------|
|        | T2 |  4 | Intel 2-way SMP machines,              |
|        |    |    | RISC 1-2 processors per box/SP(tm)     |
|        |    |    | node                                   |
|        |----+----+----------------------------------------|
|        | T3 |  6 | Intel/RISC 3-4 processors per box/SP   |
|        |    |    | node                                   |
|        |----+----+----------------------------------------|
|Midrange| T4 | 10 | Intel/RISC 5-8 processors per box/SP   |
|        |    |    | node                                   |
|        |----+----+----------------------------------------|
|        | T5 | 14 | Intel/RISC 9-16 processors per box/SP  |
|        |    |    | node                                   |
|        |----+----+----------------------------------------|
|        | T6 | 16 | Intel/RISC 17-24 processors per box/SP |
|        |    |    | node, RS/6000 7017-Sxx machines        |
|--------+----+----+----------------------------------------|
|High End| T7 | 30 | >24 processors per box/SP node,        |
|        |    |    | SUN Ultra Enterprise 10000 and Ultra   |
|        |    |    | HPC 10000 HP T-Class and V-Class       |
'--------+----+----+----------------------------------------'

Note: CU = Capacity Units required

A Capacity Unit (CU) has no direct relationship to machine capability; it is a charging-authorization term only.

There are seven tiers. Additional Capacity Units are required as you progress through the tiers. The tiers are linked to number of processors, with the exception of Tier 7, for which typical machines are named.

This list is not exhaustive and does not attempt to cover the many machines currently available. Many of the machines listed will have fewer processors than their maximum supportable. The Capacity Unit authorizations will need to be updated as new CPUs are added to existing machines.



Registered User Definition

A Registered User for MQSeries Workflow is any person who has the ability to connect, directly or indirectly, to an MQSeries Workflow server and works with MQSeries Workflow work items (for example query, start, check out, check in, transfer, and so forth).

While the number of Registered Users covers the number of defined people who can work with work items assigned by an MQSeries Workflow server, the number of all server Capacity Units (CUs) covers all other tasks that users can perform, such as process start, program execution, checking the status of a process, or checking if MQSeries Workflow starts completely automated processes. In these cases Registered Users are not applicable because the actual number of people may be unknown (for example everybody on the Internet or intranet might be a potential user) or zero (in the case of fully automated workflows).

Examples

  • Standard Example

    A company has installed one MQSeries Workflow server on one AIX machine falling into tier 3. There are four hundred employees working with MQSeries Workflow. Some of these are actually sharing a user ID. Each of these employees processes his or her user ID related work list. Some of these might also start new processes.

    This results in the need to purchase licenses for 400 Registered Users (that many people are working with work items although the number of user IDs might be less than 400). For the servers the company has to purchase six CU authorizations for the AIX machine.

  • Intranet Example

    A company has installed one MQSeries Workflow server on one AIX machine falling into tier 2. MQSeries Workflow processes are started and monitored by an unknown number of employees via the intranet and a gateway at the company's Web server (using MQSeries Workflow APIs). Two hundred employees participate in the resulting workflow (this may be via browsers and the intranet or via standard runtime clients) and process the various work items.

    This results in the need to purchase authorizations for 200 Registered Users (that many people are actually working with work items). This number remains the same if the 200 users are connected to the server through a kind of gateway concentrator that reduces the actual number of physical logons to the server. For the servers the company has to purchase authorizations for four Capacity Units for the AIX machine. There is no need to purchase any Registered User authorizations for those employees who are working via the intranet, but do not work with work items, only start or monitor processes.

  • Internet Example

    A company has installed MQSeries Workflow server components on four different NT machines falling into tier 1. One machine is used just as a database server, the other three machines host other server components connected to this database server. MQSeries Workflow processes are started by an unknown number of customers via the Internet and a gateway at the company's Web server (using MQ (TM) Series APIs). Six hundred employees participate in the resulting workflow and process the various work items.

    This results in the need to purchase licenses for 600 Registered Users (that many people are actually working with work items). For the servers the company has to purchase two CU authorizations for each of the four NT server machines (in total eight CUs for all machines). There is no need to purchase any Registered User authorizations for the customers working via the Internet as these customers do not work with work items, but just start processes.

Order
Type        Feature   Part
Number      Number    Number      Program Name

IBM MQSeries Workflow Version 3.1: 5801-AAR 3604 09L8161 -- Program Package (SBCS)

5807-AAR 1090 09L8192 -- 1 Capacity Unit 5807-AAR 1094 09L8224 -- 1 Registered User

Upgrades

IBM MQSeries Workflow Version 3.1: 5803-AAR 1484 09L8181 -- Program Upgrade Package (SBCS)

5808-AAR 0476 09L8208 -- 1 Server Upgrade Capacity Unit 5808-AAR 0480 09L8240 -- 1 Registered User Upgrade



Passport Advantage Subscription

Migration Rules: A customer who has acquired Software Advantage Upgrade Protection for FlowMark Version 2.3 servers (part number 50H0783) and a number of Registered Users (part number 77H8301) is entitled to receive new server authorizations according to the number of installed FlowMark V2.3 servers and new Registered User authorizations acquired. For an entitled customer, these rules apply:

  • The MQSeries Workflow program package is sent automatically to this customer shortly after general availability.

  • Per each Registered User of FlowMark V2.3 the customer will automatically receive one Registered User Authorization for MQSeries Workflow.

  • Per each started multiple of a hundred FlowMark V2.3 Registered Users the customer will automatically receive two server Capacity Unit Authorizations for MQSeries Workflow.

    Formula: Resulting number of CUs = 2 x ceiling (FM V2.3 Registered Users/100)

    Note: "Ceiling" represents a mathematical function returning the next higher whole integer number.

Program Package: Customers who have previously acquired Software Advantage Upgrade Protection, and have not migrated to the Passport Advantage Offering as shown in the table below, will automatically receive their program upgrade package shortly after general availability.
                     Software Advantage
               Upgrade Protection Entitlement

MQSeries Workflow Program FlowMark Package Part Part Program Name/Description Number Number

Software Advantage Upgrade Entitlement IBM MQSeries Workflow 83H1979 09L8181 Version 3.1 FlowMark for AIX OTC 33H6991 09L8181 FlowMark for OS/2 OTC 33H6992 09L8181 FlowMark for AIX QPC 33H7178 09L8181 FlowMark for OS/2 QPC 33H7179 09L8181 FlowMark Servers OTC 50H0783 09L8181 FlowMark Servers QPC 50H0784 09L8181 FlowMark Clients OTC 77H8301 09L8181 FlowMark Clients QPC 77H8302 09L8181



TERMS AND CONDITIONS

Licensing: IBM International Program License Agreement. Proofs of Entitlement (PoE) are required for all authorized use.

Limited Warranty Applies: Yes

Program Services: Program services will be available until June 30, 2001. The statement of service included with the program describes this service.

Money-back Guarantee: 30-day, money-back guarantee for program packages

Copy and Use on Home/Portable Computer: Yes

Usage Restriction: Yes

Restricted Usage of MQSeries Version 5: IBM MQSeries Workflow Version 3.1 contains a copy of IBM MQSeries Version 5. You may use this program only in association with your licensed use of the MQSeries Workflow, to provide messaging for MQSeries Workflow. Any other use, specifically with custom messaging applications, is not permitted without a full separate MQSeries license. You may transfer the copy of IBM MQSeries Version 5 included with MQSeries Workflow, but only:

  • To a person who at the same time takes over the corresponding MQSeries Workflow materials from you, and accepts all these license terms; and

  • If you transfer all copies to such person, and do not retain any copies of such materials for your own or any other use.
Restricted Usage of DB2 Universal Database Version 5: IBM MQSeries Workflow Version 3.1 contains IBM DB2 Universal Database Version 5. You may use this program only in association with your licensed use of MQSeries Workflow, to provide the database management system (DBMS) for MQSeries Workflow. Any other use, specifically with custom database applications, is not permitted without a full separate DB2 Universal Database license. You may transfer the copy of IBM DB2 Universal Database Version 5 included with MQSeries Workflow, but only:
  • To a person who at the same time takes over the corresponding MQSeries Workflow materials from you, and accepts all these license terms; and

  • If you transfer all copies to such person, and do not retain any copies of such materials for your own or any other use.
Support Line: Personal Systems, AIX

Upgrades: Customers may acquire upgrades up to the currently authorized level of use of the qualifying programs.

Volume Orders: Yes. Contact your IBM representative.

Passport Advantage Applies: Yes

AIX/UNIX (R) Upgrade Protection Applies: No

Entitled Upgrade for Current AIX/UNIX Upgrade Protection Licensees: No

Variable Charges Apply: Yes

Educational Allowance Available: No



CHARGES

The charges provided in this announcement are suggested retail prices for the U.S. only and are provided for your information only. Dealer prices may vary, and prices may also vary by country. Prices are subject to change without notice. For additional information and current prices, contact your local IBM representative.

Part                                                 One-Time
Number         Program Name                          Charge

IBM MQSeries Workflow Version 3.1: 09L8161 Program Package $25,000 U.S. English

09L8192 1 Capacity Unit 7,000 with Certificate

09L8224 1 Registered User 600 with Certificate

09L8181 Program Package 12,500 U.S. English Upgrade from FlowMark V2.3

09L8208 1 Capacity Unit 3,500 with Certificate Upgrade from FlowMark V2.3

09L8240 1 Registered User 300 with Certificate Upgrade from FlowMark V2.3

Note: For additional Passport Advantage information, ordering information, and charges, contact your IBM representative or authorized reseller, or go to the URL:



CALL NOW TO ORDER

To order, contact the IBM North America Sales Centers, your local IBM representative, or your IBM Business Partner.

IBM North America Sales Centers, our national direct marketing organization, can add your name to the mailing list for catalogs of IBM products.

 Phone:     800-IBM-CALL (TM)
 Fax:       800-2IBM-FAX
 Internet:  ibm_direct@vnet.ibm.com
 Mail:      IBM North America Sales Centers
            Dept. YE010
            P.O. Box 2690
            Atlanta, GA  30301-2690
 Reference: YE010

To identify your local IBM Business Partner or IBM representative, call 800-IBM-4YOU.

Note: Shipments will begin after the planned availability date.

Trademarks

      RS/6000, SP, MQ, and 800-IBM-CALL are trademarks of
      International Business Machines Corporation in the United
      States or other countries or both.
      MQSeries, DB2 Universal Database, DB2, AIX, SP2, FlowMark,
      OS/2, VisualAge, and ThinkPad are registered trademarks of
      International Business Machines Corporation in the United
      States or other countries or both.
      Pentium is a trademark of Intel Corporation.
      Microsoft and Windows are trademarks of Microsoft Corporation.
      Windows NT is a registered trademark of Microsoft Corporation.
      UNIX is a registered trademark in the United States and other
      countries exclusively through X/Open Company Limited.
      Notes is a trademark of Lotus Development Corporation.
      Lotus Notes and Lotus are registered trademarks of Lotus
      Development Corporation.
      Other company, product, and service names may be trademarks or
      service marks of others.