IBM WebSphere MQ Workflow V3.4 with Enhanced Capabilities

Transcription

1 Software Announcement March 4, 2003 IBM WebSphere MQ Workflow V3.4 with Enhanced Capabilities Overview WebSphere MQ Workflow V3.4, the follow-on release of MQSeries Workflow V3.3, extends functions. It continues to support long-running business process workflows as they interact with systems and people. Version 3.4 provides integration processes with rich support for human interactions and deep application connectivity, and it leverages WebSphere MQ, XML, J2EE, Web Services, and WebSphere Business Integration software. New for V3.4 Portal client LDAP directory support Enablement to export process interface definitions as WSDL for usage in WebSphere Studio Application Developer Integration Edition V5 (delivered in an upcoming SupportPac ) Upgraded JSP wizard for forms generation Additional platforms including Microsoft Windows XP Professional Edition Currency improved for prerequisite programs WebSphere MQ V5.3, DB2 UDB V8.1, Oracle 9, WebSphere Application Server V5 Per-processor license Support for Human Interactions Broad workflow client functionality Support of native Windows clients Web browser clients Portal clients JSP forms wizard in WebSphere Studio Support for Application Connectivity XML WebSphere MQ (35+ platforms) J2EE Web Services Plug-in support for CICS and IMS on z/os WebSphere MQ Workflow V3.4 supports the most competitive EAI, B2Bi, and application server software including: WebSphere Application Server WebSphere MQ Integrator Broker WebSphere InterChange Server WebSphere Business Integration WebSphere MQ Workflow helps you bring systems and people into a managed process integration environment for EAI, B2Bi, and BPM solutions, built to a service-oriented architecture based on standards. Process impact based on key performance indicators or business measures for resources is best visualized using IBM Holosofx, the new business tooling for WebSphere Business. Business process workflows designed and analyzed with IBM Holosofx Workbench can be readily deployed to WebSphere MQ Workflow and used by applications and humans. Long-running processes enacted by WebSphere MQ Workflow can be monitored using dashboards readily provided by the IBM Holosofx Monitor for business activity monitoring. Business users also can take real-time corrective actions on their processes. Key Prerequisites WebSphere MQ Workflow V3.4 is available on the following platforms: Windows NT, Windows 2000, Windows XP Professional Edition AIX HP-UX Sun Solaris z/os or OS/390 Planned Availability Dates March 4, 2003, for electronic download March 7, 2003, on CD-ROM At a Glance WebSphere MQ Workflow V3.4 extends the functions of the previous release with new capabilities: Portal client LDAP directory support WSDL and JSP support New platform support Business Activity Monitoring (BAM) support Performance improvements Per-processor pricing For ordering, contact: Your IBM representative, an IBM Business Partner, or the Americas Call Centers at 800-IBM-CALL Reference: YE001 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: IBM United States IBM is a registered trademark of International Business Machines Corporation

2 Description Within WebSphere Business Integration, WebSphere MQ Workflow V3.4 supports long-running business processes that may require human participation and may have to be interrupted and restarted. It reduces cycle time and cost by automating business processes that interact with humans and applications throughout IT and organizational infrastructures. WebSphere MQ Workflow V3.4 extends the functions and platforms supported by MQSeries Workflow V3.3, enacting business process workflows in service-oriented architectures (SOA) based on standards. Portal Client User Interactions with Workflows via Portal Server Selected Workflow client functions are now available for integration with portals and portlets, providing customers, employees, suppliers, and business partners with a single point of personalized interaction with processes and applications. Application content and workflow users can be combined on the same personalized Web page for use with standard Web browsers. The portal client of WebSphere MQ Workflow V3.4 is an extension of the JSP/servlet-based workflow Web client. Workflow client functions are available as portlets, which can be integrated with application content on personalized HTML pages using standard portal server functionality. Portal client workflow functions: List the status of work items, process instances, and process templates Work item control: Force finish, force restart Process control: Start, suspend, resume, and query state Work contribution: Select, transfer, and complete work items assigned Exchange forms with process instances (check out/check in) Portal client workflow functions can be integrated into personalized portal solutions, such as: Customer Web sites and commerce portals, providing information and offering services that may be delivered with workflow support. Processes can be started from the Internet to deliver a business service, communicate back to the customer, and provide process status information. Employee information and knowledge management portals give users access to work items and process information. Administration portals enable managers and team leaders to control business status, team workload, resource allocation, and transfer of work. They can participate in the approval steps of specific processes. Executive dashboards for business activity monitoring offer business users key performance indicators on their critical business processes and the ability to take real-time corrective actions. Trading partner exchanges and e-marketplaces, enable business partners to participate in supply chain and CRM processes directly and online. The WebSphere MQ Workflow V3.4 portal client extends the Web client and complements the native Microsoft Windows client for better Web access integration. LDAP Support WebSphere MQ Workflow V3.4 extends support for LDAP directories beyond user authentication and now also covers synchronization with staff definitions stored in external Human Resource (HR) directories. Secure single sign-on (via an authentication exit) and unified log-on (Microsoft Windows and UNIX) continue to be supported. Keeping user passwords in the workflow staff database is not necessary. New in this release is an LDAP bridge that allows you to synchronize staff model definitions between workflow databases and external HR and security directories. This enables central administration of user and staff model data using the client of a standard directory server and replication of changes into related workflow databases, for use with work assignment rules in process activities that require human interaction. Map LDAP schema entries selectively to elements of the WebSphere MQ Workflow staff model. Query the specified LDAP information, read staff definitions from WebSphere MQ Workflow, sort them, and compare them. If differences occur, build an update Flow Definition Language (FDL) to create or delete staff definitions in WebSphere MQ Workflow. Can access arbitrary LDAP directories via the standard LDAP client and JNDI (Java Naming and Directory Interface) support included in JDK 1.3. Has been verified with IBM Directory Server V4.1. Equally applies to other LDAP directories such as Tivoli Policy Director, Microsoft Windows Active Directory, iplanet directory. Substitute Person Support: When using the LDAP bridge or another tool that updates actual staff information in WebSphere MQ Workflow, if staff information is to be deleted during the run of a batch job; work items and other references to this staff information (for example, person properties to be deleted) are transferred to another user. The new Substitute Person Support is: 1. Integrated into the LDAP bridge 2. Available as SubstitutePerson Tool, which can be called before deleting a user 3. Available via new APIs in C, C++ and Java Standards-Based Tooling Integration JSP Forms, XML Schemas (XSD), WSDL WebSphere MQ Workflow V3.4 extends the exploitation of XML and Web service standards for process integration to simplify the handover between business user and IT tools for integration, forms, and component development. With WebSphere MQ Workflow, process definitions available in FDL can be mapped to HTML, JSP forms, XML DTD, XML Schema, and Web Services Description Language (WSDL) for use with related tools: All functions of WebSphere MQ Workflow continue to be externalized in FDL, a simple text-based format that provides an open interface between IBM and third-party process modeling and development tools, and the WebSphere MQ Workflow runtime. It externalizes process interfaces and process content. HTML makes process definition documents readable via Web browsers. Additional process definition standards are supported via the IBM Holosofx business user tools, which support FDL. They create verified process definitions ready for deployment to WebSphere MQ Workflow and subsequent activity monitoring in real time

