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 Axis 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 WSO2 ESB 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 WSO2 ESB, see WSO2 ESB Inbound Endpoints.
When it comes to creating and managing inbound endpoints, you can use the ESB tooling plug-in to create a new inbound endpoint or to import an existing inbound endpoint. It is also possible to manage inbound endpoints via the ESB Management Console. For detailed information on how to work with inbound endpoints, see the following topics:
- Working with Inbound Endpoints via WSO2 ESB Tooling
- Managing Inbound Endpoints via the Management Console