Various standard functions in the Standard catalog Cluster.DataGrid category enable you to work with objects in the cache. Cache load functions load items into the Rete network so they are available.
Tool tips in the user interface (and reproduced in the TIBCO BusinessEvents Functions Reference) explain the details of how to use the functions. This section explains certain patterns of use.
CacheLoad*() functions are required for working with cache only cache mode. They load entities from the cache (or backing store if not found in the cache) into the Rete network. See
Loading Cache Only Objects into the Rete Network in
TIBCO BusinessEvents Architect’s Guide for details.
Use the CacheLoad*() functions in an event preprocessor. Only use them in rules for cases where the
ID or
ExtId is not known in advance (in the preprocessor).
Never use Instance.getByExtId() unless you have first loaded the concept.
Instance.getByExtId() does not assert the concept but just returns it for use in rules, for example, as read-only reference data.
In the event preprocessor, use the Lock() function to prevent other threads or engines from operating on the same entity. The lock is automatically released at the end of the RTC.
Use Unlock() only in a preprocessor and only to handle cases where you need to release the lock, for example because some information is missing that would be required to go forward.
See Using Locks to Ensure Data Integrity Within and Across Agents in
TIBCO BusinessEvents Architect’s Guide for details on use of locks.
Index() creates an index on the specified property, which is useful when you run queries. (See
Guidelines for Use of Oracle Coherence Functions.)