By Jay Lee on Feb 07, 2015
This is the short write-up to help those who want to kick-start the OSB result caching. I've omitted all the details so one can get to start and test the feature pretty quickly.
Before proceed, port numbers that Coherence uses should be assigned. Here I assume that managed server "osb_m1", "osb_m2" is on physically different servers, and each have listen address and ports as osb_m1:9090, osb_m2:9092 respectively.
1. edit Coherence override file
Locate osb-coherence-override.xml under $OSB_HOME/config/osb/coherence and edit file as below.
<!DOCTYPE coherence SYSTEM "coherence.dtd">
Each managed servers will use this single file.
2. Edit setDomainEnv.sh of each managed server to include following settings.
3. Create Coherence server startup script.
Download the script here.
Now start Coherence server and OSB server. You can see if it's correctly set-up by seeing the log like below from Coherence.
Member(Id=1, Timestamp=2015-02-07 18:43:49.363, Address=127.0.0.1:7890, MachineId=60314, Location=site:,machine:localhost,process:23918, Role=OSB-node)
Member(Id=2, Timestamp=2015-02-07 19:37:44.98, Address=127.0.0.1:7892, MachineId=60314, Location=site:,machine:localhost,process:25937, Role=CoherenceServer)
To see whether is properly working, go to invocation trace.
cache-originated above indicates that result is served from Coherence cache.
Hope this helps.