Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 26 Backing Store Configuration : Setting up Shared Nothing Persistence

Setting up Shared Nothing Persistence
Shared Nothing persistence allows you to store data at individual node level, instead of a centralized location.
extid, id, closure, next, tti, and fired.
Following steps explain how to configure a TIBCO BusinessEvents project to use Shared Nothing persistence:
1.
2.
3.
4.
5.
When using up Shared Nothing persistence, to ensure that data is not lost when nodes leave the cluster, you must set the number of backup copies to 1 or more.
Runtime Configuration to Specify the Engine Name Property
The TIBCO BusinessEvents engine name is used to name the Shared Nothing files for that node. To enable the engine name to be used, you need to explicitly set the engine name property when running clusters with Shared Nothing. The -n <name> must be specified for all the nodes (inference and cache) in the cluster.
Note that only one node will be started in the following cases:
Nodes with duplicate engine names will not be initialized.
Features Supporting the Shared Nothing Persistence Option
You can use the Shared Nothing persistence option with the following features:
When querying by extid, you must use the functions Cluster.DataGrid.CacheLoadConceptByExtIdByUri and Cluster.DataGrid.CacheLoadEventByExtIdByUri.
Note that the following do not support the use of Shared Nothing persistence option:

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved