| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| The meaning of attributes within the JMSAdmin tool |
« View previous topic :: View next topic » |
| Author |
Message
|
| hilltops |
 Posted: Wed Apr 12, 2006 6:47 am Post subject: The meaning of attributes within the JMSAdmin tool |
 |
|
Centurion
Joined: 01 Mar 2006
Posts: 112
|
I am aghast at the paucity of documentation of the JMSAdmin tool. The definition of administration objects using this tool seems consceptually obvious, but alas lacks clarity for the not-so-straight-forward case.
I have come across the following from a document on the IBM site:
def qcf(SampleQCF) qmgr(QMGR) tran(client) chan(SYSTEM.DEF.SVRCONN) +
host(localhost) port(1414)
What do the tran, host, port and the chan attributes really mean?
Are these suppose to represent connection to the MQ server instance?
Are there combination of these attributes that are invalid?
I just tried defining the following
def qcf(TSU_QCF) qmgr(DNLU0002STSU2) host(HOSTNAME.SYSTEMS.UK.COMP) port(15110)
where my queue manager runs on HOSTNAME.SYSTEMS.UK.COMP and listens on port 15110, but got the following error;
Unable to create a valid object, please check the parameters supplied
Invalid property in this context: Client-bindings attribute clash
I thought the whole point of admin object was to independently provide connection to a resource on the network. Isn't it?
Thankx |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Apr 12, 2006 7:03 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
def"ine" q"ueue"c"onnection"f"actory"(name) q"ueue"m"ana"g"e"r"(name) tran"sport"(client/server) host(name) chan"nel"(name) port(number).
Client transport requires hostname, channel name, port number.
Server transport requires qmgr name.
The point of an admin object is to provide the connection information necessary for a particular resource to the application in a standard way that abstracts the application from having to know the connection information.
That doesn't mean that the JNDI interface will figure out missing connection information for you.
The JMSAdmin application is documented in the "Using Java" manual.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| lohitashwa |
| Posted: Tue May 23, 2006 9:02 pm Post subject: |
|
|
Newbie
Joined: 05 May 2005
Posts: 5
|
Hi,
The parameters host, port and channel are valid only when the TranportType attribute is set to "CLIENT". When you set the transport type to "CLIENT" then the connection to the queue manager would be established via TCP/IP.
HostName = the system on which the Queue Manager is running
Port = the port number on which the queue manager is listening (normally listener)
Channel = the server connection channel name for the queue manager
JNDI objects will not establish any kind of connections, they just hold the attributes and parameters required to establish a connection to the queue manager, its the responsibility of the application to fetch this resources from the JNDI environment and then create a connection.
More information for these attributes are defined in the "Using Java" manual book for WMQ.
Regards
Lohitashwa T |
|
| 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
|
|
|
|
