From Enterprise Designer, you can view, modify, and run the scripts that create or drop the monitoring and recovery database schema. First you must configure the database connection for the scripts.
Before you can run the database scripts, you need to configure the database connection information in the Project Explorer. Configure the connection for the administrator user who has privileges to your database.
In the Project Explorer, expand Sun BPM, and then expand Run Database Scripts.
Right-click Run Database Scripts, click Check Out, and then click Check Out on the dialog box.
Right-click Database Scripts and then click Properties.
Enter the database configuration information described in Configuring the Database Connection.
Click OK.
You can open the database scripts and view, modify, and run them within the Project Explorer. Consult your database administrator when making changes to the database scripts. Some of the changes you might need to make include:
For Oracle, you must specify a valid path for the DATAFILE parameter for both the bpm60db and bpel_data tablespaces. You can also change the tablespace names and disk space allocated for each tablespace.
Changing field length; for example, from varchar(255) to varchar(4000). Do this if you need to accommodate larger field lengths in the tables. You might experience errors if data exceeds the size allowed by the field.
Modifying the login ID and password used to create and access the tables. By default, both the user name and password are “bpm6user”. This is the login information that will be used by the Sun BPM Engine to access the database.
In the Project Explorer, expand Sum BPM.
Make sure Run Database Scripts is checked out, and then expand the folder.
Under Database Scripts, right-click the script you want to modify, and then click Open.
For Oracle 8.1.7 only, reduce the maximum key length for correlation keys from 4000 to 3166. The correlationvalue parameter belongs to the correlationengine and correlationbpinstance tables. The following code examples show the changes.
create table bpm60 correlationengine ( correlationvalue varchar(3166) UNIQUE, applicationreference varchar(255), ...); ... create table bpm60.correlationbpinstance ( correlationvalue varchar(3166) UNIQUE, bpid varchar(50), ...);
Make any other necessary changes to the script. Do not change any of the table or field names.
To run the database script, right-click the script name and click Run. The database instance must be running in order to perform this step.
To save your changes, right-click inside the script file and click Save, or close the file. You are prompted to save or discard your changes. To keep your changes, click Save; otherwise, click Discard.
Before running the database scripts, make sure you have a database instance running and have reviewed the information under Creating the Database Instance and Viewing and Modifying Database Scripts in Enterprise Designer. The connectivity information must also be configured for the scripts.
In the Project Explorer, expand Sum BPM, and then expand Run Database Scripts.
Right-click the file associated with the appropriate database (Oracle Install, SQL Server Install, DB2 Install, or Sybase Install).
Click Run.