Open topic with navigation

TIBCO BusinessEvents® Enterprise Edition 6.3.1

# Adding and Configuring a CDD

Start with a new CDD because the provided Cache OM template sets many default values you’ll need.

Procedure
1. In TIBCO BusinessEvents Studio Explorer, right-click the project name and select New > Cluster Deployment Descriptor.
   The New Cluster Configuration Wizard is displayed.
2. In the File Name field, type fdCache and click Next.
   Warning: If you click Finish instead of Next, you do not have the opportunity to use the Cache OM template. If you accidentally click Finish, just delete the file and add a new one, and this time click Next.

   By default, the CDD file name you specify is also used as the cluster name.

   The Object Manager Selection dialog is displayed.
3. Select the following values and click Finish.
   - Cluster Provider Type - `Clustered`
   - Object Management Type - `Cache`
   The CDD editor is displayed. The default configuration uses ActiveSpaces cluster and cache providers.
   This tutorial uses the default cluster and OM but there is an option to change them to FTL cluster and Ignite cache respectively.
4. In the Cluster tab, select Properties. You do not need to add any properties, unless you need to change the defaults for the discovery URL and the listen URL (which is used by the nodes to communicate with each other). Here are the cluster properties with their default values for your information:

          be.engine.cluster.as.discover.url=tibpgm://7888/;239.8.8.9
          be.engine.cluster.as.listen.url=tcp:// 0.0.0.0 /random port 3000+

   For details see DataGrid Discover URL and DataGrid Listen URL in TIBCO BusinessEvents Configuration Guide.

   Note: Cluster Clashes
   If you have clashes with other clusters running on your machine, use a different cluster name, discovery URL and listen URL from the other cluster or clusters.
5. In the Cluster tab, select Cluster Management and verify that Legacy ActiveSpaces is selected as the Cluster Provider. In the Object Management verify that Number of Backup Copies is `1`, which indicates that the distributed cache contains one copy of each entity in the cache.
   Limited Cache
   The Entity Cache Size and Object Table Cache Size settings in the Object Management tab take effect only if you use a limited cache. By default, the cache is not limited. In Domain Objects > Default , the setting Is Cache Limited is not selected. However, when you add a backing store, it is common to use a limited cache because you can store all objects in the backing store. You can override the limited cache setting at the object level, as desired.
6. As you did in the basic design tutorial, do the following:
   Configure the `inference-class` agent class with the Channels/Http/AllOps destination
   Configure the RuleFunctions/InitializeScorecard rule function as the startup rule function.

   For details, see Adding and Configuring a CDD.

   No configuration is needed for the cache-agent class.

7. Save and close the CDD.
8. Build the EAR file using the name `fdcache`. If you need a refresher on building the EAR file, see Building the EAR File.

What to do next

You have configured the CDD for cache cluster discovery, and you configured the processing units and agents as you did before. Now you can start the project and see how things work at runtime.

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.