LEADER 08031nam 2200661Ia 450 001 9910816468403321 005 20200520144314.0 035 $a(CKB)1000000000243572 035 $a(OCoLC)137342172 035 $a(CaPaEBR)ebrary10112541 035 $a(SSID)ssj0000281958 035 $a(PQKBManifestationID)11193352 035 $a(PQKBTitleCode)TC0000281958 035 $a(PQKBWorkID)10317014 035 $a(PQKB)11654333 035 $a(Au-PeEL)EBL3306537 035 $a(CaPaEBR)ebr10112541 035 $a(CaSebORM)0738493600 035 $a(MiAaPQ)EBC3306537 035 $a(OCoLC)811554772 035 $a(OCoLC)ocn811554772 035 $a(EXLCZ)991000000000243572 100 $a20060117d2005 uy 0 101 0 $aeng 135 $aurcn||||||||| 181 $ctxt 182 $cc 183 $acr 200 10$aMigrating applications from microsoft DNA to IBM WebSphere /$fEdward Oguejiofor et al 210 $aResearch Triangle Park, N.C. $cIBM, International Technical Support Organization$d2005 215 $a1 online resource (342 p.) 225 1 $aRedbooks 300 $a"August 2005." 311 $a0-7384-9360-0 320 $aIncludes bibliographical references and index. 327 $aFront 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. 327 $a3.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. 327 $a6.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. 330 $aThis 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. 410 0$aIBM redbooks. 606 $aWeb portals$xSecurity measures 615 0$aWeb portals$xSecurity measures. 676 $a006.7/6 700 $aOguejiofor$b Edward$01648256 701 $aKovari$b Peter$01632744 701 $aMavri$b Robert$01648257 701 $aNagarajan$b Shyam$01648258 701 $aRehman$b Ashar$01648259 701 $aSommerhauser$b Gerd$01648260 701 $aSteckner$b Thomas$01648261 712 02$aInternational Business Machines Corporation.$bInternational Technical Support Organization. 801 0$bMiAaPQ 801 1$bMiAaPQ 801 2$bMiAaPQ 906 $aBOOK 912 $a9910816468403321 996 $aMigrating applications from microsoft DNA to IBM WebSphere$93996268 997 $aUNINA