Migrate product configurations
Use the WebSphere Application Server v9.0 migration tools to migrate the product configurations. These migration tools support migration from v7.0 or later.
Read Overview of migration, coexistence, and interoperability and Migration considerations. For resources to help us plan and perform our migration, visit Knowledge Collection: Migration planning for WAS.
The following configuration upgrades of WAS versions and offerings are directly supported.
Migration Source (V7.0 or later) WAS V9.0 Target
WAS ND stand-alone WAS ND Management WAS (base) stand-alone application server Supported Not supported WAS ND stand-alone Supported Not supported WAS ND federated application server Not supported Not supported WAS ND deployment manager Not supported Supported WAS Client Not supported Not supported We can migrate a WAS ND federated application server to a standalone server, however, after migration, it becomes a federated server.
WAS v9.0 supports the migration of a subset of programming model extensions (PMEs) from WebSphere Business Integration Server Foundation.
We can migrate the product configurations using the WAS v9.0 Migration wizard or the command-line migration tools.
Before using the migration tools, consult the IBM WAS supported hardware, software, and APIs website to understand what fixes we 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.
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 rejects the updates and creates an exception. To avoid this situation, follow 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 we need to migrate federated nodes concurrently, use the following steps to minimize the potential failures:
bprac
Tasks
- Run the backupConfig command for the deployment manager and each federated node before beginning.
- Stop the nodeagent process before migrating the nodes.
- Stagger the start of the migration process for each node by 3 to 5 minutes.
- Run the restoreConfig command on that node and rerun the migration process if a failure occurs.
Subtopics
- Configuration mapping during product-configuration migration
- Use the migration tools
- Migrate to a v9.0 stand-alone application server
- Migrate to a v9.0 stand-alone application server on a remote machine
- Migrate cells using the command-line tools
- Migrate cells to new host machines using the command-line tool
- Migrate an administrative agent profile and its registered set of managed base application servers
- Migrate a job manager profile and its registered set of servers
- Migrate a large WAS ND configuration with a large number of applications
- Rolling back environments