Below is a quick overview of a new feature introduced in WebLogic Server 10.3.4 that continues to deepen the Coherence and WebLogic Server integration. Previously Oracle introduced Coherence Clusters as a concept that could be used to manage Coherence configuration for instances of Coherence that ran inside of WebLogic Server JVMs. Now Oracle has introduced Coherence Servers, which are stand-alone JVMs not running inside WebLogic Server that are thin wrappers around a Coherence DefaultCacheServer. The Coherence Server can reference the Coherence Cluster configuration as well as specify fine-grained settings for each Coherence Server such as a name, port, classpath, and JVM options. This feature ties into WebLogic Server Node Manager, which is a process that can always be running as a service on each operating system instance where your WebLogic or Coherence processes can run. From one central location WebLogic Server users can easily manage the configuration and lifecycle of their Coherence JVMs in addition to their WebLogic Server JVMs potentially running on many, many different hosts. This should be a useful feature for customers that use WebLogic Server and Coherence together as well as for Coherence customers that do not utilize WebLogic Server much today, but would like additional manageability and control over Coherence processes. Check out the documentation for detail and examples of scripts. There is a short (5 min) screencast below.