3 To support human interactions, JSP forms are generated to match the input and output data definitions in a process. A JSP form wizard support pack (WA83) for WebSphere MQ Workflow is available as a plugin to WebSphere Studio Application Developer V4. To support the automation of process steps, message format descriptions in XML and WSDL are generated for use with integration and application development tools and their respective runtimes. Support pack (WA05, WA07) tools are available to generate process interface descriptions using XML DTDs, XML schemas (XSD), or WSDL. These definitions can be used with WebSphere MQ Integrator, WebSphere InterChange Server, and WebSphere Studio Application Developer to automate individual process activities by integrating application components, public B2B protocols, or Web services into business process workflows. A buildtime enhancement to export WSDL for process interfaces will be delivered in an upcoming IBM SupportPac (WA86). FDL definitions are mapped to WSDL, and vice versa, by the different IBM SupportPacs. You can publish business processes as a Web service and consume Web services within a business process enacted by WebSphere MQ Workflow V3.4. WSDL is an XML format for describing network-accessible services, for example, the messages that a business service can accept and generate. Operations and procedures are described in an abstract manner and then they are bound to a specific network or transport protocol and message format. WSDL uses other XML technologies as its base, such as XML Schemas and XML namespaces. XML Schemas provide a way for specifying data types, starting from simple ones such as integer and string to more complex data types such as arrays and arbitrary user-defined constructs. WSDL support is provided explicitly for, but not restricted to, use with WebSphere Studio Application Developer Integration Edition V5 and will be activated with SupportPac WA86. This simplifies the creation of Web services and other composite Java applications that can interact out-of-the-box with WebSphere MQ Workflow V3.4. This new WSDL support strengthens the role of WebSphere MQ Workflow in service-oriented architectures and the support for J2EE and Web Services standard. It tightens the integration with WebSphere Studio tools based on the open Eclipse framework. And it provides a cornerstone for the standards-based exchange of process interface descriptions between business users for process management and IT tools for integration development. New Platform Support Platform coverage is extended with this new release, adding support for: Microsoft Windows XP Professional Edition (servers and clients) WebSphere MQ V5.3 DB2 UDB Enterprise Server Edition V8.1 Oracle (on AIX and Sun Solaris) WebSphere Application Server V5 (providing a J2EE runtime for hosting Web clients, Web services support, and Java programs) WebSphere Portal Server V4.1.2 Empty Activity for Decision Points in Process Model Process modeling functionality for decision points simplifies the following constructs without the overhead of invoking an external program: Branches at the beginning of a process, dependent on process input values Join after parallel branches for synchronization without the overhead of invoking an external program This further improves the ability to model a decision within a flow in a more natural way. Business Activity Monitoring (BAM) BAM comprises the visualization and analysis of business performance data about the speed and effectiveness of business processes in real time. WebSphere MQ Workflow V3.4 can be used readily with the new IBM Holosofx Workbench and Monitor for the design, analysis, and monitoring of process improvements by business users. Process impact can be verified before deployment, including ROI analysis for process improvements. Processes can be directly deployed as designed to WebSphere MQ Workflow for enactment and interaction with distributed resources. Corrective action can be taken on active process instances using WebSphere MQ Workflow client functions used by IBM Holosofx. Process activity and resource use information from the WebSphere MQ Workflow audit events provide the actuals for the monitoring of key process performance indicators in real time. Process cycle times, the cost of resource, bottlenecks, and ROI are visualized to business users in real time (actual versus planned) and at design time (as-is versus to-be). Rich process performance information on the use of distributed resources is provided by WebSphere MQ Workflow V3.4 in real time. You can employ real-time enterprise status reporting for long-running business process workflows and the performance of processes exactly as specified by business users and tailored to the specific data of each specific service request. Enhancements Through WebSphere MQ V5.3 This new release of WebSphere MQ improves buffer allocation for messages resulting in better WebSphere MQ Workflow V3.4 performance. Since the standard Workflow set up does not make use of WebSphere MQ V5.3 SSL encryption, customers have to customize their own WebSphere MQ V5.3 set up in order to use SSL encryption. This might differ from the standard setup how WebSphere MQ Workflow will customize WebSphere MQ V5.3 resources

