Cluster: Upgrade node profiles
We can use the Configuration Wizard to upgrade the nodes profiles for a cluster environment. Use the following information to get familiar with the information provide in the wizard and the configuration procedure that it generates.
Select...
Update or Maintain a Current Environment | Migrate a Cluster Step 3: Upgrade Node Profiles option
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 3: Upgrade node profiles configuration option. 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 Database management software Derby WebSphere Application Server administrator wpsadmin WebSphere Application Server administrator password Target deployment manager host name Target deployment manager soap port 10033 What is the new host name Where is the target portal installed /opt/IBM/WebSphere/PortalServer
Advanced fields
The following table lists the advanced fields unique to the Migrate a cluster step 3: Upgrade node profiles configuration option. Click Advanced on the Answer questions page for the target node 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 3: Upgrade 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: Update the ports for the deployment manager and nodes
Condition none ConfigEngine task none
- Upgrade the ConfigEngine
Condition none ConfigEngine task none
- Update database settings
Condition none ConfigEngine task none
- Validate the database settings
Condition none ConfigEngine task validate-database
- Connect to new databases
Condition none ConfigEngine task connect-database
- Manual Step: Review database schema changes
Condition IBM z/OS DB2 ConfigEngine task none
- Upgrade the base portal database component
Condition IBM z/OS DB2 ConfigEngine task grant-runtime-db-user-privileges upgrade-database
- Manual Step: Remove check pending statuses from table spaces
Condition IBM z/OS DB2 ConfigEngine task none
- Upgrade the remaining portal databases
Condition IBM z/OS DB2 ConfigEngine task grant-runtime-db-user-privileges upgrade-database
- Upgrade the portal profile
Condition none ConfigEngine task upgrade-profile
When we run this step, the sub task named action-deploy-portlets-applyMIGStatic-wp.oob.full runs and completes successfully. However, the following error messages are shown. We can ignore these error messages:
- EJPXA0161W: The web module ContactList could not be activated. Please see previous messages for reasons and possible corrective actions.
- EJPPH0048W: The synchronization mode of all nodes in the portal cluster is not consistently set. The portlet application PA_ContactList will not be started in the Application Server. Manual synchronization is assumed for all nodes. Manually start the application after all nodes were synchronized.
- EJPXA0067E: The following configuration data is needed to create a content-node resource: content-parentref.
Parent Migrate data using the configuration wizardRelated concepts:
Troubleshooting: Upgrade node profiles for a cluster environment
Configuration Wizard
Roadmap: Migrating a clustered environment