| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQFTE plugin questions |
« View previous topic :: View next topic » |
| Author |
Message
|
| RogerLacroix |
 Posted: Fri Nov 02, 2012 8:59 am Post subject: MQFTE plugin questions |
 |
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
All,
I have looked in the MQFTE Info Center and I cannot find information on how to set connection details for MQFTE plugin for connecting to a remote queue manager.
I thought the MQFTE plugin used the MQ Explorer connection parameters but the customer says that it does not. When they use MQFTE plugin and connect to a remote queue manager, it does not instantiate (load) the Java client-side security exit and connects with a blank UserID.
In the MQ Explorer, they have defined the client-side security exit and it connects to the remote queue manager correctly. But when they connect to the same remote queue manager using the MQFTE plugin, it fails because it has not instantiated the Java client-side security exit (hence, it has a blank UserID).
In the MQFTE Info Center, I have read through the "Configuring" and "Administering" sections for MQFTE but I do not see anything about configuring the MQFTE plugin's connection details.
Could someone shed a little light on this for me?
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Fri Nov 02, 2012 9:24 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You could attempt to define the default security exit and see if that takes hold.
(there's a section in the MQ Explorer client connections preferences) |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Mon Nov 05, 2012 4:59 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi Jeff,
I had them try setting a "default security exit" in MQ Explorer and it did not make any difference.
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Nov 06, 2012 4:36 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Tue Nov 06, 2012 3:26 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Wed Nov 07, 2012 4:09 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi,
It appears that the FTE plugin only uses queue manager, channel name, hostname and port number when connecting to a remote queue manager. You cannot secure it with either a security exit or SSL. Very odd.
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Nov 07, 2012 6:28 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| RogerLacroix wrote: |
Hi,
It appears that the FTE plugin only uses queue manager, channel name, hostname and port number when connecting to a remote queue manager. You cannot secure it with either a security exit or SSL. Very odd.
Regards,
Roger Lacroix
Capitalware Inc. |
Have you tried using IBM_JAVA_OPTIONS as environment variable to assign keystore, truststore and passwords and maybe SSL cipher suite?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Nov 08, 2012 4:36 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| RogerLacroix wrote: |
Hi,
It appears that the FTE plugin only uses queue manager, channel name, hostname and port number when connecting to a remote queue manager. You cannot secure it with either a security exit or SSL. Very odd.
Regards,
Roger Lacroix
Capitalware Inc. |
You should be able to get them to provide a fix for that through the PMR.
Tell them that the product clearly states that it supports the use of WebSphere MQ, and that these features are standard parts of WebSphere MQ, and the customer doesn't consider it 'supported' if they don't support them. |
|
| 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
|
|
|
|
