Migration -- table of contents
3: Migration overview
Product migration
3.1: Migrating product prerequisites
3.2: Migrating from previous product versions
3.2.1: Migration from Version 2.0x
3.2.1.1: Migration from Version 2.0x to Version 3.0
3.2.1.2: Migrating Web application files from Version 2.0x directories
3.2.1.2.1: Optimally migrating Version 2.0x Web application files
3.2.1.2.2: Quickly migrating Version 2.0x Web applications
3.2.2: Migrating from Version 3.x
API migration
3.3: Migrating APIs and specifications
3.3.1: Migrating to supported EJB specification
3.3.2: Migrating to supported Servlet specification and extensions
3.3.2.1: Example: Migrating HttpServiceResponse.callPage()
3.3.2a: New Servlet Engine option for migrating applications to Servlet 2.2
3.3.3: Migrating to supported JSP specification
3.3.3.1: Updating JSP .91 files for use with Version 3.5
3.3.3.2: Tips for migrating JSP .91 files to JSP 1.0
3.3.4: Migrating to supported XML API
3.3.5: Migrating to supported user profile APIs
3.3.6: Migrating session management
3.3.6.1: Migrating from Version 2.0 session support
3.3.7: Migrating to supported security APIs
3.3.8: Migrating to supported database connection APIs (and JDBC)
3.3.8.1: Migrating from the Version 3.0x connection pooling model
3.3.8.2: Migrating servlets from the connection manager model
3.3.8.3: Deprecated connection manager APIs
3.3.9: Migrating to supported transaction support
3.3.10: Migrating to supported XML configuration
Administrative configuration and database migration
3.4: Migrating administrative configurations
3.4.1: Using automated migration support
3.4.2: Migrating configurations manually
3.5: Switching administrative databases
3.5.1: Using the database conversion assistant to switch administrative databases
3.5.2: Settings to change when switching administrative databases
3.5.3: Switching server databases to DB2/390: Switching administrative databases