4 Supported Platforms Windows NT, Windows XP WebSphere MQ Workflow V3.4 is the business process z/os, Solaris Professional, workflow engine at the heart of Business Integration, OS/390 AIX HP UX (Sparc) Windows 2000 supporting e-business customer initiatives for BPM, BAM, Buildtime x Runtime Server x x x x x Prog. Exec. Server x Prog. Exec. Agent x x x x Admin Utility x x x x XML API x x x x x Lotus Notes(R) API x Client API x x x x x Client GUI x Web Client x x x x x Portal Client x x x Withdrawn Features Offered Under Former Releases Dropped Client support for Windows 98 and Me Dropped shrinkwrap package (box containing license, media and books) Dropped Capacity Units for licensing the workstations program Locator policies (Visibroker Smart Agent, CORBA Naming Service, Java RMI, CORBA Inter-ORB Reference URL) FlowMark V2.3 Compatibility API Accessibility by People with Disabilities These products have the following accessibility characteristics: Features for vision impaired users: Supports interfaces commonly used by screen readers (Windows only) Allows the user to request more time to complete timed responses Supports customization of display attributes such as color, contrast, and font size Communicates all information independently of color Supports interfaces commonly used by screen magnifiers (Windows only) Supports the attachment of alternative output devices Provides documentation in an accessible format Features for users with mobility impairments or limited hand use: Allows the user to request more time to complete timed responses Supports the attachment of alternative input and output devices Features for the deaf or hearing impaired users Supports alternative to audio information Supports adjustable volume control For the cognitively impaired users, the user can request more time to complete the activity Does not flash the screen at rates that could induce epileptic seizures Minor limitation: the Web client includes a graphical representation of the process monitor without text equivalent. Product Positioning EAI, B2Bi, Web Services, and Portal Integration. It supports long-running processes that may require human intervention and participation. Optimized for parallel distributed processing, WebSphere MQ Workflow V3.4 executes process definitions captured during modeling and ensures that business functions are performed reliably and correctly using the transactional integrity of MQSeries. It is extremely scalable, taking full advantage of multiple processors and clustering, and is particularly well suited to Web server farms. It executes processes running from subseconds to many months. Its full restart and recovery capability makes it truly fault tolerant. When you require high availability, essential in today s e-business on demand environment, WebSphere MQ Workflow is the engine you can bet your mission-critical business processes on. Support by business user tooling for process monitoring, analysis, design, and simulation, WebSphere MQ Workflow gives you control and feedback on the execution of complete start-to-end business processes and the resources used. It brings humans and applications into a managed process environment. Service-Oriented Architectures for Workflow and Business Integration: Business processes are rarely performed by a single application, system, or person. They are often long-running and need to interact with various resources distributed throughout the extended enterprise. A process architecture is well described in terms of process initiators, process participants, and reusable business services. Processes provide and consume business services, and automate the flow of information between steps and the selection of the resources involved. Process initiators and process participants both refer to customers, employees, partners, and applications. A process architecture needs to ensure that processes can be performed consistently across multiple access channels and the myriad of backend systems. And a process infrastructure needs to ensure reliability and scalability of process performance, so that the architecture does not break when the demand for services and process workload increases. Reusable business services can refer to: Long-running business processes and sub-processes Shorter running message flows, process collaborations, and public B2B protocols User clients (for example, portals, worklists, forms, ), applications, adapters, and Web services SOA enable the management of more complex end-to-end e-business processes by a separation of concerns and standards-based interactions. They enable managed process integration and promote loosely-coupled, component-based, cross-technology solutions. In a service-oriented process architecture, you can manage the WHAT (business processes and metrics) separate from the HOW (resources provide services to a process via the network). Teams of people can contribute to automated processes with decisions, knowledge, physical work, and exception handling. Processes can be streamlined by application development and integration projects to eliminate bottlenecks and resource constraints. Processes need to be visible,

