This file contains the Coherence integration classes for WebLogic. The file is installed regardless of whether you install Coherence. The default installation directory for this file is:
The main development and run-time library for Coherence. The default installation directory for this file is
oracle\Middleware\coherence_3.5\lib. The JAR contains a set of default XML configuration files that provide a default setup that allows Coherence to be used out-of-box with minimal changes. Among the several default configuration files, the most important in this book are coherence-cache-config.xml and tangosol-coherence.xml.
A group of Coherence nodes that share a group address which allows them to communicate. Coherence clusters consist of nodes formed by applications, modules, or application servers (WebLogic Server instances or cache servers). There can be many data caches within a single Coherence node.
This file is used to specify the various types of caches which can be used within a cluster. This file is typically referred to as the cache configuration deployment descriptor. The DTD for this file is
This JAR contains the Coherence integration for EclipseLink. This JAR is required on the classpath if you are integrating your EclipseLink JPA application with Oracle Coherence.
Contains a native plugin to WebLogic Server's HTTP Session Management interface. The WAR file provides the necessary support files to enable HTTP session management for applications running on WebLogic Server. The session state can be managed in the various caching topologies available in Coherence. This WAR is installed in the
Any application or server process that is running the Coherence software is called a Coherence node.
A single server process (WLS instance or cache server), WLS application (EAR), or application module (Web application) can be a Coherence node.
There can be many data caches within a single Coherence node.
This JAR contains the EclipseLink persistence framework. EclipseLink supports virtually any type of data source, including relational databases, XML, or EIS systems.
Provides the configuration for the Coherence caches used by the Coherence*Web SPI. This file is located inside the
coherence-web-spi.war file under the
WEB-INF\classes directory. Any cache configuration change should defined in
session-cache-config.xml, and then repackaged inside
This files provides operational and run-time settings and is used to create and configure cluster, communication, and data management services. This file is typically referred to as the operational deployment descriptor. The DTD for this file is the
You can override the settings in the default
tangosol-coherence.xml file by creating a
tangosol-coherence-override.xml file and placing it in the classpath at run time. The override file and the operational deployment descriptor have the same structure, however all of the elements in the override file are optional. The override file includes only the elements that are being changed. Any missing elements are loaded from the
The WebLogic-specific deployment descriptor file that defines how named resources in the
web.xml file are mapped to resources residing elsewhere in WebLogic Server. This file is also used to define JSP and HTTP session attributes.
The WebLogic Server-specific deployment descriptor extension for the
application.xml deployment descriptor from Sun Microsystems. This is where you configure features such as shared Java EE libraries referenced in the application and EJB caching. The file is located in the
META-INF subdirectory of the application archive.
A group of WebLogic Server instances that work to provide scalability and high-availability for applications.