Software Announcement 299-143
June 15, 1999

IBM MQSeries Workflow Version 3.2 Adds Support for e-business and New Platforms

 ENUS299-143.PDF (332KB)

(Corrected on August 20, 1999)

In the Ordering Information and Charges sections, part numbers and feature numbers were updated.

At a Glance

  • Enables you to leverage e-business with support for Java
  • Boosts performance with support for 3-tier, run-time environment
  • Provides high availability with HACMP
  • Includes a Process Monitor graphical user interface
  • Provides multiuser support for Buildtime
  • Improves installation and configuration
  • Supports two new server platforms:
    • HP 9000 workstations running HP-UX
    • Sun SPARC workstations running Solaris
  • Offers an emerging choice of Partner software

For ordering, contact:

Your IBM representative, an IBM Business Partner, or IBM Americas Call Centers at 800-IBM-CALL (Reference: YE001).

Overview

With IBM MQSeries® Workflow Version 3.2, you can implement workflow to manage all types of business processes and to achieve business integration. Organizations that have already introduced workflow, report the following benefits: improved quality, reduced cycle time, improved productivity, faster reaction on customer requests, increased efficiency.

New in Version 3.2:

e-business Support

IBM MQSeries Workflow Version 3.2 now supports workflow APIs in Java™ for seamless support of e-business. This support enables customers and Business Partners to create platform independent programs that interact with MQSeries Workflow.

In addition, MQSeries Workflow Version 3.2 also allows external partners to become part of the workflow. You may initiate workflow processes from the Internet and suppliers may participate on specific parts of the overall workflow process. Thus MQSeries Workflow Version 3.2 advances workflow to a new, e-business level.

Support for New Platforms

This new release adds two new server platforms, HP-UX running on HP 9000 and Sun Solaris running on Sun SPARC processors.

In addition, on the AIX® server platform, this new release supports high availability operation and exploitation of SMP and SP2® configurations.

Enhanced Scalability/Flexibility with 3-tier Structure

Now you can separate workflow database and workflow servers and run them on different machines. This provides you with improved performance, enhanced scalability, and enhanced flexibility.

Functional Improvements

MQSeries Workflow Version 3.2 also provides for a Process Monitor that graphically displays work status and activities, for multiuser modeling with the Buildtime environment, and for tighter interoperability between the MQSeries family members.

IBM delivers MQSeries Workflow in two different offerings:

  1. IBM MQSeries Workflow Version 3.2 includes the program code for all supported workstation operating environments with their prerequisite software in one single package.
  2. IBM MQSeries Workflow for OS/390® Version 3.2 is the server program that operates with OS/390.

Choice of Partner Software Available

IBM MQSeries Workflow Version 3.2 is the middleware that forms the underlying basis for partner offerings.

Key Prerequisites

IBM MQSeries Workflow Version 3.2 operates on:

  • OS/390, AIX, HP-UX, Sun Solaris, OS/2®, or Windows NT® for the servers
  • AIX, HP-UX, Sun Solaris, OS/2, Windows NT, or Windows™ 98/95 for the client APIs
  • Windows NT or Windows 98/95 for the GUI clients

Planned Availability Dates

  • IBM MQSeries Workflow Version 3.2.0 — June 30, 1999
  • IBM MQSeries Workflow Version 3.2.1 — September 30, 1999
  • IBM MQSeries Workflow for OS/390 Version 3.2.1 — December 10, 1999

Description

How Workflow Paves the Way to e-business

Most organizations are embracing the Internet to engage in new business opportunities and to provide their customers with unparalleled service. However, opening a simple, static Web site will not fulfil the high expectations of clients and Business Partners interested in conducting end-to-end business transactions via the Internet. Whether it is defined as e-commerce, Web marketplace, or e-business, an organization that wants to engage with her customers in this new environment needs to pay close attention to the business processes and the implementation of these business processes within the organization. It will no longer be acceptable that a credit card approval, claims handling, product or service order process takes days or weeks to complete. Workflow systems, especially IBM MQSeries Workflow Version 3.2, have demonstrated their ability to reduce cycle times and enable organizations to significantly increase their processing volumes without additional resources. IBM MQSeries Workflow Version 3.2 now paves the way to apply these proven benefits to the fast-paced world of e-business, where managing and automating business processes tightly integrated with existing business applications becomes a necessity.

In comparison to the traditional expectations set in most business transactions today, e-business is confronted with more ambitious requirements:

  • The demand for a given product or service is unpredictable and causes extreme fluctuation
  • Customers want response and processing times for standard business transactions to be instantaneous
  • If end-to-end processing times cannot be instantaneous, customers demand access to a meaningful processing status at any time, and
  • If necessary, customers are able to participate as an integral part of the business process, as the Internet makes it possible to provide "to-do items" and related information to the customer by electronic means.

All of these items require a new approach to the implementation of the organization's business processes, infrastructure and automation systems. To handle unexpected demand for a successful product or service, the automation systems need to provide a flexible, robust and highly scalable environment. The demand for short transaction times drives the need to link existing business applications together in a business process and manage the execution of these processes. An organization might consider implementing standard business processes in an automated fashion and to distribute unique transaction requests and exceptions for human processing. The workflow system needs to be able to manage fully automated processes, where existing and new business applications are linked together, as well as processes with manual intervention.

IBM MQSeries Workflow Version 3.2 provides all the functions necessary to implement and manage traditional and e-business processes. Regardless of the e-business environment chosen, the business processes to be automated need to be defined in a process model. This process model combines process steps, processing instructions, processing data, people and application resources, as well as the relationships between these entities. There are different forms to represent and document such process models, important members of the industry and IBM use Flow Definition Language (FDL).

IBM MQSeries Workflow Version 3.2 includes the Buildtime environment to generate a process model in FDL that is then loaded into the DB2® UDB runtime database. Through the use of MQSeries, MQSeries Integrator, Java and traditional API programming, it is possible to easily integrate existing and new applications into the workflow environment. As each step of the process is executed in the workflow system, work is dispatched to the appropriate resource. This resource can be a end user who is using one or more application system to process the work, or a fully automated access to application systems that perform the required function in the process. However, it is important to note that IBM MQSeries Workflow Version 3.2 connects the application and human resources between the process steps by transporting the relevant data from step to step and invoking the right application.

IBM MQSeries Workflow Version 3.2 can include resources on the Internet or an intranet through the use of its Java/CORBA interfaces. These interfaces can be deployed as a distributed Java model (applets) or by providing an ultra-thin client that renders HTML using servlet technology. As each process is executed, its status data is written to the audit trail table in the runtime database. The audit trail data provides the basis for monitoring the workflow system and providing real-time status about each running process. Implementing IBM MQSeries Workflow Version 3.2 on top of MQSeries, the market-leading messaging product, and on DB2 Universal Database®, the proven database, provides a robust workflow environment.

In summary, the technology of IBM MQSeries Workflow Version 3.2 allows organizations to speed up their activities by applying an infrastructure that is optimized with process engineering methodology. In addition, instead of adapting applications towards new requirements, it serves as a faster, more pragmatic approach to integrate existing applications for reuse with newly written applications, therefore, building an integrated IT infrastructure incorporating in-house computer resources and the Internet. IBM MQSeries Workflow Version 3.2 is a vital tool to create an organizational environment that is ready for e-business.

New in Version 3.2.0 (Available June 30, 1999)

Supports Java APIs: In addition to C or C++, the application programming interfaces (API) now support Java. This enables customers and Business Partners to connect Java-based applications and their users to MQSeries Workflow servers, to start processes, and act upon assigned work activities. Programmers can now use the same programming language to develop applications for the Internet and for workflow solutions.

The new Java APIs enable customers and Business Partners to create platform independent programs that interact with MQSeries Workflow. On the workstations only, the exploitation of CORBA technology allows you to imbed workflow within a CORBA infrastructure — thus further enhancing workload balancing and scalability of the overall system by using the features of the Object Request Broker (ORB).

To provide servlets and Java server pages, you can use the Java APIs together with IBM Websphere, so IBM MQSeries Workflow Version 3.2 customers have efficient means for the interaction of employees, customers, partners, and suppliers. In this scenario the end users just work with a thin client (Web browser) and are connected to the Web server via intranet or Internet.

e-business at work: IBM MQSeries Workflow Version 3.2 also allows external partners to become part of the workflow. Customers may initiate workflow processes from the Internet and suppliers may participate on specific parts of the overall workflow process. Thus, IBM MQSeries Workflow Version 3.2 advances workflow to a new, "e-business" level.

Supports 3-Tier Structure: IBM MQSeries Workflow Version 3.2 now allows you to implement a middle tier consisting of virtually any number of runtime servers that all connect to one single, centrally administered DB2 UDB database server on a separate tier (database tier). All these MQSeries Workflow runtime servers together with their associated database server comprise a "System Group" which can be geographically distributed. A System Group must be homogeneous — that is runtime servers and database servers must run the same operating system.

With these three tiers, you receive enhanced flexibility in scaling and balancing workload.

Supports New Platforms: This new release adds two new operating systems, HP-UX running on HP 9000 and Sun Solaris running on Sun SPARC processors. These are available in the workstations program. The server's processor or machine capacity determines the number of capacity units necessary for charging.

The client level now also supports Windows 98.

Process Monitor GUI: This graphical user interface, which operates on Windows NT or Windows 98/95, displays status information graphically in a view similar to Buildtime. Various status icons symbolize process instances, activity states, and the assignment of work to people so they can track their processes. It allows you to view:

  • Monitoring on process level
  • Activity status of all process instances including staff-related info
  • The control flow through this process
  • Steps into definition of blocks and subprocesses

Buildtime: Buildtime offers multi-user support, that allows you to model and operate, to print and access the database in a network of several personal computers. Performance has been improved, and the Diagram Editor supports the clipboard and new print functions.

Improves Installation and Configuration: Because program installation has been separated from configuration, usability has increased significantly. Documentation has been restructured to give you instructions by platform. Configuration panels on the Windows and OS/2 platform, or a configuration utility on the UNIX® platforms allow you a more convenient selection of options and setup. Error recovery has been improved. Conditions of errors can be detected and handled easier.

Supports HACMP: In an AIX environment only, you can run MQSeries Workflow under high availability conditions to provide for maximum uptime. Different scenarios of availability are possible depending on the hardware and implementation efforts. With High Availability Cluster Multiprocessing (HACMP), a failure may typically cause a delay of a few minutes only for recovery and you continue at your last transaction.

MQSeries Workflow Version 3.2 has been enabled for HACMP. You need to define, install, and configure their high availability environment on an individual basis according to their specific needs. IBM provides sample scripts to adapt your whole operating environment in order to behave in a totally controlled manner.

IBM and Business Partners offer services to implement MQSeries Workflow solutions in a high availability environment.

Migration to This New Release: The following approaches can be used:

  • From FlowMark® Version 2.3:

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

    To work with IBM MQSeries Workflow Version 3.2, 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.2.

  • From MQSeries Workflow Version 3.1:

    Buildtime Data: the FDL file stored under V3.1 must be exported and — after having upgraded — imported into Version 3.2.

    Runtime Data: a migration tool accomplishes changing the database schema and binding of new packages under Version 3.2.

For customers who use FlowMark Version 2.3 or MQSeries Workflow Version 3.1 in production and want to migrate to this new MQSeries Workflow Version 3.2, IBM and Business Partners offer upgrade services for a fee.

Commitments Met

By making the following available, IBM has successfully met our commitments as announced under the Statement of Direction in Software Announcement 298-270 , dated July 28, 1998.

  • IBM MQSeries Workflow Version 3.2 on HP-UX and Sun Solaris as new server platforms under the existing offering
  • IBM MQSeries Workflow Version 3.2 on OS/390 as a separate product

New in Version 3.2.1

Supports XML and Family Interoperability (Available September 30, 1999): As a new, upcoming, universal standard for the exchange of documents and messages, MQSeries Workflow uses XML (eXtensible Markup Language) to implement a new interface that relies on messages. It adds the capability to exchange messages among the members of the MQSeries product family and related applications.

This new release improves the integration among the MQSeries product family in providing two interfaces:

  • Call in (communication: requester to MQSeries Workflow):

    An MQSeries message in XML format, sent from MQSeries Integrator or created from any application, triggers a workflow process, thus providing a message interface to the workflow engine.

  • Call out (communication: MQSeries Workflow to application):

    A workflow process issues an activity implementation as a message in XML format that is put into any MQSeries queue.

A message in XML syntax allows you to address any application listening on an MQSeries queue, both synchronously (application has to return a completion message) and asynchronously ("fire and forget"). The queue can be input to MQSeries Integrator (facilitating message transformation) or any other MQSeries application. Thus, XML serves as a means for external program integration and "family interoperability".

Integrates S/390® Systems: Based on the workstation development, IBM ports and makes available IBM MQSeries Workflow Version 3.2.1 functionality on the OS/390 platform (Version 3.2.0 is not ported to OS/390).

As a native MQSeries Workflow implementation on OS/390, it exploits OS/390 features such as high availability, scalability, automatic workload balancing, transaction update integrity, and security through genuine OS/390 functions like workload manager (WLM), resource recovery support (RRS), and RACF®. With its "Program Execution Server" (PES), MQSeries Workflow offers plug-in support for existing business critical CICS® and IMS™ transactions.

New in this Version 3.2.1 available on December 10, 1999, IBM provides APIs in C++ and Java, XML and family interoperability, and support of 3-tier structure. Now, you can separate database and runtime servers and connect them in an S/390 Sysplex which makes up a System Group of homogeneous systems.

IBM MQSeries Workflow for OS/390 Version 3.2.1 includes a complete program package of MQSeries Workflow Version 3.2.1 — the workstations offering — to provide you with licenses of Buildtime and one Registered User. However, prerequisite software specific for the OS/390 environment, must be ordered and payed separately.

Charges, terms, and conditions remain the same as announced in Software Announcement 299-008 , dated January 26, 1999.

Supported Platforms

.-------------+------+---+-----+-------+----+-------+-------.
|             |OS/390|AIX|HP-UX|Solaris|OS/2|Windows|Windows|
|             |      |   |     |+SPARC |    |NT     |98/95  |
|-------------+------+---+-----+-------+----+-------+-------|
|Buildtime    |      |   |     |       |    |x      |x      |
|-------------+------+---+-----+-------+----+-------+-------|
|Runtime      |x     |x  |x    |x      |x   |x      |       |
| Server      |      |   |     |       |    |       |       |
|-------------+------+---+-----+-------+----+-------+-------|
|Prog. Exec.  |x     |   |     |       |    |       |       |
| Server      |      |   |     |       |    |       |       |
|-------------+------+---+-----+-------+----+-------+-------|
|Prog. Exec.  |      |x  |x    |x      |x   |x      |x      |
| Agent       |      |   |     |       |    |       |       |
|-------------+------+---+-----+-------+----+-------+-------|
|Client GUI   |      |   |     |       |    |x      |x      |
|-------------+------+---+-----+-------+----+-------+-------|
|Client API   |x     |x  |x    |x      |x   |x      |x      |
|-------------+------+---+-----+-------+----+-------+-------|
|Admin Utility|      |x  |x    |x      |x   |x      |x      |
|-------------+------+---+-----+-------+----+-------+-------|
|Lotus        |      |   |     |       |x   |x      |x      |
| Notes(R) GUI|      |   |     |       |    |       |       |
|-------------+------+---+-----+-------+----+-------+-------|
|Lotus Notes  |      |   |     |       |x   |x      |x      |
| API         |      |   |     |       |    |       |       |
'-------------+------+---+-----+-------+----+-------+-------'

Year 2000

These products are Year 2000 ready. When used in accordance with their associated documentation, they are capable of correctly processing, providing, and/or receiving date data within and between the twentieth and twenty-first centuries, provided that all products (for example, hardware, software, and firmware) used with the products properly exchange accurate date data with them.

The service end date for these Year 2000 ready products is June 30, 2002.

Euro Currency

These programs are EuroReady.

For more information on the implications of the euro, visit the IBM euro Web site at:

EuroReady Products: IBM considers an IBM product to be EuroReady if the product, when used in accordance with its associated documentation, is capable of correctly processing monetary data in the euro denomination and of respecting the euro currency formatting conventions (including the euro sign). This assumes that all other products (that is, hardware, software, firmware etc.) that are used with this product are also EuroReady. IBM hardware products that are EuroReady may or may not have an engraved euro sign key on their keyboards.

Currently, EuroReady status applies primarily to IBM products specific to the EMU countries. Products that are not specific to these countries are deemed to be "not ready" for euro unless otherwise stated in the product's country-specific specifications.

IBM Hardware Ready: IBM supplies certain IBM products which include third party software (pre-loaded or not) and / or third party attached hardware. In these instances IBM is not in a position to assert that these third party products are, in themselves, EuroReady.

Therefore such IBM products will be designated as Hardware Ready.

EuroReady Solutions: IBM considers a solution to be EuroReady when the solution providers have:

  • Analysed the euro requirements, including the need to comply with relevant EC rules
  • Built in appropriate function

and can clearly demonstrate this by:

  • Detailing euro related requirements
  • Describing how these will be implemented in the solution
  • Declaring when the implementation will be generally available

