08031nam 2200661Ia 450 991081646840332120200520144314.0(CKB)1000000000243572(OCoLC)137342172(CaPaEBR)ebrary10112541(SSID)ssj0000281958(PQKBManifestationID)11193352(PQKBTitleCode)TC0000281958(PQKBWorkID)10317014(PQKB)11654333(Au-PeEL)EBL3306537(CaPaEBR)ebr10112541(CaSebORM)0738493600(MiAaPQ)EBC3306537(OCoLC)811554772(OCoLC)ocn811554772 (EXLCZ)99100000000024357220060117d2005 uy 0engurcn|||||||||txtccrMigrating applications from microsoft DNA to IBM WebSphere /Edward Oguejiofor et alResearch Triangle Park, N.C. IBM, International Technical Support Organization20051 online resource (342 p.) Redbooks"August 2005."0-7384-9360-0 Includes bibliographical references and index.Front cover -- Contents -- Notices -- Trademarks -- Preface -- What this book is about -- What this book is not about -- The target audience -- Structure of this book -- The team that wrote this redbook -- Become a published author -- Comments welcome -- Part 1 Preparing for migration -- Chapter 1. Setting the migration scope -- 1.1 Introduction to migration stages -- 1.2 Migration scope considerations -- 1.2.1 Defining your migration objectives and requirements -- 1.2.2 Taking inventory of your migration scenario -- 1.2.3 Identifying migration skills gaps -- 1.3 Migration scope definition -- 1.3.1 Defining the solution scope -- 1.3.2 Defining the project scope -- 1.3.3 Creating the migration scope -- 1.4 Chapter summary -- 1.4.1 Migration scope recommendations -- 1.4.2 Where to get training information -- Chapter 2. Migration strategies -- 2.1 Introduction to migration strategy -- 2.2 Migration considerations -- 2.2.1 Which architecture topics to consider -- 2.2.2 What transition topics to consider -- 2.3 Analyzing your data -- 2.3.1 Architecture strategy analysis -- 2.3.2 Transition strategy analysis -- 2.4 Chapter summary -- 2.4.1 Migration strategy recommendations -- Part 2 Migration how to -- Chapter 3. Architecture migration -- 3.1 Introduction -- 3.2 Windows DNA architecture overview -- 3.2.1 N-tier architectures with DNA -- 3.2.2 Presentation tier -- 3.2.3 Business logic tier -- 3.2.4 Data resource tier -- 3.2.5 Technologies supporting the DNA architecture -- 3.3 Overview of the WebSphere platform -- 3.3.1 The WebSphere family -- 3.3.2 Overview of the J2EE platform -- 3.3.3 J2EE n-tier architecture -- 3.3.4 J2EE presentation tier -- 3.3.5 J2EE business logic tier -- 3.3.6 J2EE data resources tier -- 3.3.7 Technologies supporting the J2EE architecture -- 3.4 Comparison of Windows DNA and WebSphere/J2EE -- 3.4.1 System model.3.4.2 Component model -- 3.4.3 Persistence -- 3.4.4 Transactions -- 3.4.5 Security -- 3.5 Migrating your Windows DNA architecture to J2EE -- 3.5.1 Application model -- 3.5.2 Architecture model -- 3.6 Chapter summary -- 3.6.1 Architecture migration recommendations -- 3.6.2 Where to get more information -- Chapter 4. Development environment migration -- 4.1 Introduction -- 4.1.1 Software development as a business process -- 4.1.2 Introduction to business driven development -- 4.1.3 Application development imperatives -- 4.2 Overview of the Visual Studio Suite -- 4.2.1 The Visual Studio integrated development environments -- 4.2.2 Visual Studio tools -- 4.3 Introduction to IBM Software Development Platform -- 4.4 Migrating to IBM Software Development Platform -- 4.4.1 Requirements and analysis -- 4.4.2 Design and construction -- 4.4.3 Software quality -- 4.4.4 Software configuration management -- 4.4.5 Process and portfolio management -- 4.5 Chapter summary -- 4.5.1 Development platform migration recommendations -- 4.5.2 Where to get more information -- Chapter 5. Application migration -- 5.1 Introduction -- 5.2 Presentation tier -- 5.2.1 Windows DNA presentation tier technologies -- 5.2.2 WebSphere/J2EE presentation tier technologies -- 5.2.3 Comparison of ASP and JSP technologies -- 5.2.4 Client-side programming -- 5.2.5 Server-side programming -- 5.3 Business logic tier -- 5.3.1 Interaction patterns -- 5.3.2 Messaging and queuing -- 5.3.3 Threading -- 5.3.4 Transactions -- 5.4 Data resource tier -- 5.4.1 Windows DNA data resource technologies -- 5.4.2 WebSphere data resource technologies -- 5.5 Chapter summary -- 5.5.1 Presentation tier migration recommendations -- 5.5.2 Business logic tier migration recommendations -- 5.5.3 Data resource tier migration recommendations -- 5.5.4 Where to get more information -- Chapter 6. Runtime migration.6.1 Introduction -- 6.1.1 Key concepts -- 6.1.2 Clustering -- 6.2 Microsoft clustering solution -- 6.2.1 Network Load Balancer (NLB) -- 6.2.2 Component Load Balancer (CLB) -- 6.2.3 Microsoft Cluster Server (MSCS) -- 6.3 Introduction to WebSphere Application Server family -- 6.3.1 Stand-alone server configuration -- 6.3.2 Distributed server configuration -- 6.4 IBM WebSphere clustering solution -- 6.4.1 Workload Management -- 6.4.2 Failover -- 6.5 Migrating Windows cluster to WebSphere -- 6.5.1 Migrating clustering in the presentation tier -- 6.5.2 Migrating clustering in the business logic tier -- 6.5.3 Migrating clustering in the resource layer -- 6.6 Security -- 6.6.1 Java Security Model -- 6.6.2 Windows Security Services -- 6.6.3 Authentication -- 6.6.4 Authorization -- 6.6.5 Administration/configuration -- 6.6.6 Web content security -- 6.6.7 Enterprise JavaBeans Security -- 6.7 Chapter summary -- 6.7.1 Runtime migration best practices and recommendations -- 6.7.2 Where to get more information -- Part 3 Appendixes -- Abbreviations and acronyms -- Related publications -- IBM Redbooks -- Other publications -- Online resources -- How to get IBM Redbooks -- Help from IBM -- Index -- Back cover.This IBM Redbooks publication is about migrating your application from Microsoft DNA to IBM's WebSphere, from coming up with a strategy and scope for the migration to architecting and developing the migration solution. If you are the IT decision maker or the project manager who is responsible for setting the scope and defining the strategy for your migration, then the first part of this book is aimed at you. The second part of the book focuses on IT architects, IT specialists, or programmers who have to re-engineer, design, code, and test the migration solution. Part 1 focuses on what to do before you commence the migration, and how to set the scope within the migration constraints and come up with your migration strategy. In Part 2 we look at redesigning the architecture of your Windows DNA application, and discuss how to identify the considerations unique to your migration scenario and provide guidelines for migrating the different tiers of your application based on your migration strategy and redesigned architecture.IBM redbooks.Web portalsSecurity measuresWeb portalsSecurity measures.006.7/6Oguejiofor Edward1648256Kovari Peter1632744Mavri Robert1648257Nagarajan Shyam1648258Rehman Ashar1648259Sommerhauser Gerd1648260Steckner Thomas1648261International Business Machines Corporation.International Technical Support Organization.MiAaPQMiAaPQMiAaPQBOOK9910816468403321Migrating applications from microsoft DNA to IBM WebSphere3996268UNINA