Create the Process Center deployment environment for DB2

IBM BPM, V8.0.1, All platforms > Install IBM BPM > IBM BPM Advanced > Install IBM BPM Advanced > On Windows > Network deployment environment > Configure profiles and create an ND environment > Create an ND environment > Use the Deployment Environment wizard > DB2 database server
Create the Process Center deployment environment

After determining the pattern on which to base your ND configuration, use the Deployment Environment wizard to create the Process Center deployment environment that is based on the pattern.
You must have completed the following tasks:

Installed the product
Created the dmgr profile and the associated nodes

Additionally, one of the steps in the Deployment Environment wizard includes importing a database design document. The database design document defines the database configuration for the selected deployment environment features. IBM BPM includes a response-driven database design tool (DDT) that creates a database design document based on user inputs. In addition to creating the design document, the DDT provides an option to create the database tables as well. Typically, the person running the DDT would choose to create the database tables at that point.The document then can be used by the DDT to create the database scripts and by the IBM BPM Deployment Environment wizard to configure the databases used in the deployment environment.

DB2 considerations:

IBM Process Server and Performance Data Warehouse should not use the same database.

Procedure

If you make an error while you are working in the wizard, you can go back by clicking Back.

From the administrative console, navigate to the Deployment Environments page by clicking...
Servers | Deployment Environments

Launch the Deployment Environment wizard by clicking New on the Deployment Environments page.

The option...
Create a deployment environment based on a pattern

...is selected. This is the default pattern.
A pattern provides you with a template for the deployment environment that you are creating.
The system default pattern is...
Remote messaging and remote support

Enter a unique name for the deployment environment in the Deployment environment name field.
To view all of the configuration steps in the wizard, select
Detailed: Show all steps

If you choose Fast path: Show only needed steps the wizard displays only those pages that do not have assigned default values. Choose Fast path: Show only needed steps only if you are agreeable to accepting the system-provided default values for the deployment environment configuration.
This topic assumes that you have chosen Detailed: Show all steps
Click Next to display the Deployment Environment Features page.

On the Deployment Environment Features page, select the feature for the deployment environment and click Next to either view a list of compatible features, or to view a list of deployment environment patterns.
The list of available features is based on the dmgr profile. If your dmgr profile has been augmented to include other products alongside IBM BPM, for example IBM Business Monitor, then the Deployment Environment Features page also lists these features.
If you have configured a profile for IBM BPM, then the page includes the following details:

For IBM BPM Advanced:

WESB WebSphere Enterprise Service Bus. Provides a deployment environment that supports mediations.
BPMAPS IBM BPM Advanced, Process Server dmgr profile. Provides a Process Server deployment environment that supports mediations, business processes, human tasks, Business Space functions, and business rules.
BPMAPC IBM BPM Advanced, Process Center dmgr profile. Provides a Process Center deployment environment that supports mediations, business processes, human tasks, Business Space functions and business rules.

The default value for the deployment environment feature matches the runtime capabilities of your dmgr.

On the page...
Select compatible deployment environment features
...select additional features as necessary and click Next to view the list of patterns associated with your feature selections.
The page is displayed only if the dmgr has been augmented with other BPM features, such as IBM Business Monitor.

On the page...
Select the deployment environment pattern
...select the pattern for the selected deployment environment, then click Next to display the Select Nodes page.
The list of patterns that display is dynamic. This list is activated by, and dependent on, the following environment conditions:

The platform on which you have installed the software
The selections made on pages...
Select the deployment environment features
Select compatible deployment environment features

Optional: On the page...
Select Nodes
...select the nodes to include in this deployment environment, then click Next to display the Clusters page.
To include a node, select the check box next to the node name. Use Node Mapping to map the selected node to another node name.
Select nodes that have the required capabilities for the environment you selected on the Deployment Environment Features page.
For example, if you selected BPMSPC as your Deployment Environment type, the nodes selected should address the capabilities of that environment type.
Select at least one node for the deployment environment. For high-availability and failover environments, select at least two nodes. For scalability, select all nodes.
Optional: On the Clusters page, assign the required number of cluster members and the initial port to be used on each node for the cluster members of all cluster types.
By default one cluster member is assigned on each node for each function. You change the number by replacing the number in each column.
A 0 (zero) value for a node means that the node does not contribute to the selected function, based on features that you have selected.
After assigning cluster members, you can click Next to display the Cluster naming pages for each cluster type of the deployment environment. The Cluster naming substeps that display will vary depending on the deployment environment pattern selected.
You can specify the initial port using the text box...
Specify the port number for the first cluster group (Optional)
Port numbers are reserved and assigned to each node for the cluster members using the port number that is specified. If you specify an initial port when you create the deployment environment, that same initial port specified would be assigned to the first cluster member and subsequent cluster groups would be assigned ports after increasing the port value by 20.
For example, if the port number for the first cluster group is 2000, the port numbers of the cluster members would be 2000, 2001, 2002, and so on. The port number of the second cluster group would be 2020 and the port numbers for the members of the second cluster group would be 2020, 2021, 2022, and so on. The port number of the third cluster group would be 2040.
If there is already a node on that physical system then there may be port conflicts and these would need to be resolved manually by changing the port values.
The system generates default values for cluster names and cluster member names.
If you do not want to customize cluster names or cluster member names, you can use the wizard navigation pane to go directly to the REST Services page in a following step.
Optional: Customize the cluster names and cluster member names.
Use the Cluster Naming page to customize cluster names or cluster member names for the cluster type. There is one substep page for each cluster type in the pattern that you have selected.
For example, if you selected a Remote messaging and remote support pattern, there are 3 substeps, one for each type of cluster (Application Deployment Target, Messaging Infrastructure and Supporting Infrastructure) in that pattern.

