• clusteringMode: string
  Default Value: unicast

  Allowed Values: [ "multicast", "unicast" ]

  Specifies a clustering mode of either Unicast (default) or Multicast. If multicast is undesirable or unavailable in an environment, or when an environment is not properly configured to support multicast, then setting up the Well Known Addresses (WKA) feature is required. All cluster multicast communication is disabled if any of WKA, SSL, and/or secured production mode is/are enabled.

• clusterListenPort: integer(int32)
  Minimum Value: 0

  Maximum Value: 65535

  Default Value: 0

  The cluster listen port used by Coherence; Coherence cluster members use this port to discover and join, or create the cluster. If unspecified, the Coherence cluster multicast listen port will be used.

• globalSocketProvider: string

  Specify the Global Socket Provider name. If not specified and secured production mode is enabled, Coherence uses WebLogic SSL configuration as Global Socket Provider. Otherwise, use the specified Global Socket Provider.

• ignoreHostnameVerification: boolean
  Default Value: false

  Check if ignore hostname verification is set. In Secured Production Mode, Coherence hostname verification is enabled by default. If WebLogic isHostnameVerificationIgnored is set, then Coherence will inherite it through this property.

• multicastListenAddress: string

  The IP address for the cluster multicast listener.

• securedProduction: boolean
  Default Value: false

  Specify whether secured production mode is enabled. When it is not set, Coherence inherits the Secured Production Mode from WebLogic. Once Coherence Secured Production Mode is specified (Yes or No), then Coherence will no longer inherit the mode from WebLogic

  Default it to the corresponding WebLogic value:

  Constraints

  • secure default : true
• securityFrameworkEnabled: boolean

  Check if security framework is enabled

• timeToLive: integer(int32)
  Minimum Value: 0

  Maximum Value: 255

  Default Value: 4

  Sets the time-to-live (TTL) setting for the multicast message. The TTL setting designates how far multicast UDP/IP packets can travel on a network. The TTL is expressed in terms of how many hops a packet survives; each network interface, router, and managed switch is considered one hop. The TTL value should be set to the lowest integer value that works. Setting the value too high can use unnecessary bandwidth on other LAN segments and can even cause the operating system or network devices to disable multicast traffic.

  Typically, setting the TTL value to 1 works on a simple switched backbone. A value of 2 or more may be required on an advanced backbone with intelligent switching. A value of 0 is used for single server clusters that are used for development and testing.

• transport: string
  Allowed Values: [ "tmb", "tcp", "udp", "ssl", "ssludp", "sdmb", "imb" ]

  Specify the underlying transport protocol to use for cluster communication. Default is SSL when secured production mode is enabled; TMB otherwise.

  The transport type can be one of the following:

  • TMB: UDP + TMB

  • TCP: TCP + TMB

  • UDP: UDP + datagram

  • SSL: SSL over TCP + TMBS

  • SSLUDP: SSL over TCP + SSL over datagram

  • SDMB: UDP + SDMB

  • IMB: UDP + IMB

  Where: "TMB: UDP + TMB" means for transport type TMB, cluster service communication uses UDP; reliable point-to-point data service communication uses TMB. The default is TMB.

  The SDMB and IMB are only applicable to Exalogic environment.

• useVirtualThreads: boolean

  Check if use virtual threads is set. If WebLogic the KernelMBean.virtualThreadEnableOption or the weblogic.kernel.useVirtualThreads system property is set, Coherence inherites it through this property.