The euro capabilities of a EuroReady solution will be clearly identified as features of the Solution specification as described in the contracts document.

Product Positioning

IBM MQSeries Family of Products for Business Integration

On May 5, 1998, IBM has announced Business Integration that 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.
  • IBM MQSeries Workflow for workflow automation between applications, and applications and people.

MQSeries Integrator intercepts MQ™ messages, transforming and routing the message contents based on information stored in a rules database.

Because an MQSeries message serves as the overall connection for communication among applications and the MQSeries family members, an appropriate customer application can interact with an MQSeries Workflow process:

  • A customer application can create and start an MQSeries Workflow process. The relevant process and input data can be sent as an MQSeries message to the MQSeries Workflow server to start the execution of a predefined MQSeries Workflow process.
  • A predefined MQSeries Workflow process can trigger a customer application that is executed within the process flow. The customer application can exchange its input and output data (via put/get command) with the MQSeries Workflow process.

The MQSeries message interface also facilitates the intercommunication among all platforms where MQSeries Version 5 is supported.

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.

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 Web sites:

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.

Lotus® Workflow

On April 13, 1999, Lotus announced the acquisition of ONEstone Holding, Inc. and its workflow software technologies to enhance the ability of Lotus' customers to develop productivity-boosting workflow applications. ONEstone's primary product is Prozessware, a workflow management system that provides businesses with the means to change from paper-based processes to electronically controlled workflow.

Lotus plans, with the help of the development teams at both companies, to offer workflow software that extends Domino™ object services and design tools and makes it possible for customers and Business Partners to implement solutions that make organizations more responsive, productive, innovative and competent. This was in response to Lotus customer needs who are looking for ways to enhance their ability to develop and manage applications that contain workflow functions, and they want this capability to be an extension of their existing Domino infrastructure.

Both, ONEstone's Prozessware and IBM MQSeries Workflow are offerings that help customers to model and automate business processes.

  • ONEstone's product leverages the Domino infrastructure so customers will be able to use rules and roles based workflow as part of their knowledge management efforts.
  • MQSeries Workflow helps integrate and automate application-to-application process flow and business processes to improve corporate effectiveness. It leverages messaging queuing middleware as part of the MQSeries family for Business Integration across heterogeneous systems, exploiting and extending MQSeries and MQSeries Integrator.

While ONEstone's product is more document intensive, MQSeries Workflow is more transaction intensive and focuses more on integrating heterogeneous systems.

Both products complement each other well. IBM and Lotus continue to work together to support both solutions.

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® VisualInfo™, via workflow process models into the overall business solution.

Document management products, such as IBM ImagePlus VisualInfo, limit their built-in, internal workflow to document routing functions, such as assigning documents to work baskets. MQSeries Workflow can be used together with ImagePlus VisualInfo to gain more document processing capabilities such as automating the workflow of viewing and annotating documents, check in, check out, and e-mail notifications.

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. MQSeries Workflow has the flexibility to tie these products together in an automated 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:

Trademarks

 
IMS, MQ, and VisualInfo are trademarks of International Business Machines Corporation in the United States or other countries or both.
 
MQSeries, AIX, SP2, OS/390, OS/2, DB2, DB2 Universal Database, FlowMark, S/390, RACF, CICS, and ImagePlus are registered trademarks of International Business Machines Corporation in the United States or other countries or both.
 
Windows is a trademark of Microsoft Corporation.
 
Windows NT is a registered trademark of Microsoft Corporation.
 
Java is a trademark of Sun Microsystems, Inc.
 
UNIX is a registered trademark in the United States and other countries exclusively through X/Open Company Limited.
 
Domino 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.

Partner Software

Business Partners as well as complementary products are emerging around MQSeries® Workflow. The following lists some of the choices. BOC Ltd. offers the Business Process Management Tool ADONIS to model business work flows. It was specifically developed to meet the business modeling needs of service organizations. It includes the components Information Acquisition, Modeling, Analysis, Simulation, Evaluation, Import/Export, Transformation, Document Generation, and Process Costing.

Closely integrated with MQSeries Workflow, ADONIS provides a method library featuring LOVEM™ (Line of Visibility Enterprise Modeling), the people-oriented design methodology propagated by IBM, among other methods. In addition ADONIS offers functionality for analyzing MQSeries Workflow audit trails. ADONIS is available for Windows™ 95/98/NT and OS/2® Warp. It supports a number of relational databases including DB2® UDB. It is available in various languages including English, German, and Spanish.

BOC headquartered in Vienna, Austria, with international sales offices in all major geographies. BOC markets ADONIS worldwide and also provides a wide range of consulting services for the different applications of ADONIS. For more information, visit the following Web site:

or contact this e-mail address:


    boc@boc-eu.com
Holosofx develops and offers the Enterprise Process Management Suite designed for executives and managers to monitor, document, and manage enterprise business processes. The Suite includes these components for business process reengineering (BPR):
  • Workflow BPR Modeler to model business processes and analyze their performance
  • Workflow BPR Builder to generate workflow models and programming code for modeling and programming workflow solutions
  • Workflow Monitor to display real-time data of the workflow while business processes are in progress
  • Business Monitor to generate real-time reports about workflow performance and to publish it via the Internet

Holosofx was founded in 1989 and has its headquarter in EL Segundo, California, USA; selling via worldwide resellers.

For more information, visit the following Web site:

M&M Systemberatung Germany provides system integration services for MQSeries Workflow and integration for Microsoft™ Outlook or Exchange with MQSeries Workflow.

M&M Systemberatung GmbH is headquartered in Boeblingen, Germany. For more information, visit Web site:

or send an e-mail to:


    mm@mm.systemberatung.de
JMAC Inc. offers the full range of education courses for MQSeries Workflow: basic use of the Buildtime and Runtime interfaces, API programming, training for users working with runtime only. All courses can be customized. All platforms and industries are supported.

