Creating an Alert Management System Production Database

Currently Unwired Orchestrator does not provide support for Alert Management System (AMS) outside the default ASA database. However, you have the option of creating a separate AMS database for production. To do so, use the database template provided in the \dbs\template directory to move a clean copy of the database file to a production location.

To create an AMS production database:

  1. Locate the following file:

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

  2. Move the UORuntime.db file to its production location.

  3. (Optional) If you moved the AMS database to a different machine, do the following:

    1. 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 name and port number.

      See the EAServer product documentation for more information.

    2. 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 collection under Sybase WorkSpace Server Administration for more information.

    3. Use the Runtime Management Console to edit the Alerts Repository configuration to point to the new JNDI reference in EAServer.

      See the web-based Runtime Management Console Online Help for more information.

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