Teya Salat
HomeBlogAbout Me

Coherence 5 2 3 – Turn Websites Into Apps Using



Note:

  1. Coherence 5 2 3 – Turn Websites Into Apps Using Iphone
  2. Coherence 5 2 3 – Turn Websites Into Apps Using Itunes

Coherence allows you to turn any website into a full-blown macOS appplication in seconds. And, using the power of Google Chrome, allows each app to have separate settings and extensions.

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. Under 'Activity controls,' tap Web & App Activity. Turn Web & App Activity on or off. When Web & App Activity is on: You can check the box next to 'Include Chrome history and activity from websites and apps that use Google services.' When this box is checked, you can control whether app. The Wix App Market offers 250+ powerful web apps for your Wix website. Integrate your site with leading marketing or financial tools, sell online, and more. Aug 31, 2018 Coherence Pro allows you to turn any website into a full-blown macOS application in seconds. With the new Pro version you can now create apps in bulk and also edit them after they are created. Simply name your app, paste in a URL, and it will grab a favicon and create a web-wrapper app for your Doc.

Except where noted, this chapter pertains to the 11g Release 1 Patch Set 3 (10.3.4), or later of Oracle WebLogic Server.

This chapter contains the following sections:

Coherence 5 2 3 – Turn Websites Into Apps Using

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 Ubar 4 0 9. 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. Instadesk v2 0 2 – instagram client for photo sharing. 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.

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


WebLogic Server 9.2 MP1WebLogic Server 9.2 MP3WebLogic Server 10.3WebLogic Server 11g (10.3.1 and later)

WebLogic Smart Update

Patch ID: 616G

Patch ID: LP7B

Patch ID: 6W2W

No Patch Required


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

Parameter NameDescription

coherence-application-name

Coherence*Web uses the value of this parameter to determine the name of the application that uses the ApplicationScopeController interface to scope attributes. The value for this parameter should be provided in the following format:

application name + ! + Web module name

The application name is the name of the application that uses the ApplicationScopeController interface and Web module name is the name of the Web module in which it appears.

For example, if you have an EAR file named test.ear and a Web-module named app1 defined in the EAR file, then the default value for the coherence-application-name parameter would be test!app1.

If this parameter is not configured, then Coherence*Web uses the name of the class loader instead. Also, if the parameter is not configured and the ApplicationScopeController interface is configured, then a warning is logged saying that the application name was not configured. See 'Session Attribute Scoping' for more information.

coherence-reaperdaemon-assume-locality

This setting allows the session reaper to assume that the sessions that are stored on this node (for example, by a distributed cache service) are the only sessions that this node must check for expiration.

The default is false.

coherence-scopecontroller-class

This value specifies the class name of the optional com.tangosol.coherence.servlet.HttpSessionCollection$AttributeScopeController interface implementation.

Valid values include:

  • com.tangosol.coherence.servlet.AbstractHttpSessionCollection$ApplicationScopeController (default)

The default set by the Coherence*Web SPI is com.tangosol.coherence.servlet.AbstractHttpSessionCollection$ApplicationScopeController.


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

Parameter NameDescription

coherence-session-weblogic-compatibility-mode

This parameter is provided by the SPI version of Coherence*Web. If its value is set to true, it determines that a single session ID (with the cookie path set to '/') will map to a unique Coherence*Web session instance in each Web application. If it is false, then the standard behavior will apply: a single session ID will map to a single session instance using the Coherence*Web SPI in WebLogic Server. All other session persistence mechanisms in WebLogic use a single session ID in each Web application to refer to different session instances.

This parameter defaults to true unless the global scope controller is specified. If this controller is specified, then the parameter defaults to false.


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

Coherence 5 2 3 – Turn Websites Into Apps Using
Parameter NameDescription

coherence-factory-class

The fully qualified name of the class that implements the SessionHelper.Factory factory class. The Coherence*Web SPI sets the default value to weblogic.servlet.internal.session.WebLogicSPIFactory. This value should not be changed.


2.2.3 Configure the Session Cookies

Adobe bridge download. 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

This Session Cookie Parameter.Replaces this Coherence*Web Cookie ParameterDescription

cookie-comment

Not applicable

Specifies the comment that identifies the session tracking cookie in the cookie file.

The default is null.

Updatable? Yes

cookie-domain

coherence-session-cookie-domain

Specifies the domain for which the cookie is valid. For example, setting cookie-domain to.mydomain.com returns cookies to any server in the *.mydomain.com domain.

The domain name must have at least two components. Setting a name to *.com or *.net is not valid.

If not set, this attribute defaults to the server that issued the cookie.

For more information, see Cookie.setDomain() in the Servlet specification.

The default is null.

Updatable? Yes

cookie-max-age-secs

coherence-session-max-age Paperless 3 0 0 – digital documents manager template.

Sets the life span of the session cookie, in seconds, after which it expires on the client. For more information about cookies, see 'Using Sessions and Session Persistence' in Developing Web Applications, Servlets, and JSPs for Oracle WebLogic Server.

The default value is -1 (unlimited).

Updatable? Yes

cookie-name

coherence-session-cookie-name

Defines the session-tracking cookie name. Defaults to JSESSIONID if not set. You can set this to a more specific name for your application.

The default is JSESSIONID.

Updatable? Yes

cookie-path

coherence-session-cookie-path

Defines the session-tracking cookie path.

If not set, this attribute defaults to a slash ('/') where the browser sends cookies to all URLs served by WebLogic Server. You can set the path to a narrower mapping, to limit the request URLs to which the browser sends cookies.

The default is null.

Updatable? Yes

cookie-secure

coherence-session-cookie-secure

Tells the browser that the cookie can be returned only over an HTTPS connection. This ensures that the cookie ID is secure and should be used only on Web sites that use HTTPS. Session cookies sent over HTTP will not work if this feature is enabled.

Disable the url-rewriting-enabled element if you intend to use this feature.

WebLogic Server generates the session cookie.

The default is false.

Updatable? Yes

cookies-enabled

coherence-session-cookies-enabled

Enables use of session cookies by default and is recommended, but you can disable them by setting this property to false. You might turn this option off for testing purposes.

The default is true.

Updatable? Yes

debug-enabled

Not applicable

Enables the debugging feature for HTTP sessions. Support it by enabling HttpSessionDebug logging and the WebLogic Server trace logger.

The default value is false.

Updatable? Yes

encode-session-id-in-query-params

Not applicable

Is set to true if the latest servlet specification requires containers to encode the session ID in path parameters. Certain Web servers do not work well with path parameters. In such cases, the encode-session-id-in-query-params element should be set to true.

WebLogic Server generates the HTTP response.

The default value is false.

Updatable? Yes

http-proxy-caching-of-cookies

Not applicable

When set to false, WebLogic Server adds the following header and response to indicate that the proxy caches are not caching the cookies:“Cache-control: no-cache=set-cookie”

WebLogic Server generates the HTTP response.

The default value is true.

Updatable? Yes

id-length https://kindlspecials863.weebly.com/graphic-inspector-2-4-4.html.

coherence-session-id-length

Sets the size of the session ID.

The minimum value is 8 bytes and the maximum value is Integer.MAX_VALUE.

If you are writing a Wireless Application Protocol (WAP) application, you must use URL rewriting because the WAP protocol does not support cookies. Also, some WAP devices have a 128-character limit on URL length (including attributes), which limits the amount of data that can be transmitted using URL rewriting. To allow more space for attributes, use this attribute to limit the size of the session ID that is randomly generated by WebLogic Server.

You can also limit the length to a fixed 52 characters, and disallow special characters, by setting the WAPEnabled attribute. For more information, see 'URL Rewriting and Wireless Access Protocol' in Developing Web Applications for WebLogic Server.

The default is 52.

Updatable? No

invalidation-interval-secs

coherence-reaperdaemon-cycle-seconds

Sets the time, in seconds, that Coherence*Web waits between checks for timed-out and invalid sessions, and deleting the old sessions and freeing up memory. Use this element to tune WebLogic Server for best performance on high traffic sites.

The default is 60.

Updatable? No

timeout-secs

coherence-session-expire-seconds

