Browse Prior Art Database

JMS Message Driven Bean Simulator

IP.com Disclosure Number: IPCOM000015292D
Original Publication Date: 2001-Nov-08
Included in the Prior Art Database: 2003-Jun-20
Document File: 2 page(s) / 53K

Publishing Venue

IBM

Abstract

This Software solution simulates the message driven bean functionality that is currently not available in WebSphere on 390, but will be required for the J2EE v1.3 specification. This invention enables software programs to start session EJBs by placing messages onto message queues, prior to having the J2EE v1.3 compliant application server runtimes.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 85% of the total text.

Page 1 of 2

JMS Message Driven Bean Simulator

    This Software solution simulates the message driven bean functionality that is currently not available in WebSphere on 390, but will be required for the J2EE v1.3 specification. This invention enables software programs to start session EJBs by placing messages onto message queues, prior to having the J2EE v1.3 compliant application server runtimes.

    The problem is solved by incorporating the MQSeries triggering mechanism into the application to perform a remote method invocation on a session EJB when a message is put on a queue by a servlet running in the Web Server. This message causes the EJB to start and retrieve (consume) messages off of the application queue in a manner that is similar to the message driven bean functionality that is described in the J2EE v1.3 specification. The significant mechanism here is the triggering event which causes the trigger monitor to make a remote method invocation which essentially "activates" or starts the session EJB, simulating the message driven bean functionality outside of the WebSphere Application server runtime. All values (JNDI lookup, ejb refs etc.) used to prepare for the remote method invocation are cached in the trigger monitor at monitor start up time. See Diagram:

JM S W orkload for S ystem Test

(trigger queue on E VE R Y)

QMGR

Startup Servlet

se n d (s)

re ce ive (s)

Trig g er Monitor

- JNDI lookup, (c a c h e v a lu es ) - lo o p
- g etM s g
-d riv e rem o te method

P riceC hange...