5 measurable and changeable, and in-sync with business design. Separating business process logic from IT and organizational infrastructures enables your organization to be agile in a constantly changing and dynamic marketplace vital in the competitive world of e-business. WebSphere MQ Workflow encapsulates process logic, enhancing e-business flexibility, and links process logic to application functions and human input from teams. It ensures that your business and IT requests are processed the way you want. It gives you the flexibility to change business processes separate from upgrades to individual applications, and provides process visibility to business users. Leveraging Open Standards: Managing business process workflows in real e-business requires the integration of services provided by distributed resources, independent of the technologies used for implementation. WebSphere MQ Workflow allows you to fully leverage your existing resources in IT and organization infrastructures with your business process workflows. It supports a broad range of open standards and interfaces to support service-oriented architectures and process interactions with services provided by systems and people. Web Services, extensible Mark Up Language (XML), and J2EE are the standards that link business processes and applications; they are supported throughout all dimensions of the WebSphere software platform for on-demand e-business. XML, Web Services, and WSDL Describe Process Interfaces to the Network: XML has standardized the data syntax for document processing and exchange, and has gained worldwide acceptance for the exchange of messages between applications. Message formats are often described in DTD or XSD, and can be parsed dynamically at runtime. Web Services provide a standard for externalizing network application to the network, offering a predefined structure to message formats for process integration. Web services are often associated with, but not necessarily restricted to, SOAP messages and UDDI directories. Web Services Description Language (WSDL) provides a standard, extensible support for describing service interfaces, transaction and security needs, and transport protocols. WebSphere MQ Workflow makes extensive use of XML; for example, for message-based application integration and audit event monitoring. XML messages can be transformed using Java XSLT programs and complementary WebSphere Business Integration software. J2EE Application Programs and User Interfaces to Business Process Workflows: Today, Java is one of the most mature and commonly used programming languages for building enterprise software. J2EE provides the open standards for hosting application transactions and user interface components for the Internet. WebSphere MQ Workflow supports interaction with J2EE applications using XML messages and MQSeries Java programs (and XSLT, for example), JMS publish-subscribe (for example, for monitoring audit events), and SOAP Web Services. WebSphere MQ Workflow provides users with Web browser access to business processes providing built-in workflow, Web, and portal clients, that are based on JSPs and Servlets and can be hosted on standard J2EE runtimes such as WebSphere Application Server. A complementary JSP forms wizard further simplifies the creation of user interface applications to the process. RMI-over-IIOP and JNDI can be used to integrate with other EJBs and Corba applications. The new workflow portal client standardizes the integration of workflow client functions with user content from other sources (for example, applications and databases) on the same Web page, and leverages the latest J2EE-based portlet technology. Flow Definition Language (FDL): FDL and BPEL4WS describe process content for execution. Transferring process knowledge for digitization and execution on a workflow engine requires an open interface for process definitions that can be exchanged between runtime and tools. FDL is the proven, open process definition interface to WebSphere MQ Workflow. It is a simple text-based flat-file format and successfully used by all customers, partners, domain-specific solutions, and tools that support WebSphere MQ Workflow. Examples include IBM Holosofx tools, an IBM bridge for IDS-Prof.Scheer ARIS Toolset (available as a support pack), Adonis, and the Financial services workflow templates from IFW, WBI for Industries. It is also used to exchange process interface definitions with other tools, such as WSAD (JSP wizard), WST (SOAP SupportPac), WSADIE (flow engine) interoperability between WAS and the upcoming SupportPac WA86. This process definition language is independent from business process modeling and cost analysis methodology like LOVEM, or activity based costing (ABC), or application development methodologies like UML. You can continue to use your methodology of choice. Tools like IBM Holosofx add methodology support to FDL and capabilities to access process knowledge kept in other tools, such as UML and XMI used with Rational Rose. BPEL4WS is a new extensible standard for process content evolving for service-oriented architectures. It is based on XML, leverages WSDL for process interface definitions and extends it with process content. Workflow Management Coalition: IBM is a funding member of the Workflow Management Coalition (WfMC). Founded in August 1993, this is a non-profit, international organization of workflow vendors, users, analysts, and university/research groups. The coalition s mission is to promote and develop the use of workflow through the establishment of standards for software terminology, interoperability, and connectivity between workflow products. The coalition has developed a framework for the establishment of workflow standards. For more information, visit: WebSphere MQ Workflow is designed according to the WfMC reference model. The referring APIs are available based on this modular architecture. IBM continues to be a major contributor to future standard development. e-business on demand Workflows and Integration: Workflows are the parts of a business process run on a computer. Business processes describe the typical operations of a company. They can be described as sequences of activities, passing information automatically

