Sample migration.properties files

During migration, you create two migration.properties file and call them source_migration.properties and target_migration.properties. You update them with information about the source (existing) environment and then with information about the target (new) environment.

You create your source_migration.properties and target_migration.properties files based on a provided sample.

If you installed the new version of the product on the same computer as the source environment, the sample file is BPM_home_8.5/util/migration/resources/migration.properties.
If you installed the new version of the product on a different computer and copied the migration files to the source environment, the sample file is remote_migration_utility/util/migration/resources/migration.properties.

The following samples show the information that you might add to the migration.properties file.

Sample file for the source environment
Sample file for the target environment

Sample file for the source environment

The following sample shows a source_migration.properties file.

#------------------------------------------------------------------------------------------------------------------------------------
# General instructions for migration properties file:
#   You must edit the properties in this file before you run any migration commands.
#   Each deployment environment requires its own migration.properties file. Make a copy of this file for each deployment environment.
#
# Usage: 
# 1. Before you run the following commands, edit this properties file to point to the source environment,
# including admin.username, admin.password, bpm.home, profile.name. If the source is a network deployment environment
# you also need to edit source.*.cluster.name.
#   --BPMManageApplications (If you want to manage applications on the source environment)
#   --BPMExtractSourceInformation
#	
# 2. Before you run the following commands, edit this properties file to point to the target environment,
# including admin.username, admin.password, bpm.home, profile.name, target.config.property.file, source.product.version
#   --DBUpgrade
#   --BPMManageApplications (If you want to manage applications on the target environment)
#   --BPMMigrate
#   
###############################################################################################
#                              Details for each property
###############################################################################################
# admin.username: 
#       (Required) The user who is authorized to connect to the deployment manager server or stand-alone server through a SOAP connection		
# admin.password:
#       (Required) The password of the user who connects to the deployment manager server or stand-alone server through a SOAP connection
# bpm.home:
#       (Required) The installation root of IBM BPM. Make sure that the file separators are  / (as in C:/BPM).
#       For previous WLE V7.1/V7.2, specify <WLE_Install_Dir>/AppServer.
#       Note: Use the full path. The tilde character "~", which stands for the user's home, cannot be used here.
#		Example:
#			Windows: bpm.home=c:/IBM/BPM
#			Linux/UNIX: bpm.home=/opt/IBM/BPM
# profile.name:
#       (Required) The name of the deployment manager profile in a network deployment environment or the name
#       of the stand-alone profile in a stand-alone environment
# source.application.cluster.name
# source.support.cluster.name
# source.messaging.cluster.name
# source.web.cluster.name
#       The cluster name of each type. This property is required if the source is the Network Deployment environment of IBM BPM Advanced, IBM BPM Standard, or WebSphere Process Server 6.2.x/7.x.
#       Edit them on both the source and target environment if you want to keep the mapping between source and target clusters.
# target.config.property.file
#       (Required for target environment) The full path of the configuration properties file that you used to create your target environment
#		Example:
#			Windows: target.config.property.file=c:/config.properties
#			Linux/UNIX: target.config.property.file=/opt/config.properties
# skip.steps.list:
#       (Optional) This property is only for debugging. It can skip the following steps of the migration:
#           snapshot.message, snapshot.application, snapshot.adapter
#           migrate.scheduler, migrate.message, migrate.application, migrate.adapter
#       Usage example: skip.steps.list=snapshot.message,migrate.message
#------------------------------------------------------------------------------------------------------------------------------------
admin.username=bpmadmin
admin.password=bpmpassw0rd

bpm.home=/opt/BPM850/WebSphere/AppServer
profile.name=Dmgr01

#Enter these properties when you are working on the source or target environment
source.application.cluster.name=MyTopPC80.AppTarget
source.messaging.cluster.name=MyTopPC80.Messaging
source.support.cluster.name=MyTopPC80.Support
source.web.cluster.name=MyTopPC80.WebApp
#Enter these properties when you are working on the target environment
target.config.property.file=

#(Optional) For debugging
skip.steps.list=

Sample file for the target environment

The following sample shows a target_migration.properties file.

#------------------------------------------------------------------------------------------------------------------------------------
# General instructions for migration properties file:
#   You must edit the properties in this file before you run any migration commands.
#   Each deployment environment requires its own migration.properties file. Make a copy of this file for each deployment environment.
#
# Usage: 
# 1. Before you run the following commands, edit this properties file to point to the source environment,
# including admin.username, admin.password, bpm.home, profile.name. If the source is a network deployment environment
# you also need to edit source.*.cluster.name.
#   --BPMManageApplications (If you want to manage applications on the source environment)
#   --BPMExtractSourceInformation
#	
# 2. Before you run the following commands, edit this properties file to point to the target environment,
# including admin.username, admin.password, bpm.home, profile.name, target.config.property.file, source.product.version
#   --DBUpgrade
#   --BPMManageApplications (If you want to manage applications on the target environment)
#   --BPMMigrate
#   
###############################################################################################
#                              Details for each property
###############################################################################################
# admin.username: 
#       (Required) The user who is authorized to connect to the deployment manager server or stand-alone server through a SOAP connection		
# admin.password:
#       (Required) The password of the user who connects to the deployment manager server or stand-alone server through a SOAP connection
# bpm.home:
#       (Required) The installation root of IBM BPM. Make sure that the file separators are  / (as in C:/BPM).
#       For previous WLE V7.1/V7.2, specify <WLE_Install_Dir>/AppServer.
#       Note: Use the full path. The tilde character "~", which stands for the user's home, cannot be used here.
#		Example:
#			Windows: bpm.home=c:/IBM/BPM
#			Linux/UNIX: bpm.home=/opt/IBM/BPM
# profile.name:
#       (Required) The name of the deployment manager profile in a network deployment environment or the name
#       of the stand-alone profile in a stand-alone environment
# source.application.cluster.name
# source.support.cluster.name
# source.messaging.cluster.name
# source.web.cluster.name
#       The cluster name of each type. This property is required if the source is the Network Deployment environment of IBM BPM Advanced, IBM BPM Standard, or WebSphere Process Server 6.2.x/7.x.
#       Edit them on both the source and target environment if you want to keep the mapping between source and target clusters.
# target.config.property.file
#       (Required for target environment) The full path of the configuration properties file that you used to create your target environment
#		Example:
#			Windows: target.config.property.file=c:/config.properties
#			Linux/UNIX: target.config.property.file=/opt/config.properties
# skip.steps.list:
#       (Optional) This property is only for debugging. It can skip the following steps of the migration:
#           snapshot.message, snapshot.application, snapshot.adapter
#           migrate.scheduler, migrate.message, migrate.application, migrate.adapter
#       Usage example: skip.steps.list=snapshot.message,migrate.message
#------------------------------------------------------------------------------------------------------------------------------------
admin.username=bpmadmin
admin.password=bpmpassw0rd

bpm.home=/opt/BPM850/WebSphere/AppServer
profile.name=Dmgr01

#Enter these properties when you are working on the source or target environment
source.application.cluster.name=MyTopPC80.AppTarget
source.messaging.cluster.name=MyTopPC80.Messaging
source.support.cluster.name=MyTopPC80.Support
source.web.cluster.name=MyTopPC80.WebApp
#Enter these properties when you are working on the target environment
target.config.property.file=/opt/config85/Advanced-PC-ThreeClusters-Oracle.properties

#(Optional) For debugging
skip.steps.list=