Posted: Mon Mar 17, 2003 8:45 am Post subject: Design Options
Novice
Joined: 07 Jun 2002 Posts: 23 Location: Ohio
Soliciting for suggestions or real-world working examples:
Our current architecture has three hardware contact points for MQSeries. The originators are either a Windows PC or an AS/400 server. Both communicate through an AIX server (used to concentrate PC to AS/400 connections).
I have thousands of workstations all running MQSeries server to support asynchronous queuing while network detached. Each PC connects to one of three AIX servers via a predefined channel (FQDN is used to specify server). There are 11 AS/400's on the other end that distribute back down to the PCs. Each user typically connects through AIX to a specific AS/400.
As you can imagine, administration is a nightmare. I'm investigating possible design alternatives (this one is at least 4 years old and pre-dates MQSeries version 5 on PC and AS/400). Ideally, I'd like to have user connections deistributed dynamically across all 3 AIX servers. I'm aware of clustering now being an option (at least with V5.3). What else is being done out there?
I understand this is a somewhat vague description, but I'm looking for rough ideas, not necessarily exact fits. I'd love to hear if anyone has such a setup or can provide feedback on how well clustering functions.
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