| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ Series JMS queue and Oracle MQ Adapter |
« View previous topic :: View next topic » |
| Author |
Message
|
| vennela |
 Posted: Sun Feb 02, 2003 10:47 am Post subject: MQ Series JMS queue and Oracle MQ Adapter |
 |
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
What is an MQSeries JMS queue?
I have an iSeries QMGR. I have a win2K MQ client. I can PUT/GET messages using MQBase java app from a client machine.
I am trying to get Oracle MQ Adapter to PUT/GET messages from four queues which have to be defined on the QMGR (on iSeries).
Oracle MQ Adapter (I guess) is expecting JMS messages. The Oracle MQ Series adapter uses the MQ Series JMS URI syntax for specifying queues and topics.
My question is:
If we define an MQ Queue, do we have to do anything else so that the JMS application will be able to read from the queue.
(Specifically --- on the client box where JMS app is and on the QMGR).
Thanks
-------
Venny |
|
| Back to top |
|
 |
| yaakovd |
| Posted: Sun Feb 02, 2003 12:21 pm Post subject: |
|
|
Partisan
Joined: 20 Jan 2003
Posts: 319
Location: Israel
|
We working with JMS like this:
Under WEB Logic server we have MDBs (Message Driven Bean);
In IVTSetup.bat (MQSeries/Java/bin) you can find example of definitions. You need change it according your configuration: in MQQCF (connection factory) you define type of connection - bind or client. Client connection need regular parameters: IP address, port, QMgr name,Server connection channel.
Also you define mapping of all needed MQ queues to its JNDI names.
You can define more than one connections to different QMgrs.
Running IVTSetup.bat will create .bindings file in MQSeries directory, which used by application.
In MDB deployment descriptor we define Q-s for listener and sending messages using its JNDI name from IVTSetup.
_________________
Best regards.
Yaakov
SWG, IBM Commerce, Israel |
|
| Back to top |
|
|
| vennela |
| Posted: Sun Feb 02, 2003 1:58 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Looks like I have a bit of work to do here.
| Code: |
echo def qcf(ivtQCF) > ivtsetup.scp
echo def q(ivtQ) qu(SYSTEM.DEFAULT.LOCAL.QUEUE) >> ivtsetup.scp
echo def tcf(ivtTCF) >> ivtsetup.scp
echo def t(ivtT) topic(MQJMS/PSIVT/Information) >> ivtsetup.scp |
This is what I have found in the file you have mentioned.
Can you explain what each one means here
what is ivtQCF
what is ivtsetup.scp (I guess this would be crated on running the batch file).
what is ivtQ
Where do I find details about building this file.
Thanks
-------
Venny |
|
| Back to top |
|
|
| kingdon |
| Posted: Sun Feb 02, 2003 11:48 pm Post subject: |
|
|
Acolyte
Joined: 14 Jan 2002
Posts: 63
Location: UK
|
I'm not familiar with the Oracle adapter, but if it takes our URI syntax names then it indicates that it is creating the administered objects inline, and not using JNDI. If so, then you don't need to worry about using JMSAdmin to define the queues, which is what the script you were looking at was doing.
The simplest form of the URI syntax degenerates to just the queue name (see chapter 10 of the "Using Java" manual), so that will probably be sufficient for you to provide to the adapter. And to return to your original question, no, there are no additional steps needed to allow an MQJMS application to read from a specified queue (as compared to reading with a non-JMS Java application).
Regards,
James. |
|
| Back to top |
|
|
| yaakovd |
| Posted: Mon Feb 03, 2003 1:31 am Post subject: |
|
|
Partisan
Joined: 20 Jan 2003
Posts: 319
Location: Israel
|
Look at my IVTSetup:
| Code: |
echo def qcf(MQQCF) TRAN(CLIENT) HOST(JACOBB03) PORT(5010) QMGR(FMCQM) CHANNEL(FMC.CL.TCP)> ivtsetup.scp
echo def q(START) qu(START) QMGR(FMCQM) >> ivtsetup.scp
echo def qcf(MQQCF_ADAPTORS) TRAN(CLIENT) HOST(JACOBB03) PORT(1414) QMGR(FRMT) CHANNEL(FRMT.CL.TCP)>> ivtsetup.scp
echo def q(ASN) qu(ASN) QMGR(FRMT) >> ivtsetup.scp
echo def q(SSD) qu(SSD) QMGR(FRMT) >> ivtsetup.scp
echo def q(ORDER_EDI) qu(ORDER_EDI) QMGR(FRMT) >> ivtsetup.scp
echo def q(ORDER_EC) qu(ORDER_EC) QMGR(FRMT) >> ivtsetup.scp
echo def q(ORDER_UPDATE) qu(ORDER_UPDATE) QMGR(FRMT) >> ivtsetup.scp
echo def q(ORDER_IN) qu(ORDER_IN) QMGR(FRMT) >> ivtsetup.scp
echo def q(ORDER_XML) qu(ORDER_XML) QMGR(FRMT) >> ivtsetup.scp
echo end >> ivtsetup.scp
|
By my expirience always better to work as client (at least with WEB Logic).
Here I defined 2 client connections for 2 QMgrs:
qcf(MQQCF) - JNDI name of connection factory
TRAN(CLIENT) or TRAN(BIND) type of connection (you can use BIND only locally and for one of QMgrs)
HOST(JACOBB03) or HOST(10.15.228.45) computer name or IP address
QMGR(FMCQM) - Queue manager name
CHANNEL(FMC.CL.TCP) - server connection channel on your QMgr
q(START) - JNDI Q name that can be different from real Q
qu(ASN) - real MQ queue
QMGR(FRMT) - QMgr name
in first line use "> ivtsetup.scp" and in others ">> ivtsetup.scp".
See also alternative way suggested by kingdon
_________________
Best regards.
Yaakov
SWG, IBM Commerce, Israel |
|
| 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
|
|
|
|
