| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Unable to create a WebSphere MQ specific class |
« View previous topic :: View next topic » |
| Author |
Message
|
| nimo |
 Posted: Sun Jul 06, 2003 11:39 am Post subject: Unable to create a WebSphere MQ specific class |
 |
|
Newbie
Joined: 06 Jul 2003
Posts: 5
|
Hi
I am getting following error when I run JMSAdmin utility to setup JMS.
I have on one machine (M1) IBM MQ Series 5.3,
I want to configure this Box in such a way that the Other machine where
WebSphere 5.x is running can pull the message using JMS.
So for box M1 details as follows:
1. Windows 2000 Ad. server
2. IBM MQ Series 5.3
3. Created Queue manager named "myqm"
4. Then defined local Queue Q1 and Q2.
5. Now trying to setup JMS and I am getting following error:
I have set the class path to mq\java\lib and included all jars.
I have also started "STRMQM"
Can anybody help me to investigate what is the cause of problem.
Anyhelp to this will be a great help. By the way I am new to MQ too.
>>>>>>>>
5648-C60, 5724-B41, 5655-F10 (c) Copyright IBM Corp. 2002. All Rights Reserved.
Starting Websphere MQ classes for Java(tm) Message Service Administration
InitCtx> 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.
InitCtx> InitCtx> InitCtx> Unable to bind object
InitCtx> Unable to bind object
<<<<<<<<
Thanks
-Nimo
[b] |
|
| Back to top |
|
 |
| harwinderr |
| Posted: Sun Jul 06, 2003 9:46 pm Post subject: |
|
|
Voyager
Joined: 29 Jan 2002
Posts: 90
|
The configuration error that you are getting is maybe because you have not properly configured the JMSAdmin.config file, which is the default configuration file for the MQSeries Classes for Java Message Service Administration Tool.
By default, it indicates an LDAP service provider. If a different service provider is used, then this line should be commented out and the appropriate one should be uncommented. Same thing goes for the URL provider also.
I generally configure to use it for file system context. So I just uncomment the following two lines and comment the others:
INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
PROVIDER_URL=file:/C:/JNDI-Directory
(you need to manually create the directory)
Also make sure that you have the following jar files in the classpath:
com.ibm.mq.jar, com.ibm.mqjms.jar, fscontext.jar, jndi.jar, jms.jar,
connector.jar, and providerutil.jar.
Hope this will help
Later,
H |
|
| Back to top |
|
|
| kingdon |
| Posted: Mon Jul 07, 2003 12:54 am Post subject: |
|
|
Acolyte
Joined: 14 Jan 2002
Posts: 63
Location: UK
|
Hmm, the error message has got a bit mangled at some point. It should say:
"Unable to create a WebSphere Application Server specific class. The classes may not have been installed or added to the classpath."
and it can be generated when attempting to store or retrieve a WebSphere specific factory to/from the JNDI namespace. However, this is somewhat beside the point, since for WAS5 it is unlikely that you want to be using JMSAdmin at all. Instead, you configure WAS5 to access the external queue manager via the WAS5 admin panels.
Regards,
James. |
|
| Back to top |
|
|
| nimo |
| Posted: Mon Jul 07, 2003 5:13 am Post subject: |
|
|
Newbie
Joined: 06 Jul 2003
Posts: 5
|
Hi harwinderr,
Creating directory and making required changes for this directory in the config file worked, there is no error anymore, I do have one question
and it is from which manual I will get this each and every steps documented.
Anyway it was a great relief and help. Thanks again.
-Nimo |
|
| Back to top |
|
|
| nimo |
| Posted: Mon Jul 07, 2003 5:23 am Post subject: |
|
|
Newbie
Joined: 06 Jul 2003
Posts: 5
|
Hi James,
In my situation I have two separate machines,
e.g. Machine : M1 : for MQ Server, Queue Manager, Local Queue
Machine : M2 : Websphere 4.x/5.x.
In above mentioned situation if I need data from Queue on M1.
I did following thing:
#1 Setting up MQ
Means defining Queue Manager and Local Queue.
#2 Setting up JMS
Defining JMS Administered object and queue connection factory
which represents queue manager and Queues defined by me in MQ.
Then I think now I need to configure my Websphere on Mchine M2.
To access this remote JMS administered object.
Please tell me I am doing correct or not, according to my
understanding.
Thanks very much for your help and suggestion.
Looking forwar for reply.
-Nimo |
|
| Back to top |
|
|
| kingdon |
| Posted: Mon Jul 07, 2003 7:13 am Post subject: |
|
|
Acolyte
Joined: 14 Jan 2002
Posts: 63
Location: UK
|
Hi Nimo,
It's worth differentiating between 'setting up JMS' and anything to do with JNDI. From a pure JMS perspective, JNDI is entirely optional, and only provides a convenient mechanism for storing vendor specific details about the underlying messaging provider. In terms of setting up JMS with MQ series, for point to point messaging there is nothing to do above and beyond having a working MQ queue manager installation. For pub/sub we use some additional queues, and these are defined in the MQJMS_PSQ.mqsc script (this is described in chapter 4 of the WebSphere MQ Using Java book).
Now, the picture is complicated somewhat when using JMS from WebSphere application server. In this case, it is usual (and recommended) that the applications obtain WebSphere specific connection factory objects from the JNDI server provided by the application server. With WAS5.x such objects should be created using the WAS control panels (possibly I should be calling this the system admin console, I forget what the current name is, and I don't have the manuals to hand). Prior to WAS5.x, the objects were bound into the WAS namespace using JMSAdmin, which has to be correctly configured to access WAS's JNDI server. Since this can be a little tricky to set up, I'd recommend you use WAS5 if you have the option.
Regards,
James. |
|
| Back to top |
|
|
| nimo |
| Posted: Mon Jul 07, 2003 11:05 am Post subject: |
|
|
Newbie
Joined: 06 Jul 2003
Posts: 5
|
Hi James,
Thanks for differntiating MQ and JNDI set up.
It was a great help, In my application As I told previously that
there are two boxes (MQ, WebSphere) needs to connect each other
Here I got confused for mapping between those too.
But your point about separating the issue related to JND makes me
think that JNDI Service can be common to both of my application, and
I think I can access it through URL.
Thanks again to you and all for very excellent help.
-Nimo |
|
| 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
|
|
|
|
