Migrate a stand-alone server

We can use the Configuration Wizard to migrate a stand-alone server environment. Use the following information to get familiar with the information that provide in the wizard and the configuration procedure that it generates.

Configuration Wizard

Select Update or Maintain a Current Environment, and choose the Migrate a Stand-alone Server option.

Parent Migrate data using the configuration wizard

Related concepts:

Troubleshooting: Migrate a stand-alone server
Configuration Wizard
Roadmap: Migrating a stand-alone server environment

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 stand-alone server 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
Database management software	Derby
Target operating system
WebSphere Application Server administrator	wpsadmin
WebSphere Application Server administrator password
Portal administrator password
What is the portal profile name	wp_profile
What is the cell name	CellName
What is the portal node name	NodeName
Where is the source application server installed IBMi only: Provide the path to the source profile directory instead of the application server directory.	/opt/IBM/WebSphere/AppServer
What is the new host name
Target portal soap port	10033
Where is the target application server installed	/opt/IBM/WebSphere/AppServer
Where is the target portal installed	/opt/IBM/WebSphere/PortalServer
Target temporary path	/opt/IBM/WebSphere/PortalServer

Advanced fields

The following table lists the advanced fields unique to the migrate a stand-alone server configuration. Click Advanced on the Answer Questions page for the target system to see the advanced properties. Default values are provided for advanced fields that are required.

Field Label	Default	Your Value
JVM heap size	2048

Migrate a stand-alone server 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.

1. Manual Step: Install the latest fix packs

   Condition

   none

   ConfigEngine task

   none

2. Generate the files for remote migration

   Condition

   The target portal is on a different server than the source.

   ConfigEngine task

   none

3. 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

4. Create a backup of the remote source portal profile

   Condition

   The target portal is on a different server than the source.

   ConfigEngine task

   none

5. Create a backup profile of the source portal profile

   Condition

   none

   ConfigEngine task

   none

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

   Condition

   none

   ConfigEngine task

   none

7. Create a default profile

   Condition

   none

   ConfigEngine task

   none

8. Import backup profile

   Condition

   none

   ConfigEngine task

   none

9. Manual Step: If we cleaned up the backup profile, restore the JCR content

   Condition

   none

   ConfigEngine task

   none

10. Upgrade the ConfigEngine

    Condition

    none

    ConfigEngine task

    none

11. Manual Step: Update the ports on the target environment

    Condition

    none

    ConfigEngine task

    none

12. Manual Step: Update database settings

    Condition

    none

    ConfigEngine task

    none

13. Validate database settings

    Condition

    none

    ConfigEngine task

    validate-database

14. Connect to new database copies

    Condition

    none

    ConfigEngine task

    connect-database

15. Manual Step: Review database schema changes

    Condition

    none

    ConfigEngine task

    none

16. Upgrade the base portal database component

    Condition

    IBM z/OS

    DB2

    ConfigEngine task

    grant-runtime-db-user-privileges

    upgrade-database

17. Manual Step: Remove check pending statuses from table spaces

    Condition

    IBM z/OS

    DB2

    ConfigEngine task

    none

18. Upgrade the remaining portal databases

    Condition

    IBM z/OS

    DB2

    ConfigEngine task

    grant-runtime-db-user-privileges

    upgrade-database

19. 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.