Troubleshooting: Migrate node profiles for a cluster environment | HCL Digital Experience

Learn how to recover from a failure during the migration of the node profiles for an HCL Portal cluster environment.

Each potential step in the migrate node profiles option is included. Since the steps vary, depending on your selections, the steps are not numbered. Find the step that failed to learn more about correcting and recovering from the failure.

Manual Step: Stop the source deployment manager and node agents

About this task:

Since this is a manual step, any error that occurs is outside the context of the wizard.
Table 1. Appropriate actions for step: Stop the source deployment manager and node agentsIf you must run a configuration again, the table helps you determine what actions are appropriate.
Actions Notes®
Run the step again You can run this step again if it was not successful.
Skip the step If this step was successful, you can skip it if you run the configuration process again.
Clean up step None required

Manual Step: Start the target deployment manager

About this task:

Since this is a manual step, any error that occurs is outside the context of the wizard.
Table 2. Appropriate actions for step: Start the target deployment managerIf you must run a configuration again, the table helps you determine what actions are appropriate.
Actions Notes®
Run the step again You can run this step again if it was not successful.
Skip the step If this step was successful, you can skip it if you run the configuration process again.
Clean up step None required

Generate the files for remote migration

About this task:
Table 3. Appropriate actions for step: Generate the files for remote migrationIf you must run a configuration again, the table helps you determine what actions are appropriate.
Actions Notes®
Run the step again If this step fails, you can run this step again after you clean up the issue.
Skip the step If this step was successful, you can skip it if you run the configuration process again.
Clean up step

If this step fails, review the parameters and values that you entered in the Configuration Wizard, specifically the target temporary path and the application server path.

If the parameter and values that you entered are correct, and the step fails again, use the wp-collector tool to gather the files that are needed to contact support for help. See Data collection and symptom analysis for information about using the wp-collector tool.

Manual Step: Copy the remote migration package to the source environment

About this task:

Since this is a manual step, any error that occurs is outside the context of the wizard.
Table 4. Appropriate actions for step: Copy the remote migration package to the source environmentIf you must run a configuration again, the table helps you determine what actions are appropriate.
Actions Notes®
Run the step again Not applicable
Skip the step If this step was successful, you can skip it if you run the configuration process again.
Clean up step None required

Create a backup of the source portal profile

About this task:
Table 5. Appropriate actions for step: Create a backup of the source portal profileIf you must run a configuration again, the table helps you determine what actions are appropriate.
Actions Notes®
Run the step again If this step fails, you can run this step again after you clean up the issue.
Skip the step If this step was successful, you can skip it if you run the configuration process again.
Clean up step If this step fails, delete the path to the temporary backup profile, and run the step again.

For more information about troubleshooting the WASPreUpgrade command, see the WebSphere® Application Server documentation on Troubleshooting migration.

Manual Step: Create a backup of the remote source portal profile

About this task:

Since this is a manual step, any error that occurs is outside the context of the wizard.
Table 6. Appropriate actions for step: Create a backup of the remote source portal profileIf you must run a configuration again, the table helps you determine what actions are appropriate.
Actions Notes®
Run the step again If this step fails, you can run this step again after you clean up the issue.
Skip the step If this step was successful, you can skip it if you run the configuration process again.
Clean up step If this step fails, delete the path to the temporary backup profile, and run the step again.

For more information about troubleshooting the WASPreUpgrade command, see the WebSphere® Application Server documentation on Troubleshooting migration.

Manual Step: Update the deployment manager settings

About this task:

Since this is a manual step, any error that occurs is outside the context of the wizard.
Table 7. Appropriate actions for step: Update the deployment manager settingsIf you must run a configuration again, the table helps you determine what actions are appropriate.
Actions Notes®
Run the step again Not applicable
Skip the step If this step was successful, you can skip it if you run the configuration process again.
Clean up step None required

Manual Step: If the backup profile is larger than 2 GB, clean up the backup profile

About this task:

Since this is a manual step, any error that occurs is outside the context of the wizard.
Table 8. Appropriate actions for step: If the backup profile is larger than 2 GB, clean up the backup profileIf you must run a configuration again, the table helps you determine what actions are appropriate.
Actions Notes®
Run the step again Not applicable
Skip the step If you are running the configuration again, you can skip this step only if you skipped all the previous steps.
Clean up step None required

Create a default profile

About this task:
Table 9. Appropriate actions for step: Create a default profileIf you must run a configuration again, the table helps you determine what actions are appropriate.
Actions Notes®
Run the step again If this step fails, you can run this step again after you clean up the issue.
Skip the step If this step was successful, you can skip it if you run the configuration process again.
Clean up step If an unrecoverable error occurs and the create default profile step fails, remove the profile.
  1. Use the manageprofiles command to remove the profile.

    The command file is in the app_server_root/bin directory. The command file is a script that is named manageprofiles.sh|bat.

    Example:
     /opt/IBM/WebSphere/AppServer/bin/manageprofiles.sh -delete 
 -profileName profile_name
  2. Delete the profile directory.
  3. Then, run the Create a default profile step again.

Import the backup profile

About this task:
Table 10. Appropriate actions for step: Import the backup profileIf you must run a configuration again, the table helps you determine what actions are appropriate.
Actions Notes®
Run the step again If this step fails, you can run this step again after you clean up the issue.
Skip the step Do not skip this step, if you are running the configuration again. If you re-create the default profile from the Create a default profile step, then you must run this step again to import the new default profile.
Clean up step If an unrecoverable error occurs and the import backup profile step fails, remove the profile.
  1. Use the manageprofiles command to remove the profile.

    The command file is in the app_server_root/bin directory. The command file is a script that is named manageprofiles.sh|bat.

    Example:
     /opt/IBM/WebSphere/AppServer/bin/manageprofiles.sh -delete 
 -profileName profile_name
  2. Delete the profile directory.
  3. Then, run the Create a default profile step again before you rerun this step.

Manual Step: If you cleaned up the backup profile, restore the JCR content

About this task:

Since this is a manual step, any error that occurs is outside the context of the wizard.
Table 11. Appropriate actions for step: If you cleaned up the backup profile, restore the JCR contentIf you must run a configuration again, the table helps you determine what actions are appropriate.
Actions Notes®
Run the step again Not applicable
Skip the step Do not skip this step, if you are running the configuration again. You must restore the JCR content, if you completed the previous manual step to clean up the backup profile that is over 2 GB.
Clean up step None required