Database Reference
In-Depth Information
Coherence and OSB
In simpler cases, if our business service returns something close to static or if, as we men-
tioned above, our service consumer can tolerate the not really up-to-date result object, and
if in addition to that (optionally), service operations are quite expensive, then we can con-
figure our business service to cache results.
Cached results can be configured for
time-to-live (TTL)
, so after the cache result expires,
the next call will result in updating the cache with a fresh result by executing the business
service. The cached result is stored on a separate Coherence JVM, so it does not take any
resources from OSB JVM and can be distributed/partitioned between the Coherence nodes.
Although these machines are completely separated, WebLogic Administration Server can
still control Coherence servers on individual machines using its own node manager client,
which is connected to individual node managers on each Coherence machine.
Search WWH ::
Custom Search