Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Introduction to EIS Projects (ELUG)"
m (New page: <div style="float:right;border:1px solid #000000;padding:5px">__TOC__ Related Topics</div> This section provides an overview...) |
m |
||
| Line 1: | Line 1: | ||
<div style="float:right;border:1px solid #000000;padding:5px">__TOC__ | <div style="float:right;border:1px solid #000000;padding:5px">__TOC__ | ||
[[Special:Whatlinkshere/Introduction to EIS Projects (ELUG)|Related Topics]]</div> | [[Special:Whatlinkshere/Introduction to EIS Projects (ELUG)|Related Topics]]</div> | ||
| − | |||
| − | |||
This section provides an overview of EIS projects and their components. | This section provides an overview of EIS projects and their components. | ||
| Line 10: | Line 8: | ||
==EIS Project Concepts== | ==EIS Project Concepts== | ||
| − | |||
Use an EIS project for transactional persistence of Java objects to a ''nonrelational'' data source accessed using a Java EE Connector Architecture (JCA) adapter and EIS records. | Use an EIS project for transactional persistence of Java objects to a ''nonrelational'' data source accessed using a Java EE Connector Architecture (JCA) adapter and EIS records. | ||
| Line 22: | Line 19: | ||
We recommend using EIS projects to integrate EclipseLink with a legacy or nonrelational data source. Other methods of accessing EIS data sources include: | We recommend using EIS projects to integrate EclipseLink with a legacy or nonrelational data source. Other methods of accessing EIS data sources include: | ||
| − | |||
* Using a specialized JDBC driver that allows connecting to an EIS system as if it were a relational database. You could use a EclipseLink relational project with these drivers (see [[Introduction%20to%20Relational%20Projects%20(ELUG)|Introduction to Relational Projects]]). | * Using a specialized JDBC driver that allows connecting to an EIS system as if it were a relational database. You could use a EclipseLink relational project with these drivers (see [[Introduction%20to%20Relational%20Projects%20(ELUG)|Introduction to Relational Projects]]). | ||
* Linking to or integrating with the EIS data from a relational database, such as Oracle Database. | * Linking to or integrating with the EIS data from a relational database, such as Oracle Database. | ||
| Line 47: | Line 43: | ||
Data Source | Data Source | ||
| headers="r2c1-t2 r1c2-t2" align="left" | | | headers="r2c1-t2 r1c2-t2" align="left" | | ||
| − | For more information, see | + | For more information, see [[Introduction%20to%20Data%20Access%20(ELUG)#EISLogin|EISLogin]] and [[Introduction%20to%20Data%20Access%20(ELUG)#EIS Platforms|EIS Platforms]]. |
| − | + | ||
| − | + | ||
|- align="left" valign="top" | |- align="left" valign="top" | ||
| id="r3c1-t2" headers="r1c1-t2" align="left" | | | id="r3c1-t2" headers="r1c1-t2" align="left" | | ||
| Line 59: | Line 53: | ||
Mappings | Mappings | ||
| headers="r4c1-t2 r1c2-t2" align="left" | | | headers="r4c1-t2 r1c2-t2" align="left" | | ||
| − | For more information, see | + | For more information, see [[EIS Mappings (ELUG)]]. |
| − | + | ||
|} | |} | ||
| Line 80: | Line 73: | ||
[[Category: Draft]] | [[Category: Draft]] | ||
[[Category: Concept]] | [[Category: Concept]] | ||
| + | [[Category: EIS]] | ||
Revision as of 11:32, 17 December 2007
Contents
This section provides an overview of EIS projects and their components.
For information on project concepts and features common to more than one type of EclipseLink projects, see Introduction to Projects.
EIS Project Concepts
Use an EIS project for transactional persistence of Java objects to a nonrelational data source accessed using a Java EE Connector Architecture (JCA) adapter and EIS records.
JCA provides a Common Client Interface (CCI) API to access nonrelational EIS. This provides a similar interface to nonrelational data sources as JDBC provides for relational data sources. This API defines several types of nonrelational record types including mapped and indexed. XML has emerged as the standard format to exchange data, and most leading JCA adapter providers have extended the CCI API to define XML data records.
To use a JCA adapter with EclipseLink EIS, the JCA adapter must support the JCA CCI interface. At run time, your JCA adapter and the Java connector.jar file (that contains the javax.resource.cci and javax.resource.spi interfaces that EclipseLink EIS uses) must be on your application or application server classpath.
If you are using Workbench, you must add your JCA adapter to the Workbench classpath. By default, Workbench updates its classpath to include the Java 1.5.n connector.jar file from <ECLIPSELINK_HOME>/lib/java/api. If this version of the connector.jar file is incompatible with your environment, edit the workbench.cmd or workbench.sh file in <ECLIPSELINK_HOME>/bin to change the path to this file. For more information, see Configuring the Workbench Environment.
EIS includes legacy data sources, enterprise applications, legacy applications, and other information systems. These systems include such sources as Custormer Information Control System (CICS), Virtual Storage Access Method (VSAM), Information Management System (IMS), ADABASE database, and flat files.
We recommend using EIS projects to integrate EclipseLink with a legacy or nonrelational data source. Other methods of accessing EIS data sources include:
- Using a specialized JDBC driver that allows connecting to an EIS system as if it were a relational database. You could use a EclipseLink relational project with these drivers (see Introduction to Relational Projects).
- Linking to or integrating with the EIS data from a relational database, such as Oracle Database.
- Using a proprietary API to access the EIS system. In this case it may be possible to wrap the API with a JCA CCI interface to allow usage with a EclipseLink EIS project.
EclipseLink provides support for mapping Java objects to EIS mapped, indexed, and XML records, through JCA, using the EclipseLink mappings described in EIS Mappings (ELUG).
You configure a EclipseLink EIS descriptor to use a particular EIS record format (see onfiguring Record Format). EclipseLink EIS mappings use their EIS descriptor's record format configuration to determine how to map their Java objects to EIS records.
If you use XML records, the EclipseLink runtime performs XML data conversion based on one or more XML schemas. In an EIS project that uses XML records, Workbench directly references schemas in the deployment XML, and exports mappings configured with respect to the schemas you specify. For information on how to use Workbench with XML schemas, see Using XML Schemas. For information on how EclipseLink supports XML namespaces, see XML Namespaces Overview.
This table describes the components of an EIS project.
EIS Project Components
| Component | Supported Types |
|---|---|
|
Data Source |
For more information, see EISLogin and EIS Platforms. |
|
Descriptors |
For more information, see EIS Descriptor Concepts. |
|
Mappings |
For more information, see EIS Mappings (ELUG). |
You can create an EIS project with Workbench for use with EIS XML records (see Creating an EIS Project with XML Records) or you can build an EIS project in Java for use with any supported EIS record type (see Creating an EIS Project with Indexed or Mapped Records).
In an EIS project, your EIS interactions (see Enterprise Information System (EIS) Interactions) can make full use of EclipseLink queries (see Introduction to EclipseLink Queries). However, you cannot use EclipseLink expressions with EIS: in an EIS project, interactions replace expressions.