6 between steps and to the resources that perform a piece of work. Systems and humans can contribute to processes by providing a specific business service. Processes are not necessarily run on a computer. A workflow model may be just a small part of a larger process model, or it may encompass the whole process model. Business processes are rarely performed by only a single application, system, or person. The vast majority of processes are a mixture of work steps performed by humans and applications. Ultimately, companies may want to completely automate their processes. Applications are integrated and new application components are developed for routine steps in the process to automate standard tasks. People can enhance automated processes with human knowledge and skills, or physical work, for approvals, decisions, team work, as well as for solving exceptions, errors and complaints that cannot be fully automated in a cost-effective way. WebSphere MQ Workflow for Business Integration BPM, BAM, EAI, B2Bi, Portal Integration: WebSphere Business Integration Server provides a blending of process management with integration on the process and the message level. WebSphere MQ Workflow is best used for long-running processes supporting human interaction, supporting IBM Holosofx for process monitoring and analysis using key performance indicators and proving integration support for CICS, IMS, WebSphere MQ, JMS, J2EE, Web Services, and user clients (browser, portal, and Windows). WebSphere Interchange Server and WebSphere MQ Integrator Broker add integration support beyond standards, providing message flows, B2B public protocols, and process collaboration together with a wealth of packaged application adapters. WebSphere MQ Workflow V3.4 enables the explicit management of long-running business process workflows as they interact with systems and people for service delivery. Workflow client support via Web browsers, native windows desktops and the workflow portal client enables the LOB workforce management to contribute work to business processes via integrated user interfaces. Business Activity Monitoring and Business Process Analysis: WebSphere Business Integration tools for business process analysis, design, and simulation and business activity monitoring are fully supported by WebSphere MQ Workflow V3.4. Application and user interactions can be monitored via workflow processes, passing data container and process context information to IBM Holosofx tools. This can include application-specific events handled by process collaborations or message flows that interact with WebSphere MQ Workflow. In addition, processes designed with IBM Holosofx Workbench can be readily deployed to WebSphere MQ Workflow for execution. J2EE, XML, and Web Services are the open standards that link both workflow capabilities using the same service-oriented architecture. You can extend your use of business process workflows to new J2EE-based flow technology embedded in Java applications, with flow engine interoperability. WebSphere MQ Workflow will continue to provide the central core of business process management function within WebSphere Business Integration. It features a tops-down approach to business integration in which a business model is defined and then implemented by connecting to existing resources with little or no custom coding. WebSphere Application Server is a delivery platform for developers to build powerful Web-based applications. This involves a bottoms-up approach to integration where new business logic can be built more effectively into new, easy-to-integrate Java applications. WebSphere MQ Workflow V3.4 provides new functions and SupportPacs for Web services, WebSphere Application Server V5, and the new J2EE application development capability in WSAD IE V5: Publish process interface definitions in WSDL, as a Web service or for hand-over to WSAD IE (via upcoming SupportPac WA86) Interact with Web services and composite Java applications on WAS V5 Enterprise Trademarks SupportPac, IMS, z/os, e-business on demand, LOVEM, and zseries are trademarks of International Business Machines Corporation in the United States or other countries or both. WebSphere, MQSeries, DB2, CICS, MQ Integrator, AIX, OS/390, and FlowMark are registered trademarks of International Business Machines Corporation in the United States or other countries or both. Microsoft is a trademark of Microsoft Corporation. Windows and Windows NT are registered trademarks of Microsoft Corporation. Java is a trademark of Sun Microsystems, Inc. Tivoli is a registered trademark of International Business Machines Corporation or Tivoli Systems Inc. in the United States or other countries or both. Lotus Notes is a registered trademark of Lotus Development Corporation and/or IBM Corporation. Other company, product, and service names may be trademarks or service marks of others. Business Process Workflow and Application Workflow: Workflow, flow composition and service choreography are common requirements for both the build to integrate and the process integration styles of integration. Many customers are using MQSeries Workflow very successfully today for business integration. Access to flow technology is also desired by application developers to create composite applications from existing software assets exposing service interfaces. In response to customer requirements, we are therefore also introducing a new range of J2EE-based flow capabilities with WebSphere Application Server V5 necessary for Java programmers to develop comprehensive build-to-integrate solutions

7 IBM US Announcement Supplemental Information March 4, 2003 Services Support and Solutions Offerings IBM is committed to work with industry vendors to define interfaces for higher-value functions, APIs, tools, and management functions for Business Integration. IBM also provides partnering opportunities for solution providers and system integrators (SIs). IBM works with several partners to make available complementary solutions, applications, tools, and system management and monitoring offerings. System integrators are able to assist customers with their implementation and integration. IBM Competency Centers work jointly with Business Partners to provide all kinds of services to satisfy the WebSphere MQ Workflow customers. SupportPacs Generally, IBM makes available, free or for a fee, this category of add-on programs provided by various sources worldwide. For WebSphere MQ Workflow, development has finished these new features, available without a charge. For download, visit the Web site below. IBM is continuously preparing new features that incorporate advanced technical functions. Upon availability, IBM will make them accessible. Check this Web site regularly: txppacs Workflow Competency Center Services These centers offer you additional, customized services for a fee: Solutions Assurance: Validates all product components and services against your expectations. Installation Support: Installs and configures WebSphere MQ Workflow and prerequisites in heterogeneous environments. Migration Support: Helps you upgrade from MQSeries Workflow releases to this current offering: Buildtime process models Runtime-data process instances Application Implementation: Consultants are available for your specific project implementations: ActiveX exploitation: To customize the standard client, and to build customer-based worklists and other process-related applications on Microsoft clients. Implementation of the Web Client: to design and develop a Workflow Internet application using the Web Client on an application server. Generic API Test and Prototyping Tools: Test and tune WebSphere MQ 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 Easy performance measurements Workflow Development generates process models for WebSphere MQ Workflow with the assistance of skilled workflow engineers. High-Availability Cluster Multiprocessing maximizes system availability with services for: Installation Configuration Customization Testing Tuning 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 Business process management solution that solves the customer s needs. The typical duration will range from two to four weeks. The customer and IBM will jointly define the requirements. Both sides provide the resources to ensure success. For detailed information, visit: Visit: workflow Education Support The appropriate curriculum will include the enhancements described in this announcement. Visit also the IBM Learning Services Home Page for available courses in your country: IBM Learning Services, selected IBM Business Partners, and authorized Training Partners offer public, scheduled classes comprised of basic concepts and hands-on training on all aspects of WebSphere MQ Workflow. A modular curriculum features: Modeling Installation Deployment Administration APIs for different categories (container APIs, worklist handler APIs), and languages (ActiveX, Java) 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: IBM United States IBM is a registered trademark of International Business Machines Corporation

