| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| How to edit an existing Remote Broker Connection in WMB TK 8 |
« View previous topic :: View next topic » |
| Author |
Message
|
| PeterPotkay |
 Posted: Wed Jul 03, 2013 4:27 am Post subject: How to edit an existing Remote Broker Connection in WMB TK 8 |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I have Toolkit version 8.0.0.2-20130322-1723.
I am playing around with Security Exits and / or SSL on my connection to a remote broker. This requires trying different things and I haven't been able to figure out to:
A. View these properties on an existing connections. When I have a remote Broker highlighted in the bottom left left pane I do see a Properties tab in the bottom right, but it only has 6 basic parameters: Build Level, Name, QM name, Version, Host and Port. How can you see SSL and Security Exit parameters on an existing connection?
B. How do you change parameters on an existing connection? Right now I have to delete and recreate the connection anytime I want to try something new with SSL or the exit.
I have to delete and recreate even if I want to just check what a value is. Since there is no way to view some of these parameters that I can see, if I'm not sure what a value was set to, delete and recreate.
There's gotta be a better way.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Jul 03, 2013 4:58 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Don't know about that specific release of toolkit 8, but you're not supposed to muck much with the connections in the toolkit. You're supposed to set up the connection with the broker explorer and then use the .broker file you generated in the explorer to create the connection in the toolkit.
Just edit and verify the .broker file before applying it. In the early days there were some "features" in it like it always used the system.broker channel regardless of what you had configured. Editing the file fixed the problem.
PS there should be a ppt from me on the nynjmq.org site describing how to create an SSL connection to the broker.
You need to set the IBM_JAVA_OPTIONS for the passwd of the stores when using mqsideploy...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jul 03, 2013 5:42 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| fjb_saper wrote: |
| Don't know about that specific release of toolkit 8, but you're not supposed to muck much with the connections in the toolkit. You're supposed to set up the connection with the broker explorer and then use the .broker file you generated in the explorer to create the connection in the toolkit. |
No.
You're supposed to use Broker Toolkit for development activities, and use Broker Explorer for administrative activities.
This can mean creating a .broker file in Explorer and using it in Toolkit, or it can mean creating a .broker file in Toolkit and using it in Explorer, or it can mean neither.
| fjb_saper wrote: |
| Just edit and verify the .broker file before applying it. In the early days there were some "features" in it like it always used the system.broker channel regardless of what you had configured. Editing the file fixed the problem. |
This doesn't alter the fact that MQExplorer queue manager connections are entirely separate from Broker Explorer connections, and use different technologies under the covers (MQ vs JMS, mostly) and enforce different security models.
Which is what Peter is struggling with, at least slightly. It also has to do with trying to use Toolkit for things that are probably better done in Explorer, in a much smaller way.
Peter - You may get a better view of the information used to connect to a given Broker in BrokerExplorer than in Toolkit. Again, as FJ says, the .broker file for a given connection is exportable and editable, although it's not the best choice. And in either case, I don't think you can change information without delete/recreate. it's definitely annoying. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Jul 03, 2013 7:36 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I was able to make it work via MB Explorer and that GUI is just as bad in letting you see or change details on the connection.
However the pointer to look at the *.broker file was helpful. All the details are there. And I was able to export the file from one GUI and import it into the other GUI. The same configuration using Capitaleware's MQAUSX for Authentication works in both tools.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| 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
|
|
|
|
