In this post, we configure WebLogic and an in-memory data grid, such as Coherence and present scripts to start and stop the environment. We start with creating a Coherence Server (which will be our storage enabled node in the cluster). You can find the steps required to create a Coherence Server here.
When the server is created, click on the created server and subsequently on the server start, configuration tab, in order to set the class path and some JVM parameters.
Enter the following properties:
Above, we have specified the class path to included coherence.jar and \weblogic.server.modules.coherence.server_22.214.171.124.jar, which are needed to make Coherence available. The test.jar contains our Coherence configuration and serializable classes. These are presented in the post. JBoss RichFaces, Facelets and Coherence on WebLogic.
Note: The JVM parameters also included Coherence system settings, such as, -Dtangosol.coherence.mode=prod and -Dtangosol.coherence.cacheconfig=security-cache-config.xml. With the first one, we tell Coherence to run with production settings. The second one defines the cache configuration file to use. Unfortunately, the configuration provided in a Coherence override is not picked up. Read the full article here.
WebLogic 12c technical information: Java Message Service & Java Extensions & best practice upgrade
For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.