An endpoint is a specific destination for a message such as an address, WSDL, a failover group, a load-balance group etc. WSO2 API Manager supports a range of different endpoint types, allowing the API Gateway to connect with advanced types of backends.
|HTTP endpoint||A REST service endpoint based on a URI template.|
|Address endpoint||The direct URL of the service.|
|Failover Group endpoint||The endpoints that the service tries to connect to in case of a failure. This happens in a round robin manner.|
|Load Balance endpoint||The endpoints to which incoming requests are directed to in a round robin manner. They automatically handle fail-over as well.|
|Default endpoint||The default endpoint sends the message to the address specified in the To header.|
The system reads gateway endpoints from the
<APIM_HOME>/repository/conf/api-manager.xmlfile. When there are multiple gateway environments defined, it picks the gateway endpoint of the production environment. You can define both HTTP and HTTPS gateway endpoints as follows:
If both types of endpoints are defined, the HTTPS endpoint will be picked as the server endpoint.
Tip: When you define secure (HTTPS) endpoints, set the
<parameter name="HostnameVerifier">element to
<APIM_HOME>/repository/conf/axis2/axis2.xmlfile's HTTPS transport sender configuration:
If not, the server throws an exception.
When creating (or updating) Failover endpoints through the Publisher UI (in the Implement tab), you need to go into the Advanced Options of each endpoint and specify a set of Transport Error Codes for the endpoint to fail over on and take off the Initial Duration by setting its value to -1.
For more information about endpoints and how to add, edit or delete them, see the WSO2 ESB documentation.