Cache OM Tutorial : Add a CDD File for Cache Object Management

Add a CDD File for Cache Object Management
To set up the project for cache object management, you create a new CDD file using the template provided for cache OM. The CDD template defines an inference agent class and a cache agent class, and default values for cluster level properties, so it doesn’t take much to configure an example project to work. Other configuration options are available for different situations.
Learning Points
How do I configure cluster node discovery?  You can use the default multicast node discovery settings provided in the CDD template. You can also change the defaults as needed to avoid collisions with another cluster in the same network. Cluster discovery settings are available for different situations, such as hosts with multiple NICs. Another method of cluster discovery uses well-known addresses for situations where use of multicast is not an option.
How do I configure agents and processing units? You configure agent classes and processing units in the CDD. A deployed processing unit is a BusinessEvents engine. For this example, you don’t have to do any processing unit configuration. However, for real-world scenarios, where concurrency features are used and perhaps add-on products, processing unit configuration requires some thought and planning. The processing unit definitions are also used in the TIBCO BusinessEvents Monitoring and Management component, for deploy-time configuration.
Number of cache agents to start  For a production environment you can define how many cache agents must be started before the system startup can continue. The default is one. See the Cache Agent Quorum setting in the Object Management Configuration panel. When a backing store is used, cache agents can preload objects from a backing store at system startup. More cache agents make the preloading phase quicker.
More Information
In TIBCO BusinessEvents Developer’s Guide see the following:
Task C Add and Configure a CDD
Start with a new CDD because the provided Cache OM template sets many default values you’ll need.
1.
In Studio Explorer, right click the project name and select New > Cluster Deployment Descriptor. You see the New Cluster Configuration Wizard.
2.
In the File name field, type fdCache and click Next.
If you click Finish instead of Next, you don’t 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.
3.
You see the Object Manager Selection dialog. Select Cache from the Object Management Type drop-down list, then click Finish. You see the CDD editor.
4.
In the Cluster tab, select Properties. Expand the coherence property group. This group of properties with default values is provided in the Cache OM CDD template. If you need to change any defaults, configure the properties as follows.
a.
If it is possible to collide with any other project deployed on your network, use a non-default multicast IP address (the default is 224.3.5.2).
b.
If the default tangosol.coherence.localport value, 8088, is in use, specify a different value. (The shipped project uses 8080.)
c.
Because you will start all nodes on one machine for the tutorial, it’s a good idea to set the tangosol.coherence.ttl to 0, to keep multicast packets from leaving the originating machine. (Works on most operating systems.)
5.
Click the Agent Classes tab and 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 Task R, Add and Configure a CDD on page 44. and complete step 4 through step 7.
No configuration is needed for the cache-agent class.
6.
7.
Summary and Next Steps
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.