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 before you try to start or use Process Server.

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.

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

If you create a stand-alone profile and delay the database table setup, you must run the bootstrap command after the database and its tables have been created and before the server is started for the first time.

Procedure

Run the bootstrap utility from the command line. The bootstrap utility is found in the stand-alone profile directory. For example:

install_root/profiles/ProcSrv01/bin

Run the bootstrap utility using the following syntax:

bootstrapProcessServerData.sh

For a stand-alone profile, the -serverName and -nodeName parameters may be omitted; 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. The log information for the bootstrap operation is saved to the USER_INSTALL_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 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)
[...]

Example

Bootstrap data onto the default stand-alone profile server:

bootstrapProcessServerData.sh