| There are several migration tools that will help you get to the latest version of WAS 5. Getting from V3.5.x to Version V5 was discussed in Chapter 6, "Building a Combined WebSphere and Domino System." Here are some brief explanations on migrating from V4.x and V5.0.x to V5.1. New Migration Tools The WASPreUpgrade and the WASPostUpgrade migration tools in Version 5.1 are updated to work with V5.1. To migrate the configuration from another version of WebSphere Application Server, use the WASPreUpgrade tool from the migration/bin directory on the product CD-ROM. The tool from the previous release is not sufficient for migrating to V5.1. There are several scripts that the installer program copies to the V5.0.x install_root/bin directory when you use the Installation Wizard to migrate a V5.0.x release to V5.1. The pre_uninst50ws and the post_uninst50ws tools prevent removing the configuration of a migrated node from the deployment manager when you uninstall. The pre_uninst502mq and the post_uninst502mq tools prevent deleting a messaging queue manager when you uninstall after migrating a configuration of V5.0.2 to V5.1. Version 5.0.x Migration to 5.1 Migration from Version 5.0.x to Version 5.1 involves minimal change because both releases implement the Java 2 Platform, Enterprise Edition (J2EE) 1.3 specification. Version 5.0.x supports the Java 2 SDK Version 1.3.1. Version 5.1 supports the Java 2 SDK Version 1.4.1. V5.0.x applications can run on either release without change. V5.1 applications can run on either release without change if you compile applications on a V5.1 node with the compatibility options. There are several considerations. There are new migration tools for V5.1 to help migrate federated nodes and nodes with the embedded messaging feature installed. Use the new tools when uninstalling a node you migrate or when uninstalling the V5.1 node, if you decide to keep using the previous node. One set of tools prevents the deployment manager from removing the node as a member of the cell . The other new set of tools prevents uninstalling the messaging queue manager and deleting the code for embedded messaging feature. Version 4.x Migration Migration from Version 4.x to Version 5.1 involves minimal change because both releases implement the Java 2 Platform, Enterprise Edition (J2EE) specification. (V4 implements the J2EE 1.2 specification. V5.1 implements the J2EE 1.3 specification.) Most V4.x applications can run without change. Despite this fact, knowledge of how the migration tools migrate Version 4.x applications is important. For example, extended messaging support service is now a component of IBM WebSphere Application Server, Version 5.1. Applications that use Version 4.x extended messaging support services require migration to use in an IBM WebSphere Application Server, Version 5.1 system. If you are considering a migration to V5.1 from previous versions of WebSphere Application Server, Table A-2 summarizes potential migration concerns and answers. Table A-2. Summary of Potential Migration Areas | Functional Area | Support in V3.5.x or V4.x? | Must Migrate from V3.5.x? | Must Migrate` from V4.x? | Must Migrate from V5.0.x? | Details | | Enterprise Beans | EJB 1.0 | Yes | Not applicable | No | Many EJB 1.0 applications can run unchanged in Version 5.1, although some changes might be required or recommended. See Migrating enterprise bean code to the supported specification. | | | EJB 1.1 | Not applicable | No | No | Full support for EJB 1.1 is provided. See migrating enterprise bean code to the supported specification. | | Java 2 Connectors | Java 2 Connectors | Not applicable | Yes | No | The preliminary Java 2 Connector support in V4.x is completed in V5.1. Some changes might be necessary to take full advantage of this support. See J2EE Connector Architecture migration tips. | | JDBC API | JDBC API | Yes | Not applicable | No | Many applications can run unchanged in V5.1, although some changes might be required or recommended. See Migrating a Version 4.0 data access application to Version 5.1. | | JavaServer Pages (JSP) files | JSP 1.0 Specification | No | No | No | JSP 1.0 ASPs are a pure subset of JSP 1.2. See Developing JavaServer Pages files with WebSphere extensions. | | | JSP 1.1 Specification | Not applicable | No | No | JSP 1.1 ASPs are a pure subset of JSP 1.2. See Developing JavaServer Pages files with WebSphere extensions. | | Security | IBM Security | Yes | Yes | No | Changes might be required due to J2EE security. See Migrating security configurations from previous releases. | | Servlets | Servlet 2.1 Specification and IBM extensions | Yes | Yes | No | Many Servlet 2.1 applications can run unchanged in V5.1, although changes might be required or recommended. See Developing servlets with WebSphere Application Server extensions. | | Servlets | Servlet 2.2 Specification | No | No | No | Servlet 2.2 APIs are a pure subset of Servlet 2.3. See Developing servlets with WebSphere Application Server extensions. | | Sessions | IBM sessions | Yes | Yes | No | Many applications can run unchanged in Version 5.1, although changes might be required or recommended. See Developing session management in servlets and Migrating HTTP sessions. | | Transactions | IBM transactions | Yes | No | No | A change in the import statement. Also, one datasource connection cannot be used across multiple user transactions. See Using the transaction service. | | Web services | Apache (SOAP) 2.2 | Not applicable | Yes | No | Many applications can run unchanged, although changes to use new support are recommended. | | XML parser | XML 2.0.x supported | Yes | Not applicable | No | Changes to move to the supported API XML4J V4.0.6 level are required. See Configuring WebSphere Application Server after migration. | | XML parser | XML4J V3.1 | Not applicable | Yes | Not applicable | Recompilation is required to convert to XML4J V4.0.6. | | XML parser | XML4J V3.1 | Not applicable | Yes | Yes | Recompilation is required to convert to XML4J 4.2.2. See Configuring WebSphere Application Server after migration. | | XML configuration tool | XMLConfig | Yes | Yes | No | Use the JMX support provided by wsadmin. See Migrating from wscp V4.0 to wsadmin V5.0. | | WebSphere Control Program | WSCP | Yes | Yes | No | Use the JMX support provided by wsadmin. See Migrating from wscp V4.0 to wsadmin V5.0. |
|
