Skip Navigation Links | |
Exit Print View | |
Administering the Oracle Java CAPS Business Process Manager Database Java CAPS Documentation |
Administering the Oracle Java CAPS Business Process Manager Database
Creating the Monitoring and Recovery Database
Creating the Database Instance
Creating the Database in Sybase
Running the Scripts in NetBeans
Configuring the Database Connection
Viewing and Modifying Database Scripts in NetBeans
Running the Database Scripts from a Local Directory
Running Database Scripts Automatically
To Run the Scripts Automatically
Purging and Archiving Oracle Java CAPS BPM Data
Installing the Purge and Archive Database Components
To Install the Purge and Archive Database Components
Archiving and Purging by Retention Days
To Purge Records Based on Days
To Archive Records Based on Days
Archiving and Purging by Business Process Name
To Purge Records Based on Business Process Name
To Archive Records Based on Business Process Name
Archiving and Purging by Application Name
To create the monitoring and recovery database tables, you can either modify and run database scripts from NetBeans or you can download the scripts and run them from a local directory. Depending on which method you prefer, review one of the following sections:
Before you can run the database scripts, you must create a database instance in which the tables will be created. This is standard for Oracle and SQL Server, but requires additional steps for Sybase and DB2.
In order to run the database installation scripts in Sybase, the server page size must be 16k. Set the server page size when you create the adaptive server on which you will run the Sybase scripts.
Using DB2 with Oracle Java CAPS BPM requires a few extra setup steps. Review this section and ask your database administrator to review the installation script prior to running any scripts against your DB2 database instance. The database administrator needs to use the DBA or Sysadmin/DB2 user to create the following:
A database instance on the server.
A tablespace named BPM6USERDB.
A new user that has privileges to create objects in the database such as tables, indexes, sequences objects, and so on.
A 32k User temporary tablespace. A User temporary tablespace gives Oracle Java CAPS BPM space for declared temporary tables. Use the DB2 administrative tool to create the tablespace. For detailed information about creating a DB2 User temporary tablespace, see the DB2 documentation. When you create the temporary tablespace, use the following parameter settings:
Pagesize: 32KB
Buffer Pool Size: 32KB
System-managed space
Average table size: 2GB to 20GB
Prefetch size: 32KB
Extent size: 32KB
Overhead: 10.5 ms
Transfer rate: 0.14 ms
From NetBeans, 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 NetBeans Projects window. 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 NetBeans. 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 of the created 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 Java CAPS BPM Engine to access the database.
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 NetBeans. The connectivity information must also be configured for the scripts.
You can download the database scripts and run them outside of the Java CAPS environment. Make sure to review the information under Creating the Database Instance, which contains information specific to Sybase and DB2 databases.
The following files are included in the zipped file.
install_db.bat - Creates the tablespace, users, tables, stored procedures, and any initial values.
uninstall_db.bat - Drops any database components created by the install_db.bat script (that is, it drops tables and users, and deletes stored procedures).
database-specific SQL scripts - Scripts that are called by the install_db.bat and uninstall_db.bat scripts (such as create_tables.sql, drop_tables.sql, and so on).
Readme.txt - Contains additional instructions specific to your database application. You should review this file before running the scripts.
In order to work with the compressed script files, you need to export them to a local directory and then extract the compressed files.
Once you download the compressed database scripts and modify them as needed, you can run the scripts from a command line. The database user that executes these scripts must have permission to create tables and users. Before you run the scripts, make sure you have reviewed the installation scripts the modified them for your environment. For more information, see Viewing and Modifying Database Scripts in NetBeans. Additional information for modifying these files is available in the Readme.txt file included in each ZIP file.
For Oracle databases, enter the following command:
install_db user password database
For Sybase and SQL Server databases, enter the following command:
install_db user password server database
For DB2 databases, enter the following command:
install_db user password database server
Where:
user is the database username.
password is the database user password.
server is the name of the machine on which the database resides.
database is the database or SID name.
Note - The default user and password created from these scripts is "bpm6user". You can modify the user, password, disk space allocated for tables, and user permissions. The table and column definitions should not be modified.