Creating Additional ASA or ASE Databases

You have the option of using multiple Adaptive Server Anywhere (ASA) or Adaptive Server Enterprise (ASE) databases to separate data storage for these components. However, this process requires expert knowledge in database administration. Without this expertise, Sybase recommends using the single, default ASA Production Edition database.

Review the following recommendations before creating additional ASA or ASE runtime databases.

**Table 9-1: Database Distribution Recommendations**
Component	ASA Recommendations	ASE Recommendations
Alert Management System	Choose from the following: Use the default ASA database to support AMS data during production. Separate the Alert Management System production database from the default ASA database. Copy the existing AMS database file to the desired location, or copy the <installation directory>\Orch-5_0\dbs\template\UORuntime.db template to start with a fresh database. For the Alerts server, use EAServer Manager to reconfigure the EAServer environment entries for the Message Driven Beans that are in the deployment descriptors. Change AMS_JDBC_URL to point to the correct host and port number. See the EAServer 5.2 product documentation on the Sybase WorkSpace online bookshelf for more information. Use EAServer Manager to create an Application Server Connection Cache, set the URL for that cache, add a JNDI reference to the Runtime Management Console web application. See the EAServer 5.2 product documentation on the Sybase WorkSpace online bookshelf for more information. Use the Runtime Management Console to edit the Alerts Repository setup to point to the new JNDI reference in EAServer. See the Runtime Management Console Online Help for more information.	Unwired Orchestrator does not provide support for AMS outside the default ASA database.
BAM Dashboard	The Dashboard makes light use of the database to read its metadata at startup and save new metadata when dashboards are modified or new dashboards are created. However, you have the option of separating dashboard production data into its own database. Choose from the following: Couple the dashboard data with Alert Management System data. No ASA scripts are needed to perform this action. Use the Runtime Management Console to edit the Database URL property in the BAM Dashboard Repository. Export/import existing BAM Dashboard metatdata. See the Runtime Management Console Online Help for more information. Create a new database using Sybase Central. Enable the jConnect meta-information support, turn on case-sensitivity for comparisons and passwords, and create SYSCOLUMNS and SYSINDEXES views. Run the following script using interactive SQL or dbisql: <installation directory>\Orch-5_0 \install.sql\scripts\asa\dashboard_ part1.sql Use the Runtime Management Console to edit the Database URL property in the BAM Dashboard Repository. Export/import existing BAM Dashboard metatdata. See the Runtime Management Console Online Help for more information	The Dashboard makes light use of the database to read its metadata at startup and save new metadata when dashboards are modified or new dashboards are created. However, you have the option of separating dashboard production data into its own database. To accomplish this, do the following: Create a new database. Create a distinct database owner account. Define the database size to be 25MB for data and 10MB for the transaction log. Create the segment DASHBOARD_COMMON. Run the following script using interactive SQL or dbisql: <installation directory>\Orch-5_0 \install.sql\scripts\ase\dashboard_ part1.sql Use the Runtime Management Console to edit the Database URL property in the BAM Dashboard Repository. Export/import existing BAM Dashboard metatdata. See the Runtime Management Console Online Help for more information.
Monitor	Business Activity Monitoring has the potential of requiring significant database resources. If this potential exists, separate the monitor production data from all other component data. Do the following: Create a new database using Sybase Central that has a page size of 2KB. Enable the jConnect meta-information support, turn on case-sensitivity for comparisons and passwords, and create SYSCOLUMNS and SYSINDEXES views. Run the following scripts using interactive SQL or dbisql: <installation directory>\Orch-5_0\ install.sql\scripts\asa\monitor_part1.sql <installation directory>\Orch-5_0\ install.sql\scripts\asa\monitor_part2.sql Use a text editor to edit the following configuration file: <installation directory>\Orch-5_0\bin\ nnsyreg.dat Run the BT59ie utility to export and import SetType metadata from the existing database. See Sybase WorkSpace Development in the Sybase WorkSpace online bookshelf for more information.	Business Activity Monitoring has the potential of requiring significant database resources. If this potential exists, separate the monitor production data from all other component data. Do the following: Create a new database on a server that has a page size of 2KB. Create a distinct database owner account. Define the database size to be 100MB for data and indexes and 50MB for the transaction log. Create the segments MSGTRAK_DATA and MSGTRAK_INDEX. Turn on the ddl in tran option. Run the following script using interactive SQL or dbisql: <installation directory>\Orch-5_0\ install.sql\scripts\ase\monitor_part1.sql <installation directory>\Orch-5_0\ install.sql\scripts\ase\monitor_part2.sql Use a text editor to edit the following configuration file: <installation directory>\Orch5_0\bin\ nnsyreg.dat Run the BT59ie utility to export and import SetType metadata from the existing database. See Sybase WorkSpace Development in the Sybase WorkSpace online bookshelf for more information.
BPEE/ Quartz Timers/ JMS Queues	BPEE/Quartz Timers/JMS Queues has the potential of requiring significant database resources. If this potential exists, separate the BPEE/Quart Timers/JMS Queues production data from all other component data, especially the monitor data. Do the following: Create a new database file on a server that has a page size of 16KB. Enable the jConnect meta-information support, turn on case-sensitivity for comparisons and passwords, and create SYSCOLUMNS and SYSINDEXES views. Run the following script using interactive SQL or dbisql: <installation directory>\Orch-5_0\ install.sql\scripts\asa\quartz_create.sql Configure Unwired Orchestrator to point to the new database and redeploy your business process service. See Sybase WorkSpace Development in the Sybase WorkSpace online bookshelf for more information ASA is not a viable data source for use within BPEE. It cannot support distributed transactions in environments that require a transaction manager other than Microsoft Distributed Transaction Coordinator.	BPEE/Quartz Timers/JMS Queues has the potential of requiring significant database resources. If this potential exists, separate the BPEE/Quart Timers/JMS Queues production data from all other component data, especially the monitor data. Do the following: Create a new database on a server that has a page size of 16KB. Set the Runnable Process Search Count to 10000 to optimize performance. Create a distinct database owner account. Define the database size to be 100MB for data and 50MB for the transaction log. For Distributed Transactions, also do the following: Enable DTM on the server if you want to use Distributed Transactions within Unwired Orchestrator. This option requires that you set some configuration variables in ASE. See Using Adaptive Server Distributed Transaction Management Features Guide on the Sybase WorkSpace online bookshelf for more information. Grant the dtm_tm_role to the user login of the database owner account. Turn on the ddl in tran and allow nulls by default options. Run the following script using interactive SQL or dbisql: <installation directory>\Orch-5_0\ install.sql\scripts\ase\quartz_create.sql Configure Unwired Orchestrator to point to the new database and redeploy your business process service. See Sybase WorkSpace Development in the Sybase WorkSpace online bookshelf for more information.

