Coherence 5 2 3 – Turn Websites Into Apps Download

Note:

3.2 Configuring And Deploying Coherence.Web on GlassFish Server—Main Steps. 3.2.1 Download Oracle Coherence; 3.2.2 Set the Session Persistence Type; 3.2.3 Override the Default Coherence.Web Cache or Cluster Configuration; 3.2.4 Copy the ActiveCache for GlassFish and Session Cache Files to the Application; 3.2.5 Make Your Web Applications.

‎Download apps by Complete Coherence. Coherence Heart Trainer Health & Fitness More ways to shop: visit an Apple Store, call 0800 048 0408 or find a retailer. Oracle Coherence is an in-memory distributed data grid solution for clustered applications and application servers. Coherence makes sharing and managing data in a cluster as simple as on a single server. It accomplishes this by coordinating updates to the data using cluster-wide concurrency control, replicating and distributing data modifications across the cluster using the highest performing.

This chapter contains the following sections:

Coherence*Web provides session state persistence and management. It is a session management module that uses Coherence caches for storing and managing session data. This chapter describes how to set up and deploy Coherence*Web so that it can be used by applications running on WebLogic Server.

Coherence*Web is an alternative to the WebLogic Server in-memory HTTP state replication services. Consider using Coherence*Web if you are encountering any of these situations:

• Your application works with large HTTP session state objects

• You run into memory constraints, due to storing HTTP session object data

• You want to offload HTTP session storage to an existing Coherence cluster

• You want to share session state across enterprise applications and Web modules

2.1 Overview of the Coherence*Web SPI

The Coherence*Web Service Provider Interface (SPI) consists of the coherence-web-spi.war file. This file must be deployed with the coherence.jar file to enable Coherence*Web functionality in your applications.

In Coherence*Web, the following default cache configurations are defined:

• The Coherence*Web SPI for WebLogic Server is configured with local-storage disabled. The server will serve requests and will not be used to host data. This means a Coherence cache server must be running in its own JVM, separate from the JVM running WebLogic Server.

• The timeout for requests to the cache server to respond is 30 seconds. If a request to the cache server has not responded in 30 seconds, a com.tangosol.net.RequestTimeoutException exception is thrown.

The Coherence caches used by the Coherence*Web SPI are configured by the session-cache-config.xml file. This file is located inside the coherence-web-spi.war file under the WEB-INFclasses directory. Make any cache configuration changes in the session-cache-config.xml file.

If you are deploying the coherence-web-spi.war file as a shared library, copy the updated session-cache-config.xml file to the application's classpath. For example, when using WAR-scoped Coherence*Web, place the session-cache-config.xml file in the application's WEB-INF/classes directory. Similarly, for EAR-scope, place the updated file in the APP-INF/classes directory; for application server-scope, place it on the system classpath. Placing the file in these locations will override the session-cache-config.xml file in the shared library.

Coherence*Web provides several session locking modes to control concurrent access of sessions. Both Coherence*Web and the Coherence*Web SPI employ optimistic locking by default. This allows concurrent access to a session by multiple threads in a single JVM or multiple JVMs while prohibiting concurrent modification. See 'Session Locking Modes' for more information about locking modes.

By itself, the Coherence*Web SPI does not require a load balancer to run in front of the WebLogic Server tier. However, you will require a load balancer if you employ sticky session optimization with any of the non-Optimistic locking modes. The default load balancer enforces HTTP session JVM affinity, however, other load balancing alternatives are available. WebLogic Server ships with several different proxy plug-ins which enforce JVM session stickiness. Documentation for configuring the WebLogic Server proxy plug-in is available at this URL:

2.2 Configuring and Deploying Coherence*Web—Main Steps

Coherence*Web includes a deployable shared library that contains a native plug-in to the WebLogic Server HTTP Session Management interface. The following steps summarize how to prepare your deployments to use Coherence*Web with applications running on WebLogic Server:

