You can use the BPMConfig command
to create a typical network deployment environment using a properties
file that contains all of the values used in the configuration of
your deployment environment. At the same time as the deployment environment
is created, you can generate the scripts for creating the required
database tables, and create a new deployment manager profile and custom
profiles for managed nodes by including settings for these profiles
in the properties file used by the BPMConfig command.
Before you begin
You must have installed the product. You must
also have created all the users that you specify in the properties
file.
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.
About this task
When run with the
-create -de options,
the
BPMConfig command performs the following tasks:
- Creates any local profiles specified in the
configuration properties file that do not already exist.
- 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.
- Generates the scripts that you can use to create the database
tables.
Procedure
To create the deployment
environment for the first time, complete the following steps:
- On the computer where you want to
create the deployment environment, locate the appropriate sample properties
file: BPM_Home/BPM/samples/config.
- Find the sample properties file
that most closely represents your target deployment environment and
make a copy of this file. For each of the different
product configurations, there is a different folder containing sample
configuration files. For example, for configuring an Advanced, AdvancedOnly,
or Standard deployment
environment, there is an advanced, advancedonly,
or standard folder
containing a set of sample configuration properties files. Within
each 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],
where:
- de_type can be set to Advanced, AdvancedOnly,
or Standard .
- 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.
- suffix can be set to -WinAuth for
an SQL Server database.
For example, the sample configuration properties
file for configuring Advanced deployment environments with Process
Server in a single cluster topology using a DB2 for z/OS database
is called Advanced-PS-SingleCluster-DB2zOS.properties.
- Modify your version of the
properties file so that the values correspond to your own configuration. When modifying the sample properties file, use the guidance
provided within the file for specifying values.
When
you are configuring a Process Server environment to use Process Center
remotely, you must change the default value for the psProcessCenterHostname property
from local host to a valid host name. If you
are configuring an offline Process Server and the value for bpm.de.psOffline is
set to true, then you do not need to specify a value for the psProcessCenterHostname property.
Note: Your
modified properties file must use UTF-8 encoding.
Additional
notes for database configuration:
- By default, the bpm.de.deferSchemaCreation property
in the sample configuration properties file for DB2 for z/OS is set
to true. Do not change this setting, because, for
a z/OS database, you cannot create the database objects at the same
time that the database scripts are generated. After the BPMConfig command
completes, you can run the database scripts to manually create the
database objects at a time that you choose. When bpm.de.deferSchemaCreation is
set to true, the bootstrap utility, which loads the
Process database with system information, also must be run manually.
- Work with your DB2 for z/OS database administrator to establish
good naming conventions for DB2 components such as database names,
storage group names, schema qualifiers, and VSAM catalog names (VCATs).
Do not add any custom
properties to this file when you perform your modifications or the BPMConfig will
fail when it is run.
For more information about the available
properties, read the comments in the sample files, or see the BPMConfig command-line utility 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. For
example:
install_root/bin/BPMConfig -create -de my_environment.properties
Tip: You can also use the
BPMConfig command
to add cluster members by running the following command syntax:
BPMConfig -create -clusterMembers properties_file
The database SQL scripts are generated in the
DMGR_PROFILE/dbscripts folder
by default.
- The database scripts that can be used to
create the cell-scoped database are generated in DMGR_PROFILE/dbscripts/cell_name/DB2zOS/cell_database_name.
- The database scripts that can be used to create the cluster-scoped
database are generated in DMGR_PROFILE/dbscripts/de_name/DB2zOS/cluster_database_name.
These subdirectories also contain a
createDatabase.sh script,
which you can use to run the database scripts to create the DB2 for
z/OS database tables.
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.
- Use FTP to transfer all the generated database scripts
to the z/OS system that contains the installation of DB2. Transfer
the createDatabase.sh script as an ASCII text file,
and transfer the database schema files in binary mode.
- Optional: If you plan to
use applications with advanced content or that have been imported
into IBM Integration Designer and you are adding more than one deployment
environments to the cell, provide a way to distinguish between the
advanced content in these business level applications across the deployment
environments. For information, see the step that describes
how to set the AdvancedDeploymentDEScoped property
in Isolating deployment environments.
What to do next
After you have created your deployment environment, you can
create the product databases.
After you have created
your deployment environment and your database tables, you can start
the deployment manager, node agents, and clusters by running the BPMconfig command
with the -start action from the deployment manager
computer. If you are creating an Advanced or AdvancedOnly deployment
environment, the deployment manager and node agents need to be restarted
for the cell scoped configuration to take affect. This is only required
for the first deployment environment with Advanced or AdvancedOnly
capabilities.