Site map
Overview
Overview of migration, coexistence, and interoperability
Migrating and coexisting application servers
Premigration considerations
Migrating API and specifications
Programming model extension migration
How do I?...
Migrating product configurations
Configuration mapping during product-configuration migration
Migrating product configurations with migration tools
Migrating product configurations with the migration wizard
Migrating to standalone application servers using the Migration wizard
Migrating a Version 5.1.x or Version 6.x federated node using the Migration wizard
Migrating to a Version 7.0 deployment manager using the Migration wizard
Migrating product configurations with the migration disk
clientUpgrade command
convertScriptCompatibility command
WASPreUpgrade command
WASPostUpgrade command
Migrating standalone application servers for distributed operating systems
Migrating to a Version 7.0 standalone application server
Migrating to a Version 7.0 standalone application server on a remote machine
Migrating standalone application servers from unsupported operating systems
Migrating WebSphere Application Server, Network Deployment configurations for distributed operating systems
Migrating to a Version 7.0 deployment manager
Migrating a Version 5.1.x or Version 6.x federated node
Migrating to Version 7.0 federated nodes on remote machines
Migrating a large WebSphere Application Server, Network Deployment configuration with a large number of applications
Migrating to Version 7.0 deployment managers on remote machines
Migrating deployment managers from unsupported operating systems
Migrating IBM Cloudscape or Apache Derby databases
Migrating from the WebSphere Connect JDBC driver
Migrating root configurations to non-root
Migrating non-root configurations to root
Rolling back environments
Rolling back a WebSphere Application Server, Network Deployment cell
Rolling back a federated node
Rolling back standalone application servers
Scenario 1: Migrating a cell using the command line tools
1. Run the backupConfig command on the deployment manager and all old nodes
backupConfig command
restoreConfig command
WebSphere Application Server default directories
2. Install WebSphere Application Server Version 7.0
3. Create the target deployment manager profile
manageprofiles command
4. Run the WASPreUpgrade command from the new deployment manager profile bin directory
WASPreUpgrade command
5. Verify the console output and the WASPreUpgrade logs for success, warnings, or failure
WASPreUpgrade command
6. Run the WASPostUpgrade command from the new deployment manager profile bin directory
WASPostUpgrade command
Migrating to a Version 7.0 deployment manager
7. Verify the logs for success
WASPostUpgrade command
8. Run the backupConfig command on the Version 7.0 deployment manager
backupConfig command
restoreConfig command
9. Start the Version 7.0 deployment manager
Starting and stopping the deployment manager
10. Manually sync the nodes.
syncNode command
11. Migrate plug-ins for Web servers
Migrating Web server configurations
12. Run a migration on application client installations
clientUpgrade command
13. Migrate nodes
Migrating a Version 5.1.x or Version 6.x federated node
14. Troubleshooting
Troubleshooting migration
Scenario 2: Migrating cells across operating systems using the command-line tools
1. Run the backupConfig command on the deployment manager and all old nodes
backupConfig command
restoreConfig command
WebSphere Application Server default directories
2. Install WebSphere Application Server Version 7.0
3. Upgrade the WebSphere Application Server Version 7.0 supplemental CD to the desired fix pack level
Updating the supplemental CD
4. Create the target deployment manager profile
manageprofiles command
5. Run the WASPreUpgrade command from the updated WebSphere Application Server supplemental CD
WASPreUpgrade command
6. Verify the console output and the WASPreUpgrade logs for success, warnings, or failure
WASPreUpgrade command
7. Archive the backup directory created by the WASPreUpgrade command
8. Run the WASPostUpgrade command from the new deployment manager profile bin directory
WASPostUpgrade command
9. Verify the logs for success
WASPostUpgrade command
10. Run the backupConfig command on the Version 7.0 deployment manager
backupConfig command
restoreConfig command
11. Stop and disable the deployment manager on the old host.
12. Start the Version 7.0 deployment manager
Starting and stopping the deployment manager
startManager command
13. Manually synchronize all nodes
syncNode command
14. Migrate plug-ins for web servers
Migrating Web server configurations
15. Run a migration on application client installations
clientUpgrade command
16. Migrate nodes
17. Troubleshoot
Troubleshooting migration
Migrating Web server configurations
Migrating administrative scripts
Migrating administrative scripts from Version 5.1.x
Example: Migrating - Allowing configuration overwrite when saving configurations
Example: Migrating - Changing transaction log directory using wsadmin scripting
Example: Migrating - Changing process definitions using scripting
Example: Migrating - Modifying Web container port numbers
Migrating administrative scripts from Version 6.x to Version 7.0
Updating SSL configurations to Version 7.0 configuration definitions after migration
Running multiple application server versions
Coexistence support
Setting up Version 5.1.x or Version 6.x and Version 7.0 coexistence
Setting up Version 7.0 coexistence
Interoperating multiple application server versions
Configuring port settings
Port number settings
Troubleshooting migration
IBM Suggests