| Author |
Message
|
| 9A5YY |
 Posted: Wed Sep 12, 2007 12:32 am Post subject: WAS Websphere MQ server and client application |
 |
|
Voyager
Joined: 27 Sep 2005
Posts: 99
Location: Croatia
|
Hello!
Can every WAS server MQ application become client application or with other words can all MQ API calls which normally work at server application be issued at WAS client application? Thanks for help! |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Sep 12, 2007 12:36 am Post subject: Re: WAS Websphere MQ server and client application |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| 9A5YY wrote: |
| Can every WAS server MQ application become client application or with other words can all MQ API calls which normally work at server application be issued at WAS client application? |
Short answer - no.
Medium answer - yes and no.
Long answer - it depends on the application. The restrictions of the client connection are described in the Clients manual.
You'll also find some discussions on the forum regarding client v bindings applications.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| 9A5YY |
| Posted: Wed Sep 12, 2007 1:03 am Post subject: |
|
|
Voyager
Joined: 27 Sep 2005
Posts: 99
Location: Croatia
|
| What must be setup on WAS 6.0 to perform Two Phase Commit on MQ Client application on WAS? The MQ server 6.0 is on an other server. Client application is on the separated server with WAS. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Sep 12, 2007 1:19 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| 9A5YY wrote: |
| What must be setup on WAS 6.0 to perform Two Phase Commit on MQ Client application on WAS? |
More software which your IBM rep will be delighted to quote on.
If you'd looked in the Client manual as I suggested, you'd have noticed that this is one of the restrictions of the standard client!  
Client 2 phase commit requires the ETC.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| 9A5YY |
| Posted: Thu Sep 13, 2007 12:12 am Post subject: |
|
|
Voyager
Joined: 27 Sep 2005
Posts: 99
Location: Croatia
|
| Please, can someone help me or send me link how to configure WAS 6.0 that WAS MQ client application use Extended Trasactional Client? In Websphere MQ Client 6.0 book ther is a instruction only for configuring WAS 4. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Sep 13, 2007 12:22 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| 9A5YY wrote: |
| Please, can someone help me or send me link how to configure WAS 6.0 that WAS MQ client application use Extended Trasactional Client? |
You seem to be mixing some technologies here. Running a client application under WAS requires some configuration which, I'm told, doesn't vary much between WAS 4 & WAS 6. Others with more experence may wish to correct me.
The MQ client connection is likewise configured within WAS and again I'm told is not significantly different. But which MQ client is in use depends on which one is installed. The standard client or the ETC (which costs almost as much as an MQ Server).
There are no code changes within the client application which can't see the difference between the standard client and the ETC.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| George Carey |
| Posted: Tue Sep 18, 2007 8:06 am Post subject: to 9a5yy |
|
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
I may have to set this up myself soon as well. I am not using WAS but rather working with Oracle OC4J app server. ETC is needed of course as already mentioned by others but the JNDI objects and settings are what needs to be clarified. An XAQCF cannot be used but in transport(bind) mode but of course you need transport(client) so you must define a QCF object and set its transport to (client) mode. I assume doing this and using ETC will allow you to perform the JMS api calls for an XA compliant 2 phase commit within the configuration/architectural restrictions set out in the ETC manual. Which I have only cursorly browsed at this time.
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Sep 18, 2007 8:08 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It's perfectly possible to configure an XAQCF with client connections.
It usually fails to function, if the ETC is not installed.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| George Carey |
| Posted: Tue Sep 18, 2007 11:31 am Post subject: |
|
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Sep 18, 2007 11:43 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I don't trust any piece of "IBM" documentation that is not served off of "ibm.com".
I've run into issues - at least with WAS JNDI - where WAS administrators have checked the "XA Enabled" checkbox and then configured a client connection.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| George Carey |
| Posted: Tue Sep 18, 2007 12:00 pm Post subject: IBM manuals |
|
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
Try downloading the latest IBM website manual your self and let me know if it says something different!!
You get Java runtime exceptions as well. I don't say things with assurity unwarrantedly. Just an FYI.
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Sep 18, 2007 12:15 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I'm telling you what my experience is. Of course, what I'm not telling you is that it's from WAS v5.1, about two years ago.
And I'm not saying the doc you linked to is wrong, either. It's just not from a source that I would consider reliable.
I don't think that the installation of the ETC is going to change what options you have for configuring anything in JNDI. It may change what runs or doesn't run - but not what's valid to define.
I also haven't ever configured an app server to use the ETC.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| George Carey |
| Posted: Tue Sep 18, 2007 1:20 pm Post subject: Beating a dead horse take 2 |
|
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
jl:
| Quote: |
| I don't think that the installation of the ETC is going to change what options you have for configuring anything in JNDI. |
I never said or implied it did ... you did ! The property as noted in the IBM documentation transport mode only allows bind for XAQCFs said nothing about using ETC or not and neither did I !!
jl:
| Quote: |
| It may change what runs or doesn't run - but not what's valid to define. |
On this we agree!
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
| Back to top |
|
|
|
|
