ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ Java / JMS » Configuring MQ as JMS provider

Post new topic  Reply to topic
 Configuring MQ as JMS provider « View previous topic :: View next topic » 
Author Message
lakshmanrajagopal
PostPosted: Thu May 01, 2008 8:06 am    Post subject: Configuring MQ as JMS provider Reply with quote

Newbie

Joined: 24 Mar 2008
Posts: 3

Hi Folks –

This is almost the first time we are setting JMS using MQ solely as a provider (Client Bindings).

Now being said that we have done the following activities in the MQv6.0 server

- Created a QCF
- Queue destinations created

Now in the client application (JMS message producer)

- Installed MQ client

Is there anything else I need to do on the client application server (Siebel v8.0)?

Do I need to create any new file called jndi.properties? or will it get created automatically anywhere?

On the client end I had already add the MQ jar files to the classpath of the machine and have the right jvm but when I try to connect to and send a message to the JMS queue I get an error:

InitialContextFactory not found or jndi.properties file not found


Your help on this would be really appreciated!
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Thu May 01, 2008 10:23 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

I would strongly advise you to use the JMSAdmin utility to create your .bindings file and use the Sun initial file context.

You can then reuse this in Siebel or wherever.
It will probably be easier to use than a client J2EE app setup.

WAS will have it's own JNDI repository and initial Context.

Remember that JNDI admin is not administering the queue manager and as such each destination you define will need it's counterpart in the RW.

Enjoy
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Java / JMS » Configuring MQ as JMS provider
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.