Skip to main content

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.

Jump to: navigation, search

Configuring an EIS Project (ELUG)

Revision as of 09:31, 27 November 2007 by Rick.sapir.oracle.com (Talk | contribs) (New page: <div style="float:right;border:1px solid #000000;padding:5px">__TOC__ Related Topics</div> This section describes the various ...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


This section describes the various components that you must configure in order to use an EIS project.

For information on how to configure EclipseLink project options common to two or more project types, see Configuring a Project.

Configurable Options for EIS Projects lists the configurable options for EIS projects.


Introduction to EIS Project Configuration

This table lists the configurable options for EIS projects.


Configurable Options for EIS Projects

Option to Configure EclipseLink Workbench Java

Project save location (see Configuring Project Save Location)

Supported

Unsupported

Project classpath (see Configuring Project Classpath)

Supported

Unsupported

Comments (see Configuring Project Comments)

Supported

Unsupported

Method or direct field access (see Configuring Method or Direct Field Access at the Project Level)

Supported

Unsupported

Default descriptor advanced properties (see Configuring Default Descriptor Advanced Properties)

Supported

Unsupported

Existence checking (see Configuring Existence Checking at the Project Level)

Supported

Supported

Project deployment XML options (see Configuring Project Deployment XML Options|)

Supported

Unsupported

Model Java source code options (see Configuring Model Java Source Code Options)

Supported

Unsupported

EIS data source platform (see Configuring EIS Data Source Platform at the Project Level)

Supported

Supported

EIS connection specification options (see Configuring EIS Connection Specification Options at the Project Level)

Supported

Supported

XML parser platform (see Configuring XML Parser Platform)

Unsupported

Supported

Importing an XML schema (see How to Import an XML Schema)

Supported

Unsupported.

XML schema namespace (see How to Configure XML Schema Namespace)

Supported

Supported

Cache type and size (see Configuring Cache Type and Size at the Project Level)

Supported

Supported

Cache isolation (see Configuring Cache Isolation at the Project Level)

Supported

Supported

Cache coordination change propagation (see Configuring Cache Coordination Change Propagation at the Project Level)

Supported

Supported

Cache expiration (see Configuring Cache Expiration at the Project Level)

Supported

Unsupported


For more information, see Introduction to EIS Projects.


Configuring EIS Data Source Platform at the Project Level

For each EIS project, you must specify one of the following JCA data source platforms that you will be using:

  • Oracle AQ
  • Attunity Connect
  • IBM MQSeries

This platform configuration is overridden by the session login, if configured.

For more information, see the following:


How to Configure EIS Data Source Platform at the Project Level Using Workbench

To specify the data source platform of an EIS project, use this procedure:

  1. Select an EIS project object in the Navigator.
  2. Select the Connection Specifications tab in the Editor. The Connection Specifications tab appears.
  3. Select the Connection tab. The Connection tab appears.
    Connection Tab, Platform Option
    Connection Tab, Platform Option

Complete the fields on the Connection tab.

Select the EIS platform for this project from the list of options. For more information, see Data Source Platform Types.


Configuring EIS Connection Specification Options at the Project Level

You can configure connection information at the project level for an EIS application. This information is stored in the project.xml file. The EclipseLink runtime uses this information as its deployment login: whenever your EIS application performs a persistence operation when deployed in a Java EE application server.

This connection configuration is overridden by the connection information at the session level, if configured. For more information about session level configuration, see Configuring EIS Connection Specification Options at the Session Level.


How to Configure EIS Connection Specification Options at the Project Level Using Workbench

To specify the connection information for an EIS project, use this procedure.

  1. Select an EIS project object in the Navigator.
  2. Select the Connection Specifications tab in the Editor. The Connection Specifications tab appears.
  3. Select the Connection tab. The Connection tab appears.
    Connection Tab, Connection Specification Options
    Connection Tab, Connection Specification Options

Complete the fields on the Connection tab.

Use this table to enter data in the following fields to configure the connection specification options:


Field Description
Connection Specification Class

Specify the appropriate connection specification class for the selected Platform. Click Browse to choose from all the classes in the EclipseLink class path. (example: if Platform is org.eclipse.persistence.eis.aq.AQPlatform, use org.eclipse.persistence.eis.aq.AQEISConnectionSpec). For more information on platform configuration, see Configuring an EIS Data Source Platform at the Session Level.

Connection Factory URL Specify the appropriate connection factory URL (as a Java EE JNDI name) for the selected Connection Specification Class (example: java:comp/env/eis/attuntiy).
Username Specify the name required to log in to the data source.
Password

Specify the password required to log in to the data source. Note: When exporting Java source and deployment XML (see Exporting Project Information), Workbench writes the database password (if applicable) using JCE encryption (when using JDK 1.4). For information on how to specify password encryption options, see Configuring Password Encryption.



Copyright Statement

Back to the top