After
you install IBM® Business Process Manager V8.5, use
the BPMConfig command to create the profiles and
network deployment environment. The BPMConfig command
is required for migration. The deployment environment will use the
same databases as the source environment.
Figure 1. Sample environment after V8.5 is configured
on the target. The source environment is running and transferring
data to and from its databases. The target is not running but contains
a deployment environment. The deployment environment has three clusters
and is configured across two nodes.
Run the BPMConfig command to create
the deployment environment from a properties file that contains the
configuration values. At the same time, create a deployment manager
profile and custom profiles for managed nodes, by including settings
for these profiles in the properties file used by the BPMConfig command.
Important: If your environment contains multiple
deployment targets, each deployment environment requires its own properties
file with a unique name; for example, BPM.DE01 and BPM.DE01.
About this task
When run
with the
-create -de options, the
BPMConfig command
performs the following tasks:
- Creates the deployment manager node based on the values in the
deployment manager properties file and starts the deployment manager.
- For each node specified in the configuration properties file,
creates a managed node based on the specified values.
- Federates each managed node and adds the node to the deployment
environment.
- Generates the deployment environment.
- Creates any profiles specified in the configuration properties
file that do not already exist.
Important: Run
the BPMConfig command with the same properties
file on all computers that will participate in the deployment environment.
You must first run the command on the computer that has the deployment
manager profile and then run it on each computer that has a managed
node. At any given time, only one profile creation can be performed
on a computer and only one node federation can be performed against
a particular deployment manager. For this reason, if you are creating
multiple profiles at once on different computers, you must use the federateLater option
of the BPMConfig command when creating the managed
node profiles and then run the command with the create de option
sequentially on each computer to federate the managed nodes.
If you want WebSphere® Process
Server functionality
only, without any functionality from WebSphere Lombardi
Edition,
you can use the Advanced-Only deployment environment when you create
your deployment environment.
Procedure
For each deployment environment in your
target environment, complete the following steps:
- If you use a file-based user registry
in the source environment, use the same primary administrative user
name for the cell administrator as you used in the source environment. Reusing the administrative user name as the cell administrator
ensures that the data in the database has the same security context
and can still work with the same user after migration.
- On the computer where you want to configure
your new environment, locate the appropriate sample properties file: BPM_home\BPM\samples\config\migration\.
- Find the sample properties file that
most closely represents your target environment and make a copy of
this file. All the samples have component-specific database configuration
sections, but if you want to use the same database for multiple components,
you can do so by specifying the same database configuration properties
in different sections.
Important: You
cannot have the same database configuration properties for the Process
and Performance Data Warehouse databases. They each require their
own separate schema and database.
In
the migration folder, there is a set of files that are specific to
the different database types and configuration environments. The sample
files are named according to the following format: de_type[-environment_type]-topology-database_type[-suffix].
The following choices are valid:- de_type can be set to Advanced (if
you are migrating to IBM BPM
Advanced, with
full Process Center and Process Server functionality) or AdvancedOnly (if
you are migrating to the IBM BPM equivalent of WebSphere Process
Server)
- environment_type can be set to PS for
Process Server or PC for Process Center. This variable
is not used if de_type is AdvancedOnly.
- topology can be set to SingleCluster or ThreeClusters
- database_type can be set to DB2, DB2zOS, Oracle,
or SQLServer
- Optional: suffix can
be set to -WinAuth for an SQL Server database, or
to -MultiBus if you currently use multiple service
integration buses in the source environment and want to do the same
in the target environment. IBM BPM V8.5 supports
a single bus and messaging engine, which is the recommended configuration.
Choose the -MultiBus option only if you have a special
requirement for multiple buses.
For example, if you are
migrating to IBM BPM
Advanced,
you might select a file named Advanced-PS-ThreeClusters-DB2.properties.
- Modify your version of the properties file,
editing the properties for user credentials, database information,
hostname, and installation path. You must update all the properties
with the value @TO_BE_REPLACED@.
Important: If you have
more than one deployment environment to migrate, you must create a
separate properties file for each deployment environment. Use unique
and meaningful names for the files.
Tip: To find the database configuration
properties for each component, use the JNDI name to locate the information
in the database properties file that was extracted by the BPMExtractDBConfiguration command.
If you need to use a backslash character
(\) in your properties file when specifying path names, use an escape
backslash before it, for example bpm.dmgr.installPath=c:\\IBM\\BPM85.
Tip: In V8.5, the
common database is split into two pieces. One is cell-scoped (used
for the entire cell). The other, which includes event sequencing and
the failed event manager, is deployment-environment-scoped, and must
be configured for each deployment environment. For a single deployment
environment, you can reuse the previous common database for both cell-scoped
and deployment-environment-scoped data. For multiple deployment environments,
one of the new deployment environments can reuse the common database
but you must create a new deployment-environment-scoped database for
each extra deployment environment.
- If you are migrating to IBM BPM
Advanced (Advanced properties
file), you can use your existing common database or create a new one.
You must create a new separate Process database and Performance Data
Warehouse database:
- If you do not have a Business Space database,
define a new database for Business Space, or use your existing common
database for the Business Space tables. Specify the database properties
for BSpace capability to match the new database that
you would like to configure or your common database.
- If you already have a Business Space database, for the
database section with BSpace capability, use the
database credentials configured in the source version for the jdbc/mashupDS data
source (JNDI) name.
- Define a new common database for the deployment
environment or use the Business Space database. Specify the database
properties for CommonDB capability to match the new
database that you would like to configure or the Business Space database.
- For the database section with CellScopedDB capability,
use the database credentials configured in the source version for
the jdbc/WPSDB data source (JNDI) name.
- For the database section with BPC capability,
use the database credentials configured in the source version for
the jdbc/BPEDB data source (JNDI) name.
- Define a new Process database. Specify the database
properties for ProcessServer capability to match
the new database that you would like to configure.
- Define a new Performance Data Warehouse database.
Specify the database properties for PDW capability
to match the new database that you would like to configure.
- For the database section with Messaging capability,
use the database credentials that correspond to the database where
you want to configure messaging, usually the Business Space database.
You can also create a new messaging engine database or reuse an existing
one.
- If you are migrating to IBM BPM
Advanced: Process Server (AdvancedOnly properties
file), you can use your existing common database or create a new one:
- If you do not have a Business Space database,
define a new database for Business Space, or use your existing common
database for the Business Space tables. Specify the database properties
for BSpace capability to match the new database that
you would like to configure or your common database.
- If you already have a Business Space database, for the
database section with BSpace capability, use the
database credentials configured in the source version for the jdbc/mashupDS data
source (JNDI) name.
- Define a new common database for the deployment
environment or use the Business Space database. Specify the database
properties for CommonDB capability to match the new
database that you would like to configure or the Business Space database.
- For the database section with CellScopedDB capability,
use the database credentials configured in the source version for
the jdbc/WPSDB data source (JNDI) name.
- For the database section with BPC capability,
use the database credentials configured in the source version for
the jdbc/BPEDB data source (JNDI) name.
- For the database section with Messaging capability,
use the database credentials that correspond to the database where
you want to configure messaging, usually the Business Space database.
You can also create a new messaging engine database or reuse an existing
one.
If you had the
Business Process Archive Manager configured in your source environment
and you want to migrate your Business Process Archive Manager configuration,
you must specify the database properties for the BPCArchive capability
to match the existing Business Process Archive database in your source
version, as described in Configuring
Business Process Archive Manager.
Take special note of the following properties:
- bpm.de.deferSchemaCreation
- Set this property to true, because you are migrating and do not
want to initialize the databases while creating the deployment environment.
You will configure the databases later.
- User names and passwords
- You must provide values for several user name and password pairs
within the file because no values are provided by default. You must
use different administrative credentials for the cell and the deployment
environment.
Before running the
BPMConfig command,
you must have created all the database users that you specify in the
properties file.
Important: If you are using a SQL Server
database, make sure that the username and schema exist before the
configuration is done. The schema value should be the default schema
for the user chosen.
Do not add any custom properties to this file
when you perform your modifications or
BPMConfig will
fail when it is run.
Note: Your modified properties file must use UTF-8
encoding.
For more information about the available properties,
read the comments in the sample files, or see the BPMConfig command reference and
the sample property file descriptions in Configuration properties for the BPMConfig command.
- Run the BPMConfig command
on the computer that has the deployment manager, passing it the name
of the properties file you created.
BPM_home\bin\BPMConfig -create -de my_environment.properties
- Start the deployment manager. Run the BPMConfig command
on each computer that has one or more managed nodes, passing it the
name of the same properties file.
Note: For each node that
is to be configured on a different machine from the deployment manager,
check the soap port of the deployment manager and update the value
of bpm.dmgr.soapPort in the properties file before
running BPMConfig on the node.
Note: For each cluster member
in the properties file, BPMConfig adds http and https ports
to the virtual hosts list. Check the virtual hosts list after running BPMConfig to
make sure that the assigned ports are acceptable.
- Stop the deployment manager
after you have configured the target environment.
What to do next
Do not start the
new deployment environment until after you have upgraded the databases.