An endpoint defines an external destination for an outgoing message through WSO2 ESB. An endpoint may be specified as an address endpoint, WSDL based endpoint, a load balancing endpoint, a fail-over endpoint or an HTTP endpoint. For Typically, the endpoint is the address of a proxy service, which acts as the front end to the actual service. For example, the endpoint for the simple stock quote sample is http: //localhost :9000 /services/SimpleStockQuoteService.
Configuring
...
endpoints
...
In the XML configuration, the <endpoint> element defines an endpoint as follows:
| Code Block | ||
|---|---|---|
| ||
<endpoint [name="string"] [key="string"]>
address-endpoint | default-endpoint | wsdl-endpoint | load-balanced-endpoint | fail-over-endpoint
</endpoint>
|
Using named endpoints
You can use the name attribute to create a named endpoint. You can reuse a named endpoint by referencing it in another endpoint using the key attribute. For example, if there is an endpoint named " foo, " you can reference the "foo" endpoint in any other endpoint where you want to use "foo":
<endpoint key="foo"/>
This approach allows you to reuse existing endpoints in multiple places.
Working with endpoints
You can either use the ESB tooling plug-in to create a new endpoint as well as to import an existing endpoint or you can manage endpoints via the ESB Management Console. For detailed information on how to work with endpoints, see the following topics:
Tracing and handling errors
The endpoints also Endpoints have a trace attribute, which turns on detailed trace information for messages being sent to the endpoint. These are available in the trace.log file, which is configured in the <PRODUCT_HOME>/repository/conf/log4j.properties file. Setting the trace log level to TRACE will log logs detailed trace information including message payloads. For more information on endpoint states and handling errors, see Endpoint Error Handling.
...