| Author |
Message
|
| Sam Uppu |
 Posted: Tue Mar 23, 2010 11:22 am Post subject: SSL implementation between MQServer and client |
 |
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
Hi Guys,
We are version 6.0.2.3 of MQ on solaris 8.
We installed MQ on one box and a client on another box where the client app is running.
When we implement SSL, the client app needs to use MQCHLTAB only or they can use SVRCONN channel and still can implement SSL on SVRCONN/ CLNTCONN channels?.
Please confirm.
Thanks. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Mar 23, 2010 11:27 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The client application needs to specify SSL parameters on the CLNTCONN portion of the channel.
Using the MQ Channel Table is a relatively easy way of doing this, but it is not the only way.
Happy Reading! |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Mar 23, 2010 11:48 am Post subject: Re: SSL implementation between MQServer and client |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Sam Uppu wrote: |
| When we implement SSL, the client app needs to use MQCHLTAB only or they can use SVRCONN channel and still can implement SSL on SVRCONN/ CLNTCONN channels?. |
If I interpret your question correctly, no you can't just specify the SVRCONN in an MQSERVER variable and connect as this creates a default CLNTCONN that doesn't contain any of the SSL information needs.
You will need to use MQCHLTAB or other method to establish a client connection which does allow SSL parameters to be specified.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Sam Uppu |
| Posted: Tue Mar 23, 2010 6:08 pm Post subject: |
|
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
If we create both SVRCONN and CLNTCONN channels on QMgr and provide the SSL parameters on both channel definitions and provide SVRCONN channel name in MQSERVER environmental variable on client app, will it work?. or it is better to do it with MQCHLTAB?.
Thanks. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Mar 23, 2010 6:47 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Sam Uppu wrote: |
| If we create both SVRCONN and CLNTCONN channels on QMgr and provide the SSL parameters on both channel definitions and provide SVRCONN channel name in MQSERVER environmental variable on client app, will it work?. |
No. The MQSERVER variable creates it's own CLNTCONN as I indicated above.
| Sam Uppu wrote: |
| it is better to do it with MQCHLTAB |
Any other method will work better. Because it'll work. If MQCHLTAB is the best method for you and your application / design / site standards is a question you must answer for yourself.
There have been any number of discussions on the forum about client connection methods you might find useful.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Fri Mar 26, 2010 4:00 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
First, it would help to read and fully understand the uses and value of a CCDT (client channel definition table). MQCHLTAB is just the environment variable that tells MQ what the name of the CCDT file will be.
Note the CCDT is version specific. So, be sure to generate the correct version of CCDT for the client. You could use MO72 to do this...
Last, I see that your maintenance is only a few years out of date... I couldn't possibly see any issue with that...  |
|
| Back to top |
|
|
|
|