JMAC has its headquarter in Neshanic Station, New Jersey, USA. For more information, visit the following Web site:

or contact e-mail:


    jmac@mail.inet-images.com
MQSoftware develops and offers the client/server tool Q Pasa! to administer, configure, and monitor MQSeries Workflow. All kinds of workflow education are also offered.

MQSoftware, Inc. headquartered in Minnesota, Minneapolis/U.S.A, with international sales offices in all major geographies, provides software, consulting, implementation, installation, and training solutions for the IBM MQSeries middleware brand family. For more information, visit the following Web site:

SerCon offers a complete spectrum of IT services ranging from strategy consultation to implementation, maintenance, and training. As a System integrator SerCon optimizes business processes, creates suitable IT infrastructures, integrates and perfects application solutions in all kinds of industries.

SerCon is a leading German IT services company with about 1.600 employees with office locations in all major German business centers. SYSCOM provides system integration services for Document Management and Workflow Solutions, supported platforms are Windows NT®/95, OS/2, AS/400®, S/390®, AIX®, and other Unix based operating systems.

SYSCOM offers business process reengineering, project management, modeling, installation for MQSeries Workflow, development and integration with MQSeries, DB2, and customer applications; special skills and experiences in finance, telecommunications, health, manufacturing, and training management.

SYSCOM, Inc. is headquartered in Baltimore, Maryland USA, for more information, visit the following Web site:

or send an e-mail to Mrs. Vickie Wysokinski,


    vwysokinski@syscom-inc.com

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 Solution Providers and System Integrators (SIs). For example, IBM will work with these partners to make available 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 Competency Centers, work jointly with Business Partners to provide all kinds of services to satisfy the MQSeries Workflow customers.

SupportPacs

IBM makes available, for a fee, this new category of add-on programs sourced worldwide by IBM software engineers active in support of the field.

MQSeries Workflow — Event Handler API: Provides a generic event handling capability. This is useful when a process has to wait for an external event (for example a customer letter) or a delay.

MQSeries Workflow — Batch Client: Enables processing of automatic activities in an unattended way.

For detailed information about SupportPacs, visit the following Web site:

Workflow Competency Center Services

These centers provide you additional, customizable offerings for a fee:

Solutions Assurance: Validates all product components and services against customer's expectations.

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® and MQSeries Workflow Release 1 to this new Release 2:

  • Buildtime process models
  • Runtime-data process instances
  • Customer application migration

Generic API Test and Prototyping Tools: Test and tune MQSeries Workflow applications, and evaluate their behavior. When writing application programs for APIs in C, Java™, ActiveX, and VisualBasic, these tools provide instant feedback, and help developers in testing and training. The prototyping facility allows for rapid definition of API scenarios, load simulation on servers and clients, and easy performance measurements. These tools are 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 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)

Proof of Concept: Serves as a commitment between new customers or prospects and IBM to support a statement of work. In most cases it includes a proposal to implement a workflow solution that solves the customer's business needs. The typical duration will range from 2-4 weeks. The customer and IBM will jointly define the requirements. Both sides provide the resources to ensure success. If the customer regards the concept successful, the customer agrees to compensate IBM and the solution will be implemented; if not, the customer has no obligation to pay.

High Availability Cluster Multi-Processing: Maximizes system availability ("uptime").

The services provide:

  • Customization
  • Configuration
  • Installation
  • Tuning
  • Testing

Education Support

IBM Learning Services, selected Business Partners and authorized Training Partners offer public, scheduled classes comprising of basic concepts and hands-on training about all aspects of MQSeries Workflow. A modular curriculum features modeling, installation, administration, API programming for different categories (container APIs, worklist handler APIs), and languages (ActiveX, Java).

Ask your IBM representative or Business Partner for details and enrollment. Visit these Web sites for information:

To focus your individual education needs, customized classes can be arranged, send your request to:

    workflow@de.ibm.com

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

Publications

Workstations Program

The following publications (in U.S. English) are the genuine MQSeries Workflow documentation that is included in the workstations program package SBCS (part number 22L4429), in the S/390 program package (5655-A96), and in the Passport Advantage Documentation Package (part number 0772168). The hardcopy publications can also be ordered separately after June 30, 1999:

IBM MQSeries Workflow Version 3.2:
 
Form           Part
Number         Number   Title
 
GH12-6285      22L4280  Concepts and Architecture
                         (introduction)
SH12-6286      22L4281  Getting Started with Buildtime
SH12-6287      22L4282  Getting Started with Runtime
SH12-6288      22L4283  Installation Guide
SH12-6289      22L4284  Administration Guide
SH12-6291      22L4285  Programming Guide
GH12-6357      CT8BCML  List of Workstation Server
                         Processor Groups

To order, contact your IBM representative or Business Partner.

OS/390® Program 5655-A96

Publication will be updated to reflect the enhancements made for Version 3 Release 2.

IBM MQSeries Workflow for OS/390 Version 3.2:
 
Form
Number         Title
 
GI10-0483      Program Directory
SC33-7030      Customization and Administration
SC33-7031      Programming
SC33-7032      Messages and Codes

Displayable Softcopy Publications: These publications are part of the basic machine-readable material and can be displayed with an HTML browser or with Adobe Acrobat Reader, respectively. The publications 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

Hardware Requirements

Buildtime

  • A personal computer with Intel-based processor architecture is required (for example, Pentium™ 200 MHz).
  • Screen: Resolution 1024x768 (recommended), 432 mm (17'), measured diagonally, or larger.
  • Microsoft Windows NT Workstation V4.0 (Service Pack 4 required) or Windows 98, for Windows 95, Service Pack 1 or OSR2 is required.
  • Buildtime database: IBM DB2 Universal Database® 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.2).

               **** DB2 UDB ****       *** JetEngine ***
Operating      Main        Hard        Main        Hard
Environment    Memory      Disk        Memory      Disk
 
Windows 98/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 DB2 data and log files (table spaces) 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

  • An RS/6000™ uni-processor, SMP, or SP2® machine as supported by AIX is required. For a list of IBM machines, visit the following Web site:
  • 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
  • Operating System: AIX Version 4.2 or higher
  • IBM MQSeries for AIX Version 5 (included). Installation of MQSeries CSD 05 is required. For MQSeries CSDs, visit the following Web site:
  • IBM DB2 Universal Database for AIX Version 5 (included).
  • In a high availability environment:
    • AIX V4.3.1 with HACMP V4.2.2, or
    • AIX V4.3.2 with either HACMP V4.2.2 or HACMP V4.3

Clients for AIX: A workstation capable of running the operating system.

  • Operating System: AIX Version 4.2 or higher
  • IBM MQSeries for AIX Version 5 client (included). Installation of MQSeries CSD 05 is required. For MQSeries CSDs, visit the Web site:
  • 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 2.3 compatibility workflow client API for C++).
    • IBM C for AIX Version 3.0 (FlowMark 2.3 compatibility C language API).
    • JDK 1.1.6 or 1.1.7

Servers for HP-UX

  • An HP 9000 workstation is required.
  • Screen: A dedicated graphical display is not necessary. The system console is sufficient.

Operating      Main           Hard
Environment    Memory         Disk
 
HP 9000        256 MB         4 GB
  • Operating System: HP-UX Version 10.20
  • IBM MQSeries for AIX Version 5 (included). Installation of MQSeries CSD 05 is required. For MQSeries, visit the following Web site:
  • IBM DB2 Universal Database for HP-UX Version 5 (included).

Clients for HP-UX: A workstation capable of running the operating system.

  • Operating System: HP-UX Version 10.20 Installation of MQSeries CSD 05 is required. For MQSeries, visit the following Web site:
  • For the development of programs using the MQSeries Workflow APIs:
    • HP C/ANSI C Developer's Bundle for HP-UX V10.20 (S700)
    • JDK 1.1.6 or 1.1.7

Servers for Sun Solaris

  • A Sun workstation with SPARC processor architecture is required.
  • Screen: A dedicated graphical display is not necessary. The system console is sufficient.

Operating      Main           Hard
Environment    Memory         Disk
 
Sun SPARC      256 MB         4 GB
  • Operating System: Sun Solaris Version 7
  • IBM MQSeries for Sun Solaris Version 5.1 (included). (Deletion)
  • IBM DB2 Universal Database for Sun Solaris Version 5 (included).

Clients for Sun Solaris: A workstation capable of running the operating system.

  • Operating System: Sun Solaris Version 7
  • IBM MQSeries for Sun Solaris Version 5.1 client (included)
  • For the development of programs using the MQSeries Workflow APIs:
    • Workshop Professional C/SPARC Version 3.0
    • JDK 1.1.6 or 1.1.7

Servers for OS/2

  • A personal computer supported by OS/2 with Intel-based processor architecture, for example Pentium 200 MHz, is required.

Operating      Main           Hard
Environment    Memory         Disk
 
OS/2 Warp      128 MB         2 GB
 Server V4
OS/2 Warp V4   128 MB         2 GB
  • Operating System: OS/2 Warp V4 or Warp Server V4
  • IBM MQSeries for OS/2 Version 5 (included). Installation of MQSeries CSD 05 is required. For MQSeries CSDs, visit the Web site:
  • DB2 Universal Database Enterprise Edition for OS/2 Version 5 (included).

Clients for OS/2: 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 05 is required. For MQSeries CSDs, visit the Web site:
  • For the development of programs using the MQSeries Workflow APIs, one of:
    • IBM VisualAge® 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:
    • 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® or portable personal computer is acceptable.

Operating      Main           Hard
Environment    Memory         Disk
 
Windows NT     128 MB         2 GB
  • Operating System: Microsoft Windows NT Workstation or Server V4.0; Service Pack 4 is required.
  • IBM MQSeries for Windows NT Version 5 (included). Installation of MQSeries CSD 05 is required. For MQSeries CSDs, visit the Web site:
  • IBM DB2 Universal Database Enterprise Edition Version 5 (included).

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 4 is required.
  • IBM MQSeries for Windows NT Version 5 client (included). Installation of MQSeries CSD 05 is required. For MQSeries CSDs, visit the Web site:
  • 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).
    • JDK 1.1.6 or 1.1.7
  • For the development of programs using the MQSeries Workflow ActiveX Controls:
    • Microsoft VisualBasic Version 5.0.
  • For the MQSeries Workflow client for Lotus Notes:
    • Lotus Notes Release 4.5.
  • For an MQSeries Workflow standard client, no additional prerequisites are required.

Clients for Windows 98 or Windows 95: A personal computer capable of running the operating system and 48 MB of main memory are recommended.

  • Operating System: Microsoft Windows 98; for Windows 95 Service Pack 1 or OEM Service Release 2 is required.
  • IBM MQSeries for Windows 98 or Windows 95 Version 5 client (included). Installation of MQSeries CSD 05 is required. For MQSeries CSDs, visit the Web site:
  • 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:
    • Microsoft VisualBasic Version 5.0.
  • For the MQSeries Workflow client for Lotus Notes:
    • Lotus Notes Release 4.5.
  • For an MQSeries Workflow standard client, no additional prerequisites are required.

Required MQSeries V5 Releases: The table lists the required MQSeries V5 Releases that are included in the program package, and their availability:

                     * * * * Available at * * * *
                  June 30, 1999  September 30, 1999
Operating System  V3.2.0         V3.2.1
 
AIX               5.0            5.1
HP-UX             5.0            5.1
Solaris           5.1            5.1
OS/2              5.0            5.1
Windows NT        5.0            5.1
Windows 98/95     5.0            5.1

OS/390 Program 5655-A96

