| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQI Channel - unknown CLNTCONN creation |
« View previous topic :: View next topic » |
| Author |
Message
|
| rickwatsonb |
 Posted: Thu Jul 16, 2009 7:57 am Post subject: MQI Channel - unknown CLNTCONN creation |
 |
|
Voyager
Joined: 15 Aug 2006
Posts: 87
Location: USA: Mid-West
|
Hi,
From my reading of the Clients manual and the Intercommunication manual about MQI channels, I understand that a CLNTCONN SVRCONN pair ALWAYS exists for an MQI Channel. If this is correct, then I do not understand how our application side is creating the CLNTCONN channel. If this is incorrect, please explain why.
The client side app is written in JAVA. A messaging.properties file, shown below, is used on the application side. When I create a queue manager - this is all that is provided to the app team for the connection.
| Code: |
#Requisite connection properties for messaging framework
queueConnectionFactory = com.ibm.mq.jms.MQQueueConnectionFactory
queuePort =1414
queueTransport = JMSC.MQJMS_TP_CLIENT_MQ_TCPIP
queueCcsId = 819
# UNIT TEST MQ Configurations on ALTAIR
queueHost = abcserver001
queueChannel = APP.CHANNEL
queueManager = QM.ABC.UAT
timeout.length = 5000
header.remove = on
RETRIAL_TIME_LIMIT=43200
MESS_EXCEPTION_NO_OF_ATTEMPTS= 120
|
On the server queue manager the SVRCONN channel has the following properties:
| Code: |
DISPLAY CHANNEL(APP.CHANNEL)
6 : DISPLAY CHANNEL(APP.CHANNEL)
AMQ8414: Display Channel details.
CHANNEL(APP.CHANNEL) CHLTYPE(SVRCONN)
ALTDATE(2008-09-25) ALTTIME(11.18.27)
COMPHDR(NONE) COMPMSG(NONE)
DESCR( ) HBINT(300)
KAINT(AUTO) MAXMSGL(4194304)
MCAUSER(userabc) MONCHL(QMGR)
RCVDATA( ) RCVEXIT( )
SCYDATA( ) SCYEXIT( )
SENDDATA( ) SENDEXIT( )
SSLCAUTH(REQUIRED) SSLCIPH( )
SSLPEER( ) TRPTYPE(TCP)
|
So, how is the client channel being created? Is the CLNTCONN channel being created at runtime on the fly?
The Clients manual points to the Intercommunication manual for further detail on MQI channels, and the Intercommunication manual points to the Clients manual for info. If there is detail info somewhere on MQI channels please point me to it! Is there another manual that would be more helpful for our setup?
Thanks for your time. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Jul 16, 2009 8:17 am Post subject: Re: MQI Channel - unknown CLNTCONN creation |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| rickwatsonb wrote: |
| Is the CLNTCONN channel being created at runtime on the fly? |
 |
|
| Back to top |
|
|
| rickwatsonb |
| Posted: Thu Jul 16, 2009 9:21 am Post subject: |
|
|
Voyager
Joined: 15 Aug 2006
Posts: 87
Location: USA: Mid-West
|
Hi,
Thank you mqjeff for your reply.
It would be great to be able to read about the details of how it is created, but perhaps such detail is reserverd for the folks at Hursley.
If not, please advise. -Thanks |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Jul 16, 2009 9:43 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
...
What details are you looking for?
....
If you need to specify the full details of the CLNTCONN, there are several ways to do it, including using a CCDT.
If you don't need to specify the full details of the CLNTCONN, then there are several ways to specify sufficient connection information to create a dynamic CLNTCONN. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Jul 16, 2009 9:49 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| Is the CLNTCONN channel being created at runtime on the fly? |
If you are the curious type, for non-Java client applications, a client channel can be created with an environment variable MQSERVER=channelname/TCP/ipaddress.or.hostname.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| rickwatsonb |
| Posted: Thu Jul 16, 2009 11:54 am Post subject: |
|
|
Voyager
Joined: 15 Aug 2006
Posts: 87
Location: USA: Mid-West
|
Hi,
Thank you for the replies mqjeff and bruce2359.
I am just trying to put the pieces together in my mind as to how the app is connecting to the queue manager that I create and monitor as a novice MQ admin. The high-level understanding is very important, but I am driven by wanting to know the low-level stuff.
If I am recalling this correctly, a doc (Clients?) states that specifying the channel name, transport type and connection name at runtime on the client would create a dynamic client connection channel. The messaging.properties file shown in first post specifies these objects, except for the TCP - thus a missing piece.
I have started to read the MQ Java manual, I think this will help. It has already stated that MQ classes for JAVA do not support connection tables, or read MQ environment variables at start up... This answers some of the questions I had, along with your answers.
Thank you. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Jul 16, 2009 11:55 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
As of MQ 6.0, Java does support Client Channel tables.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Jul 16, 2009 12:12 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Your best source of information on clients is the WMQ Clients manual.
| Quote: |
| ...CLNTCONN SVRCONN pair ALWAYS exists for an MQI Channel. |
A single SVRCONN channel can support many concurrent client connections. In this sense, these are not the traditional channel pairs.
CLNTCONN channel definitions (created on a qmgr) are used to populate a channel table that is installed on (or visible from) a client platform. The client channel table offers the possibility of alternative qmgr channels for the client app to connect to. To make use of the client channel table, two environment variables are used, namely: MQCHLLIB (identifies the path to the table) and MQCHLTAB (names the table).
As with other MQ channel types, there are security exposures. Search this site for lots of posts on channel security.
You might want to consider taking a WMQ system administration class. IBM offers WM201 WMQ System Administration (Windows), WM202 (AIX), WM203 (Solaris). These are 4-day courses with extensive hands-on lab exercises - including clients. Here is the course description for the AIX version http://www-304.ibm.com/jct03001c/services/learning/ites.wss/us/en?pageType=course_description&courseCode=WM202
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Thu Jul 16, 2009 4:21 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| bruce2359 wrote: |
| Quote: |
| Is the CLNTCONN channel being created at runtime on the fly? |
If you are the curious type, for non-Java client applications, a client channel can be created with an environment variable MQSERVER=channelname/TCP/ipaddress.or.hostname. |
And a CLNTCONN channel can also be created dynamically using the MQCONNX call, with options to specify a MQCD 'channel definition' structure.
_________________
Glenn |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
