Loading the database with system information in a network deployment environment

If you are creating a network deployment environment, you must run the command before you try to start or use Process Server or Process Center.

Before you begin

Important: Before you run the bootstrap command, ensure that you have applied Mandatory Interim Fix JR44669. For more information, see

Required interim fix for APAR JR44669. To download the fix, see

Required interim fixes for IBM Business Process Manager.

About this task

When you run the bootstrapProcessServerData command, configuration data for the BPM applications is loaded into the Process Server database. This data is required for the BPM applications to run correctly

In a network deployment (ND) environment, you must run this command after a server or cluster of servers is created. For a cluster, you need to specify the cluster name. Run this command after the database and its tables have been created, after the profile and deployment environment have been created, and before the first server is started. You do not need to rerun the command if you add another cluster member.
If a single WebSphere cell contains multiple application target clusters, you must run this command on each of the clusters.

Procedure

Run the bootstrap utility from the command line. The bootstrap utility is found in the deployment manager profile directory. For example:

install_root/profiles/Dmgr01/bin
install_root\profiles\Dmgr01\bin

Run the bootstrap utility using one of the following commands:

bootstrapProcessServerData.sh -clusterName cluster_name
bootstrapProcessServerData.sh -nodeName node_name -serverName server_name

where:

-clusterName is the name of the application target cluster. You must specify this parameter when you want the bootstrap data to run on a cluster.
-nodeName is the name of the node. You must specify this parameter and the -serverName parameter when you want the bootstrap data to run on the server that is part of the network deployment environment and not part of the cluster.
-serverName is the name of the server. You must specify either this parameter and the -nodeName parameter when you want the bootstrap data to run on the server that is part of the network deployment and not part of the cluster.

The parameters are case-sensitive.

Important: For SQL Server only: Ensure that the databases you create for Process Server and Performance Data Warehouse are case insensitive. The letters CI in the COLLATE attribute value specifies this. Ensure this variable looks like this: SQL_Latin1_General_CP1_CI_AS (not SQL_Latin1_General_CP1_CS_AS). Failure to do so can result in an error like the following:

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'message.routingCache' 
defined in class path resource [registry.xml]: Instantiation of bean failed; nested exception is 
org.springframework.beans.BeanInstantiationException: Could not instantiate bean class 
[com.lombardisoftware.bpd.runtime.engine.message.DefaultMessageRoutingCache]: Constructor threw exception; 
nested exception is org.springframework.jdbc.BadSqlGrammarException: PreparedStatementCallback; 
bad SQL grammar [select "value" from lsw_system where "key"=?]; nested exception is 
com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'lsw_system'.

Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'lsw_system'.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:196)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1454)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:388)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:338)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:4026)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1416)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:185)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:160)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(SQLServerPreparedStatement.java:281)
at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:205)
at org.springframework.jdbc.core.JdbcTemplate$1.doInPreparedStatement(JdbcTemplate.java:648)
at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:591)
[...]

Results

You have loaded the database with system information before successfully starting the IBM® Business Process Manager server. The log information for the bootstrap operation is saved to the USER_INSTALL_ROOT/logs/ directory in a file called bootstrapProcessServerData.clusterName.timestamp.log or bootstrapProcessServerData.nodeName.serverName.timestamp.log depending on the target you specified. The console displays a subset of the logged information.

Example

Bootstrap data onto a server that is part of an ND environment but not part of a cluster:

bootstrapProcessServerData

Bootstrap data onto a cluster that hosts the Process Server or Process Center:

bootstrapProcessServerData -clusterName myAppCluster