Servers for OS/390: An S/390 hardware system

Operating System:

  • OS/390 Version 2.6
  • MQSeries Version 2.1
  • MQSeries Version 2.1 Client Attachment Feature (JMQ2107 deleted)
  • DB2 Universal Database for OS/390 Enterprise Edition Version 6

For the development of programs using the Workflow APIs and running on the OS/390 operating system, one of:

  • IBM COBOL for OS/390 & VM Version 2.1
  • IBM C for OS/390 Version 2.4
  • IBM C++ for OS/390 Version 2.6
  • JDK Version 1.1.6 or higher

To use the non-transactional EXCI

  • CICS Transaction Server for OS/390 Version 1.2 or CICS/ESA® Version 4
  • The CICS® interregion communication program DFHIRP

To use the transactional EXCI (for safe applications)

  • CICS Transaction Server for OS/390 Version 1.3
  • The CICS interregion communication program DFHIRP

To use the CPIC

  • IMS™ Version 5.1 or later
  • IMS Version 6 or later, if you want to support safe applications

Software Requirements

Compatibility: Process models created under FlowMark Version 2.3 can be imported to IBM MQSeries Workflow Version 3.2.

Applications developed under FlowMark Version 2.3 can be recompiled and relinked as long as IBM MQSeries Workflow Version 3.2 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 Solution Assurance review with a Workflow Competency Center expert.

Performance Considerations: The performance of IBM MQSeries Workflow Version 3.2 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 Solutions Assurance review of your specific implementation of IBM MQSeries Workflow Version 3.2.

Planning Information

Installation and Maintenance: On all workstations platforms, you can install IBM MQSeries Workflow Version 3.2 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.2)
  • IPX
  • NetBios
  • SNA LU6.2
For the actual status visit the Web sites:

Customer Responsibilities: The customer is responsible to:

  • Assign a systems administrator knowledgeable in MQ™ and DB2 UDB who has responsibility for planning, installing, maintaining, and administering an IBM MQSeries Workflow Version 3.2 installation in production.
  • Implement the management procedures for an effective operation.
  • Provide sufficient hardware resources if IBM MQSeries Workflow Version 3.2 is used in production.

Ask IBM or Business Partners to obtain assistance with customizable services offerings.

Licensing and Pricing Definition: IBM MQSeries Workflow implements a scalable and versatile pricing structure to reflect runtime 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).

As a client/server program, licensing and charging apply differently to the server and client level.

Processor-based Charges

  • The charge for runtime servers and databases depends on the capacity and quantity of processors or machines. These are assigned to tiers associated with a certain number of Capacity Units (CUs). The higher the tier and the greater the number of processors or machines, the more CUs are required. The customer must purchase CU Authorizations to use runtime 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 for the customer to be authorized to use MQSeries Workflow runtime servers or databases on processors or machines that represent a greater number of CUs.

MQSeries Workflow Workstation Server Processor Groups

.--------+----+-----------------------------------------------.
|        | CU*|Processors/Machines                            |
|--------+----+-----------------------------------------------|
| Entry  |  2 | Uniprocessor machines                         |
|--------+----+-----------------------------------------------|
|        |  4 | 2-way SMP machines, or                        |
|        |    | 1-2 processors per box/node                   |
|        +----+-----------------------------------------------|
|        |  6 | 3-4 processors per box/node                   |
|        +----+-----------------------------------------------|
|Midrange| 10 | 5-8 processors per box/node                   |
|        +----+-----------------------------------------------|
|        | 14 | 9-16 processors per box/node                  |
|        +----+-----------------------------------------------|
|        | 16 | 17-24 processors per box/node                 |
|--------+----+-----------------------------------------------|
|High End| 30 | >24 processors per box/node                   |
'--------+----+-----------------------------------------------'
*
Capacity Units required

A CU has no direct relationship to machine capability; it is a charging-authorization term only. Additional CUs are required as you increase the number of processors. This list is not exhaustive and does not attempt to cover the many processors or machines currently available. Many of the machines listed will have fewer processors than their maximum supportable. The CU authorizations will need to be updated as new CPUs are added to existing machines.

Registered Users

  • 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, and transfer) in a runtime environment.

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 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 a machine with four processors. There are 400 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 server machine.

  • Intranet Example

    A company has installed one MQSeries Workflow server on an SMP machine. 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). 200 employees participate at 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 CUs for the SMP 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 uniprocessor machines. 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 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 uniprocessor machines (in total eight CUs for all machines). There is no need to purchase any Registered User authorization for the customers working via the Internet as these customers do not work with work items, but just start processes.

Installability

Sun Solaris for SPARC: requires MQSeries Version  5.1 that is part of the program package. Other Workstations require MQSeries Version 5.0 or higher.

Before you can install IBM MQSeries Workflow Version 3.2, you must install MQSeries Version 5 and DB2 Universal Database Version 5. The program code for both is available from the MQSeries Workflow program package. To prepare for their smooth installation, you should have handy the installation instructions or the latest release of the installation manuals in respect to the intended platform.

Packaging

Program Package on Workstations: Whereas IBM MQSeries Version 5 offers multiple program packages, MQSeries Workflow consists of only one program package that supports all enabled platforms. IBM MQSeries Workflow Version 3.2 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
  • Six MQSeries Workflow Version 3.2 manuals:
    • Concepts and Architecture
    • Getting Started with Buildtime
    • Getting Started with Runtime
    • Installation Guide
    • Administration Guide
    • Programming Guide
  • List of Workstation Server Processor Groups
  • Service Statement
  • License Information
  • Customer Registration Card
  • Two CD-ROMs containing the IBM MQSeries Workflow Version 3.2 program code for all national language versions supported
  • One CD-ROM containing the IBM MQSeries Workflow Version 3.2 softcopy documentation for all national language versions supported
  • Seven CD-ROMs containing the IBM MQSeries Version 5 program code
  • Eleven CD-ROMs containing the IBM DB2 Universal Database Version 5 program code