Field Description Value
Cluster Read-only field specifying the functional role of the cluster. Value varies depending on the cluster type...

Application Deployment Target
Supporting Infrastructure
Messaging Infrastructure
Web Application Infrastructure

Cluster name System-generated default value for the cluster name. Values are based on a naming convention of Deployment Environment Name. Cluster type name, where cluster type names...

Name Role
AppTarget Application deployment target
Messaging Messaging infrastructure
Support Supporting infrastructure
Web Web applications. WebSphere Business Monitor is the primary feature.

Cluster member name System-generated default value for the cluster member name. Accept the system-generated default value or specify a name of your choosing. Default is based on the following naming convention:
cluster name. node name. node number sequence

The number of cluster member names that display in the table match the number of cluster members entered for the cluster type column and node row on the Clusters page.

On the page...
System REST Service endpoints
...configure service endpoints for Representational State Transfer (REST) API.
If you want widgets to be available in Business Space, configure the REST service endpoints for those widgets.

Configure a full URL path for all REST services by selecting either https:// or http:// from the Protocol list.
Enter a name in the field...
Host Name or Virtual Host in a Load-Balanced Environment

In the Port field, enter the port that a client needs to communicate with the server or cluster.
In the table of REST services, to modify the description of the REST service endpoint, overtype the entry in the Description field. The other fields are read-only.
Click Next to go to the Import the database configuration page.

Optional: On the page...
Import the database configuration

...click Browse to go the database design document or enter the path to the database design document and then click Next to go to the Data sources page.
If you import a design document, the information from the design document is reflected on the Database page of the wizard. The design document can be based on a database design created using the database design tool (DDT), or it can be the supplied design document based on the pattern and feature that you have selected.
The database design document that you import for the deployment environment does not change the commonDB created at Profile Creation time.

On the Database page, configure the database parameters for data sources of the deployment environment, then click Next to go to the Security page.
Where possible, the wizard supplies default information for the parameters, but change those values to match the values that you defined when you planned the environment. Whether or not this step displays for a fast path deployment environment configuration is conditional. This step displays for a fast path deployment environment configuration if more than one database has been defined or if you are using a DB2 for z/OS or an Oracle database provider.
The database specified in this panel must already exist. Deployment environment configuration never creates a new database. Additionally, if you imported a database design document, the information on the Database page reflects the data source configuration as it exists in the database design document that you imported. If you make changes to the data source configuration after importing a database design document, your changes might be incompatible with the DDL generated by the database design tool and the original values.
CAUTION:
The default schema names that are displayed on this page might conflict with your site naming convention or might conflict with existing schemas. As such, it is likely that you will need to change the schema name. Pay close attention to the values specified to avoid potential naming conflicts.

DB2 considerations:

IBM Process Server and Performance Data Warehouse should not use the same database.

For a production environment, you should set the same values for User name and Schema name and you should clear Create tables. For a production environment, create the required schemas manually and use the SQL files generated to create the tables. When you create a 4-cluster Process Server using the Deployment Environment wizard the process will take a lot of time to complete.
Perform one of the following steps to create the 4-cluster Process Server:

Increase the transaction timeout value using the Deployment Manager and re-create the deployment environment.

Do not create tables during the Deployment Environment creation. After creating the environment create the databases, tables, and then run the bootstrap command.

You cannot select Create tables for Business Space (the option is unavailable for selection). The SQL files for Business Space need to be run manually. .
You can edit all key parameters, such as the database name, whether or not to create tables, the data source runtime user name, and the password for the deployment environment. You can select which database to use for the given component.
Steps that cannot be completed through the Deployment Environment wizard, and which need to be completed manually, are listed on the Deferred Configuration page.

