This is the WSO2 Data Services Server documentation version 2.6.3

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Follow the instructions below to enable/disable transports.

1. Log on to the Application Server Management Console.



2. Click the "Configure" menu and select "Transports" to access "Transport Management."



3. The "Transport Management" page lists the available transport listeners and senders. From here, you can enable, disable and configure transport listeners and senders separately, without having to restart the server.

  • Enable transports
  • Disable transports

Enabling Transports

Follow the instructions below to enable transports.

4. Click on the "Enable" link of a certain transport listener/sender.

5. You will be taken to a page where you can specify configuration parameters for the transport listener or the sender you want to enable. You will notice that all the required fields are already populated with a set of default values. Change the default values to suit the requirements of your deployment and click "Enable" to enable the transport listener/sender.

Note

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 back 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 has not 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 Transports

Follow the instructions below to disable transports.

Note

HTTP and HTTPS transports are configured in the axis2.xml. They are always loaded from the axis2.xml at the server startup. Also HTTP and HTTPS transports cannot be disabled since those transports are required by the Carbon management console and related administrative services. In case of HTTP/HTTPS transport listeners and senders, you will receive a warning dialog indicating that those transports cannot be disabled.


4. Click on the "Disable" link of a certain transport listener/sender.

5. Confirm your request to disable transport listener/sender by clicking "Yes."

  • No labels