Storing EMS Queues in the Oracle Database

EMS messages used by BPM are written to queues in the EMS server’s $sys.nonfailsafe default store. You must ensure that these messages are replicated.

By default, $sys.nonfailsafe is a file-based store on the EMS server. If you are using Windows rather than UNIX, installation of EMS creates services, which are not automatically replicated. To ensure that messages written to these queues are replicated, change the EMS server configuration so that $sys.nonfailsafe is defined as a database store in the same Oracle database used by BPM.

This procedure assumes that EMS is either installed on both the primary and DR sites, or else installed on the primary site and replicated on the DR site.

Procedure

  • Edit the $sys.nonfailsafe entry in the EMS server’s stores.conf file. Set the following fields:
    For example: 
    [$sys.nonfailsafe] type = dbstore
dbstore_driver_url = jdbc:oracle:thin:@db-host-name:db-port-num/amxbpmdb
dbstore_driver_username = username
dbstore_driver_password = password

Example

See the TIBCO Enterprise Message Service User’s Guide for more information.
Note: The $sys.nonfailsafe default store is not used exclusively by BPM, so this configuration may also result in non-BPM related messages being stored in the database.