JMS is not a container-related API per se. It is a standard Java API (http://www.jcp.org/en/jsr/detail?id=914) that deals with asynchronous messaging.
WebSphere MQ (which is completely distinct from WebSphere AS - the container) has a JMS interface, as do other commercial and free JMS compliant products. With WebSphere MQ, you can either use the JMS API or you can use WebSphere's proprietary Java API which gives you more functionality and control (at the cost of portability). If you have WebSphere MQ on z/OS, you can use either JMS or the WMQ Java API from your Java applications and can be accessed from any Java application on z/OS - including Java running under WebSphere AS, batch, CICS, IMS, etc. Even if you don't have a WMQ Server running on z/OS, I believe that you can use a Java JMS client to connect to a WMQ server (aka "queue manager") on another box. But I'm not a WMQ expert - it could be that you need to license a "client" product/feature on z/OS to enable this, so check with your friendly IBM rep for details. Decent references: http://en.wikipedia.org/wiki/IBM_WebSphere_MQ http://en.wikipedia.org/wiki/Java_Message_Service Kirk Wolf Dovetailed Technologies http://dovetail.com ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