8 Ask your Business Partner or IBM representative for details and enrollment. Visit: mqseries/workflow Subject: Education services/learning To focus your individual education needs, customized classes can be arranged, send your request to: Call IBM Education and Training at 800-IBM-TEACH ( ) for catalogs, schedules, and enrollments. Services designed to assist you in the installation and implementation of WebSphere MQ Workflow in your organization are also available. Offering Information Product information is available through Offering Information (OITOOL) at: and through the Passport Advantage Web site at: Publications These publications apply exclusively to the IBM zseries server program, available in U.S. English only: Title WebSphere MQ Workflow for z/os V3.4 Program Directory Customization and Administration Programming Guide Messages and Codes Form Number GI SC SC SC The following publications (in U.S. English) are included in the Passport Advantage Documentation Package, and the zseries server package 5655-BPM: Title WebSphere MQ Workflow V3.4 Concepts and Architecture 1 Getting Started with Buildtime Getting Started with Runtime Installation Guide Administration Guide Programming Guide 1 Introductory information These books can be ordered separately. Business Partner or IBM representative. Form Number GH SH SH SH SH SH Contact your 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. The publications are stored as HTML and PDF files on a CD-ROM dedicated to softcopy documentation, which is shipped with the program CD-ROM. The files can also be used with an HTML browser or with an Adobe Acrobat Reader 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 Hardware Requirements: The specifications are recommended numbers for a two-tier configuration (database and runtime server reside on the same system). Buildtime PC with Intel -based processor architecture (for example, Pentium 300 MHz, or higher) Screen: Resolution SVGA 800 x 600 (minimum), 256 colors (minimum) Operating DB2(R) UDB Jet Engine Environment Main Memory Hard disk Main Memory Hard disk Windows(R) 96 MB 1 GB 96 MB 700 MB 1. Operating System: Windows NT 4.0, Windows 2000, or Windows XP Professional Edition 2. Buildtime database: DB2 UDB Enterprise Server Edition V8.1 (included) or V7.2; or Microsoft Jet Engine General Recommendations Runtime Environments When setting up your servers, for performance and safety reasons, keep database and log files (table spaces) on separate disks. The number and size of process models and process instances residing in the runtime database and 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. The supported ORBs used for RMI-IIOP are not always interoperable, not every ORB combination is functional. Servers for Windows A PC with Intel-based processor architecture, for example Pentium with 500 MHz, or higher, is required. For test or demonstration purposes, a ThinkPad or portable PC is acceptable. Operating Environment Main Memory Hard Disk Windows 256 MB 2 GB 1. Operating System: Windows NT 4.0 Server or Workstation with Service Pack 6a, or Windows 2000, or Windows XP Professional Edition 2. Communication: WebSphere MQ for Windows V5.3 + CSD 1 (included), or MQSeries for Windows V5.2 + CSD 5 3. Database: DB2 Universal Database (UDB) for Windows V8.1 (included), or DB2 UDB for Windows V

9 4. LDAP: IBM Directory Server V4.1 or V5.1, or SecureWay Directory Server V3.2.2 Clients for Windows: A PC with Intel-based processor architecture capable of running the operating system and 64 MB of main memory are recommended. Operating System: Windows NT 4.0 Workstation, Windows 2000, or Windows XP Professional Edition Communication: WebSphere MQ for Windows V5.3 +CSD 1 client (included), or MQSeries for Windows V5.2 + CSD 5 client Web Application Server: WebSphere Application Server V3.5.3, and higher, or V4.0.1, and higher, or V5.0 For RMI/IIOP communication: ORB of WebSphere Application Server V3.5.3, and higher, or V4.0.1, and higher, or V5.0 For a Portal Client: WebSphere Portal Server V4.1.2 For user access to the Web: A browser supporting HTML 4 with Cascading Style Sheets (CSS) is required, such as Netscape Navigator V4.7, or higher, or Microsoft Internet Explorer V5.5 or V6.0 For the development of programs using the WebSphere MQ Workflow APIs, one of: Microsoft Visual C++ V6 (WebSphere MQ Workflow client APIs for C and C++) IBM JDK 1.2.2, or 1.3 (WebSphere MQ Workflow client APIs for Java), or Sun JDK 1.3.1_04, or higher For the development of programs using the WebSphere MQ Workflow ActiveX Controls: Microsoft VisualBasic V6 for Windows Lotus Notes API Release 4.5 For a WebSphere MQ Workflow standard client, no additional prerequisites Servers for AIX RS/6000 uniprocessor, SMP, or SP machine as supported by AIX System for AIX 5L with PPC (PowerProcessor Chip) (support in 32-Bit mode only) Screen: Dedicated graphical display not necessary (system console is sufficient) Operating Environment Main Memory Hard Disk RS/ MB 2 GB 1. Operating System: AIX V4.3.3 or AIX fixlevel ML02, or Communication: WebSphere MQ for AIX V5.3 + CSD 1 (included), or MQSeries for AIX V5.2 with CSD number 5 3. Database: Either one of: DB2 UDB for AIX V8.1 (included), or DB2 UDB for AIX V7.2 Oracle V Oracle 9i (V ) 4. LDAP: IBM Directory Server V4.1 or V5.1, or SecureWay Directory Server V3.2.2 In a high-availability environment: AIX V4.3.1 with HACMP V4.2.2, or AIX V4.3.2 or V4.3.3 with HACMP V4.3.1 AIX V5.1 maint level 2 or AIX V5.2 with HACMP V4.5 Clients for AIX: A workstation capable of running the operating system. Operating System: AIX V4.3.3, or AIX V5.1 for PowerProcessor Chip (PPC) Communication: WebSphere MQ for AIX V5.3 + CSD 1 client (included), or MQSeries for AIX V5.2 client with CSD number 5 Web Application Server: WebSphere Application Server V3.5.3, and higher, or V4.0.1, and higher, or V5.0 For RMI/IIOP communication: ORB of WebSphere Application Server V3.5.3, and higher, or V4.0.1, and higher, or V5.0 For a Portal Client: WebSphere Portal Server V4.1.2 For user access to the Web: A browser supporting HTML 4 with Cascading Style Sheets (CSS) is required, such as Netscape Navigator V4.7, or higher For the development of programs using the WebSphere MQ Workflow APIs, one of: IBM C for AIX V5.0 VisualAge C++ Professional for AIX V5.0 IBM JDK 1.2.2, or 1.3 (WebSphere MQ Workflow client APIs for Java), or Sun JDK 1.3.1_04, or higher Servers for HP-UX An HP 9000 workstation is required. Screen: A dedicated graphical display is not necessary. The system console is sufficient. Operating Environment Main Memory Hard Disk HP MB 2 GB 1. Operating System: HP-UX V11.0 or V11i 2. Communication: WebSphere MQ for HP-UX V5.3 + CSD 1 (included), or MQSeries for HP-UX V5.2 with CSD 5 3. Database: Either one of: DB2 UDB V8.1 for HP-UX V11i (included), or V7.2 (included) for HP-UX V11.0 Oracle V LDAP: IBM Directory Server V4.1 or V5.1, or SecureWay Directory Server V3.2.2 Clients for HP-UX: A workstation capable of running the operating system. Operating System: HP-UX V11.0 or V11i Communication: WebSphere MQ for HP-UX V5.3 client + CSD 1 (included), or MQSeries for HP-UX V5.2 client with CSD 5 Web Application Server: WebSphere Application Server V4.0.1, or higher

