Restarting and verifying the migration

After you migrate to IBM® Business Process Manager, restart the deployment environment and verify that the migration was successful.

Figure 1. Sample environment after migration. The source environment is not running. The target environment is running and transferring data to and from its databases.

The details of the diagram are provided in the figure caption.

Procedure

IBM Business Process Manager V8.5.5 uses the more secure HTTPS protocol instead of HTTP.
- If you are connecting an online Process Server to Process Center, you must import the Process Server root SSL certificate into Process Center to enable HTTPS before you start the environment. Follow the instructions in steps 1 and 2 in Configuring SSL communication.
- Alternatively, if you want to switch back to using HTTP between Process Center and online Process Servers, run the following wsadmin commands on the Process Center and each Process Server. Run the commands from the bin directory of the deployment manager. In the following example, bpdServer is the name of the Process Center.
```
wsadmin -connType NONE -lang jython
wsadmin>bpdServer=AdminConfig.list("BPMProcessCenter").split()  # Use "BPMProcessServer" for Process Server
wsadmin>bpdServer  # You see the Process Center and Process Servers that you listed
wsadmin>print AdminConfig.showAttribute(bpdServer[0],'useHTTPSURLPrefixes') # You see the current value
wsadmin>AdminConfig.modify(bpdServer[0],[['useHTTPSURLPrefixes','false']]) # Set the value to false
wsadmin>AdminConfig.save()
```
  Restart all deployment managers, nodes, and deployment environments for Process Center and Process Servers.
Start the target environment. You should already have enabled the automatic starting of your applications and schedulers in the target environment in the "Enabling automatic starting, then stopping the environment" step.
1. Start the deployment manager and the nodes.
2. Start the target environment.
Verify that you can log in to the Business Process Choreographer Explorer and see all the process templates and your instances and tasks, and that the features are still working as before.
If you migrated Business Space, log in to Business Space to check that all the user-created spaces have been migrated.
To verify that Process Portal is working, complete the steps in Verifying Process Portal. If the other spaces (globe) icon in Process Portal does not work to navigate to other Process Portal spaces, delete your browser cache and reload the page.

What to do next

If you cloned your databases to test the migration, and you are satisfied with the results of your testing, retarget your new environment to point to the original source databases.

Restore and edit the previous BPMConfig configuration properties file that pointed to your source databases.
Create any new databases that are required and validate your database connections. Follow the instructions under Creating new databases and validating database connections for your specific database type. Alternatively, you can keep the databases that you created the first time that you went through the steps, especially if you want to keep the test data that you put into them.
Make sure that your target environment is shut down. Run the following command to retarget your target environment to point to your original source databases:
```
BPM_home\bin\BPMConfig -update -dataSource path_to_properties file
```
Important: To use this retarget feature, keep the user and schema name for each component the same in the cloned database as in the original database. This command updates only the host, port, and database name. It does not update the associated user authentication and schema.
Run the following command to generate the Upgrade SQL scripts again:
```
BPM_home\bin\BPMGenerateUpgradeSchemaScripts -propertiesFile target_migration_properties_file
```
where target_migration_properties_file is the full path to the migration properties file in which you specified the configuration information for the target environment
Back up your source databases before upgrading.
Copy the whole folder target_deployment_manager_profile\dbscripts\Upgrade\ to your database computer. On the database computer, run the following command to upgrade all schemas:
```
upgradeSchemaAll_de_name.bat
```
Run the DBUpgrade utility to modify your existing database schemas and data for use with IBM Business Process Manager V8.5.5. Follow the instructions under Upgrading existing databases for your specific database type. Only perform the steps necessary to run the DBUpgrade utility.