Migrating product configurations

Use the WebSphere Application Server Version 6.1.x migration tools to migrate your product configurations. These migration tools support migration from WebSphere Application Server Version 5.x and Version 6.0.x.

Before you begin

See Overview of migration, coexistence, and interoperability and Premigration considerations.

The following configuration upgrades of WebSphere Application Server versions and offerings are directly supported.
[AIX HP-UX Linux Solaris Windows]
Table 1. Directly Supported Configuration Upgrades
Migration Source WebSphere Application Server Version 6.1.x Target
Network Deployment Standalone and Custom Profiles Network Deployment Deployment Manager Profile
WebSphere Application Server Version 5.x or 6.0.x base standalone application server Supported  
WebSphere Application Server Version 5.x or 6.0.x Network Deployment standalone application server Supported  
WebSphere Application Server Version 5.x or 6.0.x Network Deployment federated application server Supported  
WebSphere Application Server Version 5.x or 6.0.x Network Deployment deployment manager   Supported
WebSphere Application Server Version 5.x or 6.0.x Client    
WebSphere Application Server Version 5.x or 6.0.x Express standalone application server Supported  
WebSphere Application Server Version 5.0.x Enterprise base standalone application server Supported  
WebSphere Application Server Version 5.0.x Enterprise Network Deployment standalone application server Supported  
WebSphere Application Server Version 5.0.x Enterprise Network Deployment federated application server Supported  
WebSphere Application Server Version 5.0.x Enterprise Network Deployment deployment manager   Supported
WebSphere Business Integration Server Foundation Version 5.1.x base standalone application server Supported *  
WebSphere Business Integration Server Foundation Version 5.1.x Network Deployment standalone application server Supported *  
WebSphere Business Integration Server Foundation Version 5.1.x Network Deployment federated application server Supported *  
WebSphere Business Integration Server Foundation Version 5.1.x Network Deployment deployment manager   Supported *
* WebSphere Application Server Version 6.1.x supports the migration of a subset of programming model extensions (PMEs) from WebSphere Business Integration Server Foundation. See Programming model extension migration for more information on this support.
[iSeries]
Table 2. Directly Supported Configuration Upgrades
Migration Source WebSphere Application Server Network Deployment Version 6.1.x Target
Standalone and Custom Profiles Deployment Manager Profile
WebSphere Application Server Version 5.x or 6.0.x base standalone application server Supported  
WebSphere Application Server Version 5.x or 6.0.x Network Deployment standalone application server Supported  
WebSphere Application Server Version 5.x or 6.0.x Network Deployment federated application server Supported  
WebSphere Application Server Version 5.x or 6.0.x Network Deployment deployment manager   Supported
WebSphere Application Server Version 5.x or 6.0.x Express standalone application server Supported  
[z/OS]
Table 3. Directly Supported Configuration Upgrades
Migration Source WebSphere Application Server for z/OS Version 6.1.x Target
Standalone Application Server Federated Application Server Deployment Manager
WebSphere Application Server for z/OS Version 5.x or 6.0.x standalone application server Supported    
WebSphere Application Server for z/OS Version 5.x or 6.0.x federated application server   Supported  
WebSphere Application Server for z/OS Version 5.x or 6.0.x deployment manager     Supported
WebSphere Business Integration Server Foundation for z/OS Version 5.1.x standalone application server Supported *    
WebSphere Business Integration Server Foundation for z/OS Version 5.1.x federated application server   Supported *  
WebSphere Business Integration Server Foundation for z/OS Version 5.1.x deployment manager     Supported *
* WebSphere Application Server for z/OS Version 6.1.x supports the migration of a subset of programming model extensions (PMEs) from WebSphere Business Integration Server Foundation. See Programming model extension migration for more information on this support.

[AIX HP-UX Linux Solaris Windows] You can migrate your product configurations using the WebSphere Application Server Version 6.1.x Migration wizard or the command-line migration tools.

[iSeries] You can migrate your product configurations using the WebSphere Application Server Version 6.1.x command-line migration tools.

[z/OS] Use this article as a starting point for the planning information, information on creating your migration jobs, as well as specific migration explanations for standalone application server nodes, deployment managers, and federated nodes.

Before using the migration tools, consult the WebSphere Application Server Version 6.1.x Release Notes document to understand what fixes you must apply to earlier versions. Applying fixes to an earlier version might also apply fixes to files that have a role in the migration. Apply any fixes to ensure the most effective migration of configurations and applications.

Best practice Best practice: The deployment manager maintains the master configuration data for all of the nodes that it manages. This configuration data is updated through the configuration manager. When the configuration manager detects that the updates to the configuration data were not made against the latest saved copy, it reject the updates and creates an exception. To avoid this situation, following these best practices:
  • Migrate each node independently. For example, let the first node complete the migration process before starting the process for the second node, and so on.
  • Ensure that the administrative console for the deployment manager is not running when the migration process is in progress.
If you need to migrate federated nodes concurrently, use the following steps to minimize the potential failures:
  1. Run the backupConfig command for the deployment manager and each federated node before you begin. For more information, see the documentation about the backupConfig command.
  2. Stagger the start of the migration process for each node by 3 to 5 minutes.
  3. Run the restoreConfig command on that node and rerun the migration process if a failure occurs. For more information, see the documentation about the restoreConfig command.
bprac

About this task [AIX HP-UX Linux Solaris Windows] [iSeries]

When you use the migration tools, the overall migration process includes these steps:
  1. Install the WebSphere Application Server Version 6.1.x product.
  2. [AIX HP-UX Linux Solaris Windows] Optional: Use the WebSphere Application Server Version 6.1.x Profile Management tool to create one or more profiles for a deployment manager, a managed node, or a standalone application server.
  3. [iSeries] Use the WebSphere Application Server Version 6.1.x manageprofiles command to create one or more profiles for a deployment manager, a managed node, or a standalone application server.
  4. Use the migration tools to migrate the previous release to the WebSphere Application Server Version 6.1.x product.

    See Using the migration tools to migrate product configurations.

    [AIX HP-UX Linux Solaris Windows]
    1. Perform one of the following actions to start the Migration wizard:
      • Go to Start > Programs > IBM WebSphere > Application Server V6.1 Network Deployment, and click Migration wizard.
      • Run the following command:
        • [AIX] [HP-UX] [Linux] [Solaris] app_server_root/bin/migration.sh
        • [Windows] app_server_root\bin\migration.bat
    2. Use the Migration wizard to migrate the previous release to the Version 6.1.x product.

      See Using the Migration wizard to migrate product configurations.

[AIX HP-UX Linux Solaris Windows] The Migration wizard calls the WASPreUpgrade and WASPostUpgrade commands.

The WASPreUpgrade command saves the configuration and applications of the previously installed version of WebSphere Application Server into a migration-specific backup directory. The WASPostUpgrade command uses the backupConfig command to save the existing Version 6.1.x configuration before performing migration, and the results are stored in the profile_name/temp directory. You can use the restoreConfig command to restore the backup if required.

For help in troubleshooting problems when migrating, see Troubleshooting migration.

Procedure




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 4:28:44 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-mp&topic=tmig_admin
File name: tmig_admin.html