10 For RMI/IIOP communication: ORB of WebSphere Application Server V4.0.1, or higher For user access to the Web: A browser supporting HTML 4 with Cascading Style Sheets (CSS) is required, such as Netscape Navigator V4.7, or higher For the development of programs using the WebSphere MQ Workflow APIs: HP ANSI C++ Compiler for HP-UX V11 IBM JDK 1.2.2, or 1.3 (WebSphere MQ Workflow client APIs for Java), or Sun JDK 1.3.1_04, or higher Servers for Sun Solaris A Sun workstation with SPARC processor architecture is required. WebSphere MQ Workflow runs in 32-bit mode only. Screen: A dedicated graphical display is not necessary. The system console is sufficient. Operating Environment Main Memory Hard Disk Sun SPARC 512 MB 2 GB 1. Operating System: Sun Solaris V7 or 8 2. Communication: WebSphere MQ for Sun Solaris V5.3 + CSD 1 (included), or MQSeries for Sun Solaris V5.2 with CSD 5 3. Database: Either one of: DB2 UDB for Sun Solaris V8.1 (included), or DB2 UDB for Sun Solaris V7.2 Oracle V Oracle 9i (V ) 4. LDAP: IBM Directory Server V4.1 or V5.1, or SecureWay Directory Server V3.2.2 Clients for Sun Solaris: A workstation capable of running the operating system. WebSphere MQ Workflow runs in 32-bit mode only. Operating System: Sun Solaris V7 or V8 Communication: WebSphere MQ for Sun Solaris V5.3 + CSD 1 client (included) or MQSeries for Sun Solaris V5.2 + CSD 5 client Web Application Server: WebSphere Application Server V3.5.3, or higher, V4.0.1, or higher, or V5.0 For RMI/IIOP communication: ORB of WebSphere Application Server V3.5.3, and higher, or V4.0.1, and higher, or V5.0 For a Portal Client: WebSphere Portal Server V4.1.2 For user access to the Web: A browser supporting HTML 4 with Cascading Style Sheets (CSS) is required, such as Netscape Navigator V4.7, or higher For the development of programs using the WebSphere MQ Workflow APIs: Sun Workshop Compiler Professional C/SPARC V4.2 or V5 Sun Workshop Compiler Professional C++/SPARC V6.2 Sun JDK 1.3.1_04 (WebSphere MQ Workflow client APIs for Java) z/os Program 5655-BPM Servers for z/os and OS/390 : A zseries 800, 900, Multiprise 3000, or S/390 hardware system 1. OS/390 R10 runs only on the following IBM (or comparable) processors: zseries 900 (z900) S/390 Parallel Enterprise Server R2 and R3 models, and Generation 3, and above On 9672-Rx2 and -Rx3 models, hardware patch MCL209 S/390 Multiprise 2000 or 3000 (all models) 2. z/os V1 runs on all zseries (or comparable) servers: 2066 zseries 800 (z800) zseries 900 (z900). IBM 7060 S/390 Multiprise 3000 Enterprise Server. IBM 9672 S/390 Parallel Enterprise Server Generation 5 (G5) and Generation 6 (G6). Driver 26 (licensed internal code V1.6.2) or later is required to support architectural enhancements required by z/os, which are shown below. 1. Operating System: One of the following: 5647-A01 OS/390 V2R10, or later 5694-A01 z/os V1R1, or later 2. Communication: 5655-F10 MQSeries V5.2, or later 5655-F10 MQSeries Client Attachment Feature V5.2, or later 3. Database: 5645-DB2 DB2 UDB for OS/390 V6.1, or later 4. LDAP: IBM Directory Server V4.1 or V5.1, or SecureWay Directory Server V3.2.2 Web Application Server 5655-F31 WebSphere Application Server V4.0.1, or later, with separately installed 5655-D35 IBM Developer Kit for OS/390, Java 2 Technology Edition, SDK For the development of programs using the Workflow APIs and running on z/os or OS/390: 5648-A25 IBM COBOL for OS/390 and VM V2R2, or later IBM C/C++ compiler (part of the operating system) 5655-D35 IBM Developer Kit for OS/390, Java 2 Technology Edition, SDK To Use the Non-Transactional ECI 5697-E93 CICS Transaction Server for OS/390 V2.1, or later To use the transactional ECI CICS Transaction Server for OS/390 V1.3, or later

