Distributed Topic and SOA Cluster

If you are wokring in a SOA Suite cluster with multiple node, you will have to face a lot of issues configuring Distributed topic.

I faced a lot of issue first time , some of the common issues were

1> how to point the distributed topic to multiple targets.
2> For one message multiple subscribers are getting triggered.
3> Messages are going to all the servers.

But all these are just a one time issue. One you know the correct steps you should be able to get it working in a first shot.

In this post we will discuss about the task to be taken care of from admin and developer side.

First step is to create a distributed topic.

first of all it is important to understand that there is a diffence between topic and distributed topic. If you are creating a topic it can just point to one of the managed server , however the distributed topic can be pointed to multiple server.

Steps to be followed for creating a distributed topic are

1> Create JMS servers pointing to individual managed server.



Next create a JMS module

And then a subdeployment

While creating a subdeployment make sure you are targetting it to the JMS server you have created in the previous step.




Now go ahead and create a distributed topic

Go for advance targeting of topic and point it to the sub deployment created.

While creating a distributed topic, one important point is that make sure you are specifying the forwarding policy as Partitioned otherwise the message will be replicated to all the servers.



Now you are good from admin side but a task is required from developer as well that is to add a singleton property in your SOA process.

<binding.jca>
<property name="singleton">true</property>
</binding.jca>

In case you are using OSB as a publisher and subscriber

Make sure you are enabling Quality of service for exactly once.



clustering in OSB is again more confusing so i will write a separate post on my next exercise to make it more clear.