| Author |
Message
|
| hopsala |
 Posted: Fri Sep 24, 2004 2:32 pm Post subject: MQ and WAS: JMSAdmin does not accept DEF WSQCF() command |
 |
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
Hi there,
after reading much of the material on the internet - both here and, in IBM books and in other sites - I have not been able to solve this problem, so I would appreciate your support.
When trying to type in JMSAdmin the command:
DEF WSQCF(SSL) QMANAGER(SSLQMGR) TRANSPORT(CLIENT) HOSTNAME(localhost) PORT(1414) CHANNEL(SSL.SVRCONN) SSLCIPHERSUITE(SSL_RSA_WITH_RC4_128_MD5)
or any other similar variation I receive this error message:
"InitCtx> Unable to create a valid object, please check the parameters supplied
Unable to create a WebSphere MQ specific class. The WebSphere MQ classes may not have been installed or added to the classpath."
Now, this command I took from the wonderfull book "WAS and MQ Family Integration" (sg246878) in chapter 15.3.1.
However, in yusufs article "Configuring SSL Connections between JMS Clients and the WebSphere MQ JMS Provider" and in most other references to this subject, I have noticed people use the "DEF QCF" command instead of my "DEF WSQCF".
Btw, the "DEF QCF" command works, though I have not tried connecting the namespace to WAS as of yet.
What I'd like to know is what's the exact difference between QCF and WSQCF and which I should use.
Also, all documentation I found was for WAS 5.0, is there no way in WAS 5.1 to use SSL channels without using JMSAdmin and all this hassle? It seems incredible to me that you cannot define it from within the administration console (though I have not found how).
I have tried this on several machines with the following properties:
WAS 5.1/5.0, MQ 5.3.0/5.3.1, windows 2000/xp/2000 proffesional.
my CLASSPATH includes all that is stated in the books and many of the articles i've read here and in other places (providerutil.jar, mqjms.jar etc etc) and my JMSAdmin.config has been taylored according with your instructions on previous posts.
CLASSPATH=.;D:\Program Files\IBM\WebSphere MQ\Java\lib\providerutil.jar;D:\Program Files\IBM\WebSphere MQ\Java\lib\com.ibm.mqjms.jar;D:\Program Files\IBM\WebSphere MQ\Java\lib\ldap.jar;D:\Program Files\IBM\WebSphere MQ\Java\lib\jta.jar;D:\Program Files\IBM\WebSphere MQ\Java\lib\jndi.jar;D:\Program Files\IBM\WebSphere MQ\Java\lib\jms.jar;D:\Program Files\IBM\WebSphere MQ\Java\lib\connector.jar;D:\Program Files\IBM\WebSphere MQ\Java\lib\fscontext.jar;D:\Program Files\IBM\WebSphere MQ\Java\lib\com.ibm.mq.jar
in JMSAdmin.config
INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
PROVIDER_URL=file:/E:/JNDI/
SECURITY_AUTHENTICATION=none
That's it, a little lengthy I know, but I think it necessary.
Tnx! |
|
| Back to top |
|
 |
| vennela |
| Posted: Fri Sep 24, 2004 3:38 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
As far as I know you CANNOT define a WSQCF in CLIENT mode. WSQCF can only be used in bindings mode. If you want to use it with CLIENT mode then you should have extended transactional client.
If you use WSQCF then websphere will the transaction co-ordinator or resource manager, if you use QCF then MQ will be the transaction co-od\rdinator |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sat Sep 25, 2004 6:14 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I think what you can do depends on what version of WAS you are running.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Sep 25, 2004 12:55 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I believe your main problem is
a) a classpath problem: have you added the additional classes for SSL to your MQ classpath ?
and
b) possibly a JVM problem. Although you can run WAS on different JVM's the default is the IBM JVM that's under the WAS filesystem.
Now I am not too sure about how that ties in with all the SSL setup and the JAVA_HOME for SSL....
Besides I would not use JMSAdmin if I can avoid it. You should use the WAS's management console and configure following resource (from memory) : Websphere JMS MQ provider...
Enjoy  |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sat Sep 25, 2004 1:07 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| fjb_saper wrote: |
| Besides I would not use JMSAdmin if I can avoid it. You should use the WAS's management console and configure following resource (from memory) : Websphere JMS MQ provider... |
To follow up on this a little bit, there's something important to note here. If you are using WAS version 5.0 or later, you really should not use JMSAdmin. If you use JMSAdmin, all of the resources you create will not be persistent. They will go away when you restart your server instance (or the node or the deployment manager, depending on what scope you create them at).
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| hopsala |
| Posted: Tue Sep 28, 2004 12:01 am Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
Tnx for the commentry.
It is clear to me that using JMSAdmin is not a very good way of doing this, but I have found no other.
The thing is, in the administration console of WAS (5.0 or 5.1) there is indeed the MQ JMS Provider part, which works wonderfully for normal client channels. However, if you will look closely at the properties one can assign to a Queue Connection Factory, you shall see that the properties for SSL (SSLCAUTH, SSLPEER, SSLCIPH) do not appear at all.
Just yesterday, someone has told me something about "custom properties" in WAS, but both he and I are unsure as to how exactly to use this feature.
Again, help would be appreciated.
hop |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Sep 28, 2004 5:17 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
read up the WAS manual. But as far as custom properties are concerned my guess is that the property name must match the MQ property name. You can then set the value.
Try it out and let us know.
Enjoy |
|
| Back to top |
|
|
| MqAndy |
| Posted: Fri Apr 08, 2005 12:17 am Post subject: |
|
|
Newbie
Joined: 07 Apr 2005
Posts: 2
Location: UK
|
I too have been trying to follow "WAS and MQ Family Integration" chapter 15 to use SSL between WAS and MQ and had the same issue with jmsadmin and "def wsqcf"
Has anyone got this to work? |
|
| Back to top |
|
|
|
|