Table 9-1: Database Distribution Recommendations

Component

ASA Recommendations

ASE Recommendations

Alert Management System

Choose from the following:

Use the default ASA database to support AMS data during production.
Separate the Alert Management System production database from the default ASA database.
- Copy the existing AMS database file to the desired location, or copy the <installation directory>\Orch-5_0\dbs\template\UORuntime.db template to start with a fresh database.
- For the Alerts server, use EAServer Manager to reconfigure the EAServer environment entries for the Message Driven Beans that are in the deployment descriptors. Change AMS_JDBC_URL to point to the correct host and port number.
  
  See the EAServer 5.2 product documentation on the Sybase WorkSpace online bookshelf for more information.
- Use EAServer Manager to create an Application Server Connection Cache, set the URL for that cache, add a JNDI reference to the Runtime Management Console web application.
  
  See the EAServer 5.2 product documentation on the Sybase WorkSpace online bookshelf for more information.
- Use the Runtime Management Console to edit the Alerts Repository setup to point to the new JNDI reference in EAServer.
  
  See the Runtime Management Console Online Help for more information.

Unwired Orchestrator does not provide support for AMS outside the default ASA database.

BAM Dashboard

The Dashboard makes light use of the database to read its metadata at startup and save new metadata when dashboards are modified or new dashboards are created. However, you have the option of separating dashboard production data into its own database.

Choose from the following:

Couple the dashboard data with Alert Management System data. No ASA scripts are needed to perform this action.
- Use the Runtime Management Console to edit the Database URL property in the BAM Dashboard Repository.
- Export/import existing BAM Dashboard metatdata.
  
  See the Runtime Management Console Online Help for more information.
Create a new database using Sybase Central. Enable the jConnect meta-information support, turn on case-sensitivity for comparisons and passwords, and create SYSCOLUMNS and SYSINDEXES views.
- Run the following script using interactive SQL or dbisql:
  
  <installation directory>\Orch-5_0 \install.sql\scripts\asa\dashboard_ part1.sql
