Activating TCP Transport on the Server Side

a. Go to the Software AG_directory /profiles/CTP/workspace/wsstack/repository/conf directory and open the axis2.xml file.

b. Uncomment the sections that define the transport receiver and transport sender with name="tcp":

The only parameter required for the transport receiver is its port number. The suggested value is 6060.

2. Restart Web Services Stack.

3. Since the TCP transport has no application level headers (and no target endpoint URI), you need WS-Addressing to dispatch the service. WS-Addressing may not be enabled in the default Web Services Stack installation. Enable WS-Addressing as follows:

a. Engage the WS-Addressing module globally by adding in the axis2.xml configuration file the following line:

b. Engage the WS-Addressing module on a <service> level. Engagement is for the service that is deployed on TCP transport.You can enable WS-Addressing in the services.xml configuration file by adding the following line:

c. Enable WS-Addressing by using the Web Services Stack plug-in to Software AG Designer. To do so, select Enable WS-Addressing from the Modules list in the Services tab. For more information, see Web Services Stack Help.

4. If not explicitly configured, a web service is deployed over all activated transports in Web Services Stack. In this case, the web service is accessible at all enabled endpoints. You may, however, want to restrict a web service to be accessible only over TCP transport.

a. Configure the web service’s services.xml file by adding the following on the <service> level:

b. Use Web Services StackDesigner plug-in at deployment time. To do this, select TCP Transport from the list of transports in the Services tab.

Note:
Since TCP transport has no application level headers, and thus no target endpoint URI, you need WS-Addressing to dispatch the service. If WS-Addressing is not globally enabled, you have to enable it for the service.