![]() ![]() Application Server-scope is not supported.ģ.2 Configuring And Deploying Coherence*Web on GlassFish Server-Main Steps Coherence*Web can run on GlassFish Server in either EAR-scoped or WAR-scoped cluster nodes. It also allows sessions to be shared across different web applications. Storing session data outside of GlassFish Server allows the Web application and the server to be restarted without any loss of session data. ![]() Heap space is made available in GlassFish Server by storing session data in the Coherence data grid. See "Session Models" for more information. The split session model (SplitHttpSessionModel), where small session attributes are stored as a single cache entry, and large attributes are stored as individual cache entries, is the default session model used by ActiveCache for GlassFish. See "Session Locking Modes" for more information about locking modes. This allows concurrent access to a session by multiple threads in a single JVM or multiple JVMs while prohibiting concurrent modification. ActiveCache for GlassFish employs Last Write Wins Locking by default. A separate Coherence cache server must be running for the Web application to work.Ĭoherence*Web provides several session locking modes to control concurrent access of sessions. See "Configure Cluster Nodes" for more information on configuring ActiveCache for GlassFish to run on EAR-scoped or WAR-scoped cluster nodes.īy default, the Coherence node running on GlassFish Server is configured as storage-disabled. ![]() Since Coherence*Web uses Coherence caches to store session data, the coherence.jar file must also be available to the Web application's classloader. The default cache and services configuration defined in the session-cache-config.xml file should satisfy most Web applications. To make this functionality available to your application, you must extract the coherence-web.jar file from the webInstaller.jar file.Ĭoherence cache configurations and services used by ActiveCache for GlassFish are defined in the session-cache-config.xml file, which must also be extracted from the webInstaller.jar file. With ActiveCache for GlassFish, the WebInstaller pre-processing step is not required for GlassFish 3.1 applications.ģ.1 Overview of ActiveCache for GlassFishĪctiveCache for GlassFish functionality is provided in the coherence-web.jar file which is contained in the webInstaller.jar file. In previous releases, the Coherence*Web WebInstaller was required to pre-process applications before they could use Coherence*Web for session storage. ActiveCache for GlassFish provides Coherence*Web functionality in Web applications deployed on Oracle GlassFish Servers. Starting with Coherence 3.7 and Oracle GlassFish Server 3.1, there is a new feature of Coherence*Web called ActiveCache for GlassFish. This chapter describes how to set up and deploy Coherence*Web so that it can be used by applications running on GlassFish Server. Oracle GlassFish Server is best suited for applications requiring lightweight infrastructure and the most recent implementations of Java Enterprise Edition. It provides a small footprint, fully featured Java EE application server that is completely supported for commercial deployment and is available as a standalone offering. Oracle GlassFish Server delivers a flexible, lightweight and extensible Java EE 6 platform. 9/21 3 Using Coherence*Web with GlassFish Server ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |