This guide documents what you must do after a TIBCO BusinessEvents Studio project is ready to be prepared for deployment and use.
• System level configuration as needed. Edit the engine TRA file for settings are read before the engine starts.
• Configuring the Cluster Deployment Descriptor (CDD) for cluster settings, object management settings, and deploytime configuration of processing units and agents. In addition some entity metadata settings set various defaults that interact with the CDD settings.
• Configuring the TIBCO BusinessEvents Monitoring and Management (MM) component. Two kinds of configuration are documented: basic configuration is about connecting with the cluster to be monitored, including defining the site topology file for cluster to be monitored. The Site Topology file configures the processing units and agents for deployment in Deployment Units (DUs) to hosts. The second type of configuration is to set up the MM settings such as health level metric thresholds, alerts, and actions.
• Configuring authentication and authorization. Certain components use authentication (BEMM, TIBCO BusinessEvents Views, TIBCO BusinessEvents Decision Manager) and certain components use authorization (TIBCO BusinessEvents Decision Manager).
• Most production systems use Cache OM with a backing store. The JDBC backing store implementation is the preferred implementation. The legacy Oracle-only backing store implementation is deprecated.
Copyright © TIBCO Software Inc. All Rights Reserved.