Skip to end of metadata
Go to start of metadata

The TCP transport is implemented in the Apache WS-Commons Transport project. All the classes required for the TCP transport are packed into the bundle named axis2-transport-tcp-<version>. The following classes act as the transport receiver and sender respectively:

  • org.apache.axis2.transport.tcp.TCPServer 
  • org.apache.axis2.transport.tcp.TCPTransportSender

The following topics explain the process of installing the TCP transport in WSO2 AS:

Step 1: Deploying the required bundles

In order to use this transport, the axis2-transport-tcp-<version> OSGi bundle should be added to the server. This can be done in two ways:

  • Install the TCP transport feature that is available in the WSO2 feature repository. See the instructions for installing features.

    Note that there is a separate feature repository for each Carbon release. You will find all the repositories listed here. Therefore, when you install a feature for your product version, make sure to use the feature version that is relevant to your product version.

  • Alternatively, you can manually download the axis2-transport-tcp-<version> bundle from here and add it to the <AS_HOME>/repository/components/dropins directory.

Step 2: Enabling the TCP transport in the product configurations

To enable the TCP transport, open the <AS_HOME>/repository/conf/axis2.xml file and add the following transport receiver/sender configurations:

<transportReceiver name="tcp">
    <parameter name="transport.tcp.port">6060</parameter>

<transportSender name="tcp"/>

Given below are the parameters that can be used in the axis2.xml file when you configure the 'transport receiver'. Note that the TCP transport sender does not accept any configuration parameters as of now. 

Parameter Name



Possible Values

Default Value


The port on which the TCP server should listen for incoming messages.


A positive integer less than 65535.



The host name of the server to be displayed in WSDLs etc.


A valid host name or an IP address.


Step 3: Restart the server

Restart the server after completing the above steps to enable the TCP transport.

  • No labels