Currently a WSDL contract is necessary when creating the connector. However, once the connector is set up, it doesn't need ongoing access to the contract. On an on-premises server setup, the contract could simply be placed in the file system and accessed from there. However, on a cloud setup, direct file system hosting isn't possible.

One suggestion is using a file system connector, which would allow users to upload the file onto the cloud server and then point to it. However, this approach is somewhat unconventional and a bit of a “rouge style”. An additional layer of complexity exists if there are linked XSD files in the WSDL. If the WSDL is to be hosted on disk, it needs to be self-contained, meaning all necessary components, like XSD files, should be integrated directly within the WSDL or be locally referenceable without external dependencies. Ultimately, the best option is that the contract need to be hosted as a proper web service or the WSDL must be modified to ensure it is self-contained if hosted from a disk.