Friday, February 22, 2008

Benefits of EJB Technology

Introduction-The Enterprise JavaBeans architecture supports server components. Server components are application components that run in an application server such as CICS. Unlike desktop components, they do not have a visual element and the container they run in is not visual.

Server components written to the Enterprise JavaBeans specification are known as enterprise beans. They are portable across any EJB-compliant application server.Some of the benefits of using enterprise beans are:

Component portability:-The EJB architecture provides a simple, elegant component container model. Java™ server components can be developed once and deployed in any EJB-compliant server.

Architecture independence:The EJB architecture is independent of any specific platform, proprietary protocol, or middleware infrastructure. Applications developed for one platform can be redeployed on other platforms.

Developer productivity:The EJB architecture improves the productivity of application developers by standardizing and automating the use of complex infrastructure services such as transaction management and security checking. Developers can create complex applications by focusing on business logic rather than environmental and transactional issues.

Customization:-Enterprise bean applications can be customized without access to the source code. Application behaviour and runtime settings are defined through attributes that can be changed when the enterprise bean is deployed.

Multitier technology:-The EJB architecture overlays existing infrastructure services.Versatility and scalabilityThe EJB architecture can be used for small-scale or large-scale business transactions. As processing requirements grow, the enterprise beans can be migrated to more powerful operating environments.

In addition to these general benefits of using EJB technology, there are specific benefits of using enterprise beans with CICS®. For example:

Superior workload management:You can balance client connections across a set of cloned listener regions.You can use CICSPlex SM or the CICS distributed routing program to balance OTS transactions across a set of cloned AORs.

Superior transaction management:Enterprise beans in a CICS EJB server benefit from CICS transaction management services—for example:
• Shunting•
System log management
• Performance optimizations
• Runaway detection
• Deadlock detection
• TCLASS management
• Monitoring and statistics

Access to CICS resourcesYou can, for example, use JCICS or the CCI Connector for CICS TS to build enterprise beans that make use of the power of existing (non-Java) CICS programs. The developer of a Java client application can use your server components to access CICS—without needing to know anything about CICS programming.

2 comments:

Unknown said...

Hi Rahul!!!
This is an excellent article. One thing I like is; these are very basic concepts which a faculty must know. In stead of refering to publishers book they can get it on this tech blog site. This is just a click away.
Excellent effort!!!

I am sure all will like to study the articles and get the benefit; which in turn will help the company to grow....

Regards,
Debapritam Mishra

Shanthi said...

The article "EJB and RMI" is explained with simple example to understand the concept.

The article can provide much better example with serialization (If the articles are meant for faculties).

I would like to suggest that whenever we develop RMI or EJB applications, it is better to use packages to avoid class file problems.


The article does not provide the clear picture of the differences between EJB and RMI. Is it the comparison for client program?(Session bean is taken as an example)

Shanthi Ramabhadran
CAH(Aptech Ghatkopar)