Migrating product configurations

Use the WebSphere® Application Server Version 7.0 migration tools to migrate your product configurations. These migration tools support migration from Version 5.1.x and Version 6.x.

Before you begin

Read Overview of migration, coexistence, and interoperability and Premigration considerations. For resources to help you plan and perform your migration, visit Knowledge Collection: Migration planning for WebSphere Application Server.

The following configuration upgrades of WebSphere Application Server versions and offerings are directly supported.
Table 1. Directly Supported Configuration Upgrades. . Table showing directly supported configuration upgrades.
Migration Source WebSphere Application Server for z/OS® Version 7.0 Target
Standalone and Custom Profiles Deployment-Manager Management Profile
WebSphere Application Server for z/OS Version 5.1.x or Version 6.x standalone application server Supported Not supported 
WebSphere Application Server for z/OS Version 5.1.x or Version 6.x federated application server Supported  Not supported 
WebSphere Application Server for z/OS Version 5.1.x or Version 6.x deployment manager Not supported  Supported
WebSphere Business Integration Server Foundation for z/OS Version 5.1.x standalone application server Supported * Not supported 
WebSphere Business Integration Server Foundation for z/OS Version 5.1.x federated application server Supported *  Not supported 
WebSphere Business Integration Server Foundation for z/OS Version 5.1.x deployment manager Not supported  Supported *
* WebSphere Application Server for z/OS Version 7.0 supports the migration of a subset of programming model extensions (PMEs) from WebSphere Business Integration Server Foundation. Read Programming model extension migration for more information on this support.

Before using the migration tools, consult the IBM® WebSphere Application Server supported hardware, software, and APIs Web site 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: [jul2010] 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.
[jul2010]
jul2010
bprac



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    

Terms of Use | Feedback

Last updated: Oct 22, 2010 2:42:00 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-zos&topic=tmig_admin
File name: tmig_admin.html