Administration Overview : Introduction

Introduction
This guide documents what you must do after a BusinessEvents Studio project is ready to 9be prepared for deployment and use.
The main administration tasks and the chapters in which they are documented are as follows:
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 Site Topology file that configures the processing units and agents for deployment in Deployment Units (DUs) to hosts.
Configuring the BusinessEvents Monitoring and Management component to connect with the Cache Manager cluster to be monitored, and configuring settings such as health level metric thresholds, alerts, and actions.
You may wish to deploy at the command line, or using TIBCO Administrator. You may also wish to use the hot-deployment feature.
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 Manager with a backing store. The JDBC backing store implementation is the preferred implementation. The legacy Oracle-only backing store implementation is deprecated.