The SleeConnectivity Example is composed by two parts: a JMX Bean to be deployed in a JBoss AS5 instance, the Java EE application which will be used to fire JAIN SLEE event to the JAIN SLEE container; and a JAIN SLEE application, to be deployed in the JAIN SLEE container, which will handle the events fired, printing information about it in the container's console.
JAIN SLEE service is simplest of all. It performs very basic actions when handling each received event:
detach from activity where the event was fired, this will allow the container to end it implicitly, since it becomes unreferenced.
log the message contained in the event, which can be seen in the container's console.
JMX Client fires events into JAIN SLEE container, using the standard SLEEConnection API.
There are two possible scenarios of client and server deployment:
- colocated
JMX Bean and JAIN SLEE run in the same JVM. In this case both parts are deployed in same JBoss AS, and no additional tools are needed.
Container class sharing
- separate
In this case JMX Client and JSLEE container run in different JVMs. The Mobicents JAIN SLEE Remote SLEE Connection Tool, which uses JCA, must be deployed in the Java EE container.
Diagram below depicts how JMX Client fires event into JSLEE:
Container class sharing