{
    "type":"object",
    "properties":{
        "WANSessionPersistenceTableName":{
            "default":"WLS_WAN_PERSISTENCE_TABLE",
            "type":"string",
            "description":"<p>Return the name of the table to be used for WAN session persistence.</p>"
        },
        "additionalAutoMigrationAttempts":{
            "default":"3",
            "type":"integer",
            "format":"int32",
            "description":"<p>A migratable server could fail to come up on every possible configured machine. This attribute controls how many further attempts, after the first one, should be tried.</p><p>Note that each attempt specified here indicates another full circuit of migrations amongst all the configured machines. So for a 3-server cluster, and the default value of 3, a total of 9 migrations will be attempted.</p><p>If it is set to -1, migrations will go on forever until the server starts.</p>"
        },
        "asyncSessionQueueTimeout":{
            "default":"30",
            "type":"integer",
            "format":"int32",
            "description":"<p>Interval in seconds until the producer thread will wait for the AsyncSessionQueue to become unblocked.  Should be similar to the RequestTimeOut as that will determine the longest that the queue should remain full.</p>"
        },
        "autoMigrationTableCreationDDLFile":{
            "default":null,
            "x-weblogic-legalNull":true,
            "type":"string",
            "description":"<p>The absolute file path of a custom DDL file for creating the automatic migration database table.</p><p>This setting applies only if the <code>MigrationBasis</code> attribute is set to <code>database</code>, the <code>AutoMigrationTableCreationPolicy</code> attribute is set to <code>Always</code>, and the table name specified by the <code>AutoMigrationTableName</code> attribute does not already exist in the database.</p><p>If the above conditions apply, and this setting is set to the default, then the system will try to find a default DDL file for the creating the leasing database table in <code>WL_HOME/server/db/DB_TYPE/leasing.ddl</code></p><p>Note that the system ignores (skips) any <code>DROP</code> commands in the DDL file, and substitutes the value configured in the <code>AutoMigrationTableName</code> attribute for all occurrences of the word <code>ACTIVE</code> in the file.</p><p><h5>Constraints</h5></p><ul><li>legal null</li></ul>"
        },
        "autoMigrationTableCreationPolicy":{
            "default":"Disabled",
            "enum":[
                "Disabled",
                "Always"
            ],
            "type":"string",
            "description":"<p>Control automatic leasing table creation behavior.</p><p>This setting applies only if the <code>MigrationBasis</code> attribute is set to <code>database</code></p><ul><li><p><code>Disabled</code></p><p>Disables automatic leasing table creation. The behavior is same as manual table creation. Any singletons dependent on cluster leasing will fail to start unless the table defined by the <code>AutoMigrationTableName</code> already exists in the database.</p></li><li><p><code>Always</code></p><p>Force automatic leasing table creation if the table is not found. The default table name is \"ACTIVE\" and can be customized using the <code>AutoMigrationTableName</code> attribute. The SQL used to create the table when it is not found can be customized using the <code>AutoMigrationTableCreationDDLFile</code> attribute.</p></li></ul>"
        },
        "autoMigrationTableName":{
            "default":"ACTIVE",
            "type":"string",
            "description":"<p>Return the name of the table to be used for server migration.</p><p>This setting applies only if the <code>MigrationBasis</code> attribute is set to <code>database</code></p><p>If the <code>AutoMigrationTableCreationPolicy</code> is set to <code>Always</code>, then the table name format must be specified in the form <code>[[[mycatalog.]myschema.]mytablename</code>; for example <code>myschema.mytablename</code>.  Each period symbol format is significant, where schema generally corresponds to username in many databases.</p><p>When no table name is specified, the table name is simply <code>ACTIVE</code> and the database implicitly determines the schema according to the JDBC data source user.</p>"
        },
        "candidateMachinesForMigratableServers":{
            "x-weblogic-restartRequired":true,
            "title":"Machine References",
            "type":"array",
            "items":{
                "title":"Machine Reference",
                "type":"object",
                "properties":{
                    "identity":{
                        "title":"Identity",
                        "type":"array",
                        "items":{
                            "type":"string",
                            "description":""
                        },
                        "description":"DOC TEAM TBD - describe an identity - it's a reference to another WLS REST resource."
                    }
                },
                "description":"Contains the machine reference."
            },
            "description":"Contains the array of machine references. <p>The set of machines (and order of preference) on which Node Manager will restart failed servers. (Requires you to enable each server for automatic migration.)</p><p>Each server can specify a subset of these cluster-wide candidates, which limits the machines on which the server can be restarted. Servers can also specify their own order of preference.</p><p><h5>Constraints</h5></p><ul><li>restart required</li></ul>"
        },
        "clientCertProxyEnabled":{
            "default":false,
            "type":"boolean",
            "description":"<p>Specifies whether to honor the WL-Proxy-Client-Cert header coming with the request or not. </p>"
        },
        "clusterAddress":{
            "type":"string",
            "description":"<p>The address that forms a portion of the URL a client uses to connect to this cluster, and that is used for generating EJB handles and entity EJB failover addresses. (This address may be either a DNS host name that maps to multiple IP addresses or a comma-separated list of single address host names or IP addresses.)</p><p>Defines the address to be used by clients to connect to this cluster. This address may be either a DNS host name that maps to multiple IP addresses or a comma separated list of single address host names or IP addresses. If network channels are configured, it is possible to set the cluster address on a per channel basis.</p>"
        },
        "clusterBroadcastChannel":{
            "type":"string",
            "description":"<p>Specifies the channel used to handle communications within a cluster. If no channel is specified the default channel is used.</p><p>ClusterBroadcastChannel is only are supported if the unicast messaging type is used.</p>"
        },
        "clusterMessagingMode":{
            "default":"unicast",
            "enum":[
                "multicast",
                "unicast"
            ],
            "type":"string",
            "description":"<p>Specifies the messaging type used in the cluster.</p><p>Multicast messaging is provided for backwards compatibility.</p>"
        },
        "clusterType":{
            "default":"none",
            "enum":[
                "none",
                "wan",
                "man"
            ],
            "type":"string",
            "description":"<p>Optimizes cross-cluster replication for the type of network that servers in the clusters use for administrative communication.</p><p>To enhance the reliability of HTTP sessions, you can configure servers in one cluster to replicate the session data to servers in a different cluster. In such an environment, configure the clusters to be one of the following types:</p><ul><li><p><code>man</code></p><p>If the clustered servers can send their data through a metro area network (man) in which latency is negligible. With this ClusterType value, servers replicate session state synchronously and in memory only. For example, when serverA in cluster1 starts an HTTP session, its backup server, serverB in cluster2, immediately replicates this session in memory to Server B.</p></li><li><p><code>wan</code></p><p>If the clusters are far apart or send their data through a wide area network (wan) that experiences significant network latency. With this ClusterType value, a server replicates session state synchronously to the backup server in the same cluster and asynchronously to a server in the remote cluster. For example, when serverA in cluster1 starts an HTTP session, it sends the data to serverB in cluster1 and then asynchronously sends data to serverX in cluster 2. ServerX will persist the session state in the database.</p><p>If you persist session data in a replicating database, and if you prefer to use the database to replicate the data instead of WebLogic Server, choose a cluster type of <code>wan</code> and leave the remote cluster address undefined. WebLogic Server saves the session data to the local database and assumes that the database replicates data as needed.</p></li></ul>"
        },
        "coherenceClusterSystemResource":{
            "x-weblogic-restartRequired":true,
            "title":"Coherence Cluster System Resource Reference",
            "type":"array",
            "items":{
                "type":"string",
                "description":""
            },
            "description":"Contains the coherence cluster system resource reference. <p>Coherence Cluster associated with this cluster.</p><p><h5>Constraints</h5></p><ul><li>restart required</li></ul>"
        },
        "concurrentSingletonActivationEnabled":{
            "default":false,
            "type":"boolean",
            "description":"<p>Specifies whether to allow the concurrent activation, deactivation, or restart of two or more singleton services.</p>"
        },
        "dataSourceForAutomaticMigration":{
            "x-weblogic-restartRequired":true,
            "title":"JDBC System Resource Reference",
            "type":"array",
            "items":{
                "type":"string",
                "description":""
            },
            "description":"Contains the JDBC system resource reference. <p>The data source used by servers in the cluster during migration. (You must configure each Migratable Server within the cluster to use this data source.)</p><p>This setting applies only if the <code>MigrationBasis</code> attribute is set to <code>database</code></p><p><h5>Constraints</h5></p><ul><li>restart required</li></ul>"
        },
        "dataSourceForJobScheduler":{
            "x-weblogic-restartRequired":true,
            "title":"JDBC System Resource Reference",
            "type":"array",
            "items":{
                "type":"string",
                "description":""
            },
            "description":"Contains the JDBC system resource reference. <p>Data source required to support persistence of jobs scheduled with the job scheduler</p><p><h5>Constraints</h5></p><ul><li>restart required</li></ul>"
        },
        "dataSourceForSessionPersistence":{
            "x-weblogic-restartRequired":true,
            "title":"JDBC System Resource Reference",
            "type":"array",
            "items":{
                "type":"string",
                "description":""
            },
            "description":"Contains the JDBC system resource reference. <p>To support HTTP Session failover across data centers, a datasource is required to dump session state on disk.</p><p><h5>Constraints</h5></p><ul><li>restart required</li></ul>"
        },
        "databaseLeasingBasisConnectionRetryCount":{
            "default":"1",
            "minimum":"1",
            "type":"integer",
            "format":"int32",
            "description":"<p>The maximum number of times Database Leasing will try to obtain a valid connection from the Data Source.</p>"
        },
        "databaseLeasingBasisConnectionRetryDelay":{
            "default":"1000",
            "type":"integer",
            "format":"int64",
            "description":"<p>The length of time, in milliseconds,Database Leasing will wait before attempting to obtain a new connection from the Data Source when a connection has failed.</p>"
        },
        "defaultLoadAlgorithm":{
            "default":"round-robin",
            "enum":[
                "round-robin",
                "weight-based",
                "random",
                "round-robin-affinity",
                "weight-based-affinity",
                "random-affinity"
            ],
            "type":"string",
            "description":"<p>Defines the algorithm to be used for load-balancing between replicated services if none is specified for a particular service. The <code>round-robin</code> algorithm cycles through a list of WebLogic Server instances in order. <code>Weight-based</code> load balancing improves on the round-robin algorithm by taking into account a pre-assigned weight for each server. In <code>random</code> load balancing, requests are routed to servers at random.</p>"
        },
        "dynamicallyCreated":{
            "readOnly":true,
            "default":false,
            "type":"boolean",
            "description":"<p>Return whether the MBean was created dynamically or is persisted to config.xml</p>"
        },
        "fencingGracePeriodMillis":{
            "default":"30000",
            "type":"integer",
            "format":"int32",
            "description":"<p>During automatic migration, if the Cluster Master determines a server to be dead, it waits for this period of time (in milliseconds) before the Cluster Master migrates the service to another server in the cluster.</p>"
        },
        "frontendHTTPPort":{
            "default":"0",
            "type":"integer",
            "format":"int32",
            "description":"<p>The name of the HTTP port to which all redirected URLs will be sent.</p><p>Sets the FrontendHTTPPort for the default webserver (not virtual hosts) for all the servers in the cluster. Provides a method to ensure that the webapp will always have the correct PORT information, even when the request is coming through a firewall or a proxy. If this parameter is configured, the HOST header will be ignored and the information in this parameter will be used in its place, when constructing the absolute urls for redirects.</p>"
        },
        "frontendHTTPSPort":{
            "default":"0",
            "type":"integer",
            "format":"int32",
            "description":"<p>The name of the secure HTTP port to which all redirected URLs will be sent.</p><p>Sets the FrontendHTTPSPort for the default webserver (not virtual hosts) for all the servers in the cluster. Provides a method to ensure that the webapp will always have the correct PORT information, even when the request is coming through a firewall or a proxy. If this parameter is configured, the HOST header will be ignored and the information in this parameter will be used in its place, when constructing the absolute urls for redirects.</p>"
        },
        "frontendHost":{
            "default":null,
            "type":"string",
            "description":"<p>The name of the host to which all redirected URLs will be sent.</p><p>Sets the HTTP FrontendHost for the default webserver (not virtual hosts) for all the servers in the cluster. Provides a method to ensure that the webapp will always have the correct HOST information, even when the request is coming through a firewall or a proxy. If this parameter is configured, the HOST header will be ignored and the information in this parameter will be used in its place, when constructing the absolute urls for redirects.</p>"
        },
        "greedySessionFlushInterval":{
            "default":"3",
            "type":"integer",
            "format":"int32",
            "description":"<p>Interval in seconds until HTTP Sessions are periodically flushed to secondary server.</p>"
        },
        "healthCheckIntervalMillis":{
            "default":"10000",
            "type":"integer",
            "format":"int32",
            "description":"<p>Interval in milliseconds at which Migratable Servers and Cluster Masters prove their liveness via the database.</p>"
        },
        "healthCheckPeriodsUntilFencing":{
            "default":"6",
            "minimum":"2",
            "type":"integer",
            "format":"int32",
            "description":"<p>Maximum number of periods that a cluster member will wait before timing out a Cluster Master and also the maximum number of periods the Cluster Master will wait before timing out a Migratable Server.</p>"
        },
        "httpTraceSupportEnabled":{
            "default":false,
            "type":"boolean",
            "description":"<p>Returns the value of HttpTraceSupportEnabled. </p>"
        },
        "id":{
            "readOnly":true,
            "type":"integer",
            "format":"int64",
            "description":"<p>Return the unique id of this MBean instance</p>"
        },
        "idlePeriodsUntilTimeout":{
            "default":"3",
            "minimum":"3",
            "type":"integer",
            "format":"int32",
            "description":"<p>Maximum number of periods that a cluster member will wait before timing out a member of a cluster.</p><p>Maximum number of periods that a cluster member will wait before timing out a member of a cluster.</p>"
        },
        "interClusterCommLinkHealthCheckInterval":{
            "default":"30000",
            "type":"integer",
            "format":"int32",
            "description":"<p>If the cluster link between two clusters goes down, a trigger will run periodically to see if the link is restored. The duration is specified in milliseconds.</p>"
        },
        "jobSchedulerTableName":{
            "default":"WEBLOGIC_TIMERS",
            "type":"string",
            "description":"<p>The table name to use for storing timers active with the job scheduler</p>"
        },
        "maxSecondarySelectionAttempts":{
            "default":"0",
            "type":"integer",
            "format":"int32",
            "description":"<p>This is the max number of attempts at choosing a suitable secondary server for replication.If it is set to 0,secondary server selection for replication will be tried on all servers in the cluster. </p>"
        },
        "memberDeathDetectorEnabled":{
            "default":false,
            "type":"boolean",
            "description":"<p>Enables faster Automatic Service Migration times with Database Leasing Basis.</p>"
        },
        "memberWarmupTimeoutSeconds":{
            "minimum":"0",
            "type":"integer",
            "format":"int32",
            "description":"<p>Maximum number of seconds that a cluster member will wait to discover and synchronize with other servers in the cluster. Normally, the member will be able to sync in 30 seconds. If the value of this attribute is higher, that does not necessarily mean that it will take longer for the member to warmup. Instead it defines an upper bound on the time that a server will wait to sync with the servers that it has discovered. If the value is set 0, servers will not attempt to discover other running server in the cluster during server initialization</p>"
        },
        "messageOrderingEnabled":{
            "default":true,
            "type":"boolean",
            "description":"<p>Forces unicast messages to be processed in order. There are scenarios where JMS may update JNDI very frequently. It will result in a lot of messages over unicast. Due to the close proximity of messages the probability of out of order handling of messages increases which would trigger frequent state dumps. Frequent JNDI tree refresh may result in NameNotFoundException. Use this property to prevent out of order handling of messages.</p>"
        },
        "migratableTargets":{
            "readOnly":true,
            "title":"Migratable Target References",
            "type":"array",
            "items":{
                "title":"Migratable Target Reference",
                "type":"object",
                "properties":{
                    "identity":{
                        "title":"Identity",
                        "type":"array",
                        "items":{
                            "type":"string",
                            "description":""
                        },
                        "description":"DOC TEAM TBD - describe an identity - it's a reference to another WLS REST resource."
                    }
                },
                "description":"Contains the migratable target reference."
            },
            "description":"Contains the array of migratable target references. <p>Returns all the MigratableTargets for this cluster</p>"
        },
        "migrationBasis":{
            "default":"database",
            "enum":[
                "database",
                "consensus"
            ],
            "type":"string",
            "description":"<p>Controls the mechanism used for server and service migration.</p><ul><li><p><b>Database</b> -- Requires the availability of a high-availability database, such as Oracle RAC, to store leasing information. Requires also configuring the <code>DataSourceForAutomaticMigration</code> attribute. Optionally also configure <code>AutoMigrationTableName</code> (default is \"ACTIVE\"), <code>AutoMigrationTableCreationPolicy</code>, and <code>AutoMigrationTableCreationDDLFile</code></p></li><li><p><b>Consensus</b> -- Stores the leasing information in-memory within a cluster member. This option requires Node Manager to be configured and running.</p></li></ul><p><b>Note:</b> Within a WebLogic Server installation, you can only use one type of leasing. Although it is possible to implement multiple features that use leasing within your environment, each must use the same kind of leasing.</p>"
        },
        "millisToSleepBetweenAutoMigrationAttempts":{
            "default":"180000",
            "type":"integer",
            "format":"int64",
            "description":"<p>Controls how long of a pause there should be between the migration attempts described in getAdditionalAutoMigrationAttempts(). Note that this delay only happens when the server has failed to come up on every machine.</p>"
        },
        "multicastAddress":{
            "default":"239.192.0.0",
            "type":"string",
            "description":"<p>The multicast address used by cluster members to communicate with each other.</p><p>The valid range is from from 224.0.0.0 to 239.255.255.255. The default value used by WebLogic Server is 239.192.0.0.  You should avoid using multicast addresses in the range x.0.0.1</p><p>This address should be unique to this cluster and should not be shared by other applications.</p>"
        },
        "multicastBufferSize":{
            "default":"64",
            "minimum":"64",
            "type":"integer",
            "format":"int32",
            "description":"<p>The multicast socket send/receive buffer size (at least 64 kilobytes).</p><p>Returns the multicast socket send/receive buffer size.</p>"
        },
        "multicastDataEncryption":{
            "default":false,
            "type":"boolean",
            "description":"<p>Enables multicast data to be encrypted. Only the multicast data is encrypted. Multicast header information is not encrypted.</p>"
        },
        "multicastPort":{
            "default":"7001",
            "minimum":"1",
            "maximum":"65535",
            "type":"integer",
            "format":"int32",
            "description":"<p>The multicast port (between 1 and 65535) used by cluster members to communicate with each other.</p><p>Defines the multicast port used by cluster members to communicate with each other.</p>"
        },
        "multicastSendDelay":{
            "default":"3",
            "minimum":"0",
            "maximum":"250",
            "type":"integer",
            "format":"int32",
            "description":"<p>The amount of time (between 0 and 250 milliseconds) to delay sending message fragments over multicast in order to avoid OS-level buffer overflow.</p><p>Defines the number of milliseconds to delay sending message fragments over multicast in order to avoid OS-level buffer overflow.</p>"
        },
        "multicastTTL":{
            "default":"1",
            "minimum":"1",
            "maximum":"255",
            "type":"integer",
            "format":"int32",
            "description":"<p>The number of network hops (between 1 and 255) that a cluster multicast message is allowed to travel.</p><p>Defines the number of network hops that a cluster multicast message is allowed to travel. 1 restricts the cluster to one subnet.</p>"
        },
        "name":{
            "readOnly":true,
            "x-weblogic-legalNull":true,
            "type":"string",
            "description":"<p>The user-specified name of this MBean instance.</p><p>This name is included as one of the key properties in the MBean's <code>javax.management.ObjectName</code></p><p><code>Name=<i>user-specified-name</i></code></p><p><h5>Constraints</h5></p><ul><li>legal null</li></ul>"
        },
        "notes":{
            "type":"string",
            "description":"<p>Optional information that you can include to describe this configuration.</p><p>WebLogic Server saves this note in the domain's configuration file (<code>config.xml</code>) as XML PCDATA. All left angle brackets (<) are converted to the XML entity <code>&lt;</code>. Carriage returns/line feeds are preserved.</p><p>Note: If you create or edit a note from the Administration Console, the Administration Console does not preserve carriage returns/line feeds.</p>"
        },
        "numberOfServersInClusterAddress":{
            "default":"3",
            "minimum":"1",
            "type":"integer",
            "format":"int32",
            "description":"<p>Number of servers to be listed from this cluster when generating a cluster address automatically. This setting has no effect if Cluster Address is explicitly set.</p>"
        },
        "oneWayRmiForReplicationEnabled":{
            "default":false,
            "type":"boolean",
            "description":"<p>Indicates if one-way RMI is being used for replication. One-way RMI also requires configuring replication ports on each server in the cluster.</p>"
        },
        "persistSessionsOnShutdown":{
            "type":"boolean",
            "description":"<p>When shutting down servers, sessions are not updated. If the primary and secondary servers of a session are shut down with no session updates, the session will be lost. Turning on PersistSessionsOnShutdown will save any active sessions to the database specified in ClusterMBean#getDataSourceForSessionPersistence() when a server is shutdown. The sessions will not be written at any other time. (For example, they are not saved via this mechanism if there is a server crash.)</p><p>This attribute is applicable both to session persistence on server shutdown or session persistence across a WAN.</p><p>Rolling upgrade can potentially have a bad interaction with traditional in-memory session replication.  As managed servers are shutdown and upgraded, in-memory servlet sessions will be lost if both primary and secondary are rebooted before a new request arrives for the session.</p>"
        },
        "rebalanceDelayPeriods":{
            "default":"2",
            "minimum":"2",
            "type":"integer",
            "format":"int32",
            "description":"<p>Gets the number of the Rebalance periods to wait to rebalance cluster targeted JMS instances in an idle system (typically 10 seconds per period).  <b>Note:</b> This setting only applies when a JMS artifact is cluster-targeted, its Rebalance Enabled is set to <code>true</code>, and its Migration Policy is set to <code>On-Failure</code> or <code>Always</code></p>"
        },
        "remoteClusterAddress":{
            "type":"string",
            "description":"<p>Set the foreign cluster. Cluster infrastructure uses this address to connect to foreign cluster for HTTP Session WAN/MAN failover.</p>"
        },
        "replicationChannel":{
            "default":"ReplicationChannel",
            "type":"string",
            "description":"<p>The channel name to be used for replication traffic. Cluster infrastructure uses this channel to send updates for HTTP sessions and stateful session beans. If none is set then the default channel will be used.</p><p>In order for this feature to work, the named channel must exist on all members of the cluster and must be configured to use the same protocol. It is valid for the selected channel to be configured to use a secure protocol.</p>"
        },
        "replicationTimeoutEnabled":{
            "default":true,
            "type":"boolean",
            "description":"<p>Indicates if timeout should be applied to session replication calls.</p>"
        },
        "replicationTimeoutMillis":{
            "type":"integer",
            "format":"int32",
            "description":"<p>Interval in milliseconds at which Migratable Servers and Cluster Masters prove their liveness via the database.</p>"
        },
        "secureReplicationEnabled":{
            "x-weblogic-secureDefault":true,
            "default":false,
            "type":"boolean",
            "description":"<p>Servers in a cluster replicate session data. If a replication channel is defined then the session data will be sent using the replication channel protocol and secured replication settings will be ignored. If no replication channel is defined and secured replication is enabled then session data for in-memory replication will be sent over SSL using the default secured channel. However, this added security for replication traffic comes with a significant cluster performance degradation. It should only be enabled if security is of greater concern than performance degradation.</p><p><h5>Constraints</h5></p><ul><li>secure default : true</li></ul>"
        },
        "servers":{
            "readOnly":true,
            "title":"Server References",
            "type":"array",
            "items":{
                "title":"Server Reference",
                "type":"object",
                "properties":{
                    "identity":{
                        "title":"Identity",
                        "type":"array",
                        "items":{
                            "type":"string",
                            "description":""
                        },
                        "description":"DOC TEAM TBD - describe an identity - it's a reference to another WLS REST resource."
                    }
                },
                "description":"Contains the server reference."
            },
            "description":"Contains the array of server references. <p>The servers which have declared membership in this cluster.</p>"
        },
        "serviceActivationRequestResponseTimeout":{
            "default":"0",
            "type":"integer",
            "format":"int32",
            "description":"<p>The maximum time, in milliseconds seconds, for services to wait for response from cluster members.</p>"
        },
        "serviceAgeThresholdSeconds":{
            "default":"180",
            "minimum":"0",
            "maximum":"65534",
            "type":"integer",
            "format":"int32",
            "description":"<p>The number of seconds (between 0 and 65534) by which the age of two conflicting services must differ before one is considered older than the other.</p><p>Defines the number of seconds by which the age of two conflicting services must differ before one is considered older than the other.</p>"
        },
        "sessionFlushInterval":{
            "default":"180",
            "type":"integer",
            "format":"int32",
            "description":"<p>Interval in seconds until HTTP Sessions are periodically flushed to the backup cluster to dump session state on disk.</p>"
        },
        "sessionFlushThreshold":{
            "default":"10000",
            "type":"integer",
            "format":"int32",
            "description":"<p>When number of sessions to be flushed reaches this threshold limit, sessions will be flushed to the backup cluster before the flush interval. This helps the server to flush sessions faster under load.</p>"
        },
        "sessionLazyDeserializationEnabled":{
            "type":"boolean",
            "description":"<p>Enables increased efficiency with session replication. Enabling this attribute should be used only when configuring a WebLogic domain for Oracle Exalogic.</p>"
        },
        "sessionStateQueryProtocolEnabled":{
            "default":false,
            "type":"boolean",
            "description":"<p>Indicates if session state query protocol is enabled.  The Session State Query protocol will query the local cluster for the location of a session state instance if a request arrives at a server that is neither the primary or secondary server.</p>"
        },
        "sessionStateQueryRequestTimeout":{
            "default":"30",
            "minimum":"1",
            "type":"integer",
            "format":"int32",
            "description":"<p>The maximum time, in seconds, for session state query request to wait for response from cluster members.</p>"
        },
        "singletonServiceRequestTimeout":{
            "default":"30000",
            "type":"integer",
            "format":"int32",
            "description":"<p>The maximum time, in milliseconds, for service activation requests will wait for response from cluster members.  </p><p>A value of <code></code> means that the request will wait indefinitely to complete.</p>"
        },
        "siteName":{
            "type":"string",
            "description":"<p>The name of the site this cluster is associated with.</p>"
        },
        "tags":{
            "title":"Items",
            "type":"array",
            "items":{
                "type":"string",
                "description":""
            },
            "description":"<p>Return all tags on this Configuration MBean</p>"
        },
        "txnAffinityEnabled":{
            "default":false,
            "type":"boolean",
            "description":"<p>If enabled, a server's transaction requests go to servers in the cluster that are already participating in the global transaction.</p>"
        },
        "type":{
            "readOnly":true,
            "x-weblogic-unharvestable":true,
            "type":"string",
            "description":"<p>Returns the type of the MBean.</p><p><h5>Constraints</h5></p><ul><li>unharvestable</li></ul>"
        },
        "unicastReadTimeout":{
            "default":"15000",
            "type":"integer",
            "format":"int32",
            "description":"<p>The specified read timeout, in milliseconds, on a unicast connection.  A timeout of zero is interpreted as an infinite timeout, that is blocking read forever.</p>"
        },
        "weblogicPluginEnabled":{
            "default":false,
            "type":"boolean",
            "description":"<p>Specifies if this cluster will receive requests from a proxy plug-in or <code>HttpClusterServlet</code></p><p>Set this attribute to <code>true</code> if the cluster will receive requests from a proxy plug-in or <code>HttpClusterServlet</code>. A call to <code>getRemoteAddr</code> will return the address of the browser client from the proprietary <code>WL-Proxy-Client-IP</code> header instead of the Web server.</p><p>Set this attribute to <code>false</code> to disable the <code>weblogic-plugin-enabled</code> parameter, <code>weblogic-plugin-enabled=false</code>, in the <code>config.xml</code>file.</p><p>Note: If you are using Oracle HTTP Server, the WebLogic Proxy Plug-In, or Oracle Traffic Director to distribute client requests to a Managed Server or a cluster, Oracle recommends setting this attribute to <code>true</code></p>"
        }
    },
    "description":""
}