Throttling prioritization

This article provides information about priority-based throttling for Open Data Protocol (OData) and custom service-based integrations.

Resource-based limits for service protection application programming interfaces (APIs) work together with the user-based limits for service protection APIs as protective settings that help prevent the over-utilization of resources. In this way, they help preserve the system's responsiveness and ensure consistent availability and performance for environments that run finance and operations apps. The resource-based limits will throttle service requests when the aggregate consumption of web server resources reaches levels that threaten service performance and availability.

For resource-based service protection API limits, you can set the relative priority for OData and custom service-based integrations, depending on your business-critical need for these integrations. The throttling manager will then honor the priorities that are set for the requests. For OData and custom service-based requests, a "Too many requests" error will be sent if system health and performance are affected.

The Throttling Priority Mapping page is used to assign priorities for integrations so that priorities can be honored when requests are throttled.

Setting appropriate priorities ensures that low-priority integrations will be throttled before high-priority integrations. For more information about how to set up integration, see Enable connectivity with external services.

Two kinds of applications are supported in Azure Active Directory (Azure AD):

  • User based – This flow uses a username and password for authentication and authorization.
  • Azure AD app based – A confidential client is an application that can keep a client password confidential. The authorization server assigned this client password to the client application.

For more information, see Authentication.

Configure priorities for integrations

After you have registered your service in Azure AD and in your finance and operations apps, you can set up priorities for integrations.

Note

You must be assigned the System administrator or Integration priority manager role to complete the set up.

  1. In finance and operations apps, go to System administration > Setup > Throttling priority mapping.
  2. Select New.
  3. In the Authentication type field, select User or Azure AD application based on your integration scenario.
  4. If Azure AD application type is selected, in the Client ID field select the application that you registered in the Azure Active Directory application.
  5. If User type is selected, in the User ID field select an appropriate service account user ID.
  6. Assign the appropriate priority and then select Save.