BPEL4WS business processes with WebSphere Business Integration : understanding, modeling, migrating / / [Martin Keen ... et al.]

• Pubblicazione: Research Triangle Park, NC, : IBM, International Technical Support Organization, c2004
• Edizione: 1st ed.
• Descrizione fisica: xiv, 370 p. : ill
• Disciplina: 005.13/3
• Soggetto topico: Web services; Programming languages (Electronic computers); Electronic commerce - Computer programs
• Altri autori: KeenMartin
• Note generali: "SG24-6381-00."
• Nota di bibliografia: Includes bibliographical references and index.
• Nota di contenuto: Front cover -- Contents -- Notices -- Trademarks -- Preface -- The team that wrote this redbook -- Become a published author -- Comments welcome -- Part 1 BPEL4WS introduction -- Chapter 1. WebSphere Business Integration and process modeling -- 1.1 Introducing BPEL4WS -- 1.1.1 On Demand Operating Environment and SOA -- 1.1.2 Abstract and executable models -- 1.2 Business Integration Reference Architecture -- 1.2.1 Development platform -- 1.2.2 Business performance management services -- 1.2.3 Enterprise Service Bus -- 1.2.4 Business application, data access, and partner services -- 1.3 WebSphere Business Integration product support -- 1.3.1 IBM WebSphere Business Integration Modeler V5.1 -- 1.3.2 IBM WebSphere Studio Application Developer Integration Edition V5.1 -- 1.3.3 IBM WebSphere MQ Workflow V3.5 -- 1.3.4 WebSphere Business Integration Server Foundation V5.1 -- 1.4 BPEL4WS usage scenarios -- 1.4.1 Scenario: Model a new business process -- 1.4.2 Scenario: Migrate an existing business process -- 1.4.3 Other scenarios -- 1.4.4 Summary of WebSphere Business Integration product options -- Chapter 2. History, heritage, and directions of BPEL4WS -- 2.1 BPEL4WS history -- 2.1.1 Web services for application interoperability -- 2.1.2 Web services for process automation -- 2.2 BPEL4WS heritage -- 2.2.1 BPEL4WS in the Web services landscape -- 2.2.2 BPEL4WS and business process management -- 2.2.3 Business process standards -- 2.3 BPEL4WS directions -- Chapter 3. Defining BPEL4WS -- 3.1 What is BPEL4WS -- 3.1.1 Overview -- 3.1.2 Relationship to other standards -- 3.2 Key BPEL4WS concepts -- 3.2.1 Partners -- 3.2.2 Partner link types -- 3.2.3 Partner links -- 3.2.4 Business partners -- 3.2.5 Endpoint references -- 3.2.6 Activities -- 3.2.7 Data handling -- 3.2.8 Correlation -- 3.2.9 Scope -- 3.2.10 Extensions for executable processes. ; 3.2.11 Extensions for business processes -- 3.3 IBM extensions to BPEL4WS -- 3.3.1 Activity type extensions -- 3.3.2 Process-related extensions -- 3.3.3 Activity extensions -- 3.3.4 Basic activity extensions -- 3.3.5 Structured activity extensions -- Chapter 4. Business scenario used in this book -- 4.1 Overall business scenario -- 4.2 Components of the business scenario -- 4.2.1 Validate input -- 4.2.2 E-mail acknowledgement ID and reservation ID -- 4.2.3 Reserve flight -- 4.2.4 Reserve hotel -- 4.2.5 Bill customer -- Part 2 Modeling new BPEL4WS processes -- Chapter 5. WebSphere Business Integration Modeler: modeling for BPEL4WS -- 5.1 Introducing WebSphere Business Integration Modeler V5.1 -- 5.1.1 Business process management and service-oriented architecture -- 5.1.2 Architecture -- 5.1.3 Technology modes and user profiles -- 5.2 Creating a new BPEL model -- 5.2.1 Understanding workspaces, projects, and catalogs -- 5.3 Mapping elements to WebSphere Business Integration Server Foundation -- 5.3.1 Files generated -- 5.3.2 Top level global process -- 5.3.3 Business items -- 5.3.4 Connection with an associated business item -- 5.3.5 Connection without an associated business item -- 5.3.6 Input and output -- 5.3.7 Input and output criteria -- 5.3.8 Local subprocess -- 5.3.9 Local task -- 5.3.10 Control nodes (fork, join, and merge) -- 5.3.11 Decision (simple and multiple) -- 5.3.12 Local repository -- 5.3.13 Resource requirement -- 5.3.14 Services -- 5.3.15 Map -- 5.3.16 While loop -- 5.3.17 Stop node -- Chapter 6. WebSphere Business Integration Modeler: modeling the scenario -- 6.1 Validate reference model -- 6.1.1 Modeling a process in BPEL mode -- 6.1.2 Exporting files from WebSphere Business Integration Modeler -- 6.1.3 Understanding the generated files -- 6.1.4 Importing files into WebSphere Studio. ; 6.1.5 Understanding the generated process in WebSphere Studio -- 6.1.6 Completing the BPEL4WS process in WebSphere Studio -- 6.1.7 Generating deployment code and testing a BPEL4WS process -- 6.2 Other reference models -- 6.2.1 Reserve Hotel reference model -- 6.2.2 Reserve Flight reference model -- 6.2.3 Bill Customer reference model -- Part 3 Migrating existing processes to BPEL4WS -- Chapter 7. WebSphere MQ Workflow: migration considerations -- 7.1 Introduction -- 7.2 Design considerations -- 7.2.1 Container reuse -- 7.2.2 Use of blocks and subprocesses -- 7.2.3 Undoing earlier activities -- 7.2.4 Staff resolution -- 7.3 Considerations for production roll-out -- 7.3.1 Replacement -- 7.3.2 Migration -- 7.3.3 Interoperability -- 7.4 Reuse of existing components -- 7.4.1 Business process constructs -- 7.4.2 Business measures -- 7.4.3 Activity implementation (UPES, JSP, Web services) -- 7.4.4 Customized Web client -- 7.4.5 Staff repository -- 7.4.6 Running instance repository -- 7.4.7 Instance archive -- 7.4.8 Monitor repository -- Chapter 8. WebSphere MQ Workflow: conversion tool -- 8.1 Purpose of the FDL2BPEL Conversion Tool -- 8.2 Scope of the conversion tool -- 8.2.1 Usage of the conversion tool -- 8.2.2 Files generated by the conversion tool -- 8.3 Mapping FDL constructs to BPEL4WS -- 8.3.1 Mapping FDL invocation interfaces -- 8.3.2 Mapping FDL data structures and data containers -- 8.3.3 Mapping FDL processes to BPEL4WS -- 8.3.4 Mapping an FDL block to BPEL4WS -- 8.3.5 Mapping an FDL subprocess call to BPEL4WS -- 8.3.6 Mapping an FDL program_activity to BPEL4WS -- 8.3.7 Mapping FDL transition conditions to BPEL4WS -- 8.3.8 Mapping an FDL start condition to BPEL4WS -- 8.3.9 Mapping an FDL exit condition to BPEL4WS -- 8.3.10 Mapping FDL activity expiration to BPEL4WS -- Chapter 9. WebSphere MQ Workflow: converting the scenario. ; 9.1 Converting activity implementations -- 9.1.1 Activity implementations used in the scenario -- 9.1.2 Converting other activity implementations -- 9.2 Performing the conversion -- 9.2.1 FDL process to migrate -- 9.2.2 Exporting an FDL process -- 9.2.3 Using the FDL2BPEL Conversion Tool -- 9.2.4 Importing generated BPEL4WS files into WebSphere Studio -- 9.2.5 Modifying the generated BPEL4WS process -- 9.2.6 Testing the modified BPEL4WS process -- Chapter 10. Migrating WebSphere Application Server Enterprise processes -- 10.1 FDML migration wizard -- 10.2 FDML constructs in BPEL4WS -- 10.2.1 Synchronous process -- 10.2.2 Asynchronous process -- 10.2.3 Java, EJB, and service activities -- 10.2.4 Fault handling -- 10.2.5 Receive event -- 10.2.6 Staff -- 10.2.7 Block -- 10.2.8 Loop -- 10.3 Migrating the scenario -- 10.3.1 Validate reference model -- 10.3.2 Reserve hotel reference model -- 10.3.3 Reserve flight reference model -- Part 4 Appendixes -- Appendix A. Additional material -- Locating the Web material -- Using the Web material -- System requirements for downloading the Web material -- How to use the Web material -- Abbreviations and acronyms -- Related publications -- IBM Redbooks -- Online resources -- How to get IBM Redbooks -- Help from IBM -- Index -- Back cover.
• Sommario/riassunto: This IBM Redbooks publication introduces the industry open standard for business processes: Business Process Execution Language for Web Services (BPEL4WS), focusing on the use of BPEL4WS throughout the WebSphere Business Integration product set. Part One introduces the BPEL4WS standard and presents appropriate usage scenarios. The heritage of BPEL4WS as the next generation of Web services and service-oriented architecture is discussed, along with a detailed description of BPEL4WS components. Part Two describes how WebSphere Business Integration Modeler can be used to create high level business process models suitable for business analysts, and explains how these models can be implemented as fully functional BPEL4WS processes using WebSphere Studio Application Developer Integration Edition . This creates a BPEL4WS process suitable for deployment to WebSphere Business Integration Server Foundation . A sample scenario with step-by-step instructions is provided. Part Three describes migration considerations for existing business process implementations. Migration considerations and tools for WebSphere Application Server Enterprise FDML processes are discussed. The reuse of WebSphere MQ Workflow process logic in BPEL4WS is also described. Step-by-step instructions are provided for both scenarios.
• Titolo autorizzato: BPEL4WS business processes with WebSphere Business Integration
• Formato: Materiale a stampa
• Livello bibliografico: Monografia
• Lingua di pubblicazione: Inglese
• Record Nr.: 9910824232403321
• Lo trovi qui: Univ. Federico II
• Serie: IBM redbooks.