SOAP Web Services Governance Overview
To optimize NetSuite application and database servers, the system employs certain mechanisms to control the consumption of SOAP web services. These mechanisms ensure the following:
-
Requests are monitored and controlled to ensure that the user experience is not excessively impacted.
-
The burden of heavy SOAP web services users is not shared among all users.
NetSuite SOAP web services governance includes:
-
Record limiting (see Understanding Record Limiting)
-
Request limiting (see Understanding Request Limiting)
For information on the maximum number of sessions, see Session Limits.
For information about the new web services and RESTlet concurrency governance, see Web Services and RESTlet Concurrency Governance.
Understanding Record Limiting
Limits exist for the following:
-
The number of records that can be included in a list operation.
-
The number of records that can be included in a page of search results. Search results are set by the pageSize field of the searchPreferences complex type. A minimum and maximum exists for this parameter.
The limit varies depending on whether the operation is synchronous or asynchronous.
Synchronous Operations
|
Minimum Record Count |
Maximum Record Count |
|---|---|---|
|
— |
200 |
|
|
— |
200 |
|
|
— |
1000 |
|
|
— |
10000 |
|
|
— |
100 |
|
|
— |
100 |
|
|
pageSize parameter of searchPreferences complex type, when used in synchronous searches |
5 |
1000 |
Asynchronous Operations
|
Minimum Record Count |
Record Count |
|---|---|---|
|
asyncAddList |
— |
400 |
|
asyncGetList |
— |
2000 |
|
asyncUpdateList |
— |
200 |
|
asyncUpsertList |
— |
200 |
|
asyncDeleteList |
— |
400 |
|
pageSize parameter of searchPreferences complex type, when used in asynchronous searches |
5 |
2000 |
For details on asynchronous processing, see Asynchronous Request Processing.
Understanding Request Limiting
Request limiting pertains to the size of your SOAP request. The size of a request cannot exceed 100MB.
Understanding Governance Errors
The following faults are thrown because of other governance violations.
-
ExceededRecordCountFault – thrown if a request exceeds the allowed record count.
-
ExceededRequestLimitFault – thrown if the allowed number of concurrent requests is exceeded.
-
ExceededRequestSizeFault – thrown if a request exceeds 100M.
For more information on exceptions, refer to SOAP Web Services Error Handling and Error Codes.
For information about concurrency governance, see Web Services and RESTlet Concurrency Governance.