Sets the time, in seconds, that Coherence*Web waits before timing out a session.

On busy sites, you can tune your application by adjusting the timeout of sessions. While you want to give a browser client every opportunity to finish a session, you do not want to tie up the server needlessly if the user has left the site or otherwise abandoned the session.

This element can be overridden by the session-timeout element (defined in minutes) in web.xml.

The default is 3600 seconds.

Updatable? No

tracking-enabled

Not applicable

Enables session tracking between HTTP requests.

WebLogic Server generates the HTTP response.

The default is true.

Updatable? No

url-rewriting-enabled

coherence-session-urlencode-enabled

Enables URL rewriting, which encodes the session ID into the URL and provides session tracking if cookies are disabled in the browser and the encodeURL or encodeRedirectedURL methods are used when writing out URLs. For more information, see:

WebLogic Server generates the HTTP response.

The default is true.

Updatable? Yes


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:

Consider the use of the application server-scoped cluster configuration very carefully. Do not use it in environments where application interaction is unknown or unpredictable.

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. Fivenotes 2 2 2.

  3. Enable Coherence*Web in your Web application.

    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

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:

Coherence 5 2 3 – Turn Websites Into Apps Using Iphone

  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.

Announcements

Is there a plugin for that?

With more than 50,000 plugins in the WordPress repository, it’s hard to find the perfect one. Each week, I will highlight an interesting plugin form the repository.

For more great plugins, download my 50 Most Useful Plugins eBook.

Coherence 5 2 3 – Turn Websites Into Apps Using Itunes

Dapper Desktop is a plugin to help you create a wallpaper with the correct size for your specific electronic devices.

A New Tool – Coherence Pro

I’ve been using this new tool recently to help me manage my windows on my Mac and turn some specific websites into their own apps.

Thank You!

Thank you to those who use my affiliate links. As you know I make a small commission when someone uses my link and I want to say thank you to the following people. For all my recommended resources, go to my Resources Page

Full Transcript

Business Transcription is provided by GMR Transcription.

On today’s episode we are going to talk about a new application that I started using in the last week or so and it’s called Coherence Pro. We’ll talk all about it right here on Your Website Engineer Podcast Episode #483. Hello and welcome to another episode of Your Website Engineer Podcast. My name is Dustin Hartzler. I’m excited to be here with you just like every single week. And, today I’ve got a new tool that I’m gonna share with you. Something that I use every single day now and it has just kinda changed the way that I use my computer as weird as that maybe sounds. So, we’ll talk about that in just a couple minutes.

I have a couple announcements to share and then a plugin of course. So, the first announcement is WooCommerce 4.0 is now out into the wild. I put this one first because I am in the WooCommerce space every single day. I work for Automatic in WooCommerce support. So, I get to help people build their websites and get their stores up and running and fix anything that’s broken. And, WooCommerce 4.0 is launched. It’s launched right on time. And, there’s been more than 3,500 changes or 3,500 commits from 45 different contributors. It’s a major release.

And, it’s stated that in the fact that it’s not backwards compatible and it went from Word – WooCommerce 3.6 to word – WooCommerce 4.0. And, we skipped a few versions in there of course. But, that main reason was because of the fact that it is a major change, with a big feature that they added was a – an additional plugin that was called WooCommerce Admin. And now, all of that has been rolled into core and now it works seamlessly together. And, the WooCommerce Admin was a really neat interface that allowed you to manage orders, run reports. The reports part was really, really cool. It was all dynamic. It was very JavaScript-based and it just was really cool.

So, if you are running a WordPress store using WooCommerce, I do recommend upgrading to Version 4.0. Do do that on or do make that upgrade on a Test Site because of course, in support, we’re gonna start to see requesting and figuring out different bugs and different things. There’s only so many things that we can test as an upgrade process. So, if you’re using WooCommerce, make sure that you upgrade that to 4.0. Do a back-up of your Live Site first and then update on a Development Site just to make sure everything works and there’s no issues whatsoever. So, that is the first announcement.

