Backward compatibility of sedex Web Service Proxy 6.0

The core functionality of the sedex Web Service Proxy 6.0 is backward compatible. A business application accessing Web services via sedex Web Service Proxy version 5.x can generally do the same with sedex Web Service Proxy version 6.0 without modification.

However, changes to business applications may be necessary in the following cases:

• Using HTTPS instead of HTTP

  If a business application should no longer access the sedex Web Service Proxy via the open HTTP protocol but via the secure HTTPS protocol, the end point of the business application must be switched to HTTPS and the SSL/TLS certificate must be included in the trust store of the application (if it is not an officially trusted certificate).

• Access control required

  If the use of a Web service now requires access control, the business application must call the sedex Web Service Proxy with the corresponding username and password via the secure HTTPS protocol.

• Changes in SOAP Messages

  If a business application can no longer handle SOAP requests and responses (i.e. the SOAP messages still conform to the scheme, but details have changed), the problem must be analyzed and solved by adapting the business application. This case should be very rare and be discussed with FSO’s sedex Customer Support.

• Accessing WSDL files at runtime

  The WS Proxy no longer contains the WSDL files of a SOAP Web service itself. Instead, it passes requests for the WSDL file (an HTTP GET request to the URL ending with ?wsdl) unchanged to the target Web service. If the target Web service offers the WSDL in this way, the business application will still be able to obtain WSDL files at runtime via the Web Service Proxy. However, the format may look slightly different.