{
    "type":"object",
    "properties":{
        "clusterListenPort":{
            "default":"0",
            "minimum":"0",
            "maximum":"65535",
            "type":"integer",
            "format":"int32",
            "description":"<p>The cluster listen port used by Coherence; Coherence cluster members use this port to discover and join, or create the cluster. If unspecified, the Coherence cluster multicast listen port will be used.</p>"
        },
        "clusteringMode":{
            "default":"unicast",
            "enum":[
                "multicast",
                "unicast"
            ],
            "type":"string",
            "description":"<p>Specifies a clustering mode of either Unicast (default) or Multicast. If multicast is undesirable or unavailable in an environment, or when an environment is not properly configured to support multicast, then setting up the Well Known Addresses (WKA) feature is required. All cluster multicast communication is disabled if any of WKA, SSL, and/or secured production mode is/are enabled.</p>"
        },
        "globalSocketProvider":{
            "type":"string",
            "description":"<p>Specify the Global Socket Provider name. If not specified and secured production mode is enabled, Coherence uses WebLogic SSL configuration as Global Socket Provider. Otherwise, use the specified Global Socket Provider.</p>"
        },
        "ignoreHostnameVerification":{
            "default":false,
            "type":"boolean",
            "description":"<p>Check if ignore hostname verification is set. In Secured Production Mode, Coherence hostname verification is enabled by default.  If WebLogic isHostnameVerificationIgnored is set, then Coherence will inherite it through this property.</p>"
        },
        "multicastListenAddress":{
            "type":"string",
            "description":"<p>The IP address for the cluster multicast listener.</p>"
        },
        "securedProduction":{
            "x-weblogic-secureDefault":true,
            "default":false,
            "type":"boolean",
            "description":"<p>Specify whether secured production mode is enabled. When it is not set, Coherence inherits the Secured Production Mode from WebLogic. Once Coherence Secured Production Mode is specified (Yes or No), then Coherence will no longer inherit the mode from WebLogic</p><p>  Default it to the corresponding WebLogic value:</p><p><h5>Constraints</h5></p><ul><li>secure default : true</li></ul>"
        },
        "securityFrameworkEnabled":{
            "type":"boolean",
            "description":"<p>Check if security framework is enabled</p>"
        },
        "timeToLive":{
            "default":"4",
            "minimum":"0",
            "maximum":"255",
            "type":"integer",
            "format":"int32",
            "description":"<p>Sets the time-to-live (TTL) setting for the multicast message. The TTL setting designates how far multicast UDP/IP packets can travel on a network. The TTL is expressed in terms of how many hops a packet survives; each network interface, router, and managed switch is considered one hop. The TTL value should be set to the lowest integer value that works. Setting the value too high can use unnecessary bandwidth on other LAN segments and can even cause the operating system or network devices to disable multicast traffic.</p><p>Typically, setting the TTL value to 1 works on a simple switched backbone. A value of 2 or more may be required on an advanced backbone with intelligent switching. A value of 0 is used for single server clusters that are used for development and testing.</p>"
        },
        "transport":{
            "enum":[
                "tmb",
                "tcp",
                "udp",
                "ssl",
                "ssludp",
                "sdmb",
                "imb"
            ],
            "type":"string",
            "description":"<p>Specify the underlying transport protocol to use for cluster communication. Default is SSL when secured production mode is enabled; TMB otherwise.</p><p>The transport type can be one of the following:</p><ul><li><p>TMB: UDP + TMB</p></li><li><p>TCP: TCP + TMB</p></li><li><p>UDP: UDP + datagram</p></li><li><p>SSL: SSL over TCP + TMBS</p></li><li><p>SSLUDP: SSL over TCP + SSL over datagram</p></li><li><p>SDMB: UDP + SDMB</p></li><li><p>IMB: UDP + IMB</p></li></ul><p>Where: \"TMB: UDP + TMB\" means for transport type TMB, cluster service communication uses UDP; reliable point-to-point data service communication uses TMB. The default is TMB.</p><p>The SDMB and IMB are only applicable to Exalogic environment.</p>"
        },
        "useVirtualThreads":{
            "type":"boolean",
            "description":"<p>Check if use virtual threads is set. If WebLogic the KernelMBean.virtualThreadEnableOption or the weblogic.kernel.useVirtualThreads system property is set, Coherence inherites it through this property.</p>"
        }
    },
    "description":""
}