11 To use the CPIC IMS/ESA V6.1, or later Corequisites for z/os or OS/ J51 IBM XML Toolkit for z/os and OS/390 V1.4 Web Application Server for z/os or OS/390 To link a Web environment to a WebSphere MQ Workflow Server, the WebSphere MQ Workflow Web Client requires a computer system with sufficient main memory and mass storage to run: 5655-F31 WebSphere Application Server Standard Edition V4.0.1, or higher (functional prerequisite) Servlet container, Servlet API 2.1, or later Servlet container, supporting JSP 1.0 (optional) Software Requirements Compatibility: Process models created under previous releases can be imported to WebSphere MQ Workflow V3.4. Applications developed under previous releases can be recompiled and relinked as long as WebSphere MQ Workflow V3.4 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 WebSphere MQ Workflow V3.4 depends heavily on: Usage characteristics of the process models and organization definitions Average and maximum size of worklists Capacity and utilization of the WebSphere MQ Workflow and database server machines Speed and memory size of the server and client machines Transmission speed and load of the communication channels To increase the number of users sharing the same processes, consider the use of multiple workflow servers sharing the same database. Contact your IBM representative or Business Partner for a Solutions Assurance review of your specific implementation. Planning Information Workstations Licensing Per Processor: For WebSphere MQ Workflow V3.4, customers will now pay a license charge that is based on the number of processors in the runtime and database server machine, regardless of whether all these processors are used to run the program; the charge unit is the Processor License Unit (PLU). This is a change from the charging per capacity unit (CU) the former charge unit. This change is effective immediately for all new orders but does not affect existing licenses until their next maintenance renewal. Customers who do not have software maintenance, are not affected and should continue with the CU licenses. Charging: Charges for authorized use of WebSphere MQ Workflow V3.4 are based on PLUs. The use of WebSphere MQ Workflow V3.4 on any runtime and database server machine requires one PLU to be acquired (from IBM or an IBM Business Partner) for each processor contained in the runtime and database server machine on which any copy of the WebSphere MQ Workflow V3.4 is to run; usage of WebSphere MQ Workflow Buildtime is free. PLUs are required for every runtime and database server machine on which the WebSphere MQ Workflow V3.4 is installed. You are also required to obtain a corresponding number of additional PLUs if the WebSphere MQ Workflow V3.4 installation is moved to a server machine with a greater number of processors, or if any additional processors are added to the runtime and database server machine on which the WebSphere MQ Workflow V3.4 is installed. Failure to comply with the requirement for the appropriate number of PLUs will invalidate the terms of this license. If you require licensing for machines with five or more processors, charges are eligible for Special Bid, contact your IBM Business Partner or IBM representative. Also refer to the Terms and Conditions supplied with your copy of WebSphere MQ Workflow V3.4. Transferability: Customers who upgrade from an earlier release of WebSphere MQ Workflow V3.4 under Passport Advantage do not need to order any additional PLUs if they retain the same number of processors. Customers who upgrade from an earlier release of WebSphere MQ Workflow V3.4 under Passport Advantage and have a greater number of processors, can use their existing CUs and then acquire additional PLUs to satisfy the licensing requirements. The CUs from the previous release will be converted to PLUs (at a rate of two capacity units to one PLU) and counted as all or part of the customer entitlement. Any spare CUs can be used towards other WebSphere MQ Workflow V3.4 entitlement, but are not refundable. Customers without a Passport Advantage contract having acquired a number of CUs should retain their printed entitlement card from the original product as Proof of Entitlement. Note that the pricing is based on the number of processors in the runtime and database server machine, regardless of whether they are all being used to execute the program. Migration: Customers having CU based licenses, should migrate at the time of maintenance renewal. A standard conversion rate of two CUs to one PLU will be used. In the majority of situations, this conversion will ensure that customers have the correct number of licenses on the processor license unit metric. However, when machines have five or more processors (and in a few other cases), the standard conversion will not give the required number of licenses. In this case, when contacted by IBM, you should discuss acquiring additional licenses so that you are correctly licensed under the processor-based pricing model. You will not be charged for additional licenses granted under this process, but maintenance renewal prices will be based on the number of processors that are licensed