MQSeries on WebSphere?

[michele]

Hi all... can anyone tells me which version of WebSphere Application Server
I need to be able to connect to MQSeries?
Which kind of connectors there are for MQ?
Can I send and receive messages from a servlet or a EJB?
Where can I find information about this?
thanks for help
mik

[aala...@my-deja.com]

If you have all the correct jar files and classpaths set , you
shouldn't have any trouble making MQSeries calls from both Servlets and
EJBs.
I have been using WAS3.0.2 Advanced, with MQSeries 5.1 ( NT platform)
from Servlets, EJBs,nad Beans ,using mqbinds as well as IBM's
implementation of JMS without any trouble.

-Ahmed Alazzawe

In article <8k23i5$e46$1...@news.software.ibm.com>,

Sent via Deja.com http://www.deja.com/
Before you buy.

[michele]

Thanks for the information...
but I'd like to understand better if you used a WebSphere feature or an
MQSeries feature...
I think you can use Mq from your servlet/EJB in two ways:
1) using the JMS implementation of MQ
2) using the MQSeries Connector
In the first case you use an MQSeries feature and you are running the MQ
Java client outside WebSphere and on the same machine where you have
WebSphere.
In the second case, you use this connector, that should be an EJB that you
deploy on WebSphere. So in this case you are actually using WebSphere to
connect to your MQSeries channels, queue, etc.
Am I right?
Did you use the mqccf.jar package (from VisualAge Java Enterprise) in your
project?
Thanks for help
miki

<aala...@my-deja.com> wrote in message news:8k2dec$6n3$1...@nnrp1.deja.com...

[aala...@my-deja.com]

I haven't used the enterprise version of Websphere that comes with the
MQSeries code generating utility. Hopefully I will use soon.

However, I have been developing SessionBeans that use JMS, as well as
mqbinds, internally to access MQSeries. This can also be done with
Servlets.

As far as using the Client or Server mode, here is how it works:

1. Server : To use it , your code has to run on the same machine where
MQSeries manager resides that you are connecting to. So , Servlets and
EJBs with their AppServers must be on the same machine. You can also
call EJBs on another machine , as long as they are where MQSeries is.

2. Clients : Anywhere , where you have the MQClients installed ( with
Java jars ) and the proper channels defined to connect to n MQ Manager.
Remember that each mqclient is an TCPIP connection itself and may not
be the most effecient way to connect , if your app uses heavy volumes
of connections to a server.

I hope that was usefull info.

-Ahmed Alazzawe

In article <8k44f1$mf6$1...@news.software.ibm.com>,

[Bill Hines]

There is supposed to be a new product, MQEveryplace, that is some sort of
servlet. Do you have any knowledge of it? We are stuck with the same
decisions about how to do MQ/WAS. Install MQ Server on the WAS box?
Install MQ Client? Is there any set of guidelines for this?

In article <8k58aj$196$1...@nnrp1.deja.com>, aala...@my-deja.com says...

[michele]

I think you have to install the MQServer on the same box as WAS...
Maybe it could be of any help the following tutorial on MQ+VAJ using
WSTestEnvironment:
http://www7.software.ibm.com/vad.nsf/Data/Document3953
keep posting if you find anything interesting
miki

"Bill Hines" <bhi...@hersheys.com> wrote in message
news:MPG.13dd1e63e...@news.software.ibm.com...

[aala...@my-deja.com]

The way MQSeries works , that is with or without Websphere , is as
following:

1. If you are running the "SERVER" mode ;i.e. using any of the
mqbind,JMS or C/C++ Server libs , Then your code has to run on the same
machine where the MQManager resides that you are connecting to. So , I
guess in Websphere's terms , it means the the AppServer that runs the
Server code , like Servlets, EJBs etc... has to be on the same machine
as the one that has the MQManager running.

2. As a client , internally MQSeries uses RPC/IIOP protocol , then
your "CLIENT" code , again can be mqbind, JMS, C/C++ , can be anywhere
on the network where the QManager, which you are connecting to , is
reachable.

Webpshere has MQSeries enabling tools , but I would be surprised to
find out that they actually changed the way MQSeries works,specially
since MQSeries can still be deployed independently without Websphere,
and therefore the guidelines above should still apply.

-Ahmed Alazzawe

In article <8l1lq5$er4$1...@news.software.ibm.com>,