Program Package on OS/390 (5655-A96): IBM MQSeries Workflow for OS/390 is available as one program package, containing all product components. The program package includes:

  • IBM MQSeries Workflow for OS/390 Server program code on tape, or cartridge, or 4-mm DAT
  • A complete workstations program package of IBM MQSeries Workflow Version 3.2 as specified above

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 compatibility.
    • The MQSeries Workflow client for Lotus Notes supports user authentication via Notes™ 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 to MQSeries Workflow resources, such as processes, and to administer the system.
  • Auditing is provided via operating system security logs and 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

OS/390 Program 5655-A96

New Customers: Orders for new licenses of Version 3 Release 2 will be accepted now. If the customer-requested arrival date is prior to availability of this new Release 2, Release 1 will be shipped. Shipment will begin on the planned availability date.

To order the workflow servers on OS/390, specify program number 5655-A96 and the appropriate PSLC feature number.

The appropriate number of clients must be ordered as Registered Users by part number under the workstations program (see below).

Existing Customers: Customers licensed for IBM MQSeries Workflow for OS/390 will receive the new release automatically. Charges, terms, and conditions remain unchanged as already announced under Version 3 Release 1.

Workstations Program

To order, specify the program package part number and the appropriate number of capacity units and registered users concerning your runtime environment.

All charges are one-time charges. The program package carries a fixed price. In addition there are two variable charge units that apply to your runtime environment:

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

Two capacity units and one registered user that are purchased with the program package or Passport Advantage entitle you for a free number of Buildtime users.

The following options apply for a customer who is licensed for a previous release of IBM MQSeries Workflow (workstation program) or FlowMark:

  • Having purchased a license without Passport Advantage Subscription, the customer is not entitled for free upgrades; if they want to obtain this new Release 2, the customer must place a new order with regular charges.
  • Having purchased a license with Passport Advantage Subscription, the customer will automatically receive this Release 2, or any new version, release, or modification level upon its general availability.

IBM MQSeries Workflow Version 3.2:
 
Order Type    Feature   Part
Number        Number    Number    Program Name
 
5801-AAR      5790      22L4429   - Program Package
                                     (SBCS)
5807-AAR      1440      0780184   - 1 Capacity-Unit
5807-AAR      1441      0780185   - 1 Registered User

Program Number          Program Name
 
5655-A96                IBM MQSeries Workflow
                         for OS/390 Version 3.2.1

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 Name/              FlowMark       Media Package
Description                Part Numbers   Part Number
 
IBM MQSeries Workflow
 Version 3.2
IBM MQSeries Workflow      D182SML        35L4331
 Version 3.1
FlowMark for AIX OTC       33H6991        35L4331
FlowMark for OS/2 OTC      33H6992        35L4331
FlowMark for AIX QPC       33H7178        35L4331
FlowMark for OS/2 QPC      33H7179        35L4331
FlowMark servers OTC       50H0783        35L4331
FlowMark servers QPC       50H0784        35L4331
FlowMark clients OTC       77H8301        35L4331
FlowMark clients QPC       77H8302        35L4331

Terms and Conditions

Licensing

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

OS/390 Program (5655-A96): IBM Customer Agreement (ICA)

License Information Form Number: GI19-0003

Limited Warranty Applies: Yes

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

Central services for IBM MQSeries Workflow for OS/390 Version 3.2 will be available until discontinued by IBM upon six months written notice.

Money-back Guarantee: Two-month, money-back guarantee

Copy and Use on Home/Portable Computer: No

Usage Restriction: Yes

Restricted Usage of MQSeries Version 5: IBM MQSeries Workflow Version 3.2 contains a copy of IBM MQSeries Version 5 which you are only authorized to use 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 all 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.2 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: Yes

Volume Orders: Yes, contact your IBM representative

Passport Advantage Applies: Yes

Passport Advantage Subscription Applies: Yes

AIX/UNIX® Upgrade Protection Applies: No

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

AS/400 Software Subscription Applies: No

Variable Charges Apply: 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.

IBM MQSeries Workflow Version 3.2:
 
Part                          One-Time
Number      Program Name      Charge
 
22L4429     Program Package   $15,200
             U.S.  English
 
0780184     1 Capacity Unit     7,000
             with Certificate
 
0780185     1 Registered User     600
             with Certificate

Passport Advantage

Note: For Passport Advantage ordering information and charges, contact your IBM Lotus® representative or authorized IBM Lotus Business Partner. Additional information is also available on the Passport Advantage URL:

Customer Financing: IBM Global Financing offers attractive financing to credit-qualified commercial and government customers and Business Partners in more than 40 countries around the world. IBM Global Financing is provided by the IBM Credit Corporation in the United States. Offerings, rates, terms and availability may vary by country. Contact your local IBM Global Financing organization. Country organizations are listed on the Web at:

Call Now to Order

To order, contact the IBM Americas Call Centers, your local IBM representative, or your IBM Business Partner.

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

 Phone:     800-IBM-CALL
 Fax:       800-2IBM-FAX
 Internet:  ibm_direct@vnet.ibm.com
 Mail:      IBM Americas Call Centers
            Dept. YE001
            P.O. Box 2690
            Atlanta, GA  30301-2690
 Reference: YE001

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

Note: Shipments will begin after the planned availability date.

Trademarks

 
LOVEM, RS/6000, IMS, and MQ are trademarks of International Business Machines Corporation in the United States or other countries or both.
 
MQSeries, OS/2, DB2, AIX, AS/400, S/390, FlowMark, OS/390, DB2 Universal Database, SP2, VisualAge, ThinkPad, CICS/ESA, and CICS are registered trademarks of International Business Machines Corporation in the United States or other countries or both.
 
Pentium is a trademark of Intel Corporation.
 
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.
 
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.