- Use the Runtime Management Console to edit the Database URL property in the BAM Dashboard Repository.
- Export/import existing BAM Dashboard metatdata.
  
  See the Runtime Management Console Online Help for more information

To accomplish this, do the following:

Create a new database.
Create a distinct database owner account.
Define the database size to be 25MB for data and 10MB for the transaction log.
Create the segment DASHBOARD_COMMON.
Run the following script using interactive SQL or dbisql:

<installation directory>\Orch-5_0 \install.sql\scripts\ase\dashboard_ part1.sql
Use the Runtime Management Console to edit the Database URL property in the BAM Dashboard Repository.
Export/import existing BAM Dashboard metatdata.

See the Runtime Management Console Online Help for more information.

Monitor

Business Activity Monitoring has the potential of requiring significant database resources. If this potential exists, separate the monitor production data from all other component data.

Do the following:

Create a new database using Sybase Central that has a page size of 2KB. Enable the jConnect meta-information support, turn on case-sensitivity for comparisons and passwords, and create SYSCOLUMNS and SYSINDEXES views.
Run the following scripts using interactive SQL or dbisql:

<installation directory>\Orch-5_0\ install.sql\scripts\asa\monitor_part1.sql

<installation directory>\Orch-5_0\ install.sql\scripts\asa\monitor_part2.sql
Use a text editor to edit the following configuration file:

<installation directory>\Orch-5_0\bin\ nnsyreg.dat
Run the BT59ie utility to export and import SetType metadata from the existing database.

See Sybase WorkSpace Development in the Sybase WorkSpace online bookshelf for more information.

Business Activity Monitoring has the potential of requiring significant database resources. If this potential exists, separate the monitor production data from all other component data.

Do the following:

Create a new database on a server that has a page size of 2KB.
Create a distinct database owner account.
Define the database size to be 100MB for data and indexes and 50MB for the transaction log.
Create the segments MSGTRAK_DATA and MSGTRAK_INDEX.
Turn on the ddl in tran option.
Run the following script using interactive SQL or dbisql:

<installation directory>\Orch-5_0\ install.sql\scripts\ase\monitor_part1.sql

<installation directory>\Orch-5_0\ install.sql\scripts\ase\monitor_part2.sql
Use a text editor to edit the following configuration file:

<installation directory>\Orch5_0\bin\ nnsyreg.dat
Run the BT59ie utility to export and import SetType metadata from the existing database.

See Sybase WorkSpace Development in the Sybase WorkSpace online bookshelf for more information.

BPEE/ Quartz Timers/ JMS Queues

BPEE/Quartz Timers/JMS Queues has the potential of requiring significant database resources. If this potential exists, separate the BPEE/Quart Timers/JMS Queues production data from all other component data, especially the monitor data.

Do the following:

Create a new database file on a server that has a page size of 16KB. Enable the jConnect meta-information support, turn on case-sensitivity for comparisons and passwords, and create SYSCOLUMNS and SYSINDEXES views.
Run the following script using interactive SQL or dbisql:

<installation directory>\Orch-5_0\ install.sql\scripts\asa\quartz_create.sql
Configure Unwired Orchestrator to point to the new database and redeploy your business process service.

See Sybase WorkSpace Development in the Sybase WorkSpace online bookshelf for more information

ASA is not a viable data source for use within BPEE. It cannot support distributed transactions in environments that require a transaction manager other than Microsoft Distributed Transaction Coordinator.

Do the following:

Create a new database on a server that has a page size of 16KB.
Set the Runnable Process Search Count to 10000 to optimize performance.
Create a distinct database owner account.
Define the database size to be 100MB for data and 50MB for the transaction log.

For Distributed Transactions, also do the following:
- Enable DTM on the server if you want to use Distributed Transactions within Unwired Orchestrator.
  
  This option requires that you set some configuration variables in ASE. See Using Adaptive Server Distributed Transaction Management Features Guide on the Sybase WorkSpace online bookshelf for more information.
- Grant the dtm_tm_role to the user login of the database owner account.
Turn on the ddl in tran and allow nulls by default options.
Run the following script using interactive SQL or dbisql:

<installation directory>\Orch-5_0\ install.sql\scripts\ase\quartz_create.sql
Configure Unwired Orchestrator to point to the new database and redeploy your business process service. See Sybase WorkSpace Development in the Sybase WorkSpace online bookshelf for more information.