Loading the database with system information in a stand-alone environment

If you created a stand-alone profile and postponed creating the database tables, you must run the bootstrapProcessServerData command after the databases and tables have been created and before you try to start or use Process Server or Process Center.

About this task

When you run the bootstrapProcessServerData command, configuration data for the IBM® Business Process Manager applications is loaded into the Process database. This data is required for these applications to run correctly.

Note: This command runs automatically when you create a stand-alone profile and choose to create the database tables during profile creation.

Procedure

From the command line, locate the bootstrapProcessServerData utility in the following stand-alone profile directory:

BPM_HOME\profiles\profile_name\bin

For example:

BPM_HOME\profiles\Server1Profiles\bin

Run the bootstrap utility using the following command:

bootstrapProcessServerData.bat [-nodeName node_name -serverName server_name]

where:

node_name is the name of the node.
server_name is the name of the server.

Note: If IBM BPM was installed as admin user and User Account Control (UAC) is enabled on Windows, use the instructions in the topic

Using command-line tools in the WebSphere Application Server product information to run the bootstrapProcessServerData command.

If you omit the -nodeName and -serverName parameters, the bootstrapProcessServerData command automatically finds the one and only server in the stand-alone profile.

Results

You have loaded the database with system information before successfully starting the Process Server or Process Center. The log information for the bootstrap operation is saved to the profile_root\logs directory in a file called bootstrapProcessServerData.timestamp.log. The console displays a subset of the logged information.

Important: If the bootstrap utility fails, check that when you created the Process Server and Performance Data Warehouse databases, the COLLATE attribute indicated case insensitive (CI), not case sensitive (CS). That is, the create command should look like this:

CREATE DATABASE database_name COLLATE SQL_Latin1_General_CP1_CI_AS

Failure to do so can result in an error like in the following message:

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)
[...]

Example

Bootstrap data onto the default stand-alone server:

bootstrapProcessServerData