Adding and Configuring a CDD

You can create multiple CDD files for a project and at deploy time use the one that has the configuration you want to use.

Procedure
1. In TIBCO BusinessEvents Studio Explorer, right-click the project name FraudDetection and select New > Cluster Deployment Descriptor.
   You will see the New Cluster Configuration Wizard.
2. In the File name field, type fd and click Next.
   Unlike in 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. In the Object Manager Selection page, select the following values and click Finish.
   • Cluster Provider Type - Unclustered
   • Object Management Type - In Memory
   You will see the CDD editor, displaying the template for In Memory OM. For an In Memory project, very little deployment configuration is required.
4. Click the Collections tab, and do the following:
   1. Select Input Destinations and click Add.
   2. In the Destinations Collection field, type Http and again click Add.
   3. In the Select Input Destinations dialog, select /Channels/HTTP/AllOps and click OK.
      A Configuration panel appears.
   4. In the Input Destination ID field, type AllOperations, replacing the generated ID.
   5. In the Preprocessor field, select /RuleFunctions/PreProcessor.
      Note: Now this preprocessor will act on events arriving at the AllOps destination.

      The Configuration panel looks like the follow image:

      

      Collections enable you to create resources you can reuse when configuring multiple agent classes. Collections are used here to demonstrate the feature. In simple projects, you could simply configure the agent class without using collections.

5. Select the Agent Classes tab and expand the default agent class, which is called inference-class.

   When configuring an agent class, you can select a subset of the project rules, select and configure destinations, and select startup and shutdown rule functions. Thus different agent classes can behave quite differently at runtime.

6. Select Input Destination Collections and click Add.
   You see the Select Input Destinations dialog. In the Reference Collections area, select Http and click OK.

   As mentioned above, you can configure input destinations here, or link to input destinations configured in the Collections tab, or use both methods. Here we reference the collection you already defined.

7. Select Startup Functions and click Add.
   In the Select Rule Functions dialog, select /RuleFunctions/InitializeScorecard and click OK. When the engine starts, this rule function executes and initializes the scorecard values.
8. Save and close the CDD.