Migrating self-service portal data

If your environment is configured so that the source OpenStack and self-service portal are connecting to different DB2® database servers, complete the following manual migration steps to migrate data for the self-service portal.

About this task

Important: These instructions are required only when you upgraded the OpenStack controller by running the command knife os manage migrate topology with the --no-ssp-openstack-in-same-database option.

To prepare for the self-service portal data migration, complete the following steps:

Procedure

Ensure that the target database exists.
Change IBM Cloud Manager - Self Service 4.3 to use the target database:
1. Open the database.properties file in the /var/opt/ibm/.SCE43 path.
2. Set the database.type property to DB2, as shown in the following example:
```
database.type=db2
```
3. Set the database.username property to the user ID that is defined for the target database, as shown in the following example:
```
database.username=db2user
```
4. Set the database.password property to the password that is defined for the target database, as shown in the following example:
```
database.password=db2passwd
```
  Note: The clear text password is replaced with an encrypted password after IBM Cloud Manager - Self Service launches the first time.
5. Set the database.db2.path property to the location of the DB2 target database, as shown in the following example:
```
database.db2.path=//localhost:50000/cfs:
```
  Note: Replace localhost with a full IP address. It can be a remote host.
Use the command service sce restart to restart IBM Cloud Manager - Self Service 4.3.
In your browser, log out and close all open self-service portal or IBM Cloud Manager - Self Service windows.
To migrate a DB2 database, use the following OSGi command:
```
upgradeDatabase ‘DB2_Path’ ‘DB2_User_Name’ ‘DB2_password’
```
where DB2_Path is the path of the DB2 database, DB2_User_Name is the name of the DB2 administrator, and DB2_password is the password for the DB2 administrator.
For example:
```
upgradeDatabase '//localhost:50001/skc' 'db2admin' 'db2passwd'
```
Notes:
- The upgradeDatabase command supports only major versions of databases.
- The source database must be DB2.
- Only approved requests can be migrated, while others such as pending requests, rejected requests, and withdrawn requests cannot be migrated. If the approved requests have related instances that are deleted, they cannot be migrated either.
- Before you migrate the self-service portal 4.2 data, wait 5 minutes after you start IBM Cloud Manager - Self Service 4.3 to ensure that the database is fully initialized.
- If any errors occur during migration, renew the target database and run the upgradeDatabase command again.
You can see migration details in the console.
You must restart IBM Cloud Manager - Self Service after migration. To restart it, use the service sce restart command.