| Author |
Message
|
| lash |
 Posted: Sun Aug 17, 2003 8:15 pm Post subject: msg from client1 to client2 |
 |
|
Apprentice
Joined: 14 May 2003
Posts: 47
|
HI,
mqClient1 is putting the msg on to a queue q1 of qmgr called SOPS,
mq Client2 has to get the msg from the queue q1 of qmgr SOPS.
can we use mqread.java stand-alone program to retrieve the msg.
how can we make it a automated task i.e. as soon as client1 puts client2 should get it at anytime of the day.
Thanks in advance,
lash |
|
| Back to top |
|
 |
| Ratan |
| Posted: Mon Aug 18, 2003 12:59 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
use triggerring. When ever client1 puts a msg, clt2 will be triggered and will retrieve the msg. The other option is client2 can continuously listen to the Q. Depending on the frequency of the messages you can make a choice between the 2 options.
_________________
-Ratan |
|
| Back to top |
|
|
| lash |
| Posted: Mon Aug 18, 2003 3:54 pm Post subject: msg from client1 to client2 |
|
|
Apprentice
Joined: 14 May 2003
Posts: 47
|
hi,
thanks for the replies.
client2 does not have queue manager of its own.
it has to use the qmanager from server which is at different ip-address.
than client2.
so will the get application at client2 triggers when we write process def on server,
if so what path i should write in application path in process def.
if it is on different box with different ip-address.
thanks to all,
lash. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Tue Aug 19, 2003 9:55 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
|
| Back to top |
|
|
| lash |
| Posted: Tue Aug 19, 2003 8:05 pm Post subject: msg from client1 to client2 |
|
|
Apprentice
Joined: 14 May 2003
Posts: 47
|
Hi friends,
we can write application name in process def.of mqserver but how we can give the ip-address of mqSeries client in application name of process def of mqSeries server.
as iam working on real time environment, anybody could work on test environment and let me know , it will be more appriciated.
eagerly waiting for the replies.
regards,
lash. |
|
| Back to top |
|
|
| EddieA |
| Posted: Wed Aug 20, 2003 8:07 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
The Process Definition is written 'as if' it were at the Client box.
The Trigger Monitor that is waiting for the message actually runs on the Client2 box and when a message appears in the queue on the Server, triggers the application locally to itself.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| tso0rxp |
| Posted: Fri Aug 22, 2003 7:51 am Post subject: |
|
|
Voyager
Joined: 07 Jan 2002
Posts: 85
|
We have a similar design to option 2 in Ratan's reply.
Client issues a 'wait' on the reply queue defined in the remote queue manger. Works nicely.
Note: Our client is an interactive routine - i.e. not always running - but the concept would be the same with multiple Clients running on separate workstations.
_________________
Bob Perry
MQ Administrator |
|
| Back to top |
|
|
|
|
