2 options
Patterns for the edge of network / [Richard Voegeli, Byron Braswell].
- Format:
- Book
- Author/Creator:
- Voegeli, Richard.
- Series:
- IBM redbooks.
- Redbooks
- Language:
- English
- Subjects (All):
- Electronic commerce.
- WebSphere.
- Physical Description:
- 1 online resource (422 p.)
- Edition:
- 1st ed.
- Place of Publication:
- Triangle Park, NC : IBM Redbooks, 2002.
- Language Note:
- English
- Contents:
- Front cover
- Contents
- Notices
- Trademarks
- Preface
- The team that wrote this redbook
- Become a published author
- Comments welcome
- Part 1 Introduction to Patterns
- 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 Selecting Application patterns
- 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. Edge of network Runtime patterns for high availability
- 2.1 High availability principles
- 2.1.1 High availability rules for Runtime environments
- 2.1.2 Redundancy
- 2.1.3 Request distribution
- 2.2 Runtime node types and tiers
- 2.2.1 Runtime nodes
- 2.2.2 Network tiers
- 2.3 Runtime patterns for high availability
- 2.3.1 Application patterns
- 2.3.2 Basic Runtime pattern
- 2.3.3 Basic Runtime pattern variation 1: Single load balancer
- 2.3.4 Basic Runtime pattern variation 2: Load balancer hot standby
- 2.3.5 Basic Runtime pattern variation 3: Mutual high availability
- 2.3.6 Basic Runtime pattern variation 4: wide area load balancing
- Chapter 3. Edge of network Runtime patterns for performance
- 3.1 Performance factors
- 3.2 Enhancing performance with proxy servers
- 3.3 Runtime nodes
- 3.4 Runtime patterns
- 3.4.1 Basic Runtime pattern variation 5: Redirectors
- 3.4.2 Basic Runtime pattern variation 6: separation
- 3.4.3 Basic Runtime pattern variation 7: caching proxy
- 3.5 Where to cache
- Part 2 Runtime patterns: guidelines
- Chapter 4. Technology guidelines
- 4.1 WebSphere Edge Server
- 4.1.1 Components
- 4.1.2 History
- 4.2 Load Balancer
- 4.2.1 Load Balancer forwarding methods
- 4.2.2 Media Access Control (MAC) forwarding.
- 4.2.3 Network Address Translation (NAT) forwarding
- 4.2.4 Network Address Port Translation (NAPT) forwarding
- 4.2.5 Load Balancer High Availability feature
- 4.2.6 Load Balancer Mutual High Availability feature
- 4.2.7 Wide Area Network Dispatcher (WAND)
- 4.2.8 Advisors
- 4.2.9 Metric Server
- 4.3 Caching Proxy
- 4.3.1 Forward proxy
- 4.3.2 Reverse proxy
- 4.3.3 Cache
- 4.4 Considerations for a high availability configuration
- 4.4.1 High availability configuration of nodes
- 4.4.2 Server affinity
- 4.4.3 Failover
- 4.5 WebSphere plug-in
- Chapter 5. Security guidelines
- 5.1 The need for security
- 5.2 Concepts of cryptography and digital certificates
- 5.2.1 Symmetric encryption algorithms
- 5.2.2 Asymmetric encryption algorithms
- 5.2.3 Performance issues of cryptosystems
- 5.2.4 Cryptosystems for data integrity
- 5.2.5 Digital signatures
- 5.2.6 Public Key Infrastructure
- 5.3 Firewall concepts
- 5.3.1 General guidelines for implementing firewalls
- 5.3.2 Firewall categories
- 5.3.3 Hardening
- 5.4 Virtual private network (VPN) and IPSec
- 5.4.1 IPSec
- 5.4.2 Alternative VPN solutions: Layer 2 Tunnelling Protocol
- 5.5 Secure Sockets Layer (SSL)
- 5.5.1 Establishing secure communications with SSL
- 5.5.2 SSL considerations
- 5.5.3 Where to use SSL
- 5.6 Authentication and authorization
- 5.6.1 User authentication
- 5.6.2 User authorization
- 5.7 Authenticating proxy
- 5.7.1 Runtime pattern variation 8: Authenticating proxy
- Part 3 Runtime implementation
- Chapter 6. Common installation and configuration guidelines
- 6.1 Common installation guidelines
- 6.1.1 General guidelines
- 6.1.2 Load Balancer
- 6.1.3 Caching Proxy
- 6.1.4 Proxy CBR
- 6.1.5 DB2 Client
- 6.1.6 Application Server
- 6.2 Common configuration guidelines
- 6.2.1 Aliasing a loopback adapter.
- Chapter 7. Test environment example
- 7.1 Scenario description
- 7.1.1 Overview
- 7.1.2 Traffic flow
- 7.2 Configuration description
- 7.2.1 Databases
- 7.2.2 WebSphere Application Server
- 7.2.3 Load balancer node
- 7.2.4 Testing the environment
- Chapter 8. Sample ASP environment
- 8.1 Scenario description
- 8.1.1 Traffic flow
- 8.1.2 Scalability
- 8.1.3 Naming
- 8.1.4 Node functionalities
- 8.2 Basic configuration description
- 8.2.1 Name resolution
- 8.2.2 DB Server
- 8.2.3 DB Client
- 8.2.4 Application servers
- 8.2.5 HTTP server
- 8.2.6 Caching proxies
- 8.2.7 Load balancers
- 8.3 Configure WebSphere Application Server for local dynacache
- 8.3.1 Web Application Servers
- 8.4 Testing local dynacache
- 8.5 Configure external dynacache
- 8.5.1 Caching proxy servers
- 8.5.2 Web Application Servers
- 8.6 Testing external dynacache
- 8.6.1 Dynamic query responses issue
- Chapter 9. Company environment
- 9.1 Scenario description
- 9.1.1 Traffic flow
- 9.1.2 Scalability
- 9.1.3 Naming
- 9.1.4 Node functionalities
- 9.2 Configuration description
- 9.2.1 Name resolution
- 9.2.2 Database server
- 9.2.3 DB clients
- 9.2.4 Application servers
- 9.2.5 HTTP servers
- 9.2.6 Caching Proxies
- 9.2.7 Load balancers
- 9.3 Testing the environment
- Appendix A. Configuration files
- ASP environment configuration files
- Glossary
- Abbreviations and acronyms
- Related publications
- IBM Redbooks
- Other resources
- Referenced Web sites
- How to get IBM Redbooks
- IBM Redbooks collections
- Index
- Back cover.
- Notes:
- "SG24-6822-00."
- Includes bibliographical references and index.
- OCLC:
- 560313612
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.