Monday, July 21, 2014

SOA Suite 12c Coherence Adapter configuration

Oracle SOA suite has introduced a new adapter called as Coherence adapter. This essentially works in the same principal as of Result caching in Oracle service bus.In this exercise we will try to understand more about coherence adapter and will use the same to do an end to end exercise.


Coherence adapter is installed by default in the integrate server however it is not targetted to the server so the very first thing is to target your coherence server to the default server so that it can be used.



Click on the Coherence adapter and then click on the targets tab.

Here Select the default server and save the changes.



After targetting and saving once you will check it again you will find that the Coherence Adapter is up and running



Next is create a JNDI to be used in the design time.

Again click on the COherence Adapter -->Select Configuration

and then select Outbound Connection pools

Create New



Provide a JNDI name and finish the wizard.



save the deployment plan




Now if you will check any of the other predefined jndi for coherence adapter you might find following type of entry


YOU can find that it is pointing to the Cache config location



I actually went back to the file location and check what exactly the file contains



The cache config file allows us to define multiple cache and define what kind of cache can be configured such as SOAAdapterTransactionalCache ,distributionCache. Based on existing schema we can create our own custom config cache and use it for our demo purpose.

We will create our own cache-config file based on the default one.

Here is how my cache-config will look like



Now go to the configuration of your JNDI and provide the details as shown below.

Here location is the path where i have stored my cache-config file locally.

Mode is custom and SErvice name will be the name specified in the config file.

Again WLSExtendProxy is set to false as we are not using any proxy



Once the changes are made, save the changes and update your deployment plan

Now your JNDI is configured and you are now ready to use it for the demo project purpose.We will see in next exercise as to how we can create a sample BPEL process and test the functionality of the coherence in SOA 12c

4 comments:

Anonymous said...

Great article! That is the type of information that should be
shared across the web. Disgrace on the seek engines for not
positioning this put up higher! Come on over and talk over with my website .

Thanks =)

Take a look at my web-site: Calvin Klein Scarves

Anonymous said...

Hi

How to check the cache is loaded or not ??


thanks
suresh

Mikku said...

the steps to validate and test coherence adapter are in the next exercise

http://soa-bpel-esb.blogspot.in/2014/07/testing-coherence-adapter-in-soa-12c.html

Unknown said...

Thanks for your post!

Could you please also share how to PUT POJO into Coherence cache.

Thanks in advance.