The request body defines the details of the resize request.
Root Schema : resize-postrequestm
Type: object
Show Source
-
components:
object components
Groups properties for the Oracle WebLogic Server component (WLS
) or the Oracle Traffic Director component (OTD
). Only one component type should be scaled at a time.
{
"properties":{
"components":{
"type":"object",
"description":"Groups properties for the Oracle WebLogic Server component (<code>WLS</code>) or the Oracle Traffic Director component (<code>OTD</code>). Only one component type should be scaled at a time.",
"properties":{
"WLS":{
"type":"object",
"description":"Properties for the Oracle WebLogic Server (WLS) component.",
"properties":{
"hosts":{
"type":"array",
"description":"A single host name. Only application cluster hosts can be specified.",
"items":{
"type":"string"
}
},
"ignoreManagedServerHeapError":{
"type":"boolean",
"description":"Flag that indicates whether to ignore Managed Server heap validation (<code>true</code>) or perform heap validation (<code>false</code>) before a scale down request is accepted. Default is <code>false</code>.<p>When the flag is not set or is <code>false</code>, heap validation is performed before scaling. If a validation error is not generated, the Managed Server JVM is restarted with the new shape after scaling down.<p>When the flag is <code>true</code>, heap validation is not performed. Before you set the flag to <code>true</code>, make sure the <code>-Xms</code> value is low enough for the Managed Server JVM to restart on the new shape after scaling down. The <code>-Xms</code> value should be lower than one-fourth the size of the memory associated with the shape. Use the WebLogic Server Administration Console to edit the value in the server start arguments, if necessary."
},
"shape":{
"type":"string",
"description":"Desired compute shape for the target host.<p>On Oracle Cloud Infrastructure, VM.Standard and BM.Standard shapes, and VM.Standard.E3.Flex, VM.Standard.E4.Flex, and VM.Standard3.Flex shapes are supported. <p>You can specify the number of OCPUs for the flex shapes. The maximum number of OCPUs for VM.Standard.E3.Flex and VM.Standard.E4.Flex is 64 OCPUs, and the maximum number of OCPUs for VM.Standard3.Flex is 32 OCPUs. The amount of memory is calculated based on the number of OCPUs as n*16, where n is the number of OCPUs. <p>Available shapes vary depending on your Oracle Cloud account and the region in which you provision a service instance.<p>See <a href='https://docs.oracle.com/pls/topic/lookup?ctx=cloud&id=oci_compute_shapes' target='_blank'>Compute Shapes</a> in the Oracle Cloud Infrastructure documentation.<p>On Oracle Cloud Infrastructure Classic, valid shapes 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>oc8: 24 OCPUs, 180 GB memory</li><li>oc9: 32 OCPUs, 240 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><li>oc8m: 24 OCPUs, 360 GB memory</li><li>oc9m: 32 OCPUs, 480 GB memory</li></ul><p>Note: Some shapes might not be available in a region."
}
},
"required":[
"hosts",
"shape"
]
},
"OTD":{
"type":"object",
"description":"Properties for the Oracle Traffic Director (OTD) component.",
"properties":{
"hosts":{
"type":"array",
"description":"Name of the host that contains the secondary or primary node.",
"items":{
"type":"string"
}
},
"shape":{
"type":"string",
"description":"Desired compute shape for the target host.<p>On Oracle Cloud Infrastructure, VM.Standard and BM.Standard shapes, and VM.Standard.E3.Flex, VM.Standard.E4.Flex, and VM.Standard3.Flex shapes are supported. <p>You can specify the number of OCPUs for the flex shapes. The maximum number of OCPUs for VM.Standard.E3.Flex and VM.Standard.E4.Flex is 64 OCPUs, and the maximum number of OCPUs for VM.Standard3.Flex is 32 OCPUs. The amount of memory is calculated based on the number of OCPUs as n*16, where n is the number of OCPUs. <p>Available shapes vary depending on your Oracle Cloud account and the region in which you provision a service instance.<p>See <a href='https://docs.oracle.com/pls/topic/lookup?ctx=cloud&id=oci_compute_shapes' target='_blank'>Compute Shapes</a> in the Oracle Cloud Infrastructure documentation.<p>On Oracle Cloud Infrastructure Classic, valid shapes 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>oc8: 24 OCPUs, 180 GB memory</li><li>oc9: 32 OCPUs, 240 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><li>oc8m: 24 OCPUs, 360 GB memory</li><li>oc9m: 32 OCPUs, 480 GB memory</li></ul><p>Note: Some shapes might not be available in a region."
}
},
"required":[
"hosts",
"shape"
]
}
}
}
},
"required":[
"components"
]
}
Nested Schema : components
Type: object
Groups properties for the Oracle WebLogic Server component (WLS
) or the Oracle Traffic Director component (OTD
). Only one component type should be scaled at a time.
Show Source
{
"type":"object",
"description":"Groups properties for the Oracle WebLogic Server component (<code>WLS</code>) or the Oracle Traffic Director component (<code>OTD</code>). Only one component type should be scaled at a time.",
"properties":{
"WLS":{
"type":"object",
"description":"Properties for the Oracle WebLogic Server (WLS) component.",
"properties":{
"hosts":{
"type":"array",
"description":"A single host name. Only application cluster hosts can be specified.",
"items":{
"type":"string"
}
},
"ignoreManagedServerHeapError":{
"type":"boolean",
"description":"Flag that indicates whether to ignore Managed Server heap validation (<code>true</code>) or perform heap validation (<code>false</code>) before a scale down request is accepted. Default is <code>false</code>.<p>When the flag is not set or is <code>false</code>, heap validation is performed before scaling. If a validation error is not generated, the Managed Server JVM is restarted with the new shape after scaling down.<p>When the flag is <code>true</code>, heap validation is not performed. Before you set the flag to <code>true</code>, make sure the <code>-Xms</code> value is low enough for the Managed Server JVM to restart on the new shape after scaling down. The <code>-Xms</code> value should be lower than one-fourth the size of the memory associated with the shape. Use the WebLogic Server Administration Console to edit the value in the server start arguments, if necessary."
},
"shape":{
"type":"string",
"description":"Desired compute shape for the target host.<p>On Oracle Cloud Infrastructure, VM.Standard and BM.Standard shapes, and VM.Standard.E3.Flex, VM.Standard.E4.Flex, and VM.Standard3.Flex shapes are supported. <p>You can specify the number of OCPUs for the flex shapes. The maximum number of OCPUs for VM.Standard.E3.Flex and VM.Standard.E4.Flex is 64 OCPUs, and the maximum number of OCPUs for VM.Standard3.Flex is 32 OCPUs. The amount of memory is calculated based on the number of OCPUs as n*16, where n is the number of OCPUs. <p>Available shapes vary depending on your Oracle Cloud account and the region in which you provision a service instance.<p>See <a href='https://docs.oracle.com/pls/topic/lookup?ctx=cloud&id=oci_compute_shapes' target='_blank'>Compute Shapes</a> in the Oracle Cloud Infrastructure documentation.<p>On Oracle Cloud Infrastructure Classic, valid shapes 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>oc8: 24 OCPUs, 180 GB memory</li><li>oc9: 32 OCPUs, 240 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><li>oc8m: 24 OCPUs, 360 GB memory</li><li>oc9m: 32 OCPUs, 480 GB memory</li></ul><p>Note: Some shapes might not be available in a region."
}
},
"required":[
"hosts",
"shape"
]
},
"OTD":{
"type":"object",
"description":"Properties for the Oracle Traffic Director (OTD) component.",
"properties":{
"hosts":{
"type":"array",
"description":"Name of the host that contains the secondary or primary node.",
"items":{
"type":"string"
}
},
"shape":{
"type":"string",
"description":"Desired compute shape for the target host.<p>On Oracle Cloud Infrastructure, VM.Standard and BM.Standard shapes, and VM.Standard.E3.Flex, VM.Standard.E4.Flex, and VM.Standard3.Flex shapes are supported. <p>You can specify the number of OCPUs for the flex shapes. The maximum number of OCPUs for VM.Standard.E3.Flex and VM.Standard.E4.Flex is 64 OCPUs, and the maximum number of OCPUs for VM.Standard3.Flex is 32 OCPUs. The amount of memory is calculated based on the number of OCPUs as n*16, where n is the number of OCPUs. <p>Available shapes vary depending on your Oracle Cloud account and the region in which you provision a service instance.<p>See <a href='https://docs.oracle.com/pls/topic/lookup?ctx=cloud&id=oci_compute_shapes' target='_blank'>Compute Shapes</a> in the Oracle Cloud Infrastructure documentation.<p>On Oracle Cloud Infrastructure Classic, valid shapes 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>oc8: 24 OCPUs, 180 GB memory</li><li>oc9: 32 OCPUs, 240 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><li>oc8m: 24 OCPUs, 360 GB memory</li><li>oc9m: 32 OCPUs, 480 GB memory</li></ul><p>Note: Some shapes might not be available in a region."
}
},
"required":[
"hosts",
"shape"
]
}
}
}
Nested Schema : OTD
Type: object
Properties for the Oracle Traffic Director (OTD) component.
Show Source
-
hosts:
array hosts
Name of the host that contains the secondary or primary node.
-
shape:
string
Desired compute shape for the target host.
On Oracle Cloud Infrastructure, VM.Standard and BM.Standard shapes, and VM.Standard.E3.Flex, VM.Standard.E4.Flex, and VM.Standard3.Flex shapes are supported.
You can specify the number of OCPUs for the flex shapes. The maximum number of OCPUs for VM.Standard.E3.Flex and VM.Standard.E4.Flex is 64 OCPUs, and the maximum number of OCPUs for VM.Standard3.Flex is 32 OCPUs. The amount of memory is calculated based on the number of OCPUs as n*16, where n is the number of OCPUs.
Available shapes vary depending on your Oracle Cloud account and the region in which you provision a service instance.
See Compute Shapes in the Oracle Cloud Infrastructure documentation.
On Oracle Cloud Infrastructure Classic, valid shapes 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
- oc8: 24 OCPUs, 180 GB memory
- oc9: 32 OCPUs, 240 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
- oc8m: 24 OCPUs, 360 GB memory
- oc9m: 32 OCPUs, 480 GB memory
Note: Some shapes might not be available in a region.
{
"type":"object",
"description":"Properties for the Oracle Traffic Director (OTD) component.",
"properties":{
"hosts":{
"type":"array",
"description":"Name of the host that contains the secondary or primary node.",
"items":{
"type":"string"
}
},
"shape":{
"type":"string",
"description":"Desired compute shape for the target host.<p>On Oracle Cloud Infrastructure, VM.Standard and BM.Standard shapes, and VM.Standard.E3.Flex, VM.Standard.E4.Flex, and VM.Standard3.Flex shapes are supported. <p>You can specify the number of OCPUs for the flex shapes. The maximum number of OCPUs for VM.Standard.E3.Flex and VM.Standard.E4.Flex is 64 OCPUs, and the maximum number of OCPUs for VM.Standard3.Flex is 32 OCPUs. The amount of memory is calculated based on the number of OCPUs as n*16, where n is the number of OCPUs. <p>Available shapes vary depending on your Oracle Cloud account and the region in which you provision a service instance.<p>See <a href='https://docs.oracle.com/pls/topic/lookup?ctx=cloud&id=oci_compute_shapes' target='_blank'>Compute Shapes</a> in the Oracle Cloud Infrastructure documentation.<p>On Oracle Cloud Infrastructure Classic, valid shapes 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>oc8: 24 OCPUs, 180 GB memory</li><li>oc9: 32 OCPUs, 240 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><li>oc8m: 24 OCPUs, 360 GB memory</li><li>oc9m: 32 OCPUs, 480 GB memory</li></ul><p>Note: Some shapes might not be available in a region."
}
},
"required":[
"hosts",
"shape"
]
}
Nested Schema : WLS
Type: object
Properties for the Oracle WebLogic Server (WLS) component.
Show Source
-
hosts:
array hosts
A single host name. Only application cluster hosts can be specified.
-
ignoreManagedServerHeapError(optional):
boolean
Flag that indicates whether to ignore Managed Server heap validation (
true
) or perform heap validation (
false
) before a scale down request is accepted. Default is
false
.
When the flag is not set or is false
, heap validation is performed before scaling. If a validation error is not generated, the Managed Server JVM is restarted with the new shape after scaling down.
When the flag is true
, heap validation is not performed. Before you set the flag to true
, make sure the -Xms
value is low enough for the Managed Server JVM to restart on the new shape after scaling down. The -Xms
value should be lower than one-fourth the size of the memory associated with the shape. Use the WebLogic Server Administration Console to edit the value in the server start arguments, if necessary.
-
shape:
string
Desired compute shape for the target host.
On Oracle Cloud Infrastructure, VM.Standard and BM.Standard shapes, and VM.Standard.E3.Flex, VM.Standard.E4.Flex, and VM.Standard3.Flex shapes are supported.
You can specify the number of OCPUs for the flex shapes. The maximum number of OCPUs for VM.Standard.E3.Flex and VM.Standard.E4.Flex is 64 OCPUs, and the maximum number of OCPUs for VM.Standard3.Flex is 32 OCPUs. The amount of memory is calculated based on the number of OCPUs as n*16, where n is the number of OCPUs.
Available shapes vary depending on your Oracle Cloud account and the region in which you provision a service instance.
See Compute Shapes in the Oracle Cloud Infrastructure documentation.
On Oracle Cloud Infrastructure Classic, valid shapes 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
- oc8: 24 OCPUs, 180 GB memory
- oc9: 32 OCPUs, 240 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
- oc8m: 24 OCPUs, 360 GB memory
- oc9m: 32 OCPUs, 480 GB memory
Note: Some shapes might not be available in a region.
{
"type":"object",
"description":"Properties for the Oracle WebLogic Server (WLS) component.",
"properties":{
"hosts":{
"type":"array",
"description":"A single host name. Only application cluster hosts can be specified.",
"items":{
"type":"string"
}
},
"ignoreManagedServerHeapError":{
"type":"boolean",
"description":"Flag that indicates whether to ignore Managed Server heap validation (<code>true</code>) or perform heap validation (<code>false</code>) before a scale down request is accepted. Default is <code>false</code>.<p>When the flag is not set or is <code>false</code>, heap validation is performed before scaling. If a validation error is not generated, the Managed Server JVM is restarted with the new shape after scaling down.<p>When the flag is <code>true</code>, heap validation is not performed. Before you set the flag to <code>true</code>, make sure the <code>-Xms</code> value is low enough for the Managed Server JVM to restart on the new shape after scaling down. The <code>-Xms</code> value should be lower than one-fourth the size of the memory associated with the shape. Use the WebLogic Server Administration Console to edit the value in the server start arguments, if necessary."
},
"shape":{
"type":"string",
"description":"Desired compute shape for the target host.<p>On Oracle Cloud Infrastructure, VM.Standard and BM.Standard shapes, and VM.Standard.E3.Flex, VM.Standard.E4.Flex, and VM.Standard3.Flex shapes are supported. <p>You can specify the number of OCPUs for the flex shapes. The maximum number of OCPUs for VM.Standard.E3.Flex and VM.Standard.E4.Flex is 64 OCPUs, and the maximum number of OCPUs for VM.Standard3.Flex is 32 OCPUs. The amount of memory is calculated based on the number of OCPUs as n*16, where n is the number of OCPUs. <p>Available shapes vary depending on your Oracle Cloud account and the region in which you provision a service instance.<p>See <a href='https://docs.oracle.com/pls/topic/lookup?ctx=cloud&id=oci_compute_shapes' target='_blank'>Compute Shapes</a> in the Oracle Cloud Infrastructure documentation.<p>On Oracle Cloud Infrastructure Classic, valid shapes 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>oc8: 24 OCPUs, 180 GB memory</li><li>oc9: 32 OCPUs, 240 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><li>oc8m: 24 OCPUs, 360 GB memory</li><li>oc9m: 32 OCPUs, 480 GB memory</li></ul><p>Note: Some shapes might not be available in a region."
}
},
"required":[
"hosts",
"shape"
]
}
Nested Schema : hosts
Type: array
Name of the host that contains the secondary or primary node.
Show Source
{
"type":"array",
"description":"Name of the host that contains the secondary or primary node.",
"items":{
"type":"string"
}
}
Nested Schema : hosts
Type: array
A single host name. Only application cluster hosts can be specified.
Show Source
{
"type":"array",
"description":"A single host name. Only application cluster hosts can be specified.",
"items":{
"type":"string"
}
}