Transports can be configured and enabled in a global-level or a service-level. Service-level transport management is applicable if the product has service management capability in it. Globally enabled and configured transports effect all services deployed in a running Carbon instance. The axis2.xml file can be used to configure and enable transports globally
...
WSO2 Carbon and all Carbon-based products are shipped with a configuration file named axis2.xml. This XML configuration file can be found at <PRODUCT_HOME>/ repository/conf/axis2 directory. This is si milar to the axis2.xml file that ships with "Apache Axis2" and "Apache Synapse." It contains the global configuration for WSO2 Carbon and the Carbon-based products. The axis2.xml configuration generally includes configuration details for modules, phases, handlers, global configuration parameters and transports. The elements <transportReceiver> and <transportSender> are used to configure transport listeners and senders respectively. In the axis2.xml file that comes with WSO2 Carbon or any Carbon-based product, some transports are already configured and enabled by default, including the HTTP and HTTPS transports.
| Info |
|---|
WSO2 products do not use the HTTP/S servlet transport configurations that are in However, products like WSO2 ESB uses use the HTTP Pass Through transport in axis2.xml. |
...