Implementing a JSLEE Resource Adaptor - A quick-starter's guide

How to create a Resource Adaptor for JAIN™ SLEE based environments - A quick-starter's guide.

The Open Source project Mobicents aims to implement a JAIN™ SLEE (JSLEE) application server capable to compete with commercial products - in the long run. At this stage, Mobicents is already quite a stable environment for first applications in the domain of JSLEE.

Beside the pure applications in a JSLEE environment there is another zone - the zone of Resouce Adaptors. These adaptors integrate external resources into JSLEE. It does not matter whether these resources are synchron, asynchron, local, remote, ... However, how is this done? How to integrate these resources via Resource Adaptors? That was one of my questions as well. This thought is the fundament for this source example and the associated document. The example explains how to integrate a very simple TCP/IP based protocol into the JSLEE environment, explains the dependencies, the deployment, the build process and introduces a tiny, little service to demonstrate the Resource Adaptor.

The described project is also available in the Mobicents CVS repository. The modul-name is "mobicents-examples".

The index:

• Introduction
• What is JAIN™ SLEE?
• What is Mobicents?
• What is a Resource Adaptor?
• The Structure of a RA
• The RAFrame Example
• The structure of the RAFrame Example
• The Protocol
• The Protocol Stack
• Testing the Protocol Stack
• Deployment Descriptors
• The RAFrame Events
• The RA Type RAFrame
• The RA Type's Activity and Activity Context
• The RA Type's offering for Sbbs
• The RA - Structure and Methods
  • entityCreated() and entityActivated()
  • onEvent()
  • getActivity() and ActivityEnded()
• RA Deployment Descriptors
• Building the RA
• Deploying the RA
  • The manual way
  • The automated way
• BounceSbb - utilizing the RA
• The Sbb's methods
  • setSbbContext()
  • Event handling
• Sbb Deployment Descriptor
• Building the Sbb
• Deploying the Sbb
  • The manual way
  • The automated way
• Testing the installation
• Understand what happens
• What's next?