The request body defines the details of the create request.
Root Schema : addotd-postrequestm
Type: object
Show Source
{
"required":[
"components"
],
"properties":{
"components":{
"type":"object",
"required":[
"OTD"
],
"description":"Groups properties for the Oracle Traffic Director component (<code>OTD</code>).",
"properties":{
"OTD":{
"type":"object",
"description":"Properties for the Oracle Traffic Director (OTD) component.",
"properties":{
"adminPort":{
"type":"integer",
"description":"Port for accessing Oracle Traffic Director using HTTP. The default value is <code>8989</code>."
},
"adminPassword":{
"type":"string",
"description":"Password for the Oracle Traffic Director administrator. The password must meet the following requirements:<ul><li>Starts with a letter</li><li>Is between 8 and 30 characters long</li><li>Has one or more upper case letters</li><li>Has one or more lower case letters</li><li>Has one or more numbers</li><li>Has one or more of the following special characters: hyphen (-), underscore (_), pound sign (#), dollar sign ($). If Exadata is the database for the service instance, the password cannot contain the dollar sign ($).</li></ul><p>If an administrator password is not explicitly set, the OTD administrator password defaults to the WebLogic Server (WLS) administrator password."
},
"adminUserName":{
"type":"string",
"description":"User name for the Oracle Traffic Director administrator. The name must be between 8 and 128 characters long and cannot contain any of the following characters:<ul><li>Tab</li><li>Brackets</li><li>Parentheses</li><li>The following special characters: left angle bracket (<), right angle bracket (>), ampersand (&), pound sign (#), pipe symbol (|), and question mark (?).</li></ul><p>If a username is not explicitly set, the OTD user name defaults to the WebLogic Server (WLS) administrator user name."
},
"haEnabled":{
"type":"boolean",
"description":"Flag that specifies whether the local load balancer HA is enabled. This value defaults to <code>false</code> (that is, HA is not enabled)."
},
"ipReservations":{
"type":"array",
"description":"This attribute is not applicable to Oracle SOA Cloud Service instances in Oracle Cloud Infrastructure.<p>A single IP reservation name or two names separated by a comma.<p>Reserved or pre-allocated IP addresses can be assigned to the local load balancer nodes. The number of names in <code>ipReservations</code> must match the number of load balancer nodes you are provisioning.<p>Note the difference between accounts where regions are supported and not supported.<ul><li>Where regions are supported: You can only use those reserved IPs created in the region where the Oracle SOA Cloud Service instance is provisioned. <p>See IP Reservations REST Endpoints for information about how to find unused IP reservations and, if needed, create new IP reservations.</li><li>Where regions are not supported: If your Oracle SOA Cloud Service instance is associated with an Oracle Database Exadata Cloud Service database deployment, you must first submit a request to get the IP reservations. See the My Oracle Support document titled <i>How to Request Authorized IPs for Provisioning an Oracle SOA Cloud Service with Database Exadata Cloud Service</i> (MOS Note 2163568.1).</li></ul>",
"items":{
"type":"string"
}
},
"listenerPort":{
"type":"integer",
"description":"Listener port for the local load balancer for accessing deployed applications using HTTP. The default value is <code>8080</code>.<p>This value is overridden by <code>privilegedListenerPort</code> unless its value is set to 0. This value has no effect if the local load balancer is disabled."
},
"listenerPortEnabled":{
"type":"boolean",
"description":"Flag that specifies whether the non-secure listener port is enabled on the local load balancer. The default value is <code>true</code>."
},
"loadBalancingPolicy":{
"type":"string",
"description":"Policy to use for routing requests to the load balancer. Valid policies include: <ul><li><code>LEAST_CONNECTION_COUNT</code> - Passes each new request to the Managed Server with the least number of connections. This policy is useful for smoothing distribution when Managed Servers get bogged down. Managed Servers with greater processing power to handle requests will receive more connections over time. This is the default.</li><li><code>LEAST_RESPONSE_TIME</code> - Passes each new request to the Managed Server with the fastest response time. This policy is useful when Managed Servers are distributed across networks.</li><li><code>ROUND_ROBIN</code> - Passes each new request to the next Managed Server in line, evenly distributing requests across all Managed Servers regardless of the number of connections or response time.</li></ul>"
},
"privilegedListenerPort":{
"type":"integer",
"description":"Privileged listener port for accessing the deployed applications using HTTP. The default value is <code>80</code>.<p>This value has no effect if the local load balancer is disabled.<p>To disable the privileged listener port, set the value to 0. In this case, if the local load balancer is provisioned, the listener port defaults to <code>listenerPort</code>, if specified, or <code>8080</code>."
},
"privilegedSecuredListenerPort":{
"type":"integer",
"description":"Privileged listener port for accessing the deployed applications using HTTPS. The default value is <code>443</code>.<p>This value has no effect if the local load balancer is disabled.<p>To disable the privileged listener port, set the value to 0. In this case, if the local load balancer is provisioned, the listener port defaults to <code>securedListenerPort</code>, if specified, or <code>8081</code>."
},
"securedListenerPort":{
"type":"integer",
"description":"Secured listener port for accessing the deployed applications using HTTPS. The default value is <code>8081</code>.<p>This value is overridden by <code>privilegedSecuredContentPort</code> unless its value is set to 0. This value has no effect if the local load balancer is disabled."
},
"shape":{
"type":"string",
"description":"Desired compute shape for the local balancer nodes. A shape defines the number of Oracle Compute Units (OCPUs) and amount of memory (RAM). Valid shapes on Oracle Cloud Infrastructure Classic include: <ul><li>oc3: 1 OCPU, 7.5 GB memory</li><li>oc4: 2 OCPUs, 15 GB memory</li><li>oc5: 4 OCPUs, 30 GB memory</li><li>oc6: 8 OCPUs, 60 GB memory</li><li>oc7: 16 OCPUs, 120 GB memory</li><li>oc1m: 1 OCPU, 15 GB memory</li><li>oc2m: 2 OCPUs, 30 GB memory</li><li>oc3m: 4 OCPUs, 60 GB memory</li><li>oc4m: 8 OCPUs, 120 GB memory</li><li>oc5m: 16 OCPUs, 240 GB memory</li></ul>On Oracle Cloud Infrastructure, only VM.Standard and BM.Standard shapes are supported. See the Bare Metal Shapes and VM Shapes tables of the topic <a href='http://www.oracle.com/pls/topic/lookup?ctx=en/cloud/paas/java-cloud&id=oci_compute_overview' target='_blank'>Overview of the Compute Service</a> in the Oracle Cloud Infrastructure documentation."
}
}
}
}
}
}
}
Nested Schema : components
Type: object
Groups properties for the Oracle Traffic Director component (OTD
).
Show Source
-
OTD:
object OTD
Properties for the Oracle Traffic Director (OTD) component.
{
"type":"object",
"required":[
"OTD"
],
"description":"Groups properties for the Oracle Traffic Director component (<code>OTD</code>).",
"properties":{
"OTD":{
"type":"object",
"description":"Properties for the Oracle Traffic Director (OTD) component.",
"properties":{
"adminPort":{
"type":"integer",
"description":"Port for accessing Oracle Traffic Director using HTTP. The default value is <code>8989</code>."
},
"adminPassword":{
"type":"string",
"description":"Password for the Oracle Traffic Director administrator. The password must meet the following requirements:<ul><li>Starts with a letter</li><li>Is between 8 and 30 characters long</li><li>Has one or more upper case letters</li><li>Has one or more lower case letters</li><li>Has one or more numbers</li><li>Has one or more of the following special characters: hyphen (-), underscore (_), pound sign (#), dollar sign ($). If Exadata is the database for the service instance, the password cannot contain the dollar sign ($).</li></ul><p>If an administrator password is not explicitly set, the OTD administrator password defaults to the WebLogic Server (WLS) administrator password."
},
"adminUserName":{
"type":"string",
"description":"User name for the Oracle Traffic Director administrator. The name must be between 8 and 128 characters long and cannot contain any of the following characters:<ul><li>Tab</li><li>Brackets</li><li>Parentheses</li><li>The following special characters: left angle bracket (<), right angle bracket (>), ampersand (&), pound sign (#), pipe symbol (|), and question mark (?).</li></ul><p>If a username is not explicitly set, the OTD user name defaults to the WebLogic Server (WLS) administrator user name."
},
"haEnabled":{
"type":"boolean",
"description":"Flag that specifies whether the local load balancer HA is enabled. This value defaults to <code>false</code> (that is, HA is not enabled)."
},
"ipReservations":{
"type":"array",
"description":"This attribute is not applicable to Oracle SOA Cloud Service instances in Oracle Cloud Infrastructure.<p>A single IP reservation name or two names separated by a comma.<p>Reserved or pre-allocated IP addresses can be assigned to the local load balancer nodes. The number of names in <code>ipReservations</code> must match the number of load balancer nodes you are provisioning.<p>Note the difference between accounts where regions are supported and not supported.<ul><li>Where regions are supported: You can only use those reserved IPs created in the region where the Oracle SOA Cloud Service instance is provisioned. <p>See IP Reservations REST Endpoints for information about how to find unused IP reservations and, if needed, create new IP reservations.</li><li>Where regions are not supported: If your Oracle SOA Cloud Service instance is associated with an Oracle Database Exadata Cloud Service database deployment, you must first submit a request to get the IP reservations. See the My Oracle Support document titled <i>How to Request Authorized IPs for Provisioning an Oracle SOA Cloud Service with Database Exadata Cloud Service</i> (MOS Note 2163568.1).</li></ul>",
"items":{
"type":"string"
}
},
"listenerPort":{
"type":"integer",
"description":"Listener port for the local load balancer for accessing deployed applications using HTTP. The default value is <code>8080</code>.<p>This value is overridden by <code>privilegedListenerPort</code> unless its value is set to 0. This value has no effect if the local load balancer is disabled."
},
"listenerPortEnabled":{
"type":"boolean",
"description":"Flag that specifies whether the non-secure listener port is enabled on the local load balancer. The default value is <code>true</code>."
},
"loadBalancingPolicy":{
"type":"string",
"description":"Policy to use for routing requests to the load balancer. Valid policies include: <ul><li><code>LEAST_CONNECTION_COUNT</code> - Passes each new request to the Managed Server with the least number of connections. This policy is useful for smoothing distribution when Managed Servers get bogged down. Managed Servers with greater processing power to handle requests will receive more connections over time. This is the default.</li><li><code>LEAST_RESPONSE_TIME</code> - Passes each new request to the Managed Server with the fastest response time. This policy is useful when Managed Servers are distributed across networks.</li><li><code>ROUND_ROBIN</code> - Passes each new request to the next Managed Server in line, evenly distributing requests across all Managed Servers regardless of the number of connections or response time.</li></ul>"
},
"privilegedListenerPort":{
"type":"integer",
"description":"Privileged listener port for accessing the deployed applications using HTTP. The default value is <code>80</code>.<p>This value has no effect if the local load balancer is disabled.<p>To disable the privileged listener port, set the value to 0. In this case, if the local load balancer is provisioned, the listener port defaults to <code>listenerPort</code>, if specified, or <code>8080</code>."
},
"privilegedSecuredListenerPort":{
"type":"integer",
"description":"Privileged listener port for accessing the deployed applications using HTTPS. The default value is <code>443</code>.<p>This value has no effect if the local load balancer is disabled.<p>To disable the privileged listener port, set the value to 0. In this case, if the local load balancer is provisioned, the listener port defaults to <code>securedListenerPort</code>, if specified, or <code>8081</code>."
},
"securedListenerPort":{
"type":"integer",
"description":"Secured listener port for accessing the deployed applications using HTTPS. The default value is <code>8081</code>.<p>This value is overridden by <code>privilegedSecuredContentPort</code> unless its value is set to 0. This value has no effect if the local load balancer is disabled."
},
"shape":{
"type":"string",
"description":"Desired compute shape for the local balancer nodes. A shape defines the number of Oracle Compute Units (OCPUs) and amount of memory (RAM). Valid shapes on Oracle Cloud Infrastructure Classic include: <ul><li>oc3: 1 OCPU, 7.5 GB memory</li><li>oc4: 2 OCPUs, 15 GB memory</li><li>oc5: 4 OCPUs, 30 GB memory</li><li>oc6: 8 OCPUs, 60 GB memory</li><li>oc7: 16 OCPUs, 120 GB memory</li><li>oc1m: 1 OCPU, 15 GB memory</li><li>oc2m: 2 OCPUs, 30 GB memory</li><li>oc3m: 4 OCPUs, 60 GB memory</li><li>oc4m: 8 OCPUs, 120 GB memory</li><li>oc5m: 16 OCPUs, 240 GB memory</li></ul>On Oracle Cloud Infrastructure, only VM.Standard and BM.Standard shapes are supported. See the Bare Metal Shapes and VM Shapes tables of the topic <a href='http://www.oracle.com/pls/topic/lookup?ctx=en/cloud/paas/java-cloud&id=oci_compute_overview' target='_blank'>Overview of the Compute Service</a> in the Oracle Cloud Infrastructure documentation."
}
}
}
}
}
Nested Schema : OTD
Type: object
Properties for the Oracle Traffic Director (OTD) component.
Show Source
-
adminPassword(optional):
string
Password for the Oracle Traffic Director administrator. The password must meet the following requirements:
- Starts with a letter
- Is between 8 and 30 characters long
- Has one or more upper case letters
- Has one or more lower case letters
- Has one or more numbers
- Has one or more of the following special characters: hyphen (-), underscore (_), pound sign (#), dollar sign ($). If Exadata is the database for the service instance, the password cannot contain the dollar sign ($).
If an administrator password is not explicitly set, the OTD administrator password defaults to the WebLogic Server (WLS) administrator password.
-
adminPort(optional):
integer
Port for accessing Oracle Traffic Director using HTTP. The default value is 8989
.
-
adminUserName(optional):
string
User name for the Oracle Traffic Director administrator. The name must be between 8 and 128 characters long and cannot contain any of the following characters:
- Tab
- Brackets
- Parentheses
- The following special characters: left angle bracket (<), right angle bracket (>), ampersand (&), pound sign (#), pipe symbol (|), and question mark (?).
If a username is not explicitly set, the OTD user name defaults to the WebLogic Server (WLS) administrator user name.
-
haEnabled(optional):
boolean
Flag that specifies whether the local load balancer HA is enabled. This value defaults to false
(that is, HA is not enabled).
-
ipReservations(optional):
array ipReservations
This attribute is not applicable to Oracle SOA Cloud Service instances in Oracle Cloud Infrastructure.
A single IP reservation name or two names separated by a comma.
Reserved or pre-allocated IP addresses can be assigned to the local load balancer nodes. The number of names in ipReservations
must match the number of load balancer nodes you are provisioning.
Note the difference between accounts where regions are supported and not supported.
-
listenerPort(optional):
integer
Listener port for the local load balancer for accessing deployed applications using HTTP. The default value is
8080
.
This value is overridden by privilegedListenerPort
unless its value is set to 0. This value has no effect if the local load balancer is disabled.
-
listenerPortEnabled(optional):
boolean
Flag that specifies whether the non-secure listener port is enabled on the local load balancer. The default value is true
.
-
loadBalancingPolicy(optional):
string
Policy to use for routing requests to the load balancer. Valid policies include:
LEAST_CONNECTION_COUNT
- Passes each new request to the Managed Server with the least number of connections. This policy is useful for smoothing distribution when Managed Servers get bogged down. Managed Servers with greater processing power to handle requests will receive more connections over time. This is the default.LEAST_RESPONSE_TIME
- Passes each new request to the Managed Server with the fastest response time. This policy is useful when Managed Servers are distributed across networks.ROUND_ROBIN
- Passes each new request to the next Managed Server in line, evenly distributing requests across all Managed Servers regardless of the number of connections or response time.
-
privilegedListenerPort(optional):
integer
Privileged listener port for accessing the deployed applications using HTTP. The default value is
80
.
This value has no effect if the local load balancer is disabled.
To disable the privileged listener port, set the value to 0. In this case, if the local load balancer is provisioned, the listener port defaults to listenerPort
, if specified, or 8080
.
-
privilegedSecuredListenerPort(optional):
integer
Privileged listener port for accessing the deployed applications using HTTPS. The default value is
443
.
This value has no effect if the local load balancer is disabled.
To disable the privileged listener port, set the value to 0. In this case, if the local load balancer is provisioned, the listener port defaults to securedListenerPort
, if specified, or 8081
.
-
securedListenerPort(optional):
integer
Secured listener port for accessing the deployed applications using HTTPS. The default value is
8081
.
This value is overridden by privilegedSecuredContentPort
unless its value is set to 0. This value has no effect if the local load balancer is disabled.
-
shape(optional):
string
Desired compute shape for the local balancer nodes. A shape defines the number of Oracle Compute Units (OCPUs) and amount of memory (RAM). Valid shapes on Oracle Cloud Infrastructure Classic include:
- oc3: 1 OCPU, 7.5 GB memory
- oc4: 2 OCPUs, 15 GB memory
- oc5: 4 OCPUs, 30 GB memory
- oc6: 8 OCPUs, 60 GB memory
- oc7: 16 OCPUs, 120 GB memory
- oc1m: 1 OCPU, 15 GB memory
- oc2m: 2 OCPUs, 30 GB memory
- oc3m: 4 OCPUs, 60 GB memory
- oc4m: 8 OCPUs, 120 GB memory
- oc5m: 16 OCPUs, 240 GB memory
On Oracle Cloud Infrastructure, only VM.Standard and BM.Standard shapes are supported. See the Bare Metal Shapes and VM Shapes tables of the topic
Overview of the Compute Service in the Oracle Cloud Infrastructure documentation.
{
"type":"object",
"description":"Properties for the Oracle Traffic Director (OTD) component.",
"properties":{
"adminPort":{
"type":"integer",
"description":"Port for accessing Oracle Traffic Director using HTTP. The default value is <code>8989</code>."
},
"adminPassword":{
"type":"string",
"description":"Password for the Oracle Traffic Director administrator. The password must meet the following requirements:<ul><li>Starts with a letter</li><li>Is between 8 and 30 characters long</li><li>Has one or more upper case letters</li><li>Has one or more lower case letters</li><li>Has one or more numbers</li><li>Has one or more of the following special characters: hyphen (-), underscore (_), pound sign (#), dollar sign ($). If Exadata is the database for the service instance, the password cannot contain the dollar sign ($).</li></ul><p>If an administrator password is not explicitly set, the OTD administrator password defaults to the WebLogic Server (WLS) administrator password."
},
"adminUserName":{
"type":"string",
"description":"User name for the Oracle Traffic Director administrator. The name must be between 8 and 128 characters long and cannot contain any of the following characters:<ul><li>Tab</li><li>Brackets</li><li>Parentheses</li><li>The following special characters: left angle bracket (<), right angle bracket (>), ampersand (&), pound sign (#), pipe symbol (|), and question mark (?).</li></ul><p>If a username is not explicitly set, the OTD user name defaults to the WebLogic Server (WLS) administrator user name."
},
"haEnabled":{
"type":"boolean",
"description":"Flag that specifies whether the local load balancer HA is enabled. This value defaults to <code>false</code> (that is, HA is not enabled)."
},
"ipReservations":{
"type":"array",
"description":"This attribute is not applicable to Oracle SOA Cloud Service instances in Oracle Cloud Infrastructure.<p>A single IP reservation name or two names separated by a comma.<p>Reserved or pre-allocated IP addresses can be assigned to the local load balancer nodes. The number of names in <code>ipReservations</code> must match the number of load balancer nodes you are provisioning.<p>Note the difference between accounts where regions are supported and not supported.<ul><li>Where regions are supported: You can only use those reserved IPs created in the region where the Oracle SOA Cloud Service instance is provisioned. <p>See IP Reservations REST Endpoints for information about how to find unused IP reservations and, if needed, create new IP reservations.</li><li>Where regions are not supported: If your Oracle SOA Cloud Service instance is associated with an Oracle Database Exadata Cloud Service database deployment, you must first submit a request to get the IP reservations. See the My Oracle Support document titled <i>How to Request Authorized IPs for Provisioning an Oracle SOA Cloud Service with Database Exadata Cloud Service</i> (MOS Note 2163568.1).</li></ul>",
"items":{
"type":"string"
}
},
"listenerPort":{
"type":"integer",
"description":"Listener port for the local load balancer for accessing deployed applications using HTTP. The default value is <code>8080</code>.<p>This value is overridden by <code>privilegedListenerPort</code> unless its value is set to 0. This value has no effect if the local load balancer is disabled."
},
"listenerPortEnabled":{
"type":"boolean",
"description":"Flag that specifies whether the non-secure listener port is enabled on the local load balancer. The default value is <code>true</code>."
},
"loadBalancingPolicy":{
"type":"string",
"description":"Policy to use for routing requests to the load balancer. Valid policies include: <ul><li><code>LEAST_CONNECTION_COUNT</code> - Passes each new request to the Managed Server with the least number of connections. This policy is useful for smoothing distribution when Managed Servers get bogged down. Managed Servers with greater processing power to handle requests will receive more connections over time. This is the default.</li><li><code>LEAST_RESPONSE_TIME</code> - Passes each new request to the Managed Server with the fastest response time. This policy is useful when Managed Servers are distributed across networks.</li><li><code>ROUND_ROBIN</code> - Passes each new request to the next Managed Server in line, evenly distributing requests across all Managed Servers regardless of the number of connections or response time.</li></ul>"
},
"privilegedListenerPort":{
"type":"integer",
"description":"Privileged listener port for accessing the deployed applications using HTTP. The default value is <code>80</code>.<p>This value has no effect if the local load balancer is disabled.<p>To disable the privileged listener port, set the value to 0. In this case, if the local load balancer is provisioned, the listener port defaults to <code>listenerPort</code>, if specified, or <code>8080</code>."
},
"privilegedSecuredListenerPort":{
"type":"integer",
"description":"Privileged listener port for accessing the deployed applications using HTTPS. The default value is <code>443</code>.<p>This value has no effect if the local load balancer is disabled.<p>To disable the privileged listener port, set the value to 0. In this case, if the local load balancer is provisioned, the listener port defaults to <code>securedListenerPort</code>, if specified, or <code>8081</code>."
},
"securedListenerPort":{
"type":"integer",
"description":"Secured listener port for accessing the deployed applications using HTTPS. The default value is <code>8081</code>.<p>This value is overridden by <code>privilegedSecuredContentPort</code> unless its value is set to 0. This value has no effect if the local load balancer is disabled."
},
"shape":{
"type":"string",
"description":"Desired compute shape for the local balancer nodes. A shape defines the number of Oracle Compute Units (OCPUs) and amount of memory (RAM). Valid shapes on Oracle Cloud Infrastructure Classic include: <ul><li>oc3: 1 OCPU, 7.5 GB memory</li><li>oc4: 2 OCPUs, 15 GB memory</li><li>oc5: 4 OCPUs, 30 GB memory</li><li>oc6: 8 OCPUs, 60 GB memory</li><li>oc7: 16 OCPUs, 120 GB memory</li><li>oc1m: 1 OCPU, 15 GB memory</li><li>oc2m: 2 OCPUs, 30 GB memory</li><li>oc3m: 4 OCPUs, 60 GB memory</li><li>oc4m: 8 OCPUs, 120 GB memory</li><li>oc5m: 16 OCPUs, 240 GB memory</li></ul>On Oracle Cloud Infrastructure, only VM.Standard and BM.Standard shapes are supported. See the Bare Metal Shapes and VM Shapes tables of the topic <a href='http://www.oracle.com/pls/topic/lookup?ctx=en/cloud/paas/java-cloud&id=oci_compute_overview' target='_blank'>Overview of the Compute Service</a> in the Oracle Cloud Infrastructure documentation."
}
}
}
Nested Schema : ipReservations
Type: array
This attribute is not applicable to Oracle SOA Cloud Service instances in Oracle Cloud Infrastructure.
A single IP reservation name or two names separated by a comma.
Reserved or pre-allocated IP addresses can be assigned to the local load balancer nodes. The number of names in ipReservations
must match the number of load balancer nodes you are provisioning.
Note the difference between accounts where regions are supported and not supported.
Show Source
{
"type":"array",
"description":"This attribute is not applicable to Oracle SOA Cloud Service instances in Oracle Cloud Infrastructure.<p>A single IP reservation name or two names separated by a comma.<p>Reserved or pre-allocated IP addresses can be assigned to the local load balancer nodes. The number of names in <code>ipReservations</code> must match the number of load balancer nodes you are provisioning.<p>Note the difference between accounts where regions are supported and not supported.<ul><li>Where regions are supported: You can only use those reserved IPs created in the region where the Oracle SOA Cloud Service instance is provisioned. <p>See IP Reservations REST Endpoints for information about how to find unused IP reservations and, if needed, create new IP reservations.</li><li>Where regions are not supported: If your Oracle SOA Cloud Service instance is associated with an Oracle Database Exadata Cloud Service database deployment, you must first submit a request to get the IP reservations. See the My Oracle Support document titled <i>How to Request Authorized IPs for Provisioning an Oracle SOA Cloud Service with Database Exadata Cloud Service</i> (MOS Note 2163568.1).</li></ul>",
"items":{
"type":"string"
}
}