Fusion Middleware Documentation
Advanced Search


Administering HTTP Session Management with Oracle Coherence*Web
Close Window

Table of Contents

Show All | Collapse

E Oracle Coherence*Web Extension for OVAB

This appendix describes Coherence*Web extensions for Oracle Virtual Assembly Builder, a tool for virtualizing installed Oracle components, modifying those components, and then deploying them into your own environment. Using Oracle Virtual Assembly Builder, you capture the configuration of existing software components in artifacts called software appliances. Appliances can then be grouped, and their relationships defined into artifacts called software assemblies which provide a blueprint describing a complete multi-tier application topology.

The Oracle Coherence*Web introspection extension for Coherence*Web extends the functionality of the WebLogic Server Introspector. It examines the configuration of Coherence cache clusters and servers configured as part of a WebLogic domain.

This appendix has the following sections:

E.1 Versions Supported

The plug-in extension works with Oracle WebLogic Server 11gR1 version 11.1.1.4.0, which includes Coherence 3.6.

E.2 Oracle Coherence*Web Introspection Parameters

There are no additional parameters required beyond those needed by Oracle WebLogic Server. For the parameters required by WebLogic Server, see ”Using the Introspection Plug-in for Oracle Virtual Assembly Builder,” in Administering Server Environments for Oracle WebLogic Server.

E.3 Reference System Prerequisites

There are no additional prerequisites beyond those defined by Oracle WebLogic Server. For the prerequisites required by WebLogic Server, see ”Using the Introspection Plug-in for Oracle Virtual Assembly Builder,” in Administering Server Environments for Oracle WebLogic Server.

E.4 Requirements

Oracle Coherence*Web has the following requirements:

Note:

In addition to the Coherence*Web requirements described in this section, all of WebLogic Server requirements must also be satisfied. For the WebLogic Server requirements, see ”Using the Introspection Plug-in for Oracle Virtual Assembly Builder,” in Administering Server Environments for Oracle WebLogic Server.

E.4.1 Deployment Model Requirement

The plug-in extension requires you to use an out-of-process deployment model for Oracle Coherence*Web, in which storage-enabled cache servers are executed as separate processes rather than running within Oracle WebLogic Server. For more information on the out-of-process deployment model, see "Out-of-Process Topology".

E.4.2 Requirement to Manually Update Custom Cluster Configuration Files

The plug-in extension examines Oracle Coherence*Web configuration defined through the WebLogic Server Administration Console and WebLogic Server MBeans (including WLST). It does not examine or modify custom cluster configuration files such as tangosol-coherence-override.xml. Custom cluster configuration files are passed through to the deployed environment, but no configuration changes are made to those files to reflect the deployed environment.

After deployment, ensure that you make appropriate manual configuration changes to any custom cluster configuration files.

E.5 Resulting Artifact Type

For each Coherence cluster that is defined in an introspected WebLogic domain, the plug-in extension creates a new appliance within the atomic Oracle WebLogic Server assembly.

E.6 Wiring

No wiring can be performed for Coherence cluster appliances. Each cluster appliance has a fixed, pre-defined connection to the domain's Administration Server, which is used at rehydration time to modify the cluster's configuration.

E.7 Wiring Properties

None.

E.8 Oracle Coherence*Web Appliance Properties

Each Oracle Coherence*Web cluster appliances has the following system and user properties:

Table E-1 describes Oracle Coherence*Web cluster appliance system properties:

Table E-1 Oracle Coherence*Web Appliance System Properties

Name Type Req'd Default Description

cache-servers

String

false

none

A list of the cache servers that are part of the cluster.

targets

String

false

none

A list of WebLogic Server Managed Servers that are part of the cluster.

<cacheserver>.node-manager-type

String

false

none

For each cache server in the above list, there is a property indicating the Node Manager type.

well-known-addresses

String

false

none

A list of well-known-addresses defined for the cluster. If no well-known-address are defined for this cluster (meaning it uses multicast), then this property will not be present.

<wellknownaddress>.server

String

false

none

For each of the well-known-addresses in the above list, there is a property indicating which cache server the well known address maps to (based on matching listen address and port information).


Table E-2 describes Oracle Coherence*Web cluster appliance user properties:

Table E-2 Oracle Coherence*Web Appliance User Properties

Name Type Req'd Default Description

<cacheserver>.node-manager-port

String

false

none

For each of the cache servers in the cluster, the Node Manager port is listed and may be modified by the user.

<cacheserver>.unicast-listen-port

String

false

none

For each of the cache servers in the cluster, the unicast listen port of that server is listed and may be modified by the user.

multicast-listen-address

String

false

none

The cluster-wide multicast listen address. If one or more well-known-addresses are listed (meaning the cluster uses unicast for cluster discovery), then this multicast property will not be present.

multicast-listen-port

String

false

none

The cluster-wide multicast listen port. If one or more well-known-addresses are listed (meaning the cluster uses unicast for cluster discovery), then this multicast property will not be present.

unicast-listen-port

String

false

none

The default unicast listen port for the cluster. This value is used by any cache servers that do not have a unicast listen port defined, as well as by any WebLogic Server Managed Servers that join the cluster.

<wellknownaddress>.server

String

true

none

If any of the defined well known addresses could not be correlated with a cache server (based on matching listen address and port information), they will be listed here, and the user is responsible for specifying a cache server name to be used as the well known address. This property is mandatory, meaning it must be specified either as an appliance property or via a deployment plan.


E.9 Supported Template Types

The supported template type is Oracle Enterprise Linux (OEL).