Troubleshooting
Problem
When promoting from one environment to another (for example: development -> test -> staging -> production), different WSDL URLs may be required. This document explains some possible strategies for accommodating those changes.
Resolving The Problem
Currently, using the standard "discovery" style web service connectors, you cannot setup a variable to represent the WSDL URL. This is an enhancement that has been requested by customers and is currently assigned to Engineering.
The workarounds in use by customers are:
1. Refer to a "dummy" entry in the server "hosts" file that resolves to the WSDL host. This way, hosts on development will point to the dev WSDL host and hosts on the production server will point to the production WSDL host.
2. Use a file:// based WSDL URL. Store the WSDL file itself in the same file path in each environment, but use different contents with custom hostnames and/or endpoint URLs therein.
3. Use the generic SOAP connector rather than the discovery-type web service connector. This will accept variables for all parameters, but is harder to configure.
Option 1 is often the simplest approach.
Historical Number
310
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21439726