1. Download Oracle Coherence to your file system. See 'Download Oracle Coherence'.

2. Modify the web.xml file in the WAR deployment if your application requires advanced configuration for Coherence*Web. 'Configure Coherence*Web' describes the parameters that can be configured for Web applications. The entire set of Coherence*Web parameters are described in Appendix A, 'Coherence*Web Context Parameters.'

3. (Optional) Configure the WebLogic-generated HTTP session cookie parameters in the weblogic.xml or weblogic-application.xml file. See 'Configure the Session Cookies'.

4. (Optional for testing; strongly suggested for production) Start a Cache Server Tier in a separate JVM from the one running WebLogic Server. See 'Start a Cache Server'.

5. Determine the appropriate packaging based on your deployment requirements and follow the packaging instructions. Depending on your version of WebLogic Server, see 'Configure Cluster Nodes'.

2.2.1 Download Oracle Coherence

All of the files needed by Coherence*Web, including the coherence-web-spi.war file, are included in the Coherence distribution.

By default, Coherence 3.6 is installed with WebLogic Server 10.3.4. The default location of the Coherence directory is C:OracleMiddlewarecoherence_3.6. If you are using WebLogic Server 10.3.4, you can download Coherence 3.7 and save it to your file system. Ensure that your applications reference coherence-web-spi.war, coherence.jar, and other library files that are in the Coherence 3.7 distribution.

Similarly, if you are working with WebLogic Server 10.3.3, you might already have Coherence installed in a coherence_3.5 directory. Again, you can download Coherence 3.7 and save it to your file system. Ensure that your applications reference coherence-web-spi.war, coherence.jar, and other library files that are in the Coherence 3.7 distribution.

Paragraphs 1 1 4 – writing tool just for writers. If you are using WebLogic Server 10.3.2 or earlier, simply download the Coherence distribution to your file system.

Applying Required Software Patches

Some older versions of WebLogic Server require you to apply software patches before you can work with Coherence and Coherence*Web. Table 2-1 identifies the versions of WebLogic Server and their associated patches.

Table 2-1 Required Software Patches for WebLogic Server

You can obtain the patches either through the SmartUpdate utility in the WebLogic Server Administration Console or by going to My Oracle Support.

To use SmartUpdate, see the instructions in the WebLogic Server Administration Console. For production environments, you should review the Smart Update production installation notes.

To use My Oracle Support, go to the My Oracle Support web site.

Select the Patches tab, click on the SimpleSearch link, and on the subsequent screen submit a search for a Patch Number/Name with the appropriate value (for example, 11399293). Download the patch zip file from the displayed results. Instructions for applying the Coherence patch are located in the README.txt included in the patch zip file.

2.2.2 Configure Coherence*Web

The Coherence*Web SPI provides a default configuration that should satisfy most Web applications. Table 2-2 describes only those Coherence*Web context parameters where the default for the SPI version is different from the non-SPI version. Table 2-3 describes the compatibility mode context parameter which is supplied by the SPI. For complete descriptions of all Coherence*Web parameters, see Appendix A, 'Coherence*Web Context Parameters.'

You can also configure the context parameters on the command line as system properties. The system properties have the same name as the context parameters, but the dash (-) is replaced with a period (.). For example, to declare a value for the context parameter coherence-enable-sessioncontext on the command line, enter it like this:

If both a system property and the equivalent context parameter are configured, the value from the system property is used.

Table 2-2 Coherence*Web Context Parameters Configured by the SPI

Table 2-3 describes the coherence-session-weblogic-compatibility-mode context parameter which is specifically provided by the Coherence*Web SPI.

Table 2-3 Context Parameter Provided by the Coherence*Web SPI

Table 2-4 describes the coherence-factory-class context parameter. The default value, which is set by the Coherence*Web SPI, should not be changed.

Table 2-4 Context Parameter Value that Should Not be Changed

2.2.3 Configure the Session Cookies

