| Author |
Message
|
| MQMB&WAS |
 Posted: Tue Jul 11, 2017 9:48 pm Post subject: when is MQ Client needed? |
 |
|
Centurion
Joined: 12 Jun 2016
Posts: 130
|
I know MQ Client is needed for applications to connect to MQ Server. But, I have a few doubts. Appreciate any help.
Do applications hosted on Websphere application server need MQ Client to connect to MQ server?
Do mainframe jobs need MQ Client to connect to MQ server queues?
And is CCDT file mandatory where MQ Client is installed?
Thank you |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Tue Jul 11, 2017 10:09 pm Post subject: Re: when is MQ Client needed? |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| MQMB&WAS wrote: |
I know MQ Client is needed for applications to connect to MQ Server. But, I have a few doubts. Appreciate any help.
Do applications hosted on Websphere application server need MQ Client to connect to MQ server?
Do mainframe jobs need MQ Client to connect to MQ server queues?
And is CCDT file mandatory where MQ Client is installed?
Thank you |
it depends, it depends, no...
So in order to connect to MQ from anywhere you still need some kind of client.
Even if it is a "bindings" connection. Does that client have to be installed?
Well for a "bindings" connection the answer is no as it is installed with the server. But it will only allow you to connect to a queue manager on the same host....
Now back to your WebSphere (WAS) question...
WAS used to come with its own MQ Client..., you can also specify the Resource Adapter (RAR file) which is just another form of a client...
To your mainframe question. The answer is yes in the strictest sense of the question. Do you have to install a client for that? I'd expect that the libraries you will need to add to your JCL come with the MQ Server install on the MF.
You can't use a client to connect to a non MF qmgr when running on the MF.
As to the CCDT file, it is but one of the possibilities for establishing a connection to a queue manager....
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| MQMB&WAS |
| Posted: Wed Jul 12, 2017 10:51 am Post subject: Re: when is MQ Client needed? |
|
|
Centurion
Joined: 12 Jun 2016
Posts: 130
|
| fjb_saper wrote: |
| MQMB&WAS wrote: |
I know MQ Client is needed for applications to connect to MQ Server. But, I have a few doubts. Appreciate any help.
Do applications hosted on Websphere application server need MQ Client to connect to MQ server?
Do mainframe jobs need MQ Client to connect to MQ server queues?
And is CCDT file mandatory where MQ Client is installed?
Thank you |
it depends, it depends, no...
So in order to connect to MQ from anywhere you still need some kind of client.
Even if it is a "bindings" connection. Does that client have to be installed?
Well for a "bindings" connection the answer is no as it is installed with the server. But it will only allow you to connect to a queue manager on the same host....
Now back to your WebSphere (WAS) question...
WAS used to come with its own MQ Client..., you can also specify the Resource Adapter (RAR file) which is just another form of a client...
To your mainframe question. The answer is yes in the strictest sense of the question. Do you have to install a client for that? I'd expect that the libraries you will need to add to your JCL come with the MQ Server install on the MF.
You can't use a client to connect to a non MF qmgr when running on the MF.
As to the CCDT file, it is but one of the possibilities for establishing a connection to a queue manager....
Have fun |
Thanks for your time, fjb_saper. I looked up online and it looks like a custom code can be used in an application to connect to MQ Server, instead of using CCDT. Am I understanding it correctly?
And when you said RAR file can be used in WAS, do you mean configuring the queue destinations, queue connection factories and activation specs to connect to MQ ? |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Jul 12, 2017 10:56 am Post subject: Re: when is MQ Client needed? |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| MQMB&WAS wrote: |
| I looked up online and it looks like a custom code can be used in an application to connect to MQ Server, instead of using CCDT. Am I understanding it correctly? |
A CCDT is not required; rather, a CCDT is a choice.
_________________
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 |
|
|
| RogerLacroix |
| Posted: Wed Jul 12, 2017 3:43 pm Post subject: Re: when is MQ Client needed? |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
| MQMB&WAS wrote: |
| it looks like a custom code can be used in an application to connect to MQ Server, instead of using CCDT. |
Bad idea to re-invent the wheel. If you are connecting in client mode (i.e. queue manager is on a different server) then either use CCDT or MQ JNDI.
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Wed Jul 12, 2017 3:55 pm Post subject: Re: when is MQ Client needed? |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| RogerLacroix wrote: |
| MQMB&WAS wrote: |
| it looks like a custom code can be used in an application to connect to MQ Server, instead of using CCDT. |
Bad idea to re-invent the wheel. If you are connecting in client mode (i.e. queue manager is on a different server) then either use CCDT or MQ JNDI.
Regards,
Roger Lacroix
Capitalware Inc. |
Maybe they meant 'custom code' as being supported properties and methods on MQ objects that allow things like client channel name, host, port to be specified in the code, obviating the need to use CCDT, JNDA, mqclient.ini, MQSERVER variable etc.
Of course these things should be pulled from application environment config info, rather than hard-coded to fixed values.
_________________
Glenn |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Wed Jul 12, 2017 4:11 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
I wish applications would get totally away from having their own property files for MQ connection information. Over the years, I have run into so many issues when applications do this from missing SSL/TLS fields, non-support of exits, etc...
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Jul 13, 2017 3:04 am Post subject: Re: when is MQ Client needed? |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| gbaddeley wrote: |
| ...Of course these things should be pulled from application environment config info, rather than hard-coded to fixed values. |
I'm with Roger on this - far easier for them to code a file url, to abstract the MQ info at least.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Jul 13, 2017 3:48 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
An MQ client is like a database client. It's needed in the same situations.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
|
|
