Backup JMS connection

[Former Member]

Hi,

I have a connection in place within PI7.1 to connect to a JMS queue using the JMS sender adapter and have a requirement to use a backup server in the case where the first is unavailable for whatever reason. Is this possible using 1 JMS sender adapter such as adding a comma between the 2 for example... server-url-stage-a, server-url-stage-b.

Appreciate any help that can be provided.

Thanks,

Nate

[Former Member]

Hi,

As far as I know, if you are using WMQ client, you have several choices on the client side to failover to a secondary JMS provider if primary is unavailable. These include:

1. Client Connection Definition Table

2. Using Wild cards in Queue Manager names

3. Using JNDI: Please look at [this note|https://service.sap.com/sap/support/notes/802754] and [this blog|http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/11493] [original link is broken] [original link is broken] [original link is broken];

Failover support really depends on the JMS client you are using. Best to check vendor's documentation. Do post back the results of how it goes for you.

Regards,

Shehryar

[Former Member]

Hi,

It is not possible to write both servers in the same channel, even if it was, they would have to have the same drivers & class names. You cannot connect two different JMS servers in a failover logic like you proposed using PI, but as Michal also proposed, you can PULL from both for the same scenario using two channels.

There could be an advanced and custom way to do it where you can develop a custom Java application deployed on PI AS Java that will constantly check your first JMS server, and using the Directory API, it can create a secondary JMS channel, or activate it using HTTP administration if the server goes down. But the effort is yours to consider, and reliability will depend on your skills & design.

Regards,

S. Gökhan TOPÇ

[Former Member]

these servers are in cluster environment??

[MichalKrawczyk]

Hi,

>>>or example... server-url-stage-a, server-url-stage-b.

this scenario has exactly the same effect as having two communication channels for one scenario

if you need it like this then just create two flows for one scenario and they will work exactly as you've specified

Regards,

Michal Krawczyk