Hi guys,

I'm working on WebSphere Application Server v6 on Windows.

Is there anybody who is familiar with MQ link configuration?
How can I determine the inbound port to connect to the WAS6 from an external MQ mangager?

I succeeded in sending a message from SIBus to the external MQ manager through a MQ link sender channel
but didn't succeed in returning a reply from the external MQ manager,
because I have no idea how to define the sender channel on the MQ manager to connect to the SIBus(MQ link). For example, how can I define its conname? How can I use, for example, 5558(InboundBasicMQLink)?

Thanks in advance,

the conname is the server and port this is done as mqm with runmqsc (note: the server name is xena)
DEFINE QL(BUS1) USAGE(XMITQ) REPLACE
DEFINE CHL(XENA.TO.BUS1) CHLTYPE(SDR) TRPTYPE(TCP) XMITQ(BUS1) conname('XENA(5558)')

Michelle Rutherforf\d

Thank you very much for your information, Michelle.

To be honest, I was perplexing with getting information about WAS6 because it is quite new and the information is limited..

Anyway, I tried it but the problem is not solved.
My sender channel in an external QMgr can't connect to the MQ link receiver channel.

The points you mentioned were,
1. WAS6 side listens 5558 by default and an external QMgr can connect to WAS6 through this port.
2. The name of XMITQ must be the same as the bus name (not foreign bus name) in a messaging engine.


Now,how can we bind listen ports(Ex.5558) with MQ links?
In other words, is there anything else that I must complete before running MQ links on WAS side?
For example, I may be required to bind a listen port(Ex.5558) with a receiver channel?

Thanks!

How can I start a MQ link receiver channel manually?

Thanx.

When you defined the reciever channel on WAS is it the same name as your sender channel? on the WAS side if you hover the cursor over the status of the reciever channel status indicator what status are you getting.

Have you restarted server 1 after you defined both.

I should tell you that all you will be able to get working is the sending of headers the message body will not make it. There is a bug that will be fixed in 6.0.0.2. The good news is you will at least get the plumbing going.
I am rebuilding my home lab so I cannot dump my config for you.

You can send direct to me if you like michellewwg at yahoo.com

How are you sending a message? Did you start the sdr channel in MQ?
Michelle

Actually, I was able to successfully send a message from the ME through the MQ link I defined to the queue manager(QMgr).
However, I couldn't send a reply from the QMgr to the ME and I found a problem that the sender channel on the QMgr didn't work.
Now I have no idea how I can start a sender channel on the QMgr.

The name of sender/receiver channel on the MQ link is exactly the same as the name of receiver/sender channels on the QMgr.
I defined the sender channel on the QMgr like
CHL(MQ.TO.SIBUS)
CHLTYPE(SDR)
TRPTYPE(TCP)
XMITQ(SIBUS)
CONNAME('SERVER(5558)').

When I tried to start the sender channel on MQ side, it didn't start with the status 'binding...'.
(By using 'netstat' command, I can see that my WAS is listening 5558 port).
I know that the status 'binding' may be caused by accessing an invalid port.


Thanks!