| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Administering: Running the Scripts in Enterprise Designer |
|
Administering the Sun Business Process Manager Database
Creating the Monitoring and Recovery Database
Creating the Database Instance
Running the Database Scripts from a Local Directory
Running Database Scripts Automatically
To run the scripts automatically
Purging and Archiving Sun BPM Data
Installing the Purge and Archive Database Components
Archiving and Purging by Retention Days
Archiving and Purging by Business Process Name
Archiving and Purging by Application Name
Using the Sun Business Process Manager Worklist Manager for User Activities
Maintaining Sun Master Indexes (Repository)
Working With the EDM for Sun Master Patient Index
Working With the EDM for Sun Master Index
Working With the Master Index Data Manager
Maintaining Sun Master Indexes
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.
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.
create table bpm60 correlationengine ( correlationvalue varchar(3166) UNIQUE, applicationreference varchar(255), ...); ... create table bpm60.correlationbpinstance ( correlationvalue varchar(3166) UNIQUE, bpid varchar(50), ...);
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.
Oracle Install, SQL Server Install, DB2 Install, or Sybase Install).