This topic describes what changes during migration, which always involves migrating a single instance to another single instance on the same machine or a separate machine. An example is a Version 5.x deployment manager migrating to a Version 6 deployment manager profile, or a Version 5.x Application Server migrating to a Version 6 stand-alone Application Server profile.
Many migration scenarios are possible. The Version 6 migration tools maps objects and attributes to the Version 6 environment when you restore a configuration from a previous version.
Migration maps a default bootstrap NameServer port setting, 900, from V4.0.x Advanced Edition or V5.x to the V6 NameServer default, 2809. The migration tools map a non-default value directly into the V6 environment.
For V4.0.x Advanced Single Server Edition migration, the bootstrap NameServer port maps to the NameServer value of the Application Server defined in the server configuration file.
The migration tools convert appropriate command line parameters to Java virtual machine (JVM) settings in the server process definition. Most settings are mapped directly. Some settings, such as memory heap sizes, are not migrated because their roles in the V6 configuration either do not exist, have different meanings, or have different scopes.
The name of the default server in Version 6 is server1. All objects previously owned by the DefaultServer of V4.0.x are owned by server1 of Version 6 after migration.
Migration does not deploy enterprise applications on cluster members when migrating from Version 4.0.x. You must manually deploy these applications on the cluster using scripting or the deployment manager administrative console. When migrating from V5.x, the applications are deployed automatically.
Version 6 significantly redefines JDBC and data source objects. The migration tools map V4.0.x data sources to Version 6 data sources, using predecessor settings as input variables.
You can migrate a V5.x node that belongs to a cell without removing the node from the cell.
Migrate the deployment manager first, before migrating any base nodes in the cell.
Use the same cell name when migrating Network Deployment from V5.x to V6. If you use a different cell name, federated nodes cannot successfully migrate to the Network Deployment V6 cell.
Migrating a base WebSphere Application Server node that is within a cell to V6 also migrates the node agent to V6. A cell can have some V6 nodes and other nodes that are at V5.x levels.
A Version 4.0.x repository can contain more than one node name and associated children. The WASPostUpgrade tool processes only those objects and children that match the node name of the migrating node. The tool identifies node names in the configuration files that it is migrating and selects any node names in a configuration file that match the long network name or short network name of the migrating machine.
The configuration of the PageList servlet has changed from V4.0.x. Direct use of the servlet has been deprecated. The PageList servlet is available as part of the servlet extension configuration in the Web archive (WAR) file. All references are updated to the servlet configuration supported in Version 6.
You can also use the Application Server Toolkit (AST) and Rational Web Developer to modify the servlet configuration. See Assembly tools for more information.
Error 500: No PageList information is configured for servlet EmpInfoApp.SearchByDept
Migration copies files from prior version directories into the Version 6 configuration. See the following section for more information.
Migration does not overlay property files.
Java 2 Security is enabled by default in Version 6. Security enablement might cause some applications to run on Versions 4.0.x and not run on Version 6. Several techniques are available that you can use to define different levels of Java 2 Security in Version 6. One is to create a was.policy file as part of the application, to enable all security permissions. The migration tools call the wsadmin command to add an existing was.policy file in the Version 6 properties directory to enterprise applications as they migrate. The migration tools perform this task while moving Version 4.0.x applications into Version 6.
Global security that uses Lightweight Third Party Authentication (LTPA) in Version 4.0.x is migrated to the base WebSphere Application Server product and to the Network Deployment product. However, although global security was enabled in Version 4.0.x, it is disabled during migration to Version 6 (security is NOT disabled when migrating from V5.x).
The Global security feature that uses localos authentication mechanisms in Version 4.0.x is migrated to the Network Deployment product. However, although global security was enabled in Version 4.0.x, it is disabled during migration to Version 6. The Network Deployment product does not support the authentication mechanism known as SWAM. Migration sets the authentication mechanism in Version 6 to LTPA. Use the administrative console to generate keys for the migrated LTPA. After generating the keys, you can enable global security.
Use the Version 6 administrative console to change these settings to match your Version 4.0.x property values, if necessary.
V4.0.x server groups are redefined in V6 as clusters. Application servers are the only objects supported as cluster members in V6.
The location for these directories is typically within the installation directory of a previous version. The default location for stdin, stdout, and stderr is the logs directory of the Version 6 installation root. The migration tools attempt to migrate existing passivation and working directories. Otherwise, appropriate Version 6 defaults are used.
Using common directories between versions in a coexistence scenario can cause problems.
The migration tools migrate all ports. The tools warn about port conflicts in a log when a port already exists. You must resolve port conflicts before running the servers that are in conflict, at the same time.
No redeployment is required when moving EJB 1.1 JAR files from Version 4.0.
Specify only one backend data store vendor per JAR file. If enterprise beans use different backend data stores, package them into separate JAR files.
All JMS resources from Version 4.0 are mapped into generic JMS resources in the Version 6 configuration. Reconfigure JMS resources that use IBM WebSphere MQ as IBM WebSphere MQ-specific resources. MQ JMS resources have better integration with system management. You do not need to manually define entries in the name space. You can see the backing MQ queue definitions through MQ JMS entries.
In Version 4.0.x, the classes generated from JSP pages are in a package based on the directory structure of the WAR file. Any JSP at the top of the context root is in the unnamed package. JSP pages in subdirectories of the root are in packages named after the subdirectories. In Version 6, the classes generated from JSP pages are all in the org.apache.jsp package. Therefore, the class files are not compatible between versions.
When migrating an enterprise application from Version 4.0.x to Version 6, recompile the JSP pages to regenerate the class files into the correct packages.
The migration tools provide this support, by using the -preCompileJSPs option of the wsadmin tool during the installation of the application.
Use the same option to install any Version 4.0.x enterprise applications that you manually move to Version 6.
You can apply security in two Version 4.0.x locations to enterprise applications. Information in the repository has precedence over information in the enterprise application bindings. The migration tools migrate information in the repository to the enterprise application.
The following SSLConfig attributes that point to user-defined key files are migrated from WebSphere Application Server Version 4.0.x (AE) or Version 5.x to Version 6 as follows:
<key_file_name>dir_name/WASLDAPKeyring.jks</key_file_name> <trust_file_name>dir_name/WASLDAPKeyring.jks</trust_file_name>The dir_name variable identifies the original location of the WASLDAPKeyring.jks file.
keyFileName="dir_name/WASLDAPKeyring.jks" trustFileName="dir_name/WASLDAPKeyring.jks"The dir_name variable identifies the original location of the WASLDAPKeyring.jks file.
<key_file_name>${WAS_HOME}/keys/WASLDAPKeyring.jks</key_file_name> <trust_file_name>${WAS_HOME}/keys/WASLDAPKeyring.jks</trust_file_name>
keyFileName="${USER_INSTALL_ROOT}/keys/WASLDAPKeyring.jks" trustFileName="${USER_INSTALL_ROOT}/keys/WASLDAPKeyring.jks"
The migration tools do not copy the key files (for example, .jks, or .kdb) to the corresponding directory in the base WebSphere Application Server product or the Network Deployment product. You must complete the migration of the SSL configuration by copying qualifying key store files to Version 6 directories.
If the key-file-name and trust-file-name attributes point to the DummyServerKeyFile.jks file in the WebSphere Application Server V4.0.x (AE) or V5.x configuration, the key-file-name and trust-file-name attributes are not migrated to V6. Instead the V6 default value of ${USER_INSTALL_ROOT}/etc/DummyServerKeyFile.jks is left unchanged.
If the web.xml Web module file for Version 4.0 defines the SimpleFileServlet servlet, the migration tools update the class name to reflect the Version 6 package. The tools also set the FileServing Enabled attribute to true.
If the web.xml file defines the InvokerServlet servlet, the migration tools update the class name to reflect the Version 6 package. The tools also set the ServeServletsByClassnameEnabled attribute to true.
If the web.xml file defines the DefaultErrorReporter servlet, the migration tools update the class name to reflect the Version 6 package.
Migrating from V5.x to V6 is much less complicated than migrating from V4.0.x. Both versions use the same underlying definitions. The task involves mapping configuration files from the V5.x to the V6 configuration and copying installed applications into the new product. The migration tools support the migration of federated nodes and support the full migration of a Network Deployment node.
java.lang.OutOfMemoryError JVMXE006:OutOfMemoryError
Increase the maximum Java heap size and follow the instructions below to install the application:
Installing the application on WebSphere Application Server, Version 6
wsadmin -conntype NONE -javaoption -Xmx###m -c "$AdminApp install C:\\WebSphere\\AppServer\\installableApps\\ EAR_file_name {-nodeployejb -appname app_name -server server_name -node node_name}"
Installing the application on WebSphere Application Server Network Deployment, Version 6
wsadmin -conntype NONE -javaoption -Xmx###m -c "$AdminApp install C:\\WebSphere\\DeploymentManager\\installableApps\\ EAR_file_name> {-nodeployejb -appname app_name -cluster cluster_name}"
Related tasks
Migrating product configurations
Task overview: Using enterprise beans in applications
Related reference
Process logs