The other announcement or another link that I have for you today to read is all about the Advice for Newcomers to Remote Work and some Lessons Learned. And, this is an article on WP Tavern. And, of course, the world is all shutting down because of this Coronavirus, things are being canceled. I’ve had a work trip canceled. My wife had a trip that was canceled. Her university and all the universities in Ohio have stopped in-person lectures until – that’s all being shut down. I mean, I can only imagine they’re gonna start shutting schools down and all kinds of things over this virus. And, I think, it’s all overkill, completely overkill.

But again, I get to work from home and I don’t have a lot of contact with outside people. And so, I don’t know, I may be a little bit on the bias side. But, if you’re new to working from home, this is a great article. And, I could probably talk the entire Podcast episode about working from home and some of the things that I take into consideration. Maybe I’ll work on that for next week. And, just because I’ve had – I mean, I’ve been working from my house since 2010. So, I’ve got 10 years of work-at-home experience. And, I think I have more work-at-home experience than I do work at a somewhere-else-type-of-a-job experience.

And so, let’s go ahead and we’ll table that discussion for next week. But, if you want a little bit of a preview there’s an article on WP Tavern that you can read and some just advice about moving into this space. If your company has said, “Okay, we’re gonna work from home until the rest of the month is over.” Here might be some things that you can think about and to make sure that you’re honing in your productivity and actually doing things while you’re at home. And, you’re not doing the laundry and you’re not cleaning up the kitchen and you’re not eating from the fridge and watching Netflix and doing all those things throughout the course of the day. So, that is an article to read.

And then, there is another thing that I found and it is called Gutenberg – Introducing the Gutenberg Templates Library. And, there’s a link specifically in Episode #483 for this. But, it is a way to add 100 different section templates and – to different areas into your Gutenberg website. So, if you wanted to add testimonials or teams or logos, galleries, features, all kinds of things. I’ll link it in the show notes so you can see it there or you can just you can search, I guess you can search and look for -- it’s on gethub – or, it’s on gutenberghub.com. So, you can find that whole thing there.

And then, the last piece of news is all about WordPress 5.4 release candidate two. We’re getting close to that launch of for – of March 31st, so just a couple weeks away, and to get 5.4 out into the wild. And, it has some fixes of course. And, you can install this on some, a Test Site somewhere and you can spend a little bit of time figuring out if its gonna work for you. And so, those are the announcements that I wanna share this week. I do have a plugin that I wanna share with you. Just like every week, there’s more than 50,000 plugins; free plugins on the WordPress repository. That’s not even counting all the other plugins that are premium plugins that aren’t on the repository.

But, this one is called “Dapper Desktop.” And, I don’t know if this is gonna be very helpful other than for a few use cases. But, this one like I said, it’s called Dapper Desktop. And, this allows you to change your desktop on your computer. And, how does a plugin do that? Well, what this does is you give it a wallpaper file and it generates the other sizes and makes it easy to download. So say, for example, you find a big image. Maybe, its 5,000 pixels wide by 3,000 pixels for a desktop and you upload this to your Media Library and then you add the Dapper Desktop plugin. You add the image to the plugin section inside of the Gutenberg editor.

And then, you publish the post and then it gives you a button that you can – on the live part of your site, it gives you a download button and then you can choose what version you want. And, it gives you different options based on what size of your – if you need a desktop image or if you’re looking for a background image for your iPad or your iPhone or something. It’s a completely weird plugin and I have no reason, no understanding of why somebody would create this to be useful on a WordPress site. But, it’s a kind of a cool way and a cool tool to use if you wanna generate different size wallpapers for the different devices in your life.

And so, if that – if you’ve been looking for something like that, I recommend checking out Dapper Desktop, and it’s by sorta brilliant, in the WordPress repository. And, as always you can find a link in the show notes for Episode #483. Alright, today, like I said, we are going to talk about Coherence Pro. And, it is a plugin that I discovered from a colleague just a couple weeks back, maybe two weeks or so ago. And, it is a plugin that allows you to turn in a website into an isolated application using Google Chrome as the backend. Now let me set this up just a little bit.

We have a – we have a technology called Happy Chat and it is an interface that we use to do live chats with customers on WooCommerce or wordpress.com. This is what I live in most days when I’m chatting with customers, we’re using this tool called Happy Chat. And, it is all browser-based. Some really experienced, really smart people developed this. It’s in an in-house tool, so automatic purchase, not purchase, but automatic employees actually created this. And so, it has all the tools that we need. We can see Dashboard items.

