You're viewing Apigee Edge documentation.
View Apigee X documentation.
The TargetEndpoint configuration defines the way Apigee Edge connects to a backend service or API. It sends the requests and receives the responses to/from the backend service. The backend service can be a HTTP/HTTPS server, NodeJS, or Hosted Target.
The backend service in the TargetEndpoint can be invoked in one of the following ways:
- Direct URL to an HTTP or HTTPS server
- ScriptTarget to an Edge-hosted Node.js script
- HostedTarget to NodeJS deployed on Hosted Target Environment
- TargetServer configuration
Likewise, the Service Callout policy can be used to make a call to any external service from the API Proxy flow. This policy supports defining HTTP/HTTPS target URLs either directly in the policy itself or using a TargetServer configuration.
TargetServer configuration decouples the concrete endpoint URLs from TargetEndpoint configurations or in Service Callout policies. A TargetServer is referenced by a name instead of the URL in TargetEndpoint. The TargetServer configuration will have the hostname of the backend service, port number, and other details.
Here is a sample TargetServer configuration:
<TargetServer name="target1"> <Host>www.mybackendservice.com</Host> <Port>80</Port> <IsEnabled>true</IsEnabled> </TargetServer>
The TargetServer enables you to have different configurations for each environment. A TargetEndpoint/Service Callout policy can be configured with one or more named TargetServers using a LoadBalancer. The built-in support for load balancing enhances the availability of the APIs and failover among configured backend server instances.
Here is a sample TargetEndpoint configuration using TargetServers:
<TargetEndpoint name="default"> <HTTPTargetConnection>> <LoadBalancer> <Server name="target1"/> <Server name="target2"/> </LoadBalancer> </HTTPTargetConnection> </TargetEndpoint>
MaxFailures configuration specifies the maximum number of request failures
to the target server after which the target server shall be marked as down and removed
from rotation for all subsequent requests.
An example configuration with
<TargetEndpoint name="default"> <HTTPTargetConnection> <LoadBalancer> <Server name="target1"/> <Server name="target2"/> <MaxFailures>5</MaxFailures> </LoadBalancer> </HTTPTargetConnection> </TargetEndpoint>
In the above example, if five consecutive requests failed for "target1" then "target1" will be removed from rotation and all subsequent requests will be sent only to target2.
Having single TargetServer in a
LoadBalancer configuration of the
TargetEndpoint or Service Callout policy with
MaxFailures set to a
non-zero value is not recommended as it can have adverse implications.
Consider the following sample configuration that has a single TargetServer
named "target1" with
MaxFailures set to 5 (non-zero value):
<TargetEndpoint name="default"> <HTTPTargetConnection> <LoadBalancer> <Algorithm>RoundRobin</Algorithm> <Server name="target1" /> <MaxFailures>5</MaxFailures> </LoadBalancer> </HTTPTargetConnection>
If the requests to the TargetServer "target1" fails five times (number specified in
the TargetServer is removed from rotation. Since there are no other TargetServers to fail over to,
all the subsequent requests to the API Proxy having this configuration will fail with
503 Service Unavailable error.
Even if the TargetServer "target1" gets back to its normal state and is capable of sending successful responses, the requests to the API Proxy will continue to return 503 errors. This is because Edge does not automatically put the TargetServer back in rotation even after the target is up and running again. To address this issue, the API Proxy must be redeployed for Edge to put the TargetServer back into rotation.
If the same configuration is used in the Service Callout policy, then the API requests will get 500 Error after the requests to the TargetServer "target1" fails 5 times.
Using a single TargetServer in a
LoadBalancer configuration of
TargetEndpoint or Service Callout policy with
MaxFailures set to a non-zero value causes:
- API Requests to fail with 503/500 Errors continuously (after the requests fail for MaxFailures number of times) until the API Proxy is redeployed.
- Longer outage as it is tricky and can take more time to diagnose the cause of this issue (without prior knowledge about this antipattern).
- Have more than one TargetServer in the
LoadBalancerconfiguration for higher availability.
Always define a Health Monitor when
MaxFailuresis set to a non-zero value. A target server will be removed from rotation when the number of failures reaches the number specified in
MaxFailures. Having a HealthMonitor ensures that the TargetServer is put back into rotation as soon as the target server becomes available again, meaning there is no need to redeploy the proxy.
To ensure that the health check is performed on the same port number that Edge uses to connect to the target servers, Apigee recommends that you omit the
<Port>child element under
<TCPMonitor>unless it is different from TargetServer port. By default
<Port>is the same as the TargetServer port.
Sample configuration with HealthMonitor:
<TargetEndpoint name="default"> <HTTPTargetConnection> <LoadBalancer> <Algorithm>RoundRobin</Algorithm> <Server name="target1" /> <Server name="target2" /> <MaxFailures>5</MaxFailures> </LoadBalancer> <Path>/test</Path> <HealthMonitor> <IsEnabled>true</IsEnabled> <IntervalInSec>5</IntervalInSec> <TCPMonitor> <ConnectTimeoutInSec>10</ConnectTimeoutInSec> </TCPMonitor> </HealthMonitor> </HTTPTargetConnection> </TargetEndpoint>
If there's some constraint such that only one TargetServer and if the HealthMonitor is not used, then don't specify
The default value of MaxFailures is 0. This means that Edge always tries to connect to the target for each request and never removes the target server from the rotation.