Site map
Overview
Overview of migration, coexistence, and interoperability
Migrating and coexisting application servers
Premigration considerations
Migrating API and specifications
How do I migrate, coexist, and interoperate?
Migrating product configurations
Configuration mapping during product-configuration migration
Migrating profiles using the migration wizard
Migrating product configurations with migration tools
Migrating product configurations with the migration wizard
Migrating to stand-alone application servers using the Migration wizard
Migrating a Version 6.1.x or Version 7.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 stand-alone application servers for distributed operating systems
Migrating to a Version 8.0 stand-alone application server
Migrating to a Version 8.0 stand-alone application server on a remote machine
Migrating stand-alone application servers from unsupported operating systems
Migrating WebSphere Application Server, Network Deployment configurations for distributed operating systems
Migrating to a Version 8.0 deployment manager
Migrating a Version 6.x or 7.x federated node
Migrating to Version 8.0 federated nodes on remote machines
Migrating a large WebSphere Application Server, Network Deployment configuration with a large number of applications
Migrating to Version 8.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 stand-alone 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 8.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 8.0 deployment manager
7. Verify the logs for success
WASPostUpgrade command
8. Run the backupConfig command on the Version 8.0 deployment manager
backupConfig command
restoreConfig command
9. Start the Version 8.0 deployment manager
Using HPEL to troubleshoot applications
10. Migrate plug-ins for web servers
tins_migWebserver.dita
11. Run a migration on application client installations
12. Migrate nodes
Migrating a Version 6.x or 7.x federated node
Using HPEL to troubleshoot applications
13. Troubleshooting
Troubleshooting migration
Scenario 2: Migrating cell configurations to new host machines using the command-line tool
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 8.0
3. Create the remote migration .jar file
4. Create the target deployment manager profile
manageprofiles command
5. Run the WASPreUpgrade command.
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
9. Verify the logs for success
WASPostUpgrade command
10. Run the backupConfig command on the Version 8.0 deployment manager
WASPostUpgrade command
11. Stop and disable the deployment manager on the old host
backupConfig command
restoreConfig command
12. Start the Version 8.0 deployment manager
Using HPEL to troubleshoot applications
13. Manually synchronize all nodes
Starting and stopping the deployment manager
startManager command
14. Migrate plug-ins for web servers
tins_migWebserver.dita
syncNode command
15. Run a migration on application client installations
Migrating web server configurations
16. Migrate nodes
clientUpgrade command
Using HPEL to troubleshoot applications
17. Troubleshoot
Scenario 3: Flexible Management: Migrating an administrative agent profile and its registered set of managed base application servers
1. Install WebSphere Application Server Version 8.0
2. Create the target administrative agent profile
manageprofiles command
3. Ensure that all the "In Progress" jobs are completed on the managed profiles
4. Stop polling the job manager
5. Run the WASPreUpgrade command from the new WebSphere Application Server install root bin directory
WASPreUpgrade command
6. Verify the console output and the WASPreUpgrade logs for success, warnings, or failure
WASPreUpgrade command
7. Run the WASPostUpgrade command from the new WebSphere Application Server install root bin directory
WASPostUpgrade command
8. Verify the logs for success
WASPostUpgrade command
9. Start the Version 8.0 administrative agent
Using HPEL to troubleshoot applications
10. Migrate managed base application servers
Using HPEL to troubleshoot applications
11. Troubleshooting
Troubleshooting migration
Scenario 4: Flexible Management: Migrating a job manager profile and its registered set of servers
1. Install WebSphere Application Server Version 8.0
2. Create the target job manager profile
manageprofiles command
3. Stop the old job manager
WASPreUpgrade command
4. Run the WASPreUpgrade command from the new WebSphere Application Server install root bin directory
WASPreUpgrade command
5. Verify the console output and the WASPreUpgrade logs for success, warnings, or failure
WASPostUpgrade command
6. Run the WASPostUpgrade command from the new WebSphere Application Server install root bin directory
WASPostUpgrade command
7. Verify the logs for success
8. Start the Version 8.0 job manager
Using HPEL to troubleshoot applications
9. Migrate the registered servers
10. Troubleshooting
Migrating web server configurations
Migrating administrative scripts
Migrating administrative scripts from a previously Version 5.1.x application server
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 or 7.x to Version 8.0
Updating SSL configurations to Version 8.0 configuration definitions after migration
Running multiple application server versions
Coexistence support
Setting up Version 6.x, Version 7.0 and Version 8.0 coexistence
Setting up Version 8.0 coexistence
Interoperating multiple application server versions
Configuring port settings
Port number settings
Troubleshooting migration