3 options
Patterns : flexible self-service applications using process choreography.
- Format:
- Book
- Author/Creator:
- International Business Machines Corporation, International Technical Support Organization Staff, Corporate Author.
- Series:
- IBM redbooks.
- IBM redbooks
- Language:
- English
- Subjects (All):
- Electronic commerce.
- Business--Data processing.
- Business.
- Software patterns.
- Physical Description:
- xiv, 274 p. : ill.
- Edition:
- 1st ed.
- Place of Publication:
- [S.l.] : IBM, International Technical Support Organization, 2004.
- Language Note:
- English
- Contents:
- 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. Patterns for e-business
- 1.1 The Patterns for e-business layered asset model
- 1.2 How to use the Patterns for e-business
- 1.2.1 Select a Business, Integration, or Composite pattern, or a Custom design
- 1.2.2 Select an Application pattern
- 1.2.3 Review Runtime patterns
- 1.2.4 Review Product mappings
- 1.2.5 Review guidelines and related links
- 1.3 Summary
- Chapter 2. Self-Service business pattern
- 2.1 Self-service applications
- 2.2 Self-Service application patterns
- 2.3 Application patterns used in this book
- 2.4 Decomposition application pattern
- 2.4.1 Business and IT drivers
- 2.4.2 Solution
- 2.4.3 Considerations
- 2.4.4 Guidelines for use
- 2.4.5 Benefits
- 2.4.6 Limitations
- 2.4.7 Putting the Application pattern to use
- 2.5 Agent application pattern
- 2.5.1 Business and IT drivers
- 2.5.2 Solution
- 2.5.3 Guidelines for use
- 2.5.4 Benefits
- 2.5.5 Limitations
- 2.5.6 Putting the Application pattern to use
- 2.6 Agent: Federation variation
- Chapter 3. Runtime patterns and product mappings
- 3.1 An introduction to the node types
- 3.1.1 Web application server node
- 3.1.2 User node
- 3.1.3 Public Key Infrastructure (PKI) front-end
- 3.1.4 Domain Name System (DNS) node
- 3.1.5 Protocol firewall node
- 3.1.6 Domain firewall node
- 3.1.7 Directory and security services node
- 3.1.8 Existing applications and data node
- 3.1.9 Web server redirector node
- 3.1.10 Application server node
- 3.1.11 Integration server node
- 3.1.12 Process manager node
- 3.1.13 Data Server / Services node
- 3.2 Runtime patterns
- 3.2.1 Decomposition runtime patterns
- 3.2.2 Agent runtime pattern
- 3.3 Product mappings.
- 3.3.1 Decomposition product mapping
- 3.3.2 Agent product mapping
- 3.4 Runtime product overview
- 3.4.1 WebSphere Application Server
- 3.4.2 IBM HTTP Server and Web server plug-in
- 3.4.3 IBM Directory Server V5.2
- 3.4.4 WebSphere Business Integration Server Foundation
- 3.4.5 IBM DB2 Universal Database product family
- 3.4.6 DB2 Information Integrator portfolio
- Part 2 Guidelines
- Chapter 4. Technology options
- 4.1 Web services
- 4.1.1 Static and dynamic Web services
- 4.1.2 JAX-RPC
- 4.1.3 Web services and the service-oriented architecture
- 4.1.4 Web services security
- 4.1.5 For more information on Web services
- 4.2 Flow languages
- 4.2.1 Flow Definition Language
- 4.2.2 Flow Definition Markup Language
- 4.2.3 Business Process Execution Language for Web Services
- 4.3 Java Connector Architecture (JCA)
- 4.4 Java Message Service
- 4.4.1 What messaging is
- 4.4.2 JMS and IBM WebSphere MQ
- 4.4.3 Advantages of JMS
- 4.4.4 Disadvantages of JMS
- 4.5 Business Rule Bean framework
- 4.6 Information integration
- 4.6.1 Data consolidation
- 4.6.2 Distributed access
- 4.6.3 For more information
- Chapter 5. Designing business processes
- 5.1 What is a "business process"?
- 5.2 Modeling business processes
- 5.3 Process choreographer programming model
- 5.4 Developing business processes
- 5.4.1 Elements of a business process
- 5.4.2 Business process clients
- 5.4.3 Enterprise services
- 5.4.4 Deployment of business processes
- 5.5 Design guidelines for business processes
- 5.5.1 Non-interruptible versus interruptible processes
- 5.5.2 Synchronous versus asynchronous processes
- 5.5.3 Human interaction
- 5.5.4 Flow versus sequence structures
- 5.5.5 Process security
- 5.5.6 Parallel processing
- 5.5.7 Audit trails
- 5.5.8 Business process monitoring
- 5.5.9 Performance and process analysis.
- 5.5.10 Exception situations
- 5.5.11 Business rules
- 5.6 Using an Operational Data Store (ODS)
- 5.6.1 Why use an ODS?
- 5.6.2 ODS design issues
- 5.6.3 Accessing an ODS from a business process
- 5.7 For more information
- Part 3 Scenarios
- Chapter 6. Building business processes with WebSphere Studio
- 6.1 WebSphere Studio Application Developer Integration Edition
- 6.1.1 Business integration tools
- 6.2 Building business processes
- 6.2.1 Create a service project
- 6.2.2 Create a business process
- 6.2.3 Update the process WSDL
- 6.2.4 Add activities
- 6.2.5 Add variables
- 6.2.6 Add partner links
- 6.3 Deploying and testing business processes
- 6.3.1 Generate the deploy code
- 6.3.2 Create the test server environment
- 6.3.3 Test the process with the Web Client
- 6.4 For more information
- Chapter 7. Business scenario overview
- 7.1 Customer overview
- 7.1.1 Business profile
- 7.1.2 Business goals
- 7.1.3 Existing environment
- 7.1.4 Non-functional requirements
- 7.2 Scenario overview
- 7.2.1 Spot Loan scenario: online funds transfer with spot loan
- 7.2.2 Staff Assisted Loan scenario: pre-approval for loans
- 7.2.3 Extended Spot Loan scenario: extended loan approval data
- Chapter 8. Decomposition application pattern
- 8.1 Business scenario
- 8.2 Business process model
- 8.3 Design guidelines
- 8.4 Development guidelines
- 8.4.1 Process overview
- 8.4.2 Preparing the workspace
- 8.4.3 Process interface definition
- 8.4.4 Banking partner interface
- 8.4.5 Business process activities and links
- 8.4.6 Triggering the business rule
- 8.5 Deploying and testing the business process
- Chapter 9. Decomposition application pattern with human interaction
- 9.1 Business scenario
- 9.2 Business process model
- 9.3 Design guidelines
- 9.4 Development guidelines
- 9.4.1 Process overview.
- 9.4.2 Preparing the workspace
- 9.4.3 Process interface definition
- 9.4.4 Banking partner interface
- 9.4.5 Business process activities and links
- 9.5 Deploying and testing the business process
- Chapter 10. Agent application pattern
- 10.1 Business scenario
- 10.2 Business process model
- 10.3 Design guidelines
- 10.3.1 ODS implementation
- 10.3.2 ODS access
- 10.4 Development guidelines
- 10.4.1 Process overview
- 10.4.2 Process development
- 10.5 Deploying and testing the business process
- Part 4 Appendixes
- Appendix A. Setting up and installing the scenarios
- Setting up the environment
- Install WebSphere Studio
- Using the sample applications
- Installing and using the Spot Loan scenario
- Installing and using the Staff Assisted Loan scenario
- Installing and using the Extended Spot Loan scenario
- Building a service interface for an EJB
- Appendix B. Business rule beans
- Preparing to use Business Rule Beans
- Update the server properties
- Create the BRBean database
- Running the Rule Management Application
- Define business rules
- Spot Loan scenario
- qualifyForSpotLoan() method
- BankRules/LevelRule
- LevelAssessor.java
- Staff Assisted Loan scenario
- needManagerApproval() method
- BankRules/RiskRule
- RiskAssessor.java
- Extended Spot Loan scenario
- Appendix C. Additional material
- Locating the Web material
- Using the Web material
- How to use the Web material
- Related publications
- IBM Redbooks
- Other publications
- Online resources
- How to get IBM Redbooks
- Help from IBM
- Index
- Back cover.
- Notes:
- "SG24-6322-00."
- "August 2004."
- Includes bibliographical references and index.
- OCLC:
- 137342153
The Penn Libraries is committed to describing library materials using current, accurate, and responsible language. If you discover outdated or inaccurate language, please fill out this feedback form to report it and suggest alternative language.