Posted: Fri Jan 21, 2005 6:29 am Post subject: Achieving Network Redundency using clustering
Newbie
Joined: 21 Jan 2005 Posts: 1
We need to achieve network redundency in the sense that if a fast ANX network fails we want our channels to use a slower T1 line
Current setup is without a cluster where we post to remote queueus using local queue definations
We we need to use cluster to achieve multiple channels (Each channel usign a different network) between same queue managers or can this be achieved without a cluster
I think clustering would actually prevent you from doing this, since clustering only ever happens over automatically defined cluster channels. You'd need to write an exit to change the cluster channel definitions on the fly.
I believe that the Intercommunications manual provides instructions, or at least patterns, for doing this kind of setup. _________________ I am *not* the model of the modern major general.
Check out the NETPRTY attribute of the Cluster channels. This allows you to define 2 or more channels per QM for clustering. Assign the one that uses your prefered network the higher priority. As long as it is running, the Workload algorithem will choose it. If that network goes down and the channel goes retrying, the next channel on the alternate network will be used. _________________ Peter Potkay
Keep Calm and MQ On
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum