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 » WAS configuration : from MQSERVER to MQCHLTAB

Post new topic  Reply to topic
 WAS configuration : from MQSERVER to MQCHLTAB « View previous topic :: View next topic » 
Author Message
sebastia
PostPosted: Wed Mar 18, 2009 11:08 am    Post subject: WAS configuration : from MQSERVER to MQCHLTAB Reply with quote

Grand Master

Joined: 07 Oct 2004
Posts: 1003

Hi all. I need some help - I am good in MQ but not on WAS.

We have a customer that has Java JMS code running
on a client-mode WAS (5.1 going to 6) connecting
to (wintel) MQ Server using MQSERVER (or similar).

Now they want some failback improvement,
so MQCHLTAB has come into play.

My simple question is :

HOW DO YOU CONFIGURE MQCHLTAB to WAS 6.1 ?
==================================

Any pointer to any information center is welcome.

PD.-
I have been told that 40% of the applications use

MQQueueConnectionFactory factory = new MQQueueConnectionFactory();
factory.setQueueManager(System.getProperty("mq.QueueManagerName"));
...
QueueConnection conn = factory.createQueueConnection();


And the rest, 60% of apps use this :

private static final String QMGRNAME =
System.getProperty("mq.QueueManagerName");

Dont know exactly what that means ...
Back to top
View user's profile Send private message Visit poster's website
fjb_saper
PostPosted: Wed Mar 18, 2009 3:09 pm    Post subject: Re: WAS configuration : from MQSERVER to MQCHLTAB Reply with quote

Grand High Poobah

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

sebastia wrote:
Hi all. I need some help - I am good in MQ but not on WAS.

We have a customer that has Java JMS code running
on a client-mode WAS (5.1 going to 6) connecting
to (wintel) MQ Server using MQSERVER (or similar).

Now they want some failback improvement,
so MQCHLTAB has come into play.

My simple question is :

HOW DO YOU CONFIGURE MQCHLTAB to WAS 6.1 ?
==================================

Any pointer to any information center is welcome.

PD.-
I have been told that 40% of the applications use

MQQueueConnectionFactory factory = new MQQueueConnectionFactory();
factory.setQueueManager(System.getProperty("mq.QueueManagerName"));
...
QueueConnection conn = factory.createQueueConnection();


And the rest, 60% of apps use this :

private static final String QMGRNAME =
System.getProperty("mq.QueueManagerName");

Dont know exactly what that means ...


Neither nor...
A good behaved WAS application retrieves the cf from JNDI and does not change any parameters on it.
The way to configure the channel tab to WAS 6.1 is to set the channel tab file URL to the correct property of the connection factory.

You can then set the qmgr name to what is in the channel tab or *alias etc... You do not set host and channel or port.

Nota: you will need the V7 libraries for load balancing. V6 only allows for failover via the chltab.

Enjoy
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
sebastia
PostPosted: Thu Mar 19, 2009 12:46 am    Post subject: Reply with quote

Grand Master

Joined: 07 Oct 2004
Posts: 1003

mr Saper - do you have a pointer to
"How to configure JNDI in WAS 6.1 for MQ Client connections" ?

6.1 Info Center is

>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp

but I cant find the right "Search parameters" to get the info I need from there ... Looks WAS people and me use diferent words for the same meaning I guess ... as CCDTURL instead of MQCHLTAB !

By example, I know "Connection Factory" is a Queue Manager, ok, so far so good. Took me one week to figure it out ...

Look to the WAS manual - it says nothing if the connection is Bindings or Client !!!???

==============================================

To create a new connection factory, complete the following steps:

1. Click New in the content pane.
2. Specify the following required properties. You can specify other properties, as described in a later step.
* Name
The name by which this connection factory is known for administrative purposes within IBM WebSphere Application Server.
* JNDI name
The JNDI name that is used to bind the connection factory into the namespace.
* CCSID
The coded character set identifier for use with the WebSphere MQ queue manager; for example: 850.
3. Click Apply. This defines the JMS connection factory to WebSphere Application Server, and enables you to browse or change additional properties.
Back to top
View user's profile Send private message Visit poster's website
fjb_saper
PostPosted: Thu Mar 19, 2009 3:17 am    Post subject: Reply with quote

Grand High Poobah

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

CCDTURL = Client Channel Definition Table URL. This is the url that points to your MQCHLTAB.

The ConnectionFactory does not care whether client or server because you fill that information in as you define it (transport type, qmgr name, hostid, channel name, port, CCDTURL)...

Remember as you fill in the CCDTURL you need as well to fill in the qmgr name as defined in the MQCHLTAB (either blank or *qmgralias etc...)

See Here in the WAS 6.1 manual

Have fun
_________________
MQ & Broker admin


Last edited by fjb_saper on Thu Mar 19, 2009 3:33 am; edited 1 time in total
Back to top
View user's profile Send private message Send e-mail
sebastia
PostPosted: Thu Mar 19, 2009 3:25 am    Post subject: Reply with quote

Grand Master

Joined: 07 Oct 2004
Posts: 1003

Thanks, mr Saper - I will try to remember it.

But, can you tell me, how is it possible to

a) open the WAS 6.1 Info Center URL

>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp

b) select the "Search" tab instead of TOC

c) write "CCDTURL" in the search argument

... and get "NOTHING" back ???

To my luck, Google is quite better : "WAS CCDTURL" gives me a lot of pointers ...

... including a techarticle called "WebSphere MQ V6 Java and JMS clients and the client channel definition table" at this url :

>>> http://www.ibm.com/developerworks/websphere/library/techarticles/0506_barrago/0506_barrago.html

Cheers.
Back to top
View user's profile Send private message Visit poster's website
fjb_saper
PostPosted: Thu Mar 19, 2009 3:41 am    Post subject: Reply with quote

Grand High Poobah

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

Bizzare as in strange... Did not find anything about CCDTURL either. But it should be a property in defining a QueueConnectionFactory. You may not be able to use this for a connection factory or a TopicConnectionFactory.

If not a property try setting it up as a special property...

Have fun.
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
sebastia
PostPosted: Thu Mar 19, 2009 4:33 am    Post subject: Reply with quote

Grand Master

Joined: 07 Oct 2004
Posts: 1003

mr Saper - I did try with WAS 7.0 and it is there :

a) WAS 7.0 info center :

>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp

b) select "Search" tab

c) enter "CCDTURL" argument ...

.... surprise ! There are few entries !!!

And "CCDTURL" is not related to version 7 of WAS, is it ?

OK - I have some pointers. Thanks a lot.
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Java / JMS » WAS configuration : from MQSERVER to MQCHLTAB
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.