Custom Connector and Standard Logic Apps

Question

I'm currently engaged with Labware Lims and leveraging Azure Logic Apps as the integration platform for our requirements. Labware Lims relies on SOAP-based communication and utilizes WSDL files for point-to-point integrations.

In this setup, I'm using Azure Logic Apps to create a custom SOAP connector to facilitate the interaction between Labware Lims and our other systems. Notably, I'm already successfully using the built-in SQL Server connector within Logic Apps.

However, during the process of providing the URL of the WSDL file while creating the custom connector, I'm encountering the error message 'Host name resolution failed. Cannot fulfill the request to the remote server.' Interestingly, when I input the same URL into a web browser, I can access the WSDL file without any issues.

Given this context, my approach involves using Azure Logic Apps as the integration platform and creating a custom SOAP connector for Labware Lims integration.

An important aspect I'd appreciate clarification on pertains to the necessity of setting up an on-premises data gateway for this custom connector. Does the custom SOAP connector operate similar to built-in connector, such as the SQL Server connector, and the labware server resides at the same place as sql server?

Considering that the Logic Apps virtual network is already peered, should I enable the checkbox for the on-premises data gateway? Or, in alignment with the smooth operation of existing built-in connectors, should I leave this checkbox unchecked?

Furthermore, I'm eager to understand potential challenges or issues that I might encounter with this custom SOAP connector. Can the connector establish a connection with the Labware Lims server out-of-the-box, or are there additional configurations I need to consider? Your detailed response would be immensely valuable as it would significantly assist me in navigating this integration setup. Thank you!