Previous Topic: SDKWS (SDK Web Services) ConnectorNext Topic: Prerequisite Knowledge


How the SDKWS Connector Works

The SDKWS sample connector is a Java connector. The connector ships with a sample web service endpoint named Forward Inc that is hosted in Apache Tomcat.

The connector sends SOAP requests to the Forward Inc web service endpoint as shown in the following diagram:

The SDKWS sample connector uses SOAP over HTTP to communicate with the Forward Inc endpoint

The connector uses generated classes named stubs to handle the communication between the connector and the endpoint. The stubs are generated at development time from the Forward Inc WSDL files. The stub classes let the programmer work with classes that represent the objects and services on the endpoint rather than directly with SOAP. Apache AXIS2 translates the stubs into SOAP.

The WSS user name token secures the Forward Inc web application. AXIS2 uses a plug-in module named Rampart to handle creation (on the client side) and validation (on the server side) of the WSS user name tokens.

The Rampart module in the connector uses SOAP over HTTP to communicate with the Rampart module  in the endpoint

Note: For more information about Apache Tomcat, see http://tomcat.apache.org/

For more information about Apache AXIS 2, see http://ws.apache.org/axis2/

For more information about Apache Rampart, see http://ws.apache.org/axis2/modules/rampart/1_0/security-module.html