And so, when somebody comes or if you come and start – wanna chat with us on wordpress.com or if you have a WooCommerce issue, we can look at your account information. We can see what you’ve purchased. We can see details and it lists out your system status report. It gives us all the information that we need to start debugging and figuring out, do you have a subscription? And, all these types of things. So, it’s a really cool thing. It’s great. It works really, really well and we’ve been using this for years.

Well, the thing is that it’s not perfect and there’s ways that we have other Happiness Engineers or other developers, who don’t – aren’t quite developers, but they have the ability to kind of hack in and to add custom scripts to make things work better. If you’ve ever heard of Tampermonkey before, this is a way that you can actually inject a JavaScript, or you – JavaScript’s the main thing that you can do. You can use JavaScript and inject JavaScript on any webpage that you want.

So, if you wanted to kind of customize the way google.com looks every time you go to it, you could go in and you could create a Tampermonkey script so when you log into google.com then it can do some funky things on the website if you’re wanting. So, we have some Happiness Engineers that have gone in and added customizations and they’ve added different arrangements and have done different things. But, in order to use this, you need to use Tampermonkey. And, I’m sorry this whole thing is getting a little long-winded.

But, basically what I wanted to do was I wanted to create a stand-alone app or stand-alone version of this Happy Chat application so that I could add these cool Tampermonkey scripts, and that I could have a place where I can Command-Tab and this on the Mac, Command-Tab, from Chrome to Happy Chat. And – or maybe I’m in Safari and Happy Chat. Or, maybe I’m looking at something in the database and I’m using Sequel Corp Pro and I need to Command-Tab to get back to my chats. Otherwise, it’s in a tab inside of a browser.

And, right now I’m recording this and I just wrapped up a LiveChat shift and I’ve got 56 different Chrome tabs open just from different issues and different things that I’ve been working on. And so, instead of trying to find that amongst the sea of tabs, I use this thing now called Coherence Pro. And, like I said, it allows you to turn a website into a Google app. It is a plugin that is, I believe its $19.99, for the Mac version is $19.99 or you can get it as part of Setapp. And, Setapp is a Mac application platform where you can get hundreds of apps for just $10.00 per month. And so, we’ll talk about Coherence Pro and what it can do.

But, I also wanna highlight the fact that there’s one called Appmaker.xyz and this you can – you can pretty much do the same thing but it gives you the ability to do it on Windows or Linux. There’s not quite all the features in Appmaker.xyz but you could do the same thing. And, where I’m kinda going with this is – where I got the idea is, if I wanted to always keep yourwebsiteengineer.com kind of opened in its own thing, what I could do is I could create a stand-alone app for yourwebsiteengineer.com. I can log in to the backend. I can see the favicon. It can use a favicon or a custom icon.

And so, it could create this own little app for myself so I wouldn’t have to keep yourwebsiteengineer.com open in a separate tab. I could just launch the app and I could have everything open that I needed. And so, that’s kind of where the premise comes from. And, you could do this with, I’m thinking about doing this for YNAB, the software that I use for all my budgeting and whatnot. Like, create an app. It’s just a web wrapper but it looks more like an app. And then, you can have it open and you don’t get it lost with – amongst all your different browsers and the different things that you have opened up.

So, that’s kind of where I’m going with and kinda how I’m tying this into WordPress and how this could benefit you in some way with your WordPress site. Most of these tools like the one that I said, the Coherence Pro and the – the other one, the Appmaker.xyz, both of these are real simple, you add the name for your app and then you put the URL of the website. So, I could call it Your Website Engineer and then I could put the URL as yourwebsiteengineer.com. I could click next and then it asks you if you wanna have any extension.

So, if you wanted to be able to login with the – one password or save to Google Drive or any of the Chrome extension that you’ve added to your Chrome browser, you can add these to Coherence Pro and build those into your apps as well. And, you could do this for some other examples, are having your own app for Netflix or for Slack if you didn’t wanna use the Slack app or if you wanted to have a special thing for YouTube. Then, you wanted YouTube to have its own kind of app. And so, Twitter, any of these things you can do and you can build it into – build them into your own apps instead of having individual things.

