Open topic with navigation

TIBCO BusinessEvents® Enterprise Edition 6.3.1

# Cluster Deployment Descriptor (CDD) and the EAR File

To deploy a project you need a CDD file and an EAR file. The CDD is not included in the project EAR. This means you can reconfigure a project’s deployment configuration without having to rebuild the EAR.

## Learning points

What is an EAR
The Enterprise Archive or EAR file contains details for all the resources in a project, and project global variables.
What is a CDD
The project’s deployment configuration is defined in an XML file called Cluster Deployment Descriptor or CDD. You edit this file using the TIBCO BusinessEvents Studio Cluster Deployment Descriptor editor.
How do I set up preprocessors and start and shut down rule functions?
The CDD is where you configure rule functions to act as event preprocessors, startup rule functions, or shutdown rule functions. Only rule functions whose Validity setting is `Action` are valid for these uses. (These rule functions cannot require anything to be in their scope, because they execute outside of the context of the Rete network and TIBCO BusinessEvents project resources.) A preprocessor is associated with a destination. It processes events arriving at that destination.
What is an object management type?
Object management (OM) refers to how TIBCO BusinessEvents manages and uses the objects generated within the TIBCO BusinessEvents application at runtime. This tutorial focuses on the basics, so it uses In Memory, the simplest OM type. Objects are kept in memory only, and are lost when the engine stops. Cache OM is explained in Cache OM Tutorial and backing store for this Cache OM is explained in Backing Store Tutorial.
Tip: Other ways to create memory-based projects is to use Cache OM or Store OM. For cache OM, you can set the “mode” to Memory Only on all objects. This method provides fault tolerance and other advantages. See Cache OM with Memory Only Mode on All Objects and Fault Tolerance in TIBCO BusinessEvents Architect Guide.
What is an inference agent?
An agent does certain work within the engine. With Cache OM, different types of agents do different work. But for this simple In Memory OM project, you use only one agent of one type, and that is the inference agent. Inference agents listen for messages arriving at destinations, and transform them into events. The events trigger rules, using the agent’s Rete network and forward chaining, and the inference agent executes the rules.
What is a processing unit?
A processing unit is deployed as a TIBCO BusinessEvents engine. It has one or more agents (depending on OM and requirements) and it runs in one JVM. For In Memory OM, you generally do not have to do much configuration of processing units. The default processing unit settings are usually sufficient.

## More Information

- In TIBCO BusinessEvents Developer Guide, see Agent and Processing Unit Configuration
- See also TIBCO BusinessEvents Configuration Guide.

Subtopics

Did you find this helpful?

YesNo
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO BusinessEvents® Enterprise Edition

Copyright © 2004-2024. Cloud Software Group, Inc. All Rights Reserved.