Posted: Mon May 27, 2002 4:57 am Post subject: Server versus Client
Newbie
Joined: 27 May 2002 Posts: 3
I am looking at implementing MQSeries with an imaging application. I would be moving 40,000 images a day from several differant clients to a central server.
What would going Server to Server give me that Client to server would not ?
I am using a Java program using MQSeries Syncpoint to actually move the images so I have assured delivery.
The main difference is that you're basically only work in an asynchronous mode inbetween server queue managers. The Client to Server connection is in effect synchronous.
What this means is that if for example your Server queue manager is on a remote platform and the network connection is down your application will fail to connect to the queue manager and stop. A problem you don't have when you're not using clients and connect to a local queue manager on your machine as that queue manager will store the messages in the transmittion queue till the network connection comes back up.
Posted: Thu May 30, 2002 9:13 am Post subject: MQ Client ver Server
Newbie
Joined: 27 May 2002 Posts: 3
Thanks all that replied. What I found was that my program will use MQCMIT and MQBACK the sending program will wait for COD that the message was successfully delivered and if no reply is received it will roll back and wait for the comms to start again.
Yes cost is a factor what I was really concerned about was REMOTE ADMIN or lack of in the client and the ability to check the Queue depth on the sending system. What I decided was that I could use Computer Management in WIN2000 to check services etc... and use the service to notify of failure
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