Transports can be configured and enabled in a global-level as well as service-level through the service's dashboard. The transport management functionality is provided by the "Service Management" feature of the WSO2 feature repository. This feature is bundled by default in all WSO2 service hosting products. If it is not available by default in the product you are using, you can install it by following the instructions given in section Feature Management.
Follow the instructions 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.
Transport Follow the steps bellow to configure and enable transports at the service-level .
1. Log on to the product's management console and select "List" under "Services."
2. The "Deployed Services" screen appears. Click on the necessary service. For example,
3. The "Service Dashboard" page appears. Click "Transports" in the "Quality of Service Configuration" panel.
4. The "Transport Management" page appears.
The Transport Management page lists the available transport listeners and senders. From here, you can add new transports and remove/configure exposed transports separately, without having to restart the server.
using the management console. Transport configurations are saved in the embedded registry and are loaded from there. Service Management feature We also supports 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.
Adding Transports
The drop-down list is populated with all enabled transports which are not added to the service. To add, simply select the transport from the drop-down list and click "Add."
You can see the transport added to the "Exposed Transports" list.
Removing Transports
To remove an added transport from the service, click the "Remove Transport" icon associated with the transport you want to remove.
Click "Yes" to confirm.
Configuring Transports
Also, HTTP and HTTPS transports are configured in axis2.xml. Therefore, they are always loaded at the server start-up from the axis2.xml.
- 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.
- To configure a transport, click the
...
- Configure Transport
...
- icon associated with a transport.
...
- Specify configuration parameters for the transport listener or the sender.
- Enter the parameter name and click
...
- Add
...
...
- to enter the
...
- value.
- Click pdate"
...
- once done.The updated settings
...
- take effect immediately and the corresponding transport listener or sender is restarted.
- If you do not want to configure parameters, you can click
...
- Cancel.
...
- The Transport Management
...
- page opens, where you can:
- Enable a disabled transport
...
- Disable or configure an enabled transport
...
To enable a transport listener or a sender, click the "Enable" link associated with the transport. You will be navigated to a page where the configuration parameters for the transport listener or sender can be specified. The required fields will be populated with default values, which you can change according to your requirements.
Click "Enable" once configuration is done.
Click "Yes" to confirm.
...
Note:
HTTP and HTTPS transports are configured in the axis2.xml. Therefore, they are always loaded at the server start-up from the axis2.xml.
Enabling a Transport
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.
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.
...
| title | Note |
|---|
...
Note You cannot disable HTTP and HTTPS transports because they are used by the management console and related administrative services
...
| hidden | true |
|---|
...
.