This guide documents what you must do after a TIBCO BusinessEvents Studio project is ready to be prepared for deployment and use.
TIBCO BusinessEvents Express Content relating to Cache OM and backing store is not relevant to TIBCO BusinessEvents Express edition.Before you begin to use TIBCO BusinessEvents Administration, gain a basic familiarity with the product by completing the tutorials in TIBCO BusinessEvents Getting Started.TIBCO BusinessEvents Developer’s Guide provides practical details on using TIBCO BusinessEvents Studio to build a project. Each chapter focuses on a different aspect of developing a project.For in-depth explanations of various topics, read TIBCO BusinessEvents Architect’s Guide. References to relevant topics in that guide are provided in TIBCO BusinessEvents Administration.When it is time to configure your application for deployment, then deploy, and manage it, refer to TIBCO BusinessEvents Administration.
• 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.
• 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.
• Using TIBCO Administrator to deploy and manage a Cache based cluster, or starting at the command line.
• Configuring authentication and authorization. Certain components use authentication (BEMM, TIBCO BusinessEvents Views, TIBCO BusinessEvents Decision Manager). Currently only TIBCO BusinessEvents Decision Manager uses authorization (access control).
• Most production systems use Cache OM with a backing store. For setup and configuration details see the following chapter.
Copyright © TIBCO Software Inc. All Rights Reserved.