Oracle Web Services On Demand Guide > Best Practices for Designing Client Application > Best Practices for Integration Design >

Best Practices for Adhering to Web Service Allotments

This topic lists several best practices to help ensure that you do not exceed the various Web services allotment values.

For the Web Services Operations allotment:

• Avoid unnecessary Web services requests:
  • Avoid issuing the same query multiple times, if you do not expect the set of records returned to change; cache the data locally to avoid repeated requests for the same information.
  • Issue subsequent page requests when necessary, do not retrieve the entire record set if it is not necessary.
• Ensure high data quality to minimize errors (this is especially important for batch requests):
  • Ensure field values are of the correct type
  • Include values for required fields in all requests
  • Do not use invalid Id values when associating records using Web services.
• Use the Oracle Data Loader On Demand tool or the Import Assistant for loading large amounts of data into Oracle CRM On Demand.
• Use the Export Assistant for extracting large amounts of data from Oracle CRM On Demand.
• Include the miniumum set of related objects in QueryPage requests.

For the Web Services Concurrent Request allotment:

• Schedule automated or low priority clients to execute during off-peak hours.
• When performing more than one operation based on a user's input, send requests sequentially, not in parallel.
• Use the Execute method in the Web Services v2.0 API to bundle multiple requests on a set of records of the same type in a single Web service request.