Patterns : serial process flows for intra-and inter-enterprise

Patterns serial process flows for intra-and inter-enterprise

The IBM Patterns for e-business are a group of proven, reusable assets. They increase the speed of developing and deploying Web applications. This IBM Redbooks publication focuses on advanced application integration using the Process-focused Application Integration: Serial Process Application patter...

Descripción completa

Detalles Bibliográficos
Autor Corporativo: International Business Machines Corporation. International Technical Support Organization (-)
Otros Autores: Endrei, Mark (-)
Formato: Libro electrónico
Idioma:Inglés
Publicado: Research Triangle Park, NC : IBM International Technical Support Organization 2004.
Edición:1st ed
Colección:IBM redbooks.
Materias:
Electronic commerce > Computer programs.
Business enterprises > Data processing.
Ver en Biblioteca Universitat Ramon Llull:https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009626888106719
Tabla de Contenidos:
  • Front cover
  • Contents
  • Notices
  • Trademarks
  • Preface
  • The team that wrote this redbook
  • Become a published author
  • Comments welcome
  • Part 1 Patterns for e-business
  • Chapter 1. Introduction to Patterns for e-business
  • 1.1 The Patterns for e-business layered asset model
  • 1.2 Using the Patterns for e-business
  • 1.2.1 Selecting a Business, Integration, or Composite pattern, or Custom design
  • 1.2.2 Selecting Application patterns
  • 1.2.3 Reviewing Runtime patterns
  • 1.2.4 Reviewing the Product mappings
  • 1.2.5 Reviewing the guidelines and related links
  • 1.3 Summary
  • Chapter 2. Fundamental concepts in process integration
  • 2.1 The need for a unifying technique
  • 2.1.1 Similarities between intra- and inter-enterprise integration
  • 2.1.2 Summary
  • 2.2 Process integration concepts and notations
  • 2.2.1 Collaboration and interaction
  • 2.2.2 Connectors and adapters
  • 2.2.3 Classification of interaction between subsystems
  • 2.3 QoS capabilities framework
  • 2.3.1 Operability
  • 2.3.2 Availability
  • 2.3.3 Federation
  • 2.3.4 Performance
  • 2.3.5 Security
  • 2.3.6 Standards compliance
  • 2.3.7 Transactionality
  • 2.4 Application patterns for Application Integration
  • 2.5 Application patterns for Extended Enterprise
  • 2.6 Summary
  • Chapter 3. Application Integration pattern
  • 3.1 Using the pattern
  • 3.2 Defining the Application Integration patterns
  • 3.2.1 Business and IT drivers
  • 3.2.2 Context
  • 3.2.3 Solution
  • 3.2.4 Putting the pattern to use
  • 3.2.5 Application Integration considerations
  • 3.2.6 What's next
  • 3.3 Application patterns
  • 3.4 Process-focused Application patterns
  • 3.4.1 Direct Connection Application pattern
  • 3.4.2 Direct Connection: Message Connection variation
  • 3.4.3 Direct Connection: Call Connection variation
  • 3.4.4 Broker Application pattern
  • 3.4.5 Broker: Router variation.
  • 3.4.6 Serial Process Application pattern
  • 3.4.7 Serial Process: Workflow variation
  • 3.4.8 Parallel Process Application pattern
  • 3.4.9 Parallel Process: Workflow variation
  • 3.5 Data-focused Application patterns
  • 3.6 Previous Application Integration patterns
  • Chapter 4. Extended Enterprise pattern
  • 4.1 Using the pattern
  • 4.2 General guidelines
  • 4.2.1 Business and IT drivers
  • 4.2.2 Context
  • 4.2.3 Solution
  • 4.2.4 Putting the pattern to use
  • 4.2.5 What's next
  • 4.3 Application patterns
  • 4.3.1 Exposed Direct Connection Application pattern
  • 4.3.2 Exposed Direct Connection: Message Connection variation
  • 4.3.3 Exposed Direct Connection: Call Connection variation
  • 4.3.4 Exposed Broker Application pattern
  • 4.3.5 Exposed Broker: Router variation
  • 4.3.6 Exposed Serial Process Application pattern
  • 4.3.7 Exposed Serial Process: Workflow variation
  • Chapter 5. Runtime patterns and Product mappings
  • 5.1 Runtime patterns
  • 5.1.1 Node types
  • 5.1.2 Serial Process Runtime pattern
  • 5.1.3 Serial Process: Workflow variation Runtime pattern
  • 5.1.4 Exposed Serial Process Runtime pattern
  • 5.2 Product mappings
  • 5.2.1 Runtime product descriptions
  • 5.2.2 Serial Process product mapping
  • 5.2.3 Serial Process: Workflow variation product mapping
  • 5.2.4 Exposed Serial Process product mapping
  • Part 2 Scenarios and guidelines
  • Chapter 6. Business scenarios used in this book
  • 6.1 Customer overview
  • 6.1.1 Business profile
  • 6.1.2 Business goals
  • 6.1.3 Existing environment
  • 6.1.4 Non-functional requirements
  • 6.2 Intra-enterprise scenarios
  • 6.2.1 Stage one: Internal ordering on demand
  • 6.2.2 Stage two: Internal ordering on demand with approval workflow
  • 6.2.3 Stage three: Ordering on demand with multiple wholesalers
  • 6.3 Inter-enterprise scenarios
  • 6.3.1 Stage four: External ordering on demand.
  • Chapter 7. Technology options
  • 7.1 Flow languages
  • 7.1.1 Flow Definition Language
  • 7.1.2 Flow Definition Markup Language
  • 7.1.3 Business Process Execution Language for Web Services
  • 7.2 Web services
  • 7.2.1 Static and dynamic Web services
  • 7.2.2 Web Services Invocation Framework
  • 7.2.3 Web services and the service-oriented architecture
  • 7.2.4 Web services security
  • 7.2.5 Advantages of Web services
  • 7.2.6 Disadvantages of Web services
  • 7.2.7 Comparing Web services with CORBA and RMI
  • 7.3 Java Message Service
  • 7.3.1 What messaging is
  • 7.3.2 JMS and IBM WebSphere MQ
  • 7.3.3 Advantages of JMS
  • 7.3.4 Disadvantages of JMS
  • Part 3 Application Integration scenarios
  • Chapter 8. Creating a simple serial process
  • 8.1 Business scenario
  • 8.2 Business process model
  • 8.3 Design guidelines
  • 8.3.1 Design overview
  • 8.3.2 Design considerations
  • 8.3.3 Process design model
  • 8.4 Development guidelines
  • 8.4.1 Setting up the development environment
  • 8.4.2 Configuring the Web services connectors
  • 8.4.3 Creating the business objects
  • 8.4.4 Creating the maps
  • 8.4.5 Developing the collaboration template
  • 8.4.6 Creating the collaboration object
  • 8.4.7 Exposing the collaboration as a Web service
  • 8.4.8 Testing the solution
  • 8.5 Runtime guidelines
  • 8.6 Best practices
  • Chapter 9. Creating a process with human interaction
  • 9.1 Business scenario
  • 9.2 Business process model
  • 9.3 Design guidelines
  • 9.3.1 Design overview
  • 9.3.2 Design considerations
  • 9.3.3 Process design model
  • 9.4 Development guidelines
  • 9.4.1 Configuring the JMS connector
  • 9.4.2 Creating the business objects
  • 9.4.3 Creating the maps
  • 9.4.4 Developing the collaboration template
  • 9.4.5 Creating the collaboration object
  • 9.4.6 Exposing the collaboration as a Web service
  • 9.4.7 Testing the solution.
  • Chapter 10. Creating a transactional process
  • 10.1 Business scenario
  • 10.2 Business process model
  • 10.3 Design guidelines
  • 10.3.1 Design overview
  • 10.3.2 Design considerations
  • 10.3.3 Process design model
  • 10.4 Development guidelines
  • 10.4.1 Creating the business objects
  • 10.4.2 Creating the maps
  • 10.4.3 Developing the collaboration template
  • 10.4.4 Creating the collaboration object
  • 10.4.5 Exposing the collaboration as a Web service
  • 10.4.6 Testing the solution
  • 10.5 Best practices
  • Part 4 Extended Enterprise scenarios
  • Chapter 11. Creating an exposed serial process
  • 11.1 Business scenario
  • 11.2 Business process model
  • 11.3 Design guidelines
  • 11.3.1 Design overview
  • 11.3.2 Using firewalls
  • 11.3.3 Web services security
  • 11.3.4 Web services gateway
  • Part 5 Appendixes
  • Appendix A. Scenario lab environment
  • Lab setup
  • Sample application setup
  • Appendix B. 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
  • Other publications
  • Online resources
  • How to get IBM Redbooks
  • Help from IBM
  • Index
  • Back cover.

Ejemplares similares