Front cover Building Multi-Tier Scenarios for WebSphere Enterprise Applications Architecting an infrastructure for seamless 3-tier integration Developing, deploying, and tooling for interoperability Security, performance, cost, and management views Holger Wunderlich Diego Cardalliaguet Russ Heald Tomokuni Shimizu Dirk Ziesemann ibm.com/redbooks International Technical Support Organization Building Multi-Tier Scenarios for WebSphere Enterprise Applications August 2003 SG24-6956-00 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. First Edition (August 2003) This edition applies to WebSphere Application Server V4.01 for z/OS and OS/390. © Copyright International Business Machines Corporation 2003. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . vii Trademarks . viii Preface . ix The team that wrote this redbook. ix Become a published author . xi Comments welcome. xi Part 1. Integrated and multi-tier solution concepts . 1 Chapter 1. Integrated and multi-tier WebSphere application deployment. 3 1.1 Multi-tiered environment considerations . 4 1.1.1 Today’s e-business infrastructures . 4 1.1.2 Platforms to run e-business applications . 6 1.1.3 Basic architectural considerations. 8 1.1.4 Separating Web components from business logic . 9 1.2 Concepts and building blocks for hybrid WebSphere solutions . 11 1.2.1 Using the Patterns approach . 11 1.2.2 Mapping the patterns to our identified motivations . 12 1.3 An introduction to tiers and architectures . 14 1.3.1 Introducing multi-tier architectures . 14 1.3.2 Multiple logical and physical tiers . 16 1.3.3 The network layer . 23 1.4 Application architecture and packaging . 25 1.4.1 Model-View-Controller (MVC) design pattern . 27 1.4.2 Application packaging . 29 1.5 Decision guidelines for handling Web applications . 30 1.5.1 Deployment choices . 31 Chapter 2. Integrated and hybrid WebSphere application deployment scenarios . 33 2.1 Static Web component relocation . 34 2.1.1 Architectural elements for static Web content acceleration . 34 2.2 Dynamic component relocation. 36 2.2.1 Application elements. 36 2.2.2 Overview of hybrid deployment assessment criteria. 37 2.2.3 Options for logical application separation . 42 2.2.4 Options for physical application separation. 47 2.2.5 Options for J2EE inter-component communication. 54 2.3 Evaluation criteria for remote component and EIS access . 58 2.3.1 Performance . 59 2.3.2 Availability . 64 2.3.3 Security . 64 2.3.4 Transaction integrity . 65 2.3.5 Infrastructure criteria . 67 2.3.6 Development and deployment criteria. 68 2.3.7 Systems management . 72 2.3.8 Strategic considerations . 73 Chapter 3. Component interaction characteristics . 75 © Copyright IBM Corp. 2003. All rights reserved. iii 3.1 Connection types . 76 3.1.1 Cross-reference table . 76 3.2 RMI/IIOP access to remote enterprise beans . 76 3.2.1 Performance . 77 3.2.2 Availability . 78 3.2.3 Security . 78 3.2.4 Transaction integrity . 79 3.2.5 Infrastructure. 79 3.2.6 Development and deployment . 80 3.2.7 Systems management . 81 3.2.8 Strategic considerations . 81 3.3 JDBC access to DB2. 82 3.3.1 DB2 Connect. 82 3.3.2 Performance . 83 3.3.3 Availability . 84 3.3.4 Security . 84 3.3.5 Transaction integrity . 87 3.3.6 Infrastructure. 87 3.3.7 Development and deployment . 87 3.3.8 Systems management . 90 3.3.9 Strategic considerations . 90 3.4 JCA access to CICS . 90 3.4.1 CICS Transaction Gateway. 92 3.4.2 Performance . 92 3.4.3 Availability . 93 3.4.4 Security . 94 3.4.5 Transaction integrity . 95 3.4.6 Infrastructure. 96 3.4.7 Development and deployment . 96 3.4.8 Systems management . ..