2 options
WebSphere application server network deployment V6 : high availability solutions / Birgit Roehm et al.
- Format:
- Book
- Author/Creator:
- Barrett, Joan.
- Series:
- IBM redbooks.
- IBM redbooks
- Language:
- English
- Subjects (All):
- Application software.
- WebSphere.
- Physical Description:
- 1 online resource (654 p.)
- Place of Publication:
- Research Triangle Park, NC : IBM, International Technical Support Organization, 2005.
- Language Note:
- English
- Contents:
- Front cover
- Contents
- Notices
- Trademarks
- Preface
- The team that wrote this redbook
- Become a published author
- Comments welcome
- Part 1 High availability concepts
- Chapter 1. Understanding high availability concepts
- 1.1 Process availability and data availability
- 1.1.1 Clustering for high availability
- 1.2 Availability definition
- 1.2.1 Levels of availability
- 1.2.2 Availability matrix
- 1.2.3 Causes of downtime
- 1.2.4 Possible single points of failure in the WebSphere system
- 1.2.5 HA technologies for WebSphere system components
- 1.2.6 Levels of WebSphere system availability
- 1.2.7 Planning and evaluating your WebSphere HA solutions
- 1.3 Failover terms and mechanisms
- Part 2 WebSphere clustering for HA and HA administration
- Chapter 2. WebSphere Application Server failover and recovery
- 2.1 Introduction to availability
- 2.1.1 Hardware-based high availability
- 2.1.2 Workload management
- 2.1.3 Failover
- 2.1.4 HAManager
- 2.1.5 Session management
- 2.2 WebSphere Application Server clustering
- 2.2.1 Clustering for scalability and failover
- 2.3 WebSphere workload management defined
- 2.3.1 Distributing workloads
- 2.3.2 Benefits
- 2.4 Managing session state among servers
- 2.4.1 HTTP sessions and the session management facility
- 2.4.2 EJB sessions or transactions
- 2.4.3 Server affinity
- 2.5 Web container clustering and failover
- 2.5.1 Session management and failover inside the plug-in
- 2.5.2 Web container failures
- 2.5.3 Web server plug-in failover tuning
- 2.6 EJB container clustering and failover
- 2.6.1 EJB container redundancy
- 2.6.2 EJB bootstrapping considerations
- 2.6.3 EJB client redundancy and bootstrap failover support
- 2.6.4 EJB types, workload management and failover
- 2.6.5 Stateful session bean failover.
- 2.6.6 WebSphere process failures, relationship to EJB processing
- 2.6.7 EJB WLM exceptions
- 2.7 Backup cluster support
- 2.7.1 Runtime behavior of backup clusters
- 2.7.2 Scenario and configuration description
- 2.8 WebSphere cell and cluster setup
- 2.8.1 Security considerations
- 2.8.2 Backup cluster configuration
- 2.8.3 Core group bridge configuration
- 2.8.4 Testing the backup cluster configuration
- 2.8.5 Troubleshooting
- Chapter 3. WebSphere administrative process failures
- 3.1 Introduction to process failures
- 3.2 Deployment Manager failures
- 3.2.1 Configuration management
- 3.2.2 Node Agent
- 3.2.3 Application server
- 3.2.4 Naming server
- 3.2.5 Security service
- 3.2.6 Application clients
- 3.2.7 Synchronization Service and File Transfer Service
- 3.2.8 RAS Service and PMI monitoring
- 3.2.9 Administrative clients
- 3.2.10 Enhancing Deployment Manager availability
- 3.3 Node Agent failures
- 3.3.1 Application servers
- 3.3.2 Deployment Manager
- 3.3.3 Security service
- 3.3.4 Naming server
- 3.3.5 Application clients
- 3.3.6 Synchronization service and File transfer service
- 3.3.7 RAS service, PMI and monitoring
- 3.3.8 Administrative clients
- 3.3.9 Enhancing Node Agent availability
- 3.4 Restarting WebSphere processes as an OS service
- 3.5 Enhancing WebSphere process availability using clustering software
- Chapter 4. High availability system administration
- 4.1 Introduction to high availability
- 4.1.1 System setup for the administration scenarios
- 4.2 Starting or stopping application servers and the Web server plug-in retry interval
- 4.3 Replacing hardware
- 4.3.1 Removing the node from the cell
- 4.3.2 Installing and configuring the new hardware or LPAR
- 4.4 Hardware upgrades
- 4.5 Installing WebSphere refresh packs
- 4.5.1 Downloading support packs.
- 4.5.2 The Update Installer for WebSphere Software
- 4.5.3 WebSphere Application Server for distributed platforms
- 4.5.4 WebSphere Application Server for OS/400
- 4.5.5 WebSphere Application Server for z/OS
- 4.5.6 Using the Update Installer
- 4.6 Sample wsadmin scripts for administration tasks
- Chapter 5. High availability application administration
- 5.1 Administering applications in an HA environment
- 5.1.1 Availability while updating an application
- 5.1.2 System capacity
- 5.2 Concepts
- 5.2.1 Persistence layer
- 5.2.2 Application update types
- 5.3 Topologies
- 5.3.1 Multiple cells environment
- 5.3.2 Single cell, multiple clusters
- 5.3.3 Single cell, single cluster
- 5.3.4 Topologies and update types
- 5.4 Application administration
- 5.4.1 Restarting an application
- 5.4.2 Rollout update (new feature of WebSphere V6)
- 5.4.3 Update types: major release or upgrade
- 5.4.4 Update type: bugfix release
- Part 3 WebSphere HAManager
- Chapter 6. WebSphere HAManager
- 6.1 Introduction to the HAManager
- 6.2 Core group
- 6.2.1 Core group coordinator
- 6.2.2 Transport buffer
- 6.2.3 Distribution and Consistency Services
- 6.2.4 Core group policy
- 6.2.5 Match criteria
- 6.2.6 Transport type
- 6.3 High availability group
- 6.3.1 State change of high availability group members
- 6.4 Discovery of core group members
- 6.5 Failure Detection
- 6.5.1 Active failure detection
- 6.5.2 TCP KEEP_ALIVE
- 6.6 JMS high availability
- 6.7 Transaction Manager high availability
- 6.7.1 Transaction Manager HA of previous versions of WebSphere
- 6.7.2 Hot-failover of Transaction Manager using shared file system
- 6.7.3 Hot-failover of transaction logs using external HA software
- 6.7.4 File System Locking Protocol Test
- Part 4 Platform specific information, IBM Eserver iSeries and zSeries.
- Chapter 7. WebSphere HA on IBM Eserver iSeries
- 7.1 Introduction to iSeries HA
- 7.1.1 WebSphere Network Deployment: High availability for WebSphere processes
- 7.1.2 iSeries clustering: High availability for other critical resources in the application path
- 7.1.3 Auxiliary Storage Pools (ASP)
- 7.1.4 Switchable disk pools (independent ASPs)
- 7.1.5 Cross-site mirroring
- 7.1.6 Cluster resource groups
- 7.1.7 Device domains
- 7.2 Sample scenario configuration
- 7.2.1 Create independent disk pool
- 7.2.2 Configuring the cluster and resource group objects
- 7.2.3 Configuring cross-site mirroring
- 7.2.4 Restoring the WebSphere application database into the independent ASP
- 7.2.5 Creating a J2C authentication alias
- 7.2.6 WebSphere data source configuration
- 7.2.7 Messaging engine datastore
- 7.2.8 Configuring iSeries TCP/IP settings
- 7.3 Transaction Manager configuration
- 7.4 Reference material
- Chapter 8. WebSphere HA on z/OS
- 8.1 zSeries Parallel Sysplex
- 8.2 WebSphere V6.0.1 for z/OS topology overview
- 8.2.1 Base application server on z/OS
- 8.2.2 Network Deployment on a z/OS LPAR
- 8.2.3 Network Deployment in a Parallel Sysplex environment
- 8.2.4 Mixed platform cells
- 8.3 z/OS workload management and WebSphere workload management
- 8.4 Distributing HTTP and IIOP requests to different systems within a Parallel Sysplex
- 8.4.1 Sysplex Distributor
- 8.5 Failover options for WebSphere Application Server V6 on z/OS
- 8.5.1 ARM and PRR
- 8.5.2 High Availability manager (HAManager)
- 8.6 Transaction logging and recovery
- 8.6.1 A word on 2-Phase Commit (2PC)
- 8.6.2 RRS
- 8.6.3 XA transactions
- 8.7 HTTP session and stateful session bean failover
- 8.7.1 HTTP session failover
- 8.7.2 Stateful session bean failover
- 8.8 JMS failover
- 8.9 DB2 data sharing
- 8.10 WebSphere MQ for z/OS high availability.
- 8.11 A sample high availability configuration
- 8.12 Hardware, software, and application upgrade
- 8.13 WebSphere Application Server for Linux on zSeries
- 8.14 Reference
- Part 5 Using external clustering software
- Chapter 9. Configuring WebSphere Application Server for external clustering software
- 9.1 Introduction
- 9.1.1 IP-based cluster failover versus non-IP based cluster failover
- 9.1.2 High availability configuration types
- 9.1.3 Failover terms and mechanisms
- 9.2 Standard practice
- 9.2.1 Gathering non-functional requirements
- 9.2.2 Choosing the HA configuration type
- 9.2.3 Configuring the environment: WebSphere Application Server binaries and profiles
- 9.2.4 Testing
- 9.3 Deployment Manager high availability
- 9.3.1 Preparing
- 9.3.2 Installing WebSphere Application Server Network Deployment
- 9.3.3 Configuring the clustering software
- 9.4 Node Agent and application server high availability
- 9.4.1 Preparing
- 9.4.2 Installing WebSphere Application Server Network Deployment
- 9.4.3 Configuring the clustering software
- 9.5 Common advanced topology
- 9.5.1 Connecting to a remote database
- 9.5.2 Connecting to a remote security service, such as LDAP
- 9.5.3 Connecting to a remote messaging engine
- 9.6 Transaction Manager failover with No Operation policy
- 9.6.1 Prerequisites for Transaction Manager with NoOP policy
- 9.6.2 Transaction Manager with No Operation policy scenario
- 9.6.3 Configuring WebSphere for TM No Operation policy
- 9.6.4 Configuring external clustering software for Transaction Manager No Operation policy recovery
- 9.7 Default messaging provider failover with No Operation policy
- 9.7.1 Prerequisites for default messaging provider with NoOP policy
- 9.7.2 Default messaging provider with No Operation policy scenario.
- 9.7.3 Configuring WebSphere for default messaging provider No Operation policy.
- Notes:
- "October 2005".
- Includes index.
- OCLC:
- 560078938
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.