If you are using Coherence*Web SPI, then WebLogic Server generates and parses the session cookie. In this case, any native Coherence*Web session cookie configuration parameters will be ignored. To configure the session cookies, use the WebLogic-generated HTTP session cookie parameters in the weblogic.xml or weblogic-application.xml files. Table 2-5 describes these parameters.

In this table, Updatable? indicates whether the value of the parameter can be changed while the server is running. Not applicable indicates that there is no corresponding Coherence session cookie parameter.

Table 2-5 WebLogic-Generated HTTP Session Cookie Parameters

2.2.4 Start a Cache Server

A Coherence cache server (also known as a data node) is responsible for storing and managing all cached data. It can be either a dedicated JVM or run within a WebLogic Server instance. The senior node (which is the first node) in a Coherence data cluster can take several seconds to start; the startup time required by subsequent nodes is minimal.

Whether you start the cache servers first or the WebLogic Server instances first, depends on the server topology you are employing:

• If you are using an In-Process topology (all storage-enabled WebLogic Server instances), then it does not matter if you start the cache servers first or WebLogic Server instances first.

• If you are using an Out-of-Process topology (storage-disabled WebLogic Server instances and standalone Coherence cache servers), then start the cache servers first, followed by the WebLogic Server instances. This will ensure that there is minimal (measured in milliseconds) startup time for applications using Coherence. Any additional Web applications that use Coherence are guaranteed not to be the senior data member, so they will have minimal impact on WebLogic Server startup.

  In this topology, if you do not start the cache servers first, Coherence will respond with an error message similar to the following:

2.2.4.1 To Start a Standalone Coherence Data Node

Follow these steps to start a standalone Coherence data node:

1. Create a script for starting a Coherence data node. The following is a very simple example of a script that starts a storage-enabled cache server. This example assumes that you are using a Sun JVM. See 'JVM Tuning' in Developer's Guide for Oracle Coherence for more information.

   You must include coherence-web.jar and coherence.jar on the classpath. The cache_configuration_file represents the absolute path to the cache configuration file on your file system. For Coherence*Web, this will be the session-cache-config.xml file. Note that the cache configuration defined for the cache server must match the cache configuration defined for the application servers which run on the same Coherence cluster.

   If you have additional Coherence caches running on Coherence*Web, then you must merge the cache configuration information (typically defined in the coherence-cache-config.xml file) with the session configuration contained in the session-cache-config.xml file. The cache and session configuration must be consistent across WebLogic Server and Coherence cache servers.

2. Start one or more Coherence data nodes using the script described in the previous step.

2.2.4.2 To Start a Storage-Enabled or -Disabled WebLogic Server Instance

By default, a Coherence*Web-enabled WebLogic Server instance starts in storage-disabled mode. To start the WebLogic Server instance in storage-enabled mode, follow these steps:

1. Create a script for starting a Coherence data node. This can be similar to the script described in the previous section.

2. Include the command-line property to enable local storage, -Dtangosol.coherence.session.localstorage=true, in the server startup command.

For more information about working with WebLogic Server through the command line, see 'weblogic.Server Command-Line Reference' in Oracle Fusion Middleware Command Reference for Oracle WebLogic Server.

2.2.5 Configure Cluster Nodes

The session management provided by Coherence*Web can have application server-scope, EAR-scope, or WAR-scope. Like Coherence clusters, scoping of Coherence*Web depends on the placement of the coherence.jar file in the classloader's hierarchy. You can find detailed information about each of the scopes in 'Cluster Node Isolation'.

WebLogic Server, versions 10.3.3 and later, provides several features, collectively known as ActiveCache, that allow your applications to more easily interact with the Coherence cache. For a complete discussion of these features see the Using ActiveCache guide.

Some earlier versions of WebLogic Server (such as version 10.3.1 and earlier) might need a software patch to use Coherence and Coherence*Web. To find out if your version of WebLogic Server requires a patch, see 'Applying Required Software Patches'.

