Web Services connections through a firewall

If your Service Manager server is behind a firewall, you may need to configure a proxy server redirection to send and receive WSDL and SOAP requests. If your firewall uses the SOCKS protocol, then it can likely handle Web Services redirection requests transparently to the user. If your firewall does not recognize the SOCKS protocol, then you can install a dedicated redirector application for SOCKS traffic such as that generated by Web Services requests.

If you install a redirector application for your Web Services SOAP traffic, then you need to modify the URLs you use to connect to the remote Web Services. To download the remote WSDL, change the URL listed in the WSDL to JS wizard to point to the dedicated socket you have established for the remote Web Service. To send and receive SOAP messages to the Web Service, you can change the location object of your custom JavaScript to the dedicated socket you have established for the remote Web Service.

Example: dedicated socket connection

Define a dedicated socket on port 8888 to the Amazon Search Service using the following proxyconnect command of the connect.c application:

proxyconnect -p 8888 -S 192.168.1.254:1080

http://soap.amazon.com/onca/soap280

To obtain the WSDL for the Amazon Search Service through this example proxy connection, update the WSDL to JS URL to point to:

http://localhost:8888/soap/servlet/rpcrouter

To send to and to receive from the Amazon Search Service SOAP messages , you could update the custom calling script AmazonSearchServiceTestwith the following new line just after the AmazonSearchService.ActorSearchRequest class is initialized.

actorSearchRequest.location =

"http://localhost:8888/soap/servlet/rpcrouter"