The other thing that you could do with these is since they’re in – they’re different apps, you could call these or you could use these apps with somebody like Keyboard Maestro or maybe some sort of display management software where you could rearrange the windows on your computer. You could move, okay, I’m gonna open up the Netflix app and I want that in the upper left-hand corner and just kinda stay up there and I’ll watch something kind of in the background. Or, I want Twitter to be open but I want it on the right-hand side and I want it to kinda stay over there and just kinda be out of my way.

And so, that’s kinda what I’m thinking when it comes to how you could use those, Coherence Pro or the Appmaker.xyz. And, like I said it is a, it’s a paid app. The one that I’m using is the – the different version. It is, like I said, $19.99 a one-time fee or it is $10 – or it’s part of Setapp which is $9.99 per month. And, the cool part is once I’ve created this, now I am using, I’ve got some Custom CSS built in and I’m using Tampermonkey. So, those are two extensions that I’m using for the Happy Chat one. So, if I wanted to change the colors, I’ve customized mine so it’s a Dark Mode. And so, I can see everything kind of in Dark Mode versus the Light Mode.

So, you could customize that if you wanted to have just Twitter opened in the – on the sidebar instead of having the Light version. Or, if you wanted to create your own custom color scheme, you could add a Stylus extension or whatnot. And then, you could customize it, put custom colors, and you can do things like that, all built into this application. This definitely isn’t for everyone. It isn’t a necessity by any stretch of the imagination. You can go in and you can log in to your WordPress site and can use – you can use it right from the browser, you could use the wordpress.com. There is a wordpress.com app, you could use that.

It’s kinda limited in some of your features. You can’t quite navigate to everything with the app itself. But, you could use something like Coherence Pro, create your own app, and then you could save your credentials. It’s just like a separate instance of Chrome. And so, you could save your credentials in Chrome and then you could log in. You could have your dashboard. You could make customizations as you needed. Or, if you wanted to work on some CSS, you could install the Stylus extension and then you could start tweaking your CSS and then you could work on that without affecting your Live Site in any way, shape, or forms.

There’ll be a link in the show notes on how to get the software. You can try it out for free to see if it’s something that you wanna use. It’s something that you can use for it’s got a two-week free trial. And, you can go ahead and do that. And then, when it comes to the Appmaker.xyz, it looks like that’s completely free. It creates the app and then you can download it and then you can use it straight away on your computer. And, it’ll email you the files I guess. And, it’s good for Windows, Linux, or Mac OS.

And so, oh I guess and if you wanna remove the branding one on Appmaker.xyz, so if you wanted to not see any notification about it being Appmaker branding, then the splash screen that’s gonna cost $50.00. So, that is an upgrade. But anyway, these are just a couple options that you can use to find out and – and see if creating a separate workspace or a separate application would be beneficial to you. So, I thought it’s been very beneficial to me over the last couple of weeks and I thought, “Hey, I’ll put this out there and see if it’s something that’s interesting to you.” If not, completely skip this episode. Don’t worry about doing anything about it.

And then, next week we’ll talk more about kinda some work-from-home strategies and how to stay not distracted or keep from being distracted with household activities while you’re at home if you’re being quarantined away from work. That’s all I’ve got for you this week. Take care and we’ll talk again soon. Bye-bye.

Speaker 2: For more great WordPress information head on over to yourwebsiteengineer.com.

Dustin: Alright, today we’re gonna talk about like I said, confer – comprehensive – com, com, what’s it called? Coherence Pro. Alright, today like I said, we’re gonna talk about ca, co, ugh. That’s what we’ll talk again. That’s what we’ll talk about next week. Take care and we’ll talk again – we’ll – how do I say it? We’ll talk again soon. That’s what we’ll talk about and we’ll take care and we’ll talk again then. Bye-bye.





Coherence 5 2 3 – Turn Websites Into Apps Using
Back to posts
This post has no comments - be the first one!

UNDER MAINTENANCE