3 options
Implementing and administering WebSphere business integration server / [Geert Van de Putte ... et al.].
- Format:
- Book
- Series:
- IBM redbooks.
- IBM redbooks
- Language:
- English
- Subjects (All):
- Electronic commerce.
- Business enterprises--Data processing.
- Business enterprises.
- Business enterprises--Computer networks--Management.
- WebSphere.
- Physical Description:
- xiv, 432 p. : ill.
- Edition:
- 1st ed.
- Place of Publication:
- Research Triangle Park, NC : IBM, International Technical Support Organization, 2004.
- Language Note:
- English
- System Details:
- text file
- Summary:
- This IBM Redbooks publication describes the big phases in a business integration project. First, we discuss the planning and system design phase for a business integration infrastructure that should be able to support several business integration projects. When the planning and design is complete, we discuss the implementation of several run-time engines of a WebSphere Business Integration Server V4.2.2 implementation. We also cover the implementation steps for a development environment and an administration environment. The next phase is the development and testing of a business integration solution that can be deployed within the infrastructure. The integration solution combines the powers of the three run-time engines of WebSphere Business Integration Server V4.2.2, providing for human interaction, straight-through processing, and message brokering and aggregation. The last phase of a business integration project is the process of moving the solution to production and determining how to manage this solution, addressing such issues as how to stop and start components in a coordinated way, and where to find answers for run-time problems. The book ends with a discussion about performance tuning that is focused on WebSphere InterChange Server V4.2.2.
- Contents:
- Front cover
- Contents
- Notices
- Trademarks
- Preface
- The team that wrote this book
- Become a published author
- Comments welcome
- Part 1 Implementing a BI solution framework
- Chapter 1. The state of business integration technology
- 1.1 Overview
- 1.2 The evolution of business integration technology
- 1.3 Integration capabilities
- Chapter 2. Building an implementation plan
- 2.1 WebSphere Business Integration Server overview
- 2.1.1 WebSphere MQ Workflow: long-running processes
- 2.1.2 WebSphere Interchange Server: objects and their interactions
- 2.1.3 WebSphere BI Message Broker: routing and reformatting
- 2.1.4 WebSphere Business Integration Adapters: connectivity
- 2.1.5 Base components
- 2.1.6 Bringing it all together
- 2.2 Business requirements
- 2.2.1 Implementation of use cases as required
- 2.2.2 Agility
- 2.2.3 Ability to integrate existing services
- 2.2.4 Business monitoring
- 2.3 Quality of service requirements
- 2.3.1 Performance
- 2.3.2 Availability
- 2.4 System design for redbook scenario
- 2.5 Planning considerations
- 2.5.1 WebSphere MQ Workflow
- 2.5.2 InterChange Server
- 2.5.3 WebSphere BI Message Broker
- 2.6 Planning documents
- Chapter 3. Implementation of the runtime components
- 3.1 WebSphere MQ Workflow installation and configuration
- 3.1.1 Install WebSphere MQ Workflow Runtime
- 3.1.2 Configure WebSphere MQ Workflow
- 3.1.3 Verify WebSphere MQ Workflow server
- 3.2 InterChange Server installation and configuration
- 3.2.1 Prerequisite tasks
- 3.2.2 Installation of WebSphere BI Server components
- 3.2.3 Configuration of the InterChange Server
- 3.2.4 Verifying the configuration
- 3.3 Installing WebSphere Business Integration Adapters
- 3.4 WebSphere BI Message Broker installation and configuration
- 3.4.1 Prerequisite software
- 3.4.2 Installation.
- 3.4.3 Create WebSphere BI Message Broker infrastructure
- 3.5 Summary
- Chapter 4. Implementation of client components
- 4.1 Implementing WebSphere MQ Workflow Web Client
- 4.1.1 Setting up the application server machine on Windows
- 4.1.2 WebSphere MQ Workflow Web client installation
- 4.1.3 WebSphere MQ Workflow Web client configuration
- 4.1.4 WebSphere MQ Workflow Web client validation
- 4.2 Implementing a development client
- 4.2.1 Implementing a WebSphere MQ Workflow development environment
- 4.2.2 Implementing a WebSphere InterChange Server development environment
- 4.2.3 Implementing a WebSphere BI Message Broker development environment
- 4.3 Implementing a management client
- 4.3.1 Implementing a WebSphere MQ Workflow management client
- 4.3.2 Implementing a management client for InterChange Server
- 4.3.3 Implementing a management client for WebSphere BI Message Broker
- 4.4 Summary
- Part 2 Implementing business integration solution components
- Chapter 5. Application scenario and solution design
- 5.1 Business scenario
- 5.1.1 Customer order process
- 5.1.2 Entry audit process
- 5.1.3 Subprocesses
- 5.2 What we implemented
- Chapter 6. Implementing a process model in WebSphere MQ Workflow
- 6.1 Overview
- 6.2 Creating the process model
- 6.2.1 Creating data structures
- 6.2.2 Creating program objects
- 6.2.3 Creating the process diagram
- 6.2.4 Creating data mapping
- 6.3 Deploying the process flow in Runtime server
- 6.4 Validating the workflow process flow
- 6.5 Update activities to integrate automated activities
- 6.5.1 Create user-defined program execution servers
- 6.5.2 Create program objects for InterChange Server
- 6.5.3 Update activities in process diagram
- Chapter 7. Sales order management in InterChange Server
- 7.1 Introduction
- 7.2 Application database ORDERMGT.
- 7.3 Create business objects
- 7.3.1 DB2 application-specific business object
- 7.3.2 WebSphere MQ Workflow application-specific business object
- 7.3.3 Generic business object
- 7.4 Create maps
- 7.4.1 From ASBO MQWF_Order_Form to GBO Order
- 7.4.2 From the GBO Order to the ASBO JDBC_ORDERS
- 7.4.3 From ASBO JDBC_ORDERS to GBO Order
- 7.4.4 From GBO Order to ASBO MQWF_Form_OrderDetail
- 7.5 Adapter configuration
- 7.5.1 Importing the adapters in System Manager
- 7.5.2 WebSphere MQ Workflow adapter configuration
- 7.5.3 JDBC adapter configuration
- 7.6 Configure meta-objects for the data handler
- 7.7 Collaboration template
- 7.8 Collaboration object
- 7.9 Create a new user project
- 7.10 Deploy user project
- 7.11 Runtime validation of infrastructure
- 7.12 Runtime validation of application
- 7.12.1 Using the Visual Test Connector
- 7.12.2 Using the WebSphere MQ Workflow Web client
- Chapter 8. Part replenishment in WebSphere BI Message Broker
- 8.1 Overview
- 8.2 Implementation steps
- 8.3 WebSphere MQ configuration
- 8.4 Implementation of the fan-out and fan-in flow
- 8.4.1 Building the graphical flow
- 8.4.2 Developing ESQL in the Compute nodes
- 8.5 Supporting message flow
- 8.6 Deployment and testing of the message flow
- 8.7 Testing from the Web Client
- Part 3 Managing a business integration solution
- Chapter 9. Handling deployment and change
- 9.1 Preparing for production deployment
- 9.1.1 Preparing an WebSphere MQ Workflow solution for production
- 9.1.2 Preparing a message broker solution for production
- 9.1.3 Preparing InterChange Server solutions for production
- 9.2 Managing runtime-specific changes
- 9.2.1 Changes to WebSphere MQ Workflow process model
- 9.2.2 Changes to a message flow
- 9.2.3 Changes to a collaboration
- 9.3 Managing interface changes.
- 9.3.1 Changes to the data structure used to invoke the collaboration
- 9.3.2 Changes to the data structure used to invoke the message flow
- 9.4 Summary
- Chapter 10. Operational aspects of a WebSphere Business Integration Server implementation
- 10.1 Starting and stopping components
- 10.2 Management and problem determination tools
- 10.2.1 Sources of information
- 10.2.2 Obtaining additional information
- Chapter 11. Tuning a WebSphere Business Integration Server infrastructure
- 11.1 Introduction
- 11.2 General performance checklist
- 11.3 InterChange Server
- 11.3.1 Configure threads in collaborations and adapter controllers
- 11.3.2 Use caches for maps and collaborations (instance reuse)
- 11.3.3 Configure threading for CORBA / IIOP
- 11.3.4 Configure database connection pools
- 11.3.5 Setting flow control queue sizes
- 11.3.6 Turn off component tracing
- 11.3.7 Turn off event sequencing for Server Access Interface
- 11.4 WebSphere Business Integration Adapters
- 11.4.1 Configure poll frequency and poll quantity
- 11.4.2 Multiple WebSphere MQ listener threads
- 11.5 Database (general)
- 11.5.1 Place database tablespaces on a fast disk subsystem
- 11.5.2 Size database cross-referencing tables correctly
- 11.5.3 Place logs on separate device from table spaces
- 11.6 Database: DB2-specific
- 11.6.1 Maintain current indexes on tables
- 11.6.2 Update catalog statistics
- 11.6.3 Set bufferpool size correctly
- 11.7 Database: Oracle-specific
- 11.7.1 Set buffer, block, and shared pool area sizes correctly
- 11.7.2 Set processes, Open_Cursors, and IO_Slaves
- 11.7.3 Use dedicated connection if possible
- 11.7.4 Query optimization
- 11.8 WebSphere MQ
- 11.8.1 Place MQ logs on fast disk subsystem
- 11.8.2 Monitor message queue depth
- 11.8.3 Configure WebSphere MQ log files and buffer pages
- 11.9 Java.
- 11.9.1 Set heap size and nursery size for efficient garbage collection
- 11.9.2 Set AIX threading parameters
- 11.9.3 Use HotSpot server instead of client
- 11.9.4 Setting thread stack size if using many threads
- 11.9.5 Reduce or increase heap size if out-of-memory errors occur
- 11.10 Large objects
- 11.10.1 Factors affecting large object size processing
- 11.10.2 Mitigating large object issues
- 11.11 Tuning other WebSphere BI runtime components
- Appendix A. Hardware and software configuration
- Configuration of client machines
- Configuration of runtime servers
- Appendix B. Additional material
- Locating the Web material
- Using the Web material
- System requirements for downloading and using 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.
- Notes:
- "SG24-7006-00."
- Includes bibliographical references and index.
- OCLC:
- 61447602
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.