Transports facilitates receiving and sending messages over a multitude of transport and application-level protocols. For more information on transports and to configure them globally, see Transports.
Follow the steps bellow to configure and enable transports at the service-level using the management console. Transport configurations are saved in the embedded registry and are loaded from there. We also support the traditional axis2.xml file-based transport configuration model. For instance, you can override the transport configurations in the registry by specifying different configurations in the
<PRODUCT_HOME>/conf/axis2/axis2.xml file. Transport configuration details given in the axis2.xml file gets priority over the transport configuration details saved in the registry. Any changes to axis2.xml file require a server restart to take effect. Also, HTTP and HTTPS transports are configured in axis2.xml. Therefore, they are always loaded at the server start-up from the axis2.xml.
If any of the dependencies required to enable the transport listener or the sender are missing, the transport will not be enabled and you will be redirected to the Transport Management page. The Enable option is still available for that particu lar transport listener or sender, indicating that it hasn't been enabled. Therefore, it is important that you put all the required jars in the
<PRODUCT_HOME>/repository/components/dropins f older before attempting to activate a transport listener or a sender.
You cannot disable HTTP and HTTPS transports because they are used by the management console and related administrative services.