In this JMS-Application Serverintegrationthe JMS provider implements advanced JMS APIs. These APIs deliver messages to consumers within the context of an Application Server session.
Download the sample (AppServer-JMS Sample Applications) that illustrates the utility of JMS APIs, which allow Application Server Sessions to be registered with the FioranoMQ JMS Server. Messages are delivered to the consumers within the context of the Application Server Session.
Message Driven Beans
FioranoMQ integrates with most Application Servers to provide the Message Driven Bean function.
Message-Driven Beans (MDB's) are stateless, server-sided and transaction-aware components used to process asynchronous JMS messages. Introduced in EJB 2.0, message-driven beans process messages that are delivered through the Java Message Service. MDBs can receive JMS messages and process them. While a MDB is responsible for processing messages, its container automatically manages the entire environment of the component including transactions, security, resources, concurrency and message acknowledgment.
Following topics are covered in this section:
- EJB Application Server Integration
- FioranoMQ Client Logging
- Integrating FioranoMQ with J2EE Servers
- JBOSS Application Server
- ATG Dynamo Message Service
- Oracle Weblogic Application Server 9.0
- Borland Enterprise Server 5.1
- Orion Application Server
- IBM WebSphere Application Server 5.1
- IPlanet Application Server 7
- Apache Tomcat
- OC4J Application Server
- Sun GlassFish Server
- Running JMS Java Applications
- Integrating with Apache TomEE
- Integrating with Wildfly Application Server
- Integrating FioranoMQ with Apache TomEE
Overview
Content Tools
ThemeBuilder