How To Connect The GAR Scoped Cache Services Deployed on a WebLogic Server Domain Using Coherence Console Client?
(Doc ID 2334313.1)
Last updated on NOVEMBER 09, 2020
Applies to:Oracle Coherence - Version 220.127.116.11.0 and later
Oracle WebLogic Server - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Coherence applications must be packaged as a GAR module for deployment. A GAR module includes the artifacts that comprise a Coherence application and adheres to a specific directory structure. A GAR can be left as an unarchived directory or can be archived with a .gar extension. A GAR is deployed as both a standalone module and within an EAR. If a GAR is used for deployment on a cache server, then cache services are restricted by an application scope name. Clients must use the same application scope name; otherwise, the clients cannot access the cache services. By default Out-Of-The-Box, coherence console script (coherence.sh/.cmd) is not ready to connect to the GAR scoped services deployed on a WebLogic Domain based coherence cluster. The below helps to customize the coherence.sh script and ensure that joins the scope based cluster cache services.
How to configure coherence console to join to the WLS cluster and access the GAR scope cache services?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document