The following sections describe how you can configure the different cluster node configurations to run Coherence*Web:

Note:

An example of such an environment might be a deployment where multiple application teams are deploying applications written independently, without carefully coordinating and enforcing their conventions and naming standards. With this configuration, all applications are part of the same cluster—the likelihood of collisions between namespaces for caches, services, and other configuration settings is quite high and could lead to unexpected results.

For these reasons, Oracle Coherence strongly recommends that you use EAR-scoped and WAR-scoped cluster node configurations. If you are in doubt regarding which deployment topology to choose, or if this warning applies to your deployment, then donot choose the application server-scoped cluster node configuration.

2.2.5.1 Configuring Application Server-Scoped Cluster Nodes

If you are adding Coherence*Web for session management to a Coherence cluster, follow these steps:

1. Edit your WebLogic Server system classpath to include the coherence.jar file or copy the JAR file to your $DOMAIN_HOME/lib directory.

2. Use the WebLogic Server Administration Console or the command line to deploy coherence-web-spi.war file as a shared library.

3. Enable Coherence*Web in your Web application. Cleanmymac 3 1 2.

   Add the library reference code illustrated in Example 2-1 to the weblogic.xml file in each WAR file deployed in the WebLogic Server that intends to use Coherence*Web.

2.2.5.2 Configuring EAR-Scoped Cluster Nodes

Coherence 5 2 3 – Turn Websites Into Apps Downloads

If you are using Coherence*Web for session management in EAR-scoped cluster nodes, and your applications are running on WebLogic Server 10.3.2 or earlier, follow these steps:

1. Use the WebLogic Server Administration Console to deploy the coherence.jar and coherence-web-spi.war files as shared libraries to all of the target servers where the application will be deployed. See 'Install a Java EE Library' in Oracle Fusion Middleware Oracle WebLogic Server Administration Console Help for more information.

   If you receive an error when you attempt to deploy coherence.jar through the WebLogic Server Administration Console, you can use WLST commands. See Oracle Fusion Middleware Oracle WebLogic Server Administration Console Help for more information.

2. Reference the coherence.jar file in the weblogic-application.xml file. Store the file in the EAR's META-INF directory.

   Example 2-2 illustrates a weblogic-application.xml file.

   Example 2-2 Coherence JAR Referenced in weblogic-application.xml

3. Reference the coherence-web-spi.war file in the weblogic.xml file.

   Example 2-3 illustrates a weblogic.xml file.

   Example 2-3 Coherence Web SPI WAR Referenced in weblogic.xml

2.2.5.3 Configuring WAR-Scoped Cluster Nodes

If you are using Coherence*Web for session management in WAR-scoped cluster nodes, follow these steps:

1. Use the WebLogic Server Administration Console or the command line to deploy the coherence-web-spi.war file as a shared library to all of the target servers where the application will be deployed. See 'Install a Java EE Library' in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Help.

2. Add the coherence.jar file to the application. You can do this in any of the following ways:

   • Import coherence.jar file as an optional package in the manifest.mf file of each module that will be using Coherence. Example 2-4 illustrates a manifest.mf file.

     Example 2-4 Manifest File that References the Coherence JAR File

   • Copy the coherence.jar file to the WAR file's WEB-INF/lib directory.

3. If you deploy the coherence-web-spi.war file as a shared library, you must also create a shared library reference by adding the stanza illustrated in Example 2-5 to theweblogic.xml file in the WAR file's WEB-INF directory.

   Example 2-5 Library Reference for a Web Application

2.3 Scoping the Session Cookie Path

WebLogic Server and Coherence*Web handle session scoping and the session lifecycle in different ways. This can impact your decision to implement a single sign-on (SSO) strategy for your applications.

By default, WebLogic Server uses the same session ID in every Web application for a given client, and sets the session cookie path to a slash (/). This is a requirement of the WebLogic Server default thin SSO implementation, which is enabled by default. By generating a session cookie with a path of '/', clients always return the same session ID in every request to the server. In WebLogic Server, a single session ID can be mapped to multiple session objects. Each Web application will have a different session object instance even though the session ID is identical (unless session sharing is enabled).

In contrast, Coherence*Web maps a session ID to a single session instance. This means that the behavior of having multiple session instances mapped to the same ID is not replicated by default if an application uses Coherence*Web. Because the session cookie is mapped to '/' by default, a single Coherence*Web session is shared across all Web applications. The default configuration in Coherence*Web is that all session attributes are scoped to a Web application. For most purposes, this single session approach is transparent. The major difference of having a single session across all Web applications is the impact of session invalidation. If Coherence*Web is enabled and you invalidate a session in one Web application, then you invalidate that session in all Web applications that use that session instance. If your Web applications do not use thin SSO, then you can avoid this issue by scoping the session cookie to the Web application path.

Therefore, you have the following options regarding SSO:

• Enable 'WebLogic Server session compatibly mode'. This configuration is set with the coherence-session-weblogic-compatibility-mode parameter and mirrors all of the native WebLogic Server session persistence types: memory (single-server, non-replicated), file system persistence, JDBC persistence, cookie-based session persistence, and in-memory replication (across a cluster). By default, this mode is enabled. See 'Using Sessions and Session Persistence' in Developing Web Applications, Servlets, and JSPs for Oracle WebLogic Server for more information.

• Enable thin SSO functionality. Clients will use a single session across all Web applications. This means that the session life cycle will be inconsistent with all other session persistence types.

• Disable the thin SSO functionality by scoping the session cookie path to the Web application context path. This will allow the session life cycle to be consistent with all other session persistence types.

1. Use the WebLogic Server Administration Console or the command line to deploy the coherence-web-spi.war file as a shared library to all of the target servers where the application will be deployed. See 'Install a Java EE Library' in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Help.

2. Add the coherence.jar file to the application. You can do this in any of the following ways:

   • Import coherence.jar file as an optional package in the manifest.mf file of each module that will be using Coherence. Example 2-4 illustrates a manifest.mf file.

     Example 2-4 Manifest File that References the Coherence JAR File

   • Copy the coherence.jar file to the WAR file's WEB-INF/lib directory.

3. If you deploy the coherence-web-spi.war file as a shared library, you must also create a shared library reference by adding the stanza illustrated in Example 2-5 to theweblogic.xml file in the WAR file's WEB-INF directory.

   Example 2-5 Library Reference for a Web Application

2.3 Scoping the Session Cookie Path

WebLogic Server and Coherence*Web handle session scoping and the session lifecycle in different ways. This can impact your decision to implement a single sign-on (SSO) strategy for your applications.

By default, WebLogic Server uses the same session ID in every Web application for a given client, and sets the session cookie path to a slash (/). This is a requirement of the WebLogic Server default thin SSO implementation, which is enabled by default. By generating a session cookie with a path of '/', clients always return the same session ID in every request to the server. In WebLogic Server, a single session ID can be mapped to multiple session objects. Each Web application will have a different session object instance even though the session ID is identical (unless session sharing is enabled).

In contrast, Coherence*Web maps a session ID to a single session instance. This means that the behavior of having multiple session instances mapped to the same ID is not replicated by default if an application uses Coherence*Web. Because the session cookie is mapped to '/' by default, a single Coherence*Web session is shared across all Web applications. The default configuration in Coherence*Web is that all session attributes are scoped to a Web application. For most purposes, this single session approach is transparent. The major difference of having a single session across all Web applications is the impact of session invalidation. If Coherence*Web is enabled and you invalidate a session in one Web application, then you invalidate that session in all Web applications that use that session instance. If your Web applications do not use thin SSO, then you can avoid this issue by scoping the session cookie to the Web application path.

Therefore, you have the following options regarding SSO:

