...
Sample application policy definition JSON
The following are sample configurations that can be used in a JSON to define an application policy:
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
...
| Panel | |||||
|---|---|---|---|---|---|
|
Main properties
| Property |  W |  R |  U | Description |  M |  DV | Data Type | Example | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| JSON | UI | ||||||||||||||
id | √ | √ | ID of the application policy. | Yes | N/A | String | application-policy-1 | ||||||||
algorithm | √ | √ | Defines the algorithm that needs to be applied between network partitions. The available algorithms are as follows:
| Yes | N/A | String | one-after-another | ||||||||
networkPartitions | √ | √ | This defines one or more partitions that are network bound and where communication among the partitions take place very efficiently. For more information, see Partition Groups. | Yes | N/A | String | network-partition-1 | ||||||||
properties | √ | √ | This defines any properties that need to be passed in the application policy JSON. The properties will be listed as name value pairs. For more information on the sub-properties, see properties. | No | N/A | properties array | N/A | ||||||||
Sub-properties
properties
| Property | W | R | U | Description | M | DV | Data Type | Example | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| JSON | UI | ||||||||||||||
| √ | √ | Name of the property being passed as a name value pair. | No | N/A | String | key-1 | ||||||||
| √ | √ | Value that corresponds to the name value pair. | No | N/A | String | value-2 | ||||||||