Page created: 12 May 2021 |
Page updated: 1 Nov 2021
This topic discusses exception handling by PingIntelligence policy when ASE is unavailable. To ensure High-Availability the policy supports Primary and Secondary ASEs. In the event of an exception the gateway processes the current request or response to the corresponding destination. From the subsequent request or response a switch happens between the ASEs and the metadata is routed to the other ASE. The following diagram shows, the flow when an exception occurs.
You can configure an Availability profile to define the way PingAccess manages network requests. For more information, see Availability profiles