An overview of the sample tools and components that provide models for customizing web services.
The required components of the SDK custom web services are generated automatically using Apache Axis org.apache.axis.wsdl.Java2WSDL and org.apache.axis.wsdl.WSDL2Java generation tools.
For more information about these tools, see the
Apache Axis User Guide, the
Apache Axis Java2WSDL Reference Guide, and the
Apache Axis WSDL2Java Reference Guide.
Important: Web services are meant to be used for testing SOAP API calls and should
never be exposed publicly. There are several ways to prevent the
/webservices directory from being accessed:
- By using advanced firewall rules.
- By using load balancing rules.
- By restricting the path in the apache-tomcat/conf/server.xml file.
If you have developers who work with SOAP API calls and need access to
/webservices, you could implement one of the first two options so that the URL can only be accessed internally. The third option completely disables any
/webservices path.
To implement the third option, open the
server.xml file with a text editor and add the following lines within
<Host> elements:
<Context path="/ws-legacy/webservices" docBase="" >
<Valapp className="org.apache.catalina.valapps.RemoteAddrValapp" deny="*" />
</Context>
For example: