An inbound endpoint is a message entry point that can inject messages directly from the transport layer to the mediation layer, without going through the Axis2 engine. The following diagram illustrates the inbound endpoint architecture.
Out of the existing transports only the HTTP transport supports multi-tenancy, this is one limitation that is overcome with the introduction of the inbound architecture. Another limitation when it comes to conventional Axis2 based transports is that the transports do not support dynamic configurations. With the ESB profile inbound endpoints, it is possible to create inbound messaging channels dynamically, and there is also built-in cluster coordination as well as multi-tenancy support for all transports.
For detailed information on each type of inbound endpoint available with the ESB profile, see WSO2 EI Inbound Endpoints.
Working with Inbound Endpoints
When it comes to creating and managing inbound endpoints, you can use tooling to create a new inbound endpoint and to import an existing inbound endpoint, or you can manage inbound endpoints via the WSO2 EI Management Console. For detailed information on how to work with inbound endpoints, see the following topics: