After you
migrate to IBM® Business Process Manager,
enable the automatic starting of all applications and schedulers in
the new version, and then restart the deployment environment. 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.
Procedure
- IBM Business Process Manager V8.5.6 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.
- Enable the automatic starting of all your
applications and schedulers in the target environment by running the
following command:
install_root\bin\BPMManageApplications.bat -autoStart true -target -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.
- -target specifies that the command will enable
the target environment.
You can follow the progress of the command by reading the
output, which includes the following actions:
- Changing the auto start setting for each individual application
- Setting the auto start for each scheduler
- Synchronizing all custom nodes with the cell repository
After the command has completed successfully, you see
a message similar to the following message:
CWMCO4021I: Auto-start properties were set for all applications and the scheduler daemon.
- Restart the target environment:
- Stop the target environment.
- Stop the deployment manager and the nodes.
- Start the deployment manager and the nodes.
- Start the target environment.
If you are migrating three clusters and using a DB2 for z/OS
database, you might receive an error and exception in the Performance
Admin console when you select any option other than the Welcome or View
Instrumentation option. For example:An error occurred while trying to view business performance server statistics
com/lombardisoftware/server/tracking/statistics/RecordCounts
This
problem is intermittent, but you can generally resolve the problem
by stopping and then starting the servers in the correct order to
resolve cross-dependencies between the three clusters. To stop and
then start the servers in the correct order, stop AppCluster, SupportCluster,
and MECluster, then start MECluster, SupportCluster,
and AppCluster.
- For a Process Center migration, use the Process
Center console and the Designer view in IBM Process
Designer to
verify that all process applications, toolkits, and assets are available
in the repository. From the Process Center console, verify
that connected servers are showing up and that previously installed
snapshots are accurately listed. Use the Inspector view in IBM Process
Designer to
check active instances.
- To verify that Process Portal is
working, complete the steps in Verifying Process Portal.
If there are problems with the index or searches
in Process Portal, you might need to rebuild the index. Follow the
instructions in Updating the Process Portal index.
If
you want to customize the index creation, for example, calculate the
completion dates for instances that are migrated from previous versions
of IBM BPM,
follow the instructions in Updating the Process Portal index.
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.
- If you are migrating from IBM BPM V8.0
or later, the cleanup of shared business objects is automatically
disabled. If you are using shared business objects in the source version,
you might want to change the cleanupMaxVersionCount property
to explicitly enable cleanup. See Cleaning up shared business objects for
instructions.
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:
install_root\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:
install_root\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.6. Follow
the instructions under Upgrading existing databases for
your specific database type. Only perform the steps necessary to run
the DBUpgrade utility.
- Export the service integration bus
(SIB) messages and advanced IBM BPM applications
from the source environment. See Exporting SIB messages and applications from the source environment.
- If you installed IBM Business Process Manager V8.5.6 on a
different computer from your source environment, copy the snapshot
to the target computer. See Copying the snapshot to the target computer.
- Disable the automatic starting of
applications and schedulers in the target environment, start the deployment
manager, start the managed node or nodes, and then start the servers.
See Starting the target environment.
- Import the SIB messages and advanced IBM BPM applications
into the target environment. See Importing SIB messages and applications to the target environment.