Cluster: Migrate node profiles
We can use the Configuration Wizard to upgrade the node profiles for a cluster environment. Use the following information to get familiar with the information that provide in the wizard and the configuration procedure that it generates.
Select option...
Update or Maintain a Current Environment | Migrate a Cluster Step 2: Migrate Node Profiles
Worksheet
To set up the migration, we answer questions about your desired configuration. Some fields apply to migration configurations. Some fields are required based on the environment. The remaining fields are advanced and do not apply to most configurations.
Minimal required fields
The following table lists the fields unique to the Migrate a cluster step 2: Migrate node profiles configuration. We might be prompted for additional information about system or user IDs and passwords defined during the portal installation process.
Field Label Default Your Value Target operating system Linux
Target portal profile name wp_profile
Target portal profile home directory /opt/IBM/WebSphere/wp_profile
Is the target portal on the same server or a different server Same server
WebSphere Application Server administrator wpsadmin
WebSphere Application Server administrator password
What is the portal profile name wp_profile
What is the cell name CellName
What is the portal node name NodeName
What is the deployment manager node name dmgr
Where is the source application server installed /opt/IBM/WebSphere/AppServer
What is the new host name
Where is the target application server installed /opt/IBM/WebSphere/AppServer
Target temporary path /tmp
Advanced fields
The following table lists the advanced fields unique to the Migrate a cluster step 2: Migrate node profiles configuration option. Click Advanced on the Answer questions page for the target system to see the advanced properties. Default values are provided for advanced fields required.
Field Label Default Your Value JVM heap size 2048
Migrate a cluster step 2: Migrate node profiles option
After we answer questions and provide information about your migration, the wizard generates a custom configuration procedure.
Depending on our environment, the wizard generates a configuration process. The following steps reflect all possible steps in the configuration process. The steps do not represent a literal configuration. The steps are provided as a reference.
If we click View Step Command, we can see the task and properties associated with each step in the wizard.
- Manual Step: Stop the source deployment manager and node agents
Condition none ConfigEngine task none
- Manual Step: Start the target deployment manager
Condition none ConfigEngine task none
- Generate the files for remote migration
Condition The target portal is on a different server than the source. ConfigEngine task none
- Manual Step: Copy the remote migration package to the source environment
Condition The target portal is on a different server than the source. ConfigEngine task none
- Create a backup of the source portal profile
Condition none ConfigEngine task none
- Manual Step: Create a backup of the remote source portal profile
Condition The target portal is on a different server than the source. ConfigEngine task none
- Manual Step: Update the deployment manager settings
Condition none ConfigEngine task none
- Manual Step: If the backup profile is larger than 2 GB, clean up the backup profile
Condition none ConfigEngine task none
- Create a default profile
Condition none ConfigEngine task none
- Import the backup profile
Condition none ConfigEngine task none
- Manual Step: If we cleaned up the backup profile, restore the JCR content
Condition none ConfigEngine task none
Parent Migrate data using the configuration wizardRelated concepts:
Troubleshooting: Migrate node profiles for a cluster environment
Configuration Wizard
Roadmap: Migrating a clustered environment