...
- Log in to the management console and select Services > List under the Main menu.
- From the Deployed Services page that appears, click the service in which you want to configure transports.
- The service's dashboard opens. Click Transports from the Quality of Service Configuration panel
- The Transport Management page appears. It lists the available transport listeners and senders. From here, you can add new transports and remove/configure exposed transports separately, without restarting the server.
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.xmlfile. 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.
Configuring Transports
To configure a transport, click the "Configure Transport" link associated with a transport. You will be taken to a page where you can specify configuration parameters for the transport listener or the sender.
...
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. You will notice that the Enable option is still available for that particular transport listener or sender, indicating that it hasn't been enabled. Therefore it is important that you put all the required jars in the <CARBON_HOME>/repository/components/dropins directory before attempting to activate a transport listener or a sender.
Disabling a Transport
To disable an already active transport listener or a sender, click the "Disable" link given on the Transport Management page.
Click "Yes" to confirm.
| Info | ||
|---|---|---|
| ||
TTP and HTTPS transports cannot be disabled since those transports are required by the management console and related administrative services. | ||
| Excerpt | ||
|