Skip to main content


developerWorks  >  SOA and Web services  >

From Web interfaces to native code

A J2EE Connector Architecture white paper for basic resource adaptation including non-Java programming interfaces

developerWorks

Level: Intermediate

Contributors: IBM

19 Apr 2007

This white paper details the basics of implementing Java™ 2 Platform, Enterprise Edition (J2EE) Connector Architecture (JCA) with managed connections and inbound resource adaptation. It also describes two different means to access and drive native instrumentation services: the Java Native Interface (JNI) and a Surrogate Process/Inter-Process Communication (IPC).

The demand for Web-driven and automated resource management is constantly increasing. Designs vary, but the common theme among them is Service-Oriented Architecture (SOA). It provides the benefit of being a modular, reusable, object-oriented division of responsibility among the various components that provide access to manageable resources.

This white paper takes a comprehensive look at creating such a modular system using J2EE technology. Learn about the employment of various types of Enterprise JavaBeans (EJB) components that enable rapid development and portable deployment of Web applications and Web services. And examine the use of a variety of other technologies, including the JNI and IPC.

DescriptionDateAccess method
From Web interfaces to native code: A J2EE Connector Architecture white paper for basic resource adaptation including non-Java programming interfaces February 2007PDF


Back to top


Document options

Document options requiring JavaScript are not displayed

Discuss


My developerWorks needs you!

Connect to your technical community