• Enable 'WebLogic Server session compatibly mode'. This configuration is set with the coherence-session-weblogic-compatibility-mode parameter and mirrors all of the native WebLogic Server session persistence types: memory (single-server, non-replicated), file system persistence, JDBC persistence, cookie-based session persistence, and in-memory replication (across a cluster). By default, this mode is enabled. See 'Using Sessions and Session Persistence' in Developing Web Applications, Servlets, and JSPs for Oracle WebLogic Server for more information.

• Enable thin SSO functionality. Clients will use a single session across all Web applications. This means that the session life cycle will be inconsistent with all other session persistence types.

• Disable the thin SSO functionality by scoping the session cookie path to the Web application context path. This will allow the session life cycle to be consistent with all other session persistence types.

One advantage of enabling thin SSO with Coherence*Web is that it will work across all Web applications that are using the same Coherence cluster for Coherence*Web. The Coherence cluster is completely independent from the WebLogic Server cluster. The thin SSO functionality can even span multiple domains by enabling cross-domain trust in the WebLogic Server security layer.

2.4 Sharing Coherence*Web Sessions with Other Application Servers

If you are running Coherence*Web on WebLogic Server and on other application servers within a single cluster, then the session cookies created by WebLogic Server will not be decoded correctly by Coherence*Web on the other servers. This is because WebLogic Server adds a session affinity suffix to the cookie which is not part of the session ID stored in Coherence*Web. The other application servers must remove the WebLogic session affinity suffix from the session cookie value for Coherence*Web to be able to retrieve the session from the Coherence cache.

To strip the WebLogic session affinity suffix from the session cookie, add the coherence-session-affinity-token context parameter to the web.xml file used in the other application servers. Set the parameter value to an exclamation point (!), as illustrated in Example 2-6. The session affinity suffix will be removed from the session cookie when it is processed by the other application server.

See Appendix A, 'Coherence*Web Context Parameters' for more information on the coherence-session-affinity-token context parameter.

Download Coherence X 3.1.1 for Mac full version program setup free. Coherence X 3 is a popular application developed for turning any website into a chromium-based and native application.

Coherence X 3.1.1 for Mac Review

Coherence X 3 for macOS is a unique program with the ability to turn any website into native app. This program is the perfect middle-ground between websites and apps on your Mac. It comes with a feature-rich, yet well-structured interface that enables smooth navigation between the various functions. Using this app, you can easily turn any websites into a chromium-based, native application on your Mac. You may also like Coherence X 3 for Mac Free Download

It makes the app creation process so simple and easy. You don't need complex coding or programming skills, simply enter a name for your app, enter a URL, pick an icon, and launch your app. Moreover, it also empowers you to choose some additional settings for your app such as status bar mode, compact mode, and intelligent whitelisting. It also supports custom features tailored specifically for app, like shortcuts, whitelisting, customization, and more all in an incredibly lightweight package. All things considered, Coherence X is a perfect choice to turn any website into a chromium-based and native application.

Features of Coherence X 3.1.1 for Mac

• A perfect app to turn any website into native Mac app
• No program or complex coding skills are required for working
• Perfect middle-ground between websites and apps on Mac
• Empowers you to easily share apps between licensed users
• Enables you to create multiple apps with the same settings

Technical Details of Coherence X 3.1.1 for Mac

• Software Name: Coherence X 3
• Software File Name: Coherence-X-3.1.1.dmg
• File Size: 17 MB
• Developer: Coherence

Coherence 5 2 3 – Turn Websites Into Apps Download Free

System Requirements for Coherence X 3.1.1 for Mac

• macOS 10.10 or later
• 100 MB free HDD
• 2 GB RAM
• Intel Core 2 Duo or higher

Download Coherence X 3.1.1 for macOS Free

Coherence 5 2 3 – Turn Websites Into Apps Download Windows 7

Click on the button given below to download Coherence X for macOS setup free. It is a complete offline setup of Coherence X macOS X with a single click download link.