Posted: Mon Jan 10, 2005 11:09 am Post subject: quick question on WAS embedded messaging
Acolyte
Joined: 21 Oct 2004 Posts: 50
We have set up WAS 5.1 and used WMQ 5.3 server as the JMS provider also.
However, it has been asked if we can use embedded messaging on a development server instead of using the full blown WMQ 5.3 server version.
How difficult would it be to use this instead? Is it simply a matter of re-adding the queues (jndi) under the Websphere JMS provider as opposed to the Websphere MQ JMS provider and turning on the embedded server in the server components screen in the admin console?
also, how does embedded messaging handle the the Inbound/Oubound queues. What I mean is the queues the MDB is listening to (the messages being sent to it are from a legacy as400 system running native MQ)
and the remote queue definition to send the messages back? How are they set up in the embedded version.
All this had been achieved in using the full version but like I said I just needed a quick answer to see what Im getting myself into before setting up a Dev box.
Remember the embedded messaging server is a toned down version of MQ. NO COMMUNICATION with the outside.
So your AS400 will not be able to send any data into WAS.
What it is good for though is creating the right "pipes" for asynchronous communication within the WAS.
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