Prior to the introduction of the J2EE Architecture there was no standardized method to integrate enterprise systems with legacy data. However, with the advent of JCA, and using Attachmate's Java 2 Enterprise Edition (J2EE)-compliant resource adapter, you are able to access host data and integrate with supported application servers.
A resource adapter is a system-level software driver used by an application server or client to connect to an enterprise system. A resource adapter plays a central role in the integration and connectivity between your enterprise system and an application server it is the point of contact between application components, application servers, and enterprise information systems.
The Attachmate J2EE resource adapter is written to the Sun J2EE Connector Architecture Specification, version 1.0, and implements the JCA Common Client Interface (CCI). CCI is a set of interfaces, which provides a framework for basic interaction with resource adapters. Because both the application servers and the Attachmate J2EE resource adapter adhere to the industry-standard J2EE architecture, you are ensured of complete compatibility between the supported application servers and your enterprise system.
Attachmate J2EE support uses the Java Naming and Directory Interface (JNDI) to deploy enterprise applications to your application server. These applications use both session Enterprise JavaBean version 1.1 (EJB) and resource adapter functionality. The session EJBs generated by Synapta Services Builder access host data through the resource adapter. J2EE session EJBs and resource adapters are managed and deployed to selected application servers through your Synapta Services Builder management component in MCS.
Synapta Services Builder J2EE support integrates IMS host systems with the following J2EE-compliant application servers:
With the management tools provided in Synapta Services Builder you can register your application servers, package your task as an application containing both session EJB and resource adapters, and then deploy it to whatever application server you are running. To access host data in your application, you can open the generated EJB in your IDE, or access the J2EE resource adapter directly.
Session EJBs are efficient and lightweight Java beans that work well in J2EE environments. When an EJB is generated a JAR file is created, along with a resource adapter RAR file as part of an enterprise application, and then deployed to your selected application server on a per task basis.
This sample illustrates how to create a web-based application that sends input to and receives output from your Synapta Services Builder for IMS task, deployed to a WebLogic app server as a session EJB generated from MCS.
This sample illustrates how to create a web-based application that sends input to and receives output from your Synapta Services Builder for IMS task, deployed to a WebLogic app server as a J2EE resource adapter generated from MCS.
|Using Tasks in Your Applications|
|Registering Application Servers|
|Packaging J2EE Session EJBs|
|Deploying J2EE Session EJBs|
|Integrating your J2EE Session EJB with an Application|
|Accessing Data with the Attachmate J2EE Resource Adapter|
|How to Provide Tasks in a J2EE App Server|