Migrating applications from WebLogic, JBoss and Tomcat to WebSphere V6

This IBM Redbook will help you plan and execute the migration of J2EE 1.3 applications developed for BEA WebLogic Server 8.1, JBoss 3.2.7 and Apache Tomcat 5.5.9, so that they will run on WebSphere Application Server V6. This redbook provides detailed information to help you plan migrations, best p...

Descripción completa

Detalles Bibliográficos
Autor Corporativo: International Business Machines Corporation. International Technical Support Organization (-)
Otros Autores: Cunico, Hernan (-)
Formato: Libro electrónico
Idioma:Inglés
Publicado: Research Triangle Park, NC : IBM, International Technical Support Organization 2005.
Edición:1st ed
Colección:IBM redbooks.
WebSphere software.
Materias:
Ver en Biblioteca Universitat Ramon Llull:https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009627350206719
Tabla de Contenidos:
  • Front cover
  • Contents
  • Notices
  • Trademarks
  • Preface
  • The team that wrote this redbook
  • Become a published author
  • Comments welcome
  • Chapter 1. Introduction
  • 1.1 Our objective
  • 1.2 Scope of this book
  • 1.3 Applications covered in this book
  • 1.4 What is not covered in this book
  • 1.5 How to use this book
  • Chapter 2. WebSphere overview
  • 2.1 About WebSphere
  • 2.2 WebSphere Application Server
  • 2.2.1 WebSphere Application Server V6 - Express
  • 2.2.2 WebSphere Application Server V6 - Base
  • 2.2.3 WebSphere Application Server V6 - Network Deployment
  • 2.2.4 WebSphere Extended Deployment
  • 2.2.5 Supported platforms and software
  • 2.3 Development and deployment tools
  • 2.3.1 Rational Application Developer V6
  • 2.3.2 Rational Web Developer V6
  • 2.3.3 Application Server Toolkit (ASTk)
  • 2.3.4 WebSphere Rapid Deployment
  • 2.4 Performance and analysis tools
  • 2.4.1 Memory analysis
  • 2.4.2 Thread analysis
  • 2.4.3 Execution time analysis
  • 2.4.4 Code coverage
  • 2.4.5 Probe kit
  • Chapter 3. Migration strategy and planning
  • 3.1 Migration strategy considerations
  • 3.1.1 Getting help
  • 3.1.2 Migrating the different environments
  • 3.1.3 Strategies to handle migration complexity
  • 3.2 Application servers interoperability
  • 3.3 Migration planning activities
  • 3.3.1 Gathering concerned parties together
  • 3.3.2 Evaluating current assets
  • 3.3.3 Assessing the high-level application architecture
  • 3.3.4 Reviewing and validating the application code
  • 3.3.5 Reviewing the development environment
  • 3.3.6 Reviewing the runtime environment
  • 3.3.7 Reviewing the current build and deployment processes
  • 3.3.8 Assessing current skills
  • 3.3.9 Reviewing time constraints
  • 3.3.10 Creatng a detailed migration plan
  • 3.4 Migration alternatives
  • 3.4.1 Alternative 1: Keeping the existing development environment.
  • 3.4.2 Alternative 2: Migrating XDoclet tags to WRD
  • 3.4.3 Alternative 3: Using XDoclet support for WebSphere
  • 3.4.4 Alternative 4: Developing using Rational Application Developer V6
  • 3.5 Migrating the site
  • 3.5.1 Switchover migration
  • 3.5.2 Coexistence migration
  • 3.5.3 Offline migration
  • 3.5.4 Database migration
  • 3.6 Testing the migrated site
  • 3.7 Going live
  • 3.8 Naming conventions
  • Chapter 4. Installation and configuration
  • 4.1 Introduction
  • 4.2 Hardware and software installed
  • 4.3 Rational Application Developer V6
  • 4.3.1 Installing the interim fix
  • 4.3.2 Testing the application server
  • 4.4 WebSphere Application Server V6
  • 4.4.1 Installing the latest fixpack
  • 4.4.2 WebSphere profiles
  • 4.4.3 Creating new WebSphere profiles
  • 4.5 WebSphere Administrative Console
  • 4.5.1 Managing the application servers
  • 4.5.2 Universal Test Client
  • 4.6 Administrative scripting
  • 4.6.1 Examples
  • 4.7 DB2 Universal Database V8.2
  • 4.8 Installation directories
  • Chapter 5. Common migration issues
  • 5.1 J2EE application server compability
  • 5.1.1 Differences in J2EE implementations
  • 5.1.2 Using vendor-specific features
  • 5.1.3 Class loader related problems
  • 5.1.4 Deployment descriptors
  • 5.2 Application portability
  • 5.2.1 Application packaging
  • 5.2.2 Use of native code
  • 5.2.3 Database-related issues
  • 5.2.4 JMS
  • 5.2.5 JNDI
  • 5.2.6 J2EE application clients
  • 5.3 J2EE 1.3 to 1.4 migration considerations
  • 5.3.1 Enterprise Java Beans
  • 5.3.2 Java Server Pages
  • 5.3.3 Servlets
  • Chapter 6. Migrating from BEA WebLogic
  • 6.1 Introduction
  • 6.2 Prerequisites and assumptions
  • 6.3 BEA WebLogic Server 8.1 installation
  • 6.4 Trade for BEA WebLogic Server 8.1 migration
  • 6.4.1 Migration approach
  • 6.4.2 Configuring the initial environment
  • 6.4.3 Migrating the sample application
  • 6.4.4 Summary.
  • 6.5 xPetstore EJB migration
  • 6.5.1 Migration approach
  • 6.5.2 Configuring the initial environment
  • 6.5.3 Migrating the sample application
  • 6.5.4 Summary
  • Chapter 7. Migrating from JBoss
  • 7.1 Introduction
  • 7.2 Prerequisites and assumptions
  • 7.3 Software installation
  • 7.3.1 JBoss
  • 7.3.2 Apache Ant
  • 7.4 xPetstore EJB migration using Alternative 2
  • 7.4.1 Migration approach
  • 7.4.2 Configuring the initial environment
  • 7.4.3 Migrating the application
  • 7.5 xPetstore EJB migration using Alternative 3
  • 7.5.1 Migration approach
  • 7.5.2 Configuring the initial environment
  • 7.5.3 Migrating the xPetstore EJB application
  • Chapter 8. Migrating from Tomcat
  • 8.1 Introduction
  • 8.2 Prerequisites and assumptions
  • 8.3 Software installation
  • 8.3.1 Apache Tomcat
  • 8.3.2 Apache Maven
  • 8.3.3 Apache Ant
  • 8.3.4 hMailServer
  • 8.4 ivata groupware migration
  • 8.4.1 Migration approach
  • 8.4.2 Configuring the source environment
  • 8.4.3 Migrating the ivata groupware application
  • 8.5 xPetstore Servlet migration
  • 8.5.1 Migration approach
  • 8.5.2 Configuring the source environment
  • 8.5.3 Migrating the xPetstore Servlet application
  • Appendix A. Development tips for portable applications
  • End-to-end life cycle
  • Software development life cycle key concepts
  • The Rational Unified Process
  • General development best practices
  • Iterative development
  • Requirements definition
  • Object Oriented (OO) approach to design and programming
  • Modeling languages
  • Regular reviews and check points
  • Java development best practices
  • Code documentation
  • Unit testing
  • Automation
  • Enterprise Java development best practices
  • Modularization
  • Follow the standards
  • Design patterns
  • J2EE best practices
  • Appendix B. Additional material
  • Locating the Web material
  • Using the Web material.
  • System requirements for downloading the Web material
  • How to use the Web material
  • Related publications
  • IBM Redbooks
  • Online resources
  • How to get IBM Redbooks
  • Help from IBM
  • Index
  • Back cover.