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.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 the Cluster Deployment Descriptor, or CDD. You edit this file using the BusinessEvents Studio Cluster Deployment Descriptor editor.How do I set up preprocessors and startup and shutdown 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. Such rule functions cannot require anything to be in their scope, because they execute outside of the context of the Rete network and BusinessEvents project resources.What is an object manager? Object management refers to how BusinessEvents manages the objects generated within the BusinessEvents application at runtime. For some applications, the objects are more important than for others. This tutorial focuses on the basics, so it uses In Memory, the simplest object manager. Objects are kept in memory only, and are lost when the engine stops.What are agents An agent does certain work within the engine. With the cache object manager, different types of agents do different work. But for a simple In Memory project, you use only one agent of one type, and that is the inference agent.What is a processing unit? A processing unit is deployed as a BusinessEvents Studio Explorer engine. It has one or more agents and it runs in one JVM.In TIBCO BusinessEvents Administration, see these chapters:Task R Add a CDD
1. In Studio Explorer, right click the project name, FraudDetection, and select New > Cluster Deployment Descriptor. You see the New Cluster Configuration Wizard.You can create multiple CDD files for a project and at deploy time use the one that has the configuration you want to use.
2. Unlike other project resources, you can change the name later as desired. Short names are easier to type when starting the engine at the command line.
3. At the Template Selection page, select In Memory from the Object Management Type drop-down list. Then click Finish.You see the CDD editor. For an In Memory project, very little deployment configuration is required.
4. In the Agent Classes tab, expand the default agent class, which is called inference-class. (Agent classes can be used in cache object manager to define different types of agents.)When configuring an agent class, you can select a subset of the project rules, select and configure various destinations, and select rule functions that execute at engine startup and shut down, as needed.
5. Select Destination Collections and click Add. In the Select Destinations dialog, select /Channels/HTTP/AllOps and click OK.In the Configuration panel, a generated ID for the destination appears, along with various configuration options.In the Preprocessor field, select /RuleFunctions/PreProcessor.
6. In the Threading Model field select Caller. For the HTTP channel, this threading model is required.
7. Select Startup Functions and click Add. In the Select Destinations dialog, select /Channels/HTTP/AllOps and click OK. When the engine starts, this rule function executes and initializes the scorecard values.Task S Build the EAR FileYou must build the EAR file outside the project tree, or it will be recursively included in the next EAR file you build!
1. In Studio Explorer, highlight the project name, then from the top menus select Project > Build Enterprise Archive.If you see a message asking you to save all project resources, click Yes. It means an unsaved resource editor is open.At the Build Enterprise Archive dialog, change the name to fd. (Short names are easier to type when starting the engine at the command line.)
2. In the File Location field, browse to and select the directory above the project directory. To build the EAR in the provided example location, choose BE_HOME/examples/FraudDetection/FD.ear. Replace BE_HOME with your actual value.
3. Press Apply, then press OK. You see messages as the EAR file builds, then you see a message that the EAR file has built correctly:Summary and Next Step
Copyright © TIBCO Software Inc. All Rights Reserved.