Skip Headers
Oracle® Coherence User's Guide for Oracle Coherence*Web
Release 3.4.2

Part Number E14408-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

1 Introduction

This chapter provides general information about Coherence*Web. It describes what Coherence*Web is, what containers it is supported on, and provides a road map for the deployment decisions you should consider based on your environment.

1.1 What is Coherence*Web?

Coherence*Web is an HTTP session management module dedicated to managing session state in clustered environments. Built on top of Oracle Coherence, Coherence*Web:

Using Coherence*Web with WebLogic Server and WebLogic Portal

Starting with Coherence 3.4.2, Coherence*Web integrates with WebLogic Server 10.3 and WebLogic Portal 10.3 using the native WebLogic session management SPI. The result of this tighter integration with WebLogic is simplified installation and deployment that no longer requires application instrumentation (using the WebInstaller).

Coherence*Web and other Application Servers

For earlier versions of WebLogic Server and other third-party application servers, Coherence*Web provides a generic installer that transparently instruments your Web applications.

Chapter 3, "Installing Coherence*Web on Other Application Servers," describes the implementation of Coherence*Web with WebInstaller in more detail.

1.2 Supported Web Containers

Table 1-1 summarizes the Web containers supported by the Coherence*Web Session Management Module. It also provides links to the information required to install Coherence*Web on them. You will notice that all of the Web containers (with the exception of Oracle WebLogic Server 10.3) share the same general installation instructions. A few, such as Oracle OC4J, Caucho, and WebLogic 10.x, require extra, container-specific steps that you must complete before starting the general installation instructions.

To install the Coherence*Web Session Management Module on WebLogic Server 10.3 and later, you can use only SPI-based installation. For instructions on installing the Management Module on WebLogic Server 10.3, see Chapter 2, "Installing Coherence*Web on the WebLogic Server 10.3.".

Note:

The value in the Server Type Alias column is used only by the Coherence*Web WebInstaller installation. The value is passed to the WebInstaller though the -server command line option.

Table 1-1 Web Containers Supported by Coherence*Web

Application Server Server Type Alias See this Installation Section

Apache Tomcat 4.1.x

Generic

"General Instructions for Installing Coherence*Web Session Management Module"

Apache Tomcat 5.0.x

Generic

"General Instructions for Installing Coherence*Web Session Management Module"

Apache Tomcat 5.5.x

Generic

"General Instructions for Installing Coherence*Web Session Management Module"

Apache Tomcat 6.0.x

Generic

"General Instructions for Installing Coherence*Web Session Management Module"

Caucho Resin 3.0.x

Resin/3.0.x

"Installing on Caucho Resin 3.0.x"

Caucho Resin 3.1.x

Resin/3.1.x

"Installing on Caucho Resin 3.1.x"

IronFlare Orion 2.0.x

Orion/2.0.x

"General Instructions for Installing Coherence*Web Session Management Module"

IBM WebSphere 5.x

WebSphere/5.x

"General Instructions for Installing Coherence*Web Session Management Module"

IBM WebSphere 6.x

WebSphere/6.x

"General Instructions for Installing Coherence*Web Session Management Module"

JBoss Application Server

Jetty/4.2.x, Jetty/5.1.x, or Generic

"General Instructions for Installing Coherence*Web Session Management Module"

Jetty 4.2.x

Jetty/4.2.x

"General Instructions for Installing Coherence*Web Session Management Module"

Jetty 5.1.x

Jetty/5.1.x

"General Instructions for Installing Coherence*Web Session Management Module"

Jetty 6.1.x

Generic

"General Instructions for Installing Coherence*Web Session Management Module"

New Atlanta ServletExec 5.0

ServletExec/5.x

"General Instructions for Installing Coherence*Web Session Management Module"

Oracle OC4J 10.1.2.x

Oracle/10.1.2.x

"Installing on Oracle OC4J 10.1.2.x"

Oracle OC4J 10.1.3.x

Oracle/10.1.3.x

"General Instructions for Installing Coherence*Web Session Management Module"

Oracle WebLogic 8.x

WebLogic/8.x

"General Instructions for Installing Coherence*Web Session Management Module"

Oracle WebLogic 9.x

WebLogic/9.x

"General Instructions for Installing Coherence*Web Session Management Module"

Oracle WebLogic 10.x

WebLogic/10.x

"Installing on Oracle WebLogic 10.x"

Oracle WebLogic 10.3 and later

NA

Only SPI-based installation is available for versions 10.3 and later. See Chapter 2, "Installing Coherence*Web on the WebLogic Server 10.3."

Sun ONE 6.x

Generic

"General Instructions for Installing Coherence*Web Session Management Module"

Sun ONE 7.x

Generic

"General Instructions for Installing Coherence*Web Session Management Module"

Sun ONE 8.x

Generic

"General Instructions for Installing Coherence*Web Session Management Module"


1.3 Installation and Deployment Road Map

This section provides a general outline of the deployment decisions you should make before you configure and install Coherence*Web. Coherence*Web is supported on a number of different application servers. The type of application server that you are deploying on determines whether you will be installing Coherence*Web using the WebLogic SPI installation or the WebInstaller. Regardless of which application server you are using, you may need to change some of the Coherence*Web configuration options to meet your particular requirements, such as packaging considerations, session model, session locking mode and deployment topology.

1.3.1 Choose your Cluster Node Isolation

Cluster node isolation refers to the number of Coherence nodes that will be created within each application server JVM and where the Coherence library is deployed. A few different isolation modes are supported.

For example: you may be deploying multiple applications to the container that require the use of the same cluster (or one coherence node); you may have multiple Web applications packaged in a single EAR file that want to use a single cluster; or you may have web applications that must keep their session data separate and need to be deployed to their own individual Coherence cluster. These choices and the deployment descriptors and elements that need to be configured are described in "Cluster Node Isolation".

1.3.2 Choose your Locking Mode

Locking mode refers to the behavior of HTTP sessions when they are accessed concurrently by multiple web container threads. You can choose to allow multiple nodes in a cluster to access an HTTP session simultaneously, to not allow more than one node in the cluster to access an HTTP session, or to not allow more than one thread in the cluster to access an HTTP session. These choices, and the deployment descriptors and elements that need to be configured are described in "Session Locking Modes".

1.3.3 Choose How to Scope Sessions and Session Attributes

Session and session attribute scoping refers to the fine-grained control over how both session data and session attributes are scoped (or "shared") across application boundaries. Coherence*Web supports sharing sessions across web applications as well as restricting what attributes within a session are shared across the application boundaries. These choices, and the deployment descriptors and elements that need to be configured are described in "Session and Session Attribute Scoping".

1.3.4 Choose the Installation Method

The installation procedure that you follow will depend on your application server. "Supported Web Containers" provides a list of the application servers supported by Coherence*Web.