Transport Handling

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.

1. Log in to the management console and select Services > List under the Main menu.  
2. From the Deployed Services page that appears, click the service in which you want to configure transports. 
3. The service's dashboard opens. Click Transports from the Quality of Service Configuration panel
4. 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.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.

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.

Enter the parameter name and click "Add." For example,

You will be prompted to enter the parameter value.

Click "Update" once done. The updated settings will take effect immediately and the corresponding transport listener or sender is restarted.

If you do not want to configure parameters, you can click "Cancel." You will be navigated to a "Transport Management" page where you can:

• Enable a disabled transport.
• Disable or configure an enabled transport

 

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

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.

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.