Account Cloud Attachment Properties Default object
The AccountCloudAttachmentPropertiesDefault object lets the runtime cloud owner retrieve and update the default cloud attachment properties for each runtime cloud cluster.
Structure
Initial GET response
<bns:AsyncOperationTokenResult responseStatusCode="202">
<bns:asyncToken token=""/>
</bns:AsyncOperationTokenResult>
Subsequent GET response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<bns:AsyncOperationResult xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:bns="http://api.platform.boomi.com/" responseStatusCode="200">
<bns:result xsi:type="bns:AccountCloudAttachmentPropertiesDefault" accountDiskUsage="" numberofAtomWorkers="" atomInputSize="" atomOutputOverflowSize="" atomWorkingOverflowSize="" httpRequestRate="" workerMaxExecutionTime="" workerMaxGeneralExecutionTime="" workerMaxRunningExecutions="" workerMaxQueuedExecutions="" workerQueuedExecutionTimeout="" maxConnectorTrackDocs="" httpWorkload="" as2Workload="" cloudAccountExecutionLimit="" cloudAccountExecutionWarningOffset="" enableAtomWorkerWarmup="" minNumberofAtomWorkers="" testModeMaxDocs="" testModeMaxDocBytes="" enableAccountDataArchiving="" listenerMaxConcurrentExecutions="" downloadRunnerlogs=""/>
</bns:AsyncOperationResult>
| Field | Type | Represents UI property | Description |
|---|---|---|---|
| accountDiskUsage | integer | Account Disk Usage | Represented in bytes, this property is used to set the size limit for an account that uses the private runtime cloud. |
| as2Workload | string | Default AS2 Workload | Used to select the process run mode for AS2 listener processes.Accepted values: 1. inherited — (Default) The setting is inherited from the Runtime cluster, 2. general — The default process mode for all new processes. 3. low_latency_debug — All AS2 listener processes use an Execution worker. Note: After you change this property value you must restart the Runtime cloud cluster or Runtime. If you select Low_Latency_Debug, Trading Partner components that use AS2 listeners also use that run mode. |
| atomOutputOverflowSize | integer | Atom Output Overflow Size | Represented in bytes, if specified, this value must be a positive number. For Execution worker processes, this property limits the number of bytes per output datastore maintained in memory before overflowing to disk. |
| atomWorkingOverflowSize | integer | Atom Working Overflow Size | Represented in bytes. For Execution worker processes, this property limits the number of bytes per working datastore maintained in memory before overflowing to disk. |
| atomInputSize | integer | Web Service Request Input Size | Represented in bytes. For Web Services Server listener processes, limits the input size of a web service request. If reaching this limit, it rejects the request.For Flow Services Server listener processes, limits the request size and response size. If reaching this limit, it rejects the request. If reaching this limit, it rejects the request with a 400 error code. If reaching the limit on a response, it rejects the request with a 503 error code. |
| cloudAccountExecutionLimit | integer | Account Concurrent Execution Limit | The total number of concurrent runs allowed. If specified, this value must be a positive number. If this field does not contain a value, there is no limit. On a Cloud, for this limit to take effect, you must also set the Cloud Partition Size property. The Cloud Partition Size property is set in the Properties panel, under Runtime Management. |
| cloudAccountExecutionWarningOffset | integer | Account Concurrent Execution Warning Offset | If specified, this value must be a positive number. If this field does not contain a value, it does not generate a warning. This value is subtracted from the Account Concurrent Execution Limit to determine when the Atom generates a warning that the account is close to exceeding its number of concurrent runs. For example, if this property is set to 5 and the Account Concurrent Execution Limit is set to 20, the Atom generates a warning in the container log when the account exceeds 15 concurrent runs. |
| downloadRunnerlogs | string | Enable Download of Execution Artifacts and Worker Logs | Runtime cloud owners can set this property to give account users or specific tenants the ability to download Execution worker log files from Runtime Management and run artifacts from Process Reporting.Accepted values: 1. Inherited (false) — The setting is inherited from the runtime cloud clusters, and the feature is turned off. 2. False — The feature is not enabled, and users cannot download Execution worker logs or run artifacts. 3. True — (default) The feature is enabled. Users can download Execution worker logs and run artifacts. Note: This property is turned on automatically for public runtime clouds. |
| enableAtomWorkerWarmup | string | Execution Worker Warmup Enabled | Accepted values: 1. inherited- indicating that the property inherits what is set in the runtime cloud clusters. 2. true- indicating that when an Execution worker is within 30 minutes of shutting down, the Cloud starts (“warm-up”) another Execution worker to replace it. 3. false- indicates that you did not enable the feature. You can use this feature if you provision your account with at least one Execution worker. If you provision your account with more than one Execution worker, and if there are multiple Execution workers within 30 minutes of shutting down, then by default it replaces only one Execution worker. However, if one of those Execution workers has a load greater than “LOW”, then it is replaced even though there is another Execution worker running. If you have set the Minimum Execution Workers property, then it replaces the appropriate number of Execution workers so that you do not go below the minimum. |
| enableAccountDataArchiving | string | Enable Processed Document Archiving | Accepted values: 1. inherited- (plus the value of the setting being inherited. For example, inherited(true) or inherited(false)) indicates that the property inherits what is set in the runtime cloud clusters. 2. true- If true or Inherited (true), the owner of the selected attached Atom can enable processed document archiving. 3. false- indicates that the feature is not enabled. |
| flowControlParallelProcessTypeOverride | string | NONE THREADS PROCESSES | Overrides the Parallel Process Type setting in Flow Control shapes at a global Runtime cloud or Attachment Quota level. You can set the property only if you are a private runtime cloud owner.The default value is NONE. |
| httpRequestRate | integer | HTTP Request Rate | Limits the number of Web Services Server requests per second. This limitation is per node in the Runtime cloud , and per Cloud or Atom attachment (not per account).If it exceeds this value, callers receive a 503 error.After you change this property value you must restart the Runtime cloud cluster or Runtime. Note: If you set an HTTP Request Rate value, API Management uses this limit before the values specified in the API Contract for Rate Limit or Quota Limit. |
| httpWorkload | string | Default HTTP Workload | Accepted values: 1. inherited- (plus the value of the setting being inherited. For example, inherited(true) or inherited(false)) indicating that the property inherits what is set in the runtime cloud clusters. 2. general- The default process mode for all new processes. General mode processes do not use an Execution worker, but Low_Latency mode processes do use one. 3. low_latency- All Web Services Server processes use an Execution worker and run in Low_Latency mode. 4. low_latency_debug- All Web Services Server processes use an Execution worker. Processes configured in Generalmode run in Low_Latency_Debug mode. |
| listenerMaxConcurrentExecutions | integer | Maximum Concurrent Executions per Listener | The maximum number of concurrent runs allowed per listener — that is, the maximum listener pool size. |
| maxConnectorTrackDocs | integer | Maximum Connector Tracking Documents | You must set a positive integer less than or equal to 10,000. For example, in a process run, the maximum number of connector tracking generated documents for a single connector step.After reaching this limit, it does not report more tracking documents to the platform for that step in that run. |
| minNumberofAtomWorkers | integer | Minimum Execution workers | The minimum number of Execution workers that run continuously in the Cloud.If this property is set to a number greater than zero, then a few minutes after the Cloud starts and stabilizes, this number of Execution workers begin to run. Their starting is not dependent upon receiving incoming process run requests. This behavior is like having multiple runners at the starting line of a race. All runners are ready and start to run as soon as the starter pistol is fired. This property works in conjunction with the Execution Worker Warmup Enabled property. If you set Minimum Execution Workers > 0, then it enables Execution Worker Warmup behavior. As your minimum number of Execution workers reach the end of their life span, they are replaced with new Execution workers. If the load on active execution workers drop, the Runtime cloud reduces the number of execution workers to the value you set for this property. Note: Setting this property to a number greater than the number of provisioned execution workers in your account does not cause additional execution workers to run. If you would like to have additional execution workers provisioned in your account, contact the Support team. |
| numberofAtomWorkers | integer | Execution workers | Allocated number of execution workers. |
| testModeMaxDocs | integer | Test Mode Maximum Document Count | The maximum number of files (documents) per inbound connector shape during the run of a process in test mode. A negative value means there is no maximum.This field is present only if you enable enhanced test mode feature in the account. |
| testModeMaxDocBytes | integer | Test Mode Maximum Aggregate Document Size | Represented in bytes, the maximum aggregate data size across the run of a process in test mode. A negative value means there is no maximum.This field is present only if you enable the enhanced test mode feature in the account. If you want to enable this feature, contact your sales representative. |
| workerMaxExecutionTime | integer | Execution Worker Maximum Run Time | Maximum run time in milliseconds for Execution worker processes.For example, an accepted value is 30000. After this amount of time passes, a 522 HTTP status code message is returned to the client saying that the process exceeds the time limit and then cancels the process run. After you change this property value, you must restart the Runtime cloud cluster or Runtime. |
| workerMaxGeneralExecutionTime | integer | Execution Worker Maximum General Execution Time | Maximum run time in milliseconds for Execution worker processes that use Low_Latency_Debug mode. For example, an accepted value is 60000. After you change this property value, you must restart the Runtime cloud cluster or Runtime. |
| workerMaxRunningExecutions | integer | Execution Worker Maximum Running Executions | The maximum number of simultaneous processes that can run in a single Execution worker.After you change this property value, you must restart the Runtime cloud cluster or Runtime. |
| workerMaxQueuedExecutions | integer | Execution Worker Maximum Queued Executions | Maximum number of extra processes that can queue in a single Execution worker, when the maximum number of processes is running. If specified, this value must be a positive number. After you change this property value you must restart the Runtime cloud cluster or Runtime. |
| workerQueuedExecutionTimeout | hr:min:sec:ms | Execution Worker Queued Execution Time-out | Maximum time that a job in the queue can wait to run. After this amount of time, the job fails with a time-out exception.For example, an accepted value is 0:10:00. After you change this property value you must restart the Runtime cloud cluster or Runtime. |
| accountDiskUsage | integer | Account Disk Usage | Represented in bytes, this property sets the size limit for an account that uses the private runtime cloud. |
Supported operations
| GET | QUERY | CREATE | UPDATE | EXECUTE | DELETE |
|---|---|---|---|---|---|
Using the GET operation
Retrieving the default cloud attachment properties is an asynchronous process:
-
Send a GET request that specifies both the account ID and runtime ID to the Boomi Enterprise Platform.
https://api.boomi.com/api/rest/v1/{accountId}/async/AccountCloudAttachmentPropertiesDefault/{runtimeId}where
{accountId}is the ID of the authenticating account for the request and{runtimeId}is the ID of the runtime cloud cluster. -
The platform returns a token.
-
Send one or more GET requests that include the token.
-
The platform returns a list of the cloud attachments associated with the runtime cloud cluster.
The runtime cloud cluster and cloud attachments to which you are calling must be online.
Using the UPDATE operation
Sets the default cloud attachment properties for runtime cloud clusters.
If you have multiple runtime cloud clusters, you need to set the defaults for each runtime cloud cluster individually. You can use the AccountCloudAttachmentSummary API to see the runtime cloud cluster status.
If a value is not included in the Update call or is explicitly set to null, the value will be reset to its original default value for the runtime cloud cluster.
Send an HTTP POST to:
https://api.boomi.com/api/rest/v1/{accountId}/AccountCloudAttachmentPropertiesDefault/{runtimeId}
Where accountId is the ID of the authenticating account.
SOAP implementation
- GET
- UPDATE
Request (first GET request):
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:api="http://api.platform.boomi.com/">
<soapenv:Body>
<api:asyncGet>
<api:objectType>AccountCloudAttachmentPropertiesDefault</api:objectType>
<api:objectId>35097b28-2418-406a-819d-6a47cd7bf385</api:objectId>
</api:asyncGet>
</soapenv:Body>
</soapenv:Envelope>
Response (first GET response):
<?xml version='1.0' encoding='UTF-8'?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body>
<bns:asyncGetResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:bns="http://api.platform.boomi.com/">
<bns:result responseStatusCode="202">
<bns:asyncToken token="AccountCloudAttachmentPropertiesDefault-5d3bb172-4d74-46e1-a917-45ce3fc5c5e2"/>
</bns:result>
</bns:asyncGetResponse>
</S:Body>
</S:Envelope>
Request (second GET request):
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:api="http://api.platform.boomi.com/">
<soapenv:Body>
<api:asyncResult>
<api:token>AccountCloudAttachmentPropertiesDefault-5d3bb172-4d74-46e1-a917-45ce3fc5c5e2</api:token>
</api:asyncResult>
</soapenv:Body>
</soapenv:Envelope>
Response (second GET response):
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body>
<bns:asyncResultResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:bns="http://api.platform.boomi.com/">
<bns:results responseStatusCode="200">
<bns:result xsi:type="bns:AccountCloudAttachmentPropertiesDefault"
accountDiskUsage="-1"
numberofAtomWorkers="0"
atomInputSize="-1"
atomOutputOverflowSize="-1"
atomWorkingOverflowSize="-1"
httpRequestRate="-1"
workerMaxExecutionTime="30000"
workerMaxGeneralExecutionTime="600000"
workerMaxRunningExecutions="20"
workerMaxQueuedExecutions="10"
workerQueuedExecutionTimeout="10000"
maxConnectorTrackDocs="10000"
httpWorkload="GENERAL"
as2Workload="GENERAL"
cloudAccountExecutionLimit="-1"
cloudAccountExecutionWarningOffset="-1"
enableAtomWorkerWarmup="false"
minNumberofAtomWorkers="0"
enableAccountDataArchiving="false"
listenerMaxConcurrentExecutions="10"
downloadRunnerlogs="true"
flowControlParallelProcessTypeOverride="NONE"
queueIncomingMessageRateLimit="-1"
workerElasticScalingThreshold="75"
queueCommitBatchLimit="100"
queueMaxBatchSize="-1"
queueMaxDocSize="-1"
queueMsgThrottleRate="0"
queueUseFilePersistence="false"/>
</bns:results>
</bns:asyncResultResponse>
</S:Body>
</S:Envelope>
Request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:api="http://api.platform.boomi.com/" xmlns:par="http://api.platform.boomi.com/">
<soapenv:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:UsernameToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="UsernameToken">
<wsse:Username>user@boomi.com</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">password123</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</soapenv:Header>
<soapenv:Body>
<api:update xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<object xsi:type="api:AccountCloudAttachmentPropertiesDefault"
containerId="1b2a345e-6d78-9fa0-bdba-1b2caeaec34d"
accountDiskUsage="429496729600"
numberofAtomWorkers="1"
atomInputSize="413132133313"
atomOutputOverflowSize="421313313"
atomWorkingOverflowSize="31313313"
httpRequestRate="31313313"
workerMaxExecutionTime="30000"
workerMaxGeneralExecutionTime="600000"
workerMaxRunningExecutions="20"
workerMaxQueuedExecutions="10"
workerQueuedExecutionTimeout="10000"
maxConnectorTrackDocs="10000"
httpWorkload="LOW_LATENCY"
as2Workload="GENERAL"
cloudAccountExecutionLimit="2147383646"
cloudAccountExecutionWarningOffset="31313213"
enableAtomWorkerWarmup="false"
minNumberofAtomWorkers="1"
testModeMaxDocs="100"
testModeMaxDocBytes="10485760"
enableAccountDataArchiving="false"
listenerMaxConcurrentExecutions="6"
downloadRunnerlogs="true" </object>
</api:update>
</soapenv:Body>
</soapenv:Envelope>
Response:
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body>
<bns:updateResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:bns="http://api.platform.boomi.com/">
<result xsi:type="bns:AccountCloudAttachmentPropertiesDefault"/>
</bns:updateResponse>
</S:Body>
</S:Envelope>