On the Security page, configure the authentication aliases used when accessing secure components
You can change the authentication alias user name and password on this page. These aliases are used to access secure components but do not provide access to data sources

On the Business Process Choreographer page, set parameters for the Business Process Choreographer configuration and then click Next to display the Web application context roots page. On this page you specify the values for:

Security roles
Authentication aliases

Optional: On the Web application context roots page, set the context root for component-based web applications in your deployment environment or accept the system-provided default values for the context roots.
The Web application context roots page displays for deployment environments using the Remote Messaging, Remote Support, and Web Applications pattern.
The table contains the following control information.

Web Application Name of the web application.
Some of the components that are part of the deployment environment you are creating contain web applications. The Web Application column can include the following components:

Business Space
Business Process Choreographer Explorer
Business Process Rules Manager

Context Root Current value of the context root for the component.
By default, the default context root for the web application applies. You can change the context roots by typing over the value in the Context Root field. The Business Space context root is read only and cannot be edited.

Verify that the information on the Summary page is correct and perform the following substeps:

If you do not want to save the deployment environment configuration, you can click Cancel.
If you want to exit without generating the configuration, click Finish.
To get back to the panel (if you exited without completing), from the administrative console:
Deployment Environments | name of deployment environment | Generate Environment

To save the deployment environment configuration, click Finish and from within the Messages window, click Save.
Clicking Save saves the deployment environment to the master configuration. If an error should occur during deployment environment generation, the configuration settings will have been saved to the master configuration.
Check for deferred configuration steps

Deployment Environments | name of deployment environment | Deferred Configuration

You need to address any existing deferred configuration steps before starting the Deployment Environment.
If you are satisfied, click Finish and Generate Environment to save.

Load the database with system information by running the bootstrapProcessServerData command.
This command must be run before starting any cluster members.

Complete your Process Portal configuration :

If you are using a three or four cluster configuration, and you have not yet configured a routing server for Business Space, to ensure that requests for Process Portal are redirected to the correct cluster, perform the actions in one of the following.

Configure IBM HTTP Server for Business Space: .
Configure a WebSphere Application Server proxy server for Business Space: .
Mapping Business Space URLs for a reverse proxy server: .

The reason why you need a routing server for three and four cluster configurations is because Process Portal uses web components that are distributed across two clusters. If you do not configure a suitable server to redirect requests to the appropriate clusters, the web browser’s same origin policy will prevent Process Portal from working correctly. In a three cluster configuration, Process Portal relies on applications on both the application deployment target cluster and the support cluster. In a four cluster configuration, Process Portal relies on applications on both the application deployment target cluster and the web cluster.
If you want users to be able to access Process Portal using HTTP rather than the Business Space default of HTTPS, perform Designating HTTP or HTTPS settings for Business Space: .

Perform Verifying Process Portal: .

Results

When the configuration completes, you can examine the configuration files to view the changes.

What to do next

Either save the changes to the master configuration or discard them.
After you have configured an ND environment, if you test the data store connection (for example, in the administrative console, on the page Resources > JDBC > Data sources), you get a message saying that the test connection operation failed with the exception com.ibm.wsspi.runtime.variable.UndefinedVariableException: Undefined Variable WAS_INSTALL_ROOT. This does not necessarily indicate that there will be a problem accessing the data source at run time. Ensure that the location of your JDBC driver files is accessible to every client that must use the data source, and configure the variable with the full path of that location. Disregard the test connection error unless you are also experiencing trouble connecting to the data store at run time. For additional information, see the WebSphere Application Server documentation about the test connection service.
If you use additional servers with unique ports, WebSphere Application Server does not automatically configure the virtual host for the server. Specifically, WebSphere Application Server does not automatically add the host alias ports to a virtual host. However, you can use the administrative console to add a new host alias for each of the ports used by the new server. Clean all applicable profile logs or save them in another directory. You may want to clean or move the logs as they will be appended with the last configuration. This can make it difficult to view the most current information.
If you are using DB2 PureScale, you must also configure automatic client rerouting and configure workload balancing.

Related tasks:
Planning your ND environment:
Create database design files
Create database design files
For DB2 for z/OS
Create database design files
Loading the database with system information

WESB	WebSphere Enterprise Service Bus. Provides a deployment environment that supports mediations.
BPMAPS	IBM BPM Advanced, Process Server dmgr profile. Provides a Process Server deployment environment that supports mediations, business processes, human tasks, Business Space functions, and business rules.
BPMAPC	IBM BPM Advanced, Process Center dmgr profile. Provides a Process Center deployment environment that supports mediations, business processes, human tasks, Business Space functions and business rules.