Managing Master Data with webMethods OneData 10.5 | Managing Master Data with webMethods OneData | Developing for webMethods OneData | REST Web Services | REST URL Parameters | batchSize
You can use batchsize in both GET and POST calls for different purposes.
*GET calls. When you use batchsize, you define the number of records to include for a data object or a conceptual object in the OneData response. Use any positive integer value for batchsize, for example, batchSize=25. When used with pageNum in a GET call, you control the number of records on each page of the response. For more details on how to use batchsize and pageNum together, see pageNum.
*POST calls. batchsize indicates the number of records for OneData to process as a batch. The default value is 100, and is specified in the property onedata.interchangeexecution.batchsize in the file. For more details on onedata.interchangeexecution.batchsize, see Administering webMethods OneData.
Use this parameter only in XML REST APIs. JSON payload handles a small set of records, which would generally be part of a single batch. Therefore, OneData ignores this parameter during JSON payload processing. Additionally, during JSON in-memory processing, OneData does not support concurrent processing.
Tip: The batch size you choose must depend on the amount of memory available for processing on the server. Conceptual objects use more memory. You should decrease batchSize for conceptual objects because they use more memory and increase it for data objects. For large conceptual objects, try configuring different values for batchSize to find the size that offers the best response time without generating an OutOfMemoryException error.

Copyright © 2011-2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.