03-04 C-485 Part of J2EE, the Java Message Service application program interface from Sun Microsystems defines a standard programmatic interface from Java programs to standard middleware message facilities. Often the JMS provider receiving the message acts as a broker or router, delivering messages of different types from one Java application to another.

• Using Connect JMS rules (Rule-Connect-JMS rule type), a Process Commander application, as a client, can act as a JMS producer (by sending a request message to an external system) and JMS consumer (by accepting a response).
• Using Service JMS rules (Rule-Service-JMS), a Process Commander application can deliver services to an external system through JMS facilities.

Process Commander supports both point-to-point JMS communications and publish/subscribe operations. The latter type usually operate asynchronously, with no response or acknowledgment returned to the consumer client system. These facilities require that the application server hosting Process Commander be J2EE compliant. Accordingly, JMS connectors and services operate on IBM WebSphere implementations and Oracle WebLogic implementations, but not on Apache Tomcat implementations.

When Process Commander is deployed as an enterprise application in a J2EE application server, JMS facilities work with message driven beans.

	J2EE, message driven beans
	About Connect JMS rules About JMS Listener data instances About JMS Producer Model data instances About Service JMS Rules Connect-JMS method

Definitions — J