Configuration Coherence Server Out-of-Process in OSB 12C

Hello guys,

Today I’m going to introduce the Coherence Server Out-of-Process configuration.
Once this configuration has changed a lot between versions 11G to 12C, the post will be a little bit more detailed (than usual).

The table below summarize these changes:

From To
 osb-coherence-cache-config.xml Coherence Cache Config resource
 osb-coherence-override.xml Coherence Cluster resoruce
Out-Of-Process Cache Server New WLS node/cluster

Follow the steps:

1 – Create the managed servers for coherence and also the cluster for these managed servers:

1

2 – Restart all managed servers (including OSB);

3 – Add the cluster created for the managed servers of coherence to the targets of the “Coherence cluster” automatically created in the default installation (defaultCoherenceCluster):

3

3.1

4 – Restart the coherence’s managed servers;

5 – Deploy the artifact “resultcache.gar” in Coherence_Cluster target:

5

5.1

6 – Add to the arguments in server start of the managed servers of OSB: “-DOSB.coherence.cluster=CoherenceCluster -Dtangosol.coherence.distributed.localstorage=false”;

7 – Add to the arguments in server start of the managed servers of Coherence: “-DOSB.coherence.cluster=CoherenceCluster”;*

*the name CoherenceCluster should be the same as in (Environment > Coherence Clusters)

8 – Restart all managed servers;

That’s all for today.
Jackson.

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Discover more from grepOra

Subscribe now to keep reading and get access to the full archive.

Continue reading