InfoCenter Home > 3.2.2.2.3: Restoring the previous configuration to the new installationA set of migration tools is provided with the product to help migrate system configurations for installations at Version 3.x and later. The product installation program calls these tools as part of automated migration support. You can call them yourself from the command line. The tool that restores the Version 3.x configuration is called WASPostUpgrade. This tool uses the information created by the WASPreUpgrade tool to restore the previous Version 3.x configuration to a Version 4.0 installation. Because the Version 4.0 product adheres to the J2EE programming model and earlier versions do not, significant changes are required to apply the Version 3.x configuration to a Version 4.0 installation. Creating and deploying J2EE applicationsThe J2EE programming model specifies an architecture for how applications are created and deployed. Because applications in Version 3.x were not architected in the same manner, the migration process re-creates these applications. All migrated Web resources and enterprise beans are created in J2EE applications. All enterprise applications defined in the Version 3.x installation are mapped into J2EE applications with the same name and deployed in the default server. All other Web resources and enterprise beans that are mapped but not included in an enterprise application are mapped into a default J2EE application called DefaultApplication. Web applications are mapped to J2EE WAR files. Enterprise beans are deployed as EJB 1.1 beans in J2EE JAR files. These resources are combined in a J2EE EAR file and deployed in the Version 4.0 configuration. There are some differences between the EJB 1.0 and EJB 1.1 specifications, but in most cases, EJB 1.0 beans can run successfully as EJB 1.1 beans. It is recommended that you carefully analyze WASPostUpgrade.log (see the end of this topic), because detailed information specific to each bean deployed is saved in the log. SecuritySecurity settings that were applicable in the Version 3.x environment are applied to J2EE security attributes as part of the migration process. LTPA security is not supported on Advanced Single Server Edition; this data cannot be migrated, so it is ignored. SamplesSamples are not migrated; they have been updated specifically for J2EE in Version 4.0. The new samples should be used instead of the ones previously provided with Version 3.x product. Mapping detailsSee the Related information for more specific information about how objects and attributes are mapped to the Version 4.0 configuration. WASPostUpgrade parameterscom.ibm.websphere.migration.postupgrade.WASPostUpgrade backupDirectoryName [-import xml_data_file] [-adminNodeName primary_node_name] [-configFile server_configuration_file] [-traceString trace_spec [-traceFile file_name]] [-substitute "key1=value1[;key2=value2;[...]]"] The first parameter of the command is required. The others are optional, except as noted. A summary follows:
LoggingThe WASPostUpgrade tool displays status to the screen while it is running. WASPostUpgrade also saves a more extensive set of logging information in the logs directory. The file, WASPostUpgrade.log, can be viewed with a text editor. |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|