Guidelines for Creating Multiple Adaptive Server Anywhere Databases

Review the following Sybase recommendations before installing multiple Adaptive Server Anywhere (ASA) runtime databases.

Adaptive Server Anywhere

Unwired Orchestrator ComponentRecommendation

Alert Management System

Choose from the following:

  • Use the default ASA database to support Alert Management System (AMS) data during production.

  • Separate the Alert Management System production database from the default ASA database.

    1. Copy the existing AMS database file to the desired location, or copy the following template and start with a fresh database:

      <installation directory>\Orch-5_1\dbs\template\UORuntime.db

    2. For the Alerts server, use EAServer Manager to reconfigure the EAServer envrionment 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 collection under Sybase WorkSpace Server Administration for more information.

    3. Use EAServer Manager to create an Application Server Connection Cache, set the URL for that cache, and add a JNDI reference to the Runtime Management Console web application.

      See the EAServer product documentation for more information.

    4. Use the Runtime Management Console to edit the Database URL property in the BAM Dashboard Repository.

      See the Runtime Management Console online help for more information.

BAM Dashboard

The BAM 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.

    1. Use the Runtime Management Console to edit the Database URL property in the BAM Dashboard Repository.

    2. (Optional) Export/import existing BAM Dashboard metatdata.

      See the Runtime Management Console online help for more information.

  • Create a new database file using Sybase Central. Enable the jConnect meta-information support, turn on case-sensitivity for comparisons and passwords, and create SYSCOLUMNS and SYSINDEXES views.

    1. Run the following script using interactive SQL or dbisql:

      <installation directory>\Orch-5_1\install.sql\scripts\asa\dashboard_part1.sql

    2. Use the Runtime Management Console to edit the Database URL property in the BAM Dashboard Repository.

    3. (Optional) 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_1\ install.sql\scripts\asa\monitor_part1.sql

    <installation directory>\Orch-5_1\ install.sql\scripts\asa\monitor_part2.sql

  • Use a text editor to edit the following configuration file:

    <installation directory>\Orch-5_1\bin\ nnsyreg.dat

  • Run the BT59ie utility to export and import setType metadata from the existing database.

    See Exporting SetTypes or Importing SetTypes 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/BPRE/Quart Timers/JMS Queues production data from all other component data, especially the monitor data.

Do the following:

  1. 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.

  2. Run the following script using interactive SQL or dbisql:

    <installation directory>\Orch-5_1\ install.sql\scripts\asa\quartz_create.sql

  3. Configure Unwired Orchestrator to point to the new database and redeploy your business process service.

    See the EAServer collection under Sybase WorkSpace Server Administration for more information on configuring a database connection.

Note

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

Send your feedback on this help topic to Sybase Tech Pubs: pubs@sybase.com