| Author |
Message
|
| klabran |
 Posted: Thu Jul 15, 2004 2:22 pm Post subject: Test install of WBIM 5 |
 |
|
Master
Joined: 19 Feb 2004
Posts: 259
Location: Flagstaff AZ
|
I just installed WBIM 5 on a test server.
I installed
DB2 8.1 with fix pack 6
MQ 5.3 with the latest fix pack and created a queue manager.
MDAC 2.8
IBM Agent Controller 5.0.X whatever the latest is....
WBIM 5 with fix pack 3.
I then created my broker db and config db.
I then set the user rights for them and the MQ groups
I then created my broker and config mgr using the already existing qmgr on this test server.
I set my capacity and started the broker and config mgr.
Now I'm running the Toolkit from the test server and I can't connect. It is given my a reason code of 2059 but my listener is running??? Have I missed a step?
Thanks for any pointers!
Kevin |
|
| Back to top |
|
 |
| kirani |
| Posted: Thu Jul 15, 2004 2:54 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Try using some sample program (like amqsput) to put a message on test queue on the broker queue manager.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| klabran |
| Posted: Thu Jul 15, 2004 3:01 pm Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 259
Location: Flagstaff AZ
|
| thanks for the tip.... It's not connecting either. I set the MQSERVER variable and I still get 2059. ??? |
|
| Back to top |
|
|
| kirani |
| Posted: Thu Jul 15, 2004 3:10 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Is your queue manager up and running? Look for errors/warning messages into Event viewer. MQSERVER variable is required when you are trying to connect in Client mode. But since you are on the server itself you can try running the server version of the program.
Are you logged on to the test server or connecting remotely using PCAnywhere?
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| klabran |
| Posted: Thu Jul 15, 2004 3:12 pm Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 259
Location: Flagstaff AZ
|
I am trying it directly on the box and either setting MQSERVER or not didn't work. The QM is running and the services are all running according to the MMC???
I get rc 2059 when using MQSERVER.
I get rc 2058 when not using it. |
|
| Back to top |
|
|
| kirani |
| Posted: Thu Jul 15, 2004 3:26 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Which utility are you trying to run? amqsput or amqsputc? If running amqsputc you will need to set yout MQSERVER variable. Did you see any errors when starting up the services (config mgr and Broker)?
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| klabran |
| Posted: Thu Jul 15, 2004 3:30 pm Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 259
Location: Flagstaff AZ
|
Duh!!! amqsput works.... I was trying amqsputc but I don't have the mq client installed on the server.
Does the toolkit need the mq client installed?
No I have not seen any errors when I started up the config mgr and the broker. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Jul 15, 2004 7:56 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| Quote: |
Does the toolkit need the mq client installed?
|
Yes.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Jul 16, 2004 7:01 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| PeterPotkay wrote: |
| Quote: |
Does the toolkit need the mq client installed?
|
Yes. |
Are you sure?
I know it needs the Java MQ classes installed (which the original poster didn't mention installing...). But I can't find anything that says it needs the MQ Client installation.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Jul 16, 2004 7:51 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
The toolkit connects to the QM thru the SYSTEM.BKR.CONFIG channel, a SVRCONN channel. I just came back from a class on WBIMB, and the whole discussion on Security with the toolkit was predicated o the fact that it made this client connection.
All the security hooey associated with any SVRCONN channel applies here. If you leave the MCAUSER blank, use SSL or an exit on this channel. Otherwise you got a wide open hole into that QM.
The toolkit allows you to specify an exit in the connection properties in the BrokerAdmin perspective.
The teacher said that security exits can now be written in Java, as long as the SVRCONN channel was created by a Java app.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Jul 16, 2004 7:56 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| PeterPotkay wrote: |
| The toolkit connects to the QM thru the SYSTEM.BKR.CONFIG channel, a SVRCONN channel. |
Right. But that connection is made using the Java client, not the regular Client - at least as far as I know. So you need to run a custom install, and install the Java feature for MQ - but not the Client feature.
| PeterPotkay wrote: |
| The teacher said that security exits can now be written in Java, as long as the SVRCONN channel was created by a Java app. |
You still can't define security exits on the Queue Manager that are written in Java, as far as I know.
But maybe I am misunderstanding this.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Jul 16, 2004 8:02 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| Quote: |
Right. But that connection is made using the Java client, not the regular Client - at least as far as I know. So you need to run a custom install, and install the Java feature for MQ - but not the Client feature.
|
Yes, OK. Maybe a better way of saying it is you can't connect in bindings mode. The toolkit machine will need the java jars that contain the MQClient stuff.
| Quote: |
You still can't define security exits on the Queue Manager that are written in Java, as far as I know.
|
I to looked for documentation on that. I wanted to use kolbans Explorer exit on the toolkit, but the instructor said that since it is not written in Java, the toolkit that is in Java wont be able to call it. That is when I was told that as of CSD5 or CSD6, the MQ code will support Java exits on Java channels. That might not have been officially available info though. Maybe it will be official in MQ 6.0?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Jul 16, 2004 8:27 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Here's the direct quote from the online help.
| Quote: |
Security exits
You can use security exit programs to verify that the partner at the other end of the channel is genuine.
When you start the Message Brokers Toolkit for WebSphere Studio, it does not invoke a security exit to monitor its connection to the Configuration Manager by default. If you want to protect access to the Configuration Manager from client programs, you can use the WebSphere MQ channel security exit facility. This works in a standard way for the Configuration Manager end of the connection. You can find information about how to set up the security exit at the server end of the connection in the WebSphere MQ Intercommunication manual.
If you want to use a security exit one can be defined when a new domain is created within the Domains view of the Message Brokers Toolkit for WebSphere Studio to provide connection security. These security exits are standard WebSphere MQ security exits, are written in Java, and must be written to implement the WebSphere MQ exit interface.
For an overview of security exits, refer to the section "Channel security exit programs" in the chapter "Channel exit programs" in the WebSphere MQ Intercommunication manual. |
I believe the relevant section that caused your teacher to answer the way they did is what I have bolded. Also, a more direct response in a different section
| Quote: |
Using security exits
To invoke a security exit for communications between the Message Brokers Toolkit for WebSphere Studio and the Configuration Manager, one must be defined when the domain connection is created.
Select File > New > Domain and the Domain view appears.
Enter the queue manager name, host and port you wish to use.
Enter the security exit name. This must be a valid Java class name.
When the connection is attempted, the security exit is invoked. |
My emphasis, again.
So that seems to say that you can define Java security exits to the queue manager. But I don't know how. Time to dig into the manuals...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kirani |
| Posted: Fri Jul 16, 2004 10:41 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Wouldn't the MQ Jar files get installed with the toolkit. I believe those were old days (MQSI 2.0.x) when you were required to install MQSeries Java classes separately.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Jul 16, 2004 11:02 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| kirani wrote: |
| Wouldn't the MQ Jar files get installed with the toolkit. I believe those were old days (MQSI 2.0.x) when you were required to install MQSeries Java classes separately. |
No, I don't think so. There's an error listed in the install.htm for version 5 that says "If you see this message it's because you didn't install the MQSeries for Java classes".
And it's also part of the preqrequisite checking that happens during installation, I believe. If the Java classes aren't installed, I think the prerequisite for MQ is listed as "partial".
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
