Abstract
The open and standardized nature of J2EE makes it a good choice to create and deploy added-value services in a dynamic way. However the main challenge when integrating telecom services on a J2EE environment has been to fit the asynchronous character of the networks with the mainly synchronous models supported at the platform level. Usually this integration required proprietary solutions, introducing architectural breakpoints in the form of gateway-like artifacts, bridging the triggers from the network into the J2EE space. Those bridges introduce weaknesses in the system, as they often need a standalone development, deployment and monitoring model while requiring special considerations when distributing and scaling on a clustered system.
Two technologies open new perspectives for the deployment of network services on Java :
- Java Connector Architecture 1.5, which is included in J2EE 1.4
- JAIN SLEE 1.0, which offers an alternative application server solution
Java Connector Architecture 1.5
JCA 1.5 introduces support for full-duplex communication at the adaptor level, which enables network elements to be directly integrated with the application server. The possibility to use resources of the application server for connector specific tasks eliminates static distribution of resources and increases the manageability and robustness of the system, while the generalization of message types at the message driven bean level means that for the first time, J2EE platforms are capable of natively accepting triggers from the network and respond to them accordingly.
JAIN Service Logic Execution Environment 1.0
In the network services and control layer, propietary solutions reign, as Java had yet to prove its strenghts in environments where 'real time' is the keyword. With the advent of the JAIN Service Logic Execution Environment 1.0 (JAIN SLEE) specification, this is not necessarily so. Optimized for high-throughput and low latency, offering a standard component model and designed from the ground up for efficient and flexible asynchronous logic, there is now a standard Java application server which can be used for many of the basic network services. So from now on, operators can choose a standard solution to develop and deploy network services, making use of the large Java developer community without having to make sacrifices in performance or elegance.
In our session we will highlight the features of these technologies that make them suitable for the telecom domain and how they can interoperate and work in a complementary fashion. We will also present our vision on how Java is there to gradually replace legacy proprietary solutions.
Date and Time
Audience
<Novice> J2EE background is desired.
Speaker(s)
Interesting Links
