Adding a CDD File to the Project

The configuration settings for an application are defined in the CDD file. You can use the wizard to specify the default cluster and object management(OM) mode of your project.

If you choose an OM type in the wizard, the template for that OM type is used and all the default settings are loaded. For example, if you choose Cache, then a cache agent with default values is created for you. For example, if you change from Cache to Store and save, the cache agent and its configuration are lost. For all OM types, however, the General settings are configured in the same way. Similarly, you can choose the Cluster Provider Type to get a template for the cluster of your choice.

Note: Names in the CDD must conform to the NCName datatype. See the following page for more details:

REC-xml-names

Some Japanese characters, such as half-width Katakana, have issues when they are used in XML names. See the following document for more details:

japanese-xml

    Procedure
  1. In TIBCO BusinessEvents Studio Explorer, right-click the folder where you want to store the CDD and select New > Cluster Deployment Descriptor. The New Cluster Configuration Wizard opens up.
  2. In the File name field, type a name for the CDD and click Next. You can change the name in the editor as required.
    Note:  When you are using TIBCO Administrator for deployment, by default, TIBCO Administrator looks for a processing unit named default and a CDD file named default.
  3. In the Object Manager Selection page, select a cluster type for the project.

    • Unclustered
    • Clustered

    Based the cluster type, the values of the Object Management Type field are listed.

  4. Select the Object Management Type for the deployment and click Finish.

    The available options are described in the following table:

    Cluster TypeObject Management Type
    Unclustered
    In Memory
    Sets In Memory as the Object Management Mode (in CDD).
    Store
    Sets Store as the Object Management Mode. The default Store Provider is Apache Cassandra; however, you can change it later in CDD, if required
    Clustered
    Cache
    Sets Legacy ActiveSpaces as the Cluster Provider and Cache as the Object Management Mode. The default cache provider is Legacy ActiveSpaces.
    Store
    Sets TIBCO FTL as the Cluster Provider and Store as the Object Management Mode. The default store provider is Apache Cassandra; however, you can change it, if required.

    The CDD editor opens up.

    Tip: Check the Object Management node on the left and ensure that you have selected the correct Object Management type.

    You can also right-click the Object Management element and select Change to OM Type.

  5. In the CDD editor, on the Cluster tab, select General and specify the following:

    The cluster name, although it already contains the file name that you have provided in the new CDD wizard, but you can update it, if needed. If Legacy ActiveSpaces is the cluster provider, any spaces in the name are converted to underscore characters internally.

    Note: Do not use the names $cluster or default as they are reserved names.
    If required, you can update the author name and add comments as suitable. (Version and date are not editable.)
  6. Save the new CDD file.
What to do next

Configure the CDD file settings on different tabs.

  • For details about different cluster, object management, and metrics options available in CDD, see Cluster Configurations For Your Project.
  • For configuring database concepts, see TIBCO BusinessEvents Data Modelling Developer's Guide.

    The database concepts are applicable only for JDBC stores.