Migrate WSA URLs to use the SOAP transport
- Last Updated: January 23, 2026
- 2 minute read
- OpenEdge
- Version 12.8
- Documentation
How you connect SOAP web service clients varies significantly with the client platform, but they all provide a way to specify a URL to the WSDL file and the web service they are connecting to.
-WSDL
connection parameter to the CONNECT( ) method might be
the following for a classic OpenEdge Web Services Adapter (WSA) connection:
|
|
If the soap URI is soap or omitted, then it connects to the default ROOT ABL web application. If soap is asbroker1WebAppl/soap, then it
connects to the ABL web application with the name, asbroker1WebAppl, which is deployed in the WAR file, asbroker1WebAppl.war.
wsa1.
This is to illustrate that all three web connection transports can be supported in a
single ABL web application on PAS for OpenEdge as long as they can all ultimately access
the same server ABL code base.Note also that just as for a connection to the classic WSA, you specify the exact URL for a connection to an OpenEdge SOAP web service when you deploy the web service. This generates the deployment WSDL file that contains the updated connection URL. It might also be possible to deploy the same WSM file to PAS for OpenEdge that you originally created from generating an existing SOAP web service for the classic WSA using ProxyGen. For more information on OpenEdge SOAP web service deployment to PAS for OpenEdge, see Deploy SOAP services in Manage Progress Application Server (PAS) for OpenEdge, and Manage SOAP transports in Manage Progress Application Server (PAS) for OpenEdge with OpenEdge Management.
For more information on connecting to a SOAP web service from an ABL client, see the topics on creating ABL clients to consume SOAP web services in Develop an ABL SOAP Client.