Guidelines for Creating Multiple Adaptive Server Enterprise Databases

Review the following Sybase recommendations before installing multiple Adaptive Server Enterprise (ASE) runtime databases.

Adaptive Server Enterprise

ComponentRecommendation

Alert Management System

Unwired Orchestrator does not provide support for Alert Management System data outside the default ASA database.

See Guidelines for Creating Multiple ASA Databases 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.

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_1\install.sql\scripts\ase\dashboard_part1.sql

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

  • (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 on a server that has a page size of 2KB.

  • Set the network packet size to 8192.

    See the Adaptive Server Enterprise collection under Sybase WorkSpace Server Administration for more information.

  • 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_1\ install.sql\scripts\ase\monitor_part1.sql

    <installation directory>\Orch-5_1\ 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 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 on a server that has a page size of 16KB.

  2. Set the Runnable Process Search Count to 10000 to optimize performance.

  3. Create a distinct database owner account.

  4. Define the database size to be 100MB for data and 50MB for the transaction log.

    For Distributed Transactions, do the following:

    1. Enable DTM on the server if you want to use Distributed Transactions within Unwired Orchestrator.

      Note

      This option requires that you set some configuration variables in ASE. See Using Adaptive Server Distributed Transaction Management Features Guide in the Adaptive Server Enterprise 12.5.1 production documentation for more information.

    2. Grant the dtm_tm_role to the user login.

    3. Redeploy your business process service.

  5. Turn on the ddl in tran and allow nulls by default options.

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

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

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

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