Loading
Understanding EclipseLink, 2.4
  Go To Table Of Contents
Contents
 Search
Other Searches
 PDF
PDF
Comments
Comments

Integrating with an Application Server

This section describes concepts unique to application server integration, including the following:

Software Requirements

To run EclipseLink applications within a Java EE container, your system must meet the following software requirements:

  • An application server or Java EE container

  • XML parser

  • A JDBC driver configured to connect with your local database system (for more information, see your database administration documentation);

  • Any of the following:

    • Any Java environment that is compatible with the Sun JDK 1.6 or later;

    • A command-line JVM executable (such as java.exe or jre.exe).

Setting Security Permissions

By default, when you run applications in a JVM configured with a nondefault java.lang.SecurityManager, the runtime environment executes certain internal functions by executing a PrivilegedAction with java.security.AccessController method doPrivileged. This ensures that you do not need to grant many permissions to EclipseLink for it to perform its most common operations. You need only grant certain permissions depending on the types of optional features you use.

If you run EclipseLink-enabled applications in a JVM without a nondefault SecurityManager, you do not need to set any permissions. For more information, see "Using Oracle EclipseLink with the Oracle Database" in Solutions Guide for EclipseLink.

Migrating Applications to the EclipseLink Persistence Manager

You can configure an application server to use EclipseLink as the persistence manager. You can use only one persistence manager for all of the entities with container-managed persistence in a JAR file.

Comments powered by Disqus