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.

For example, an ABL client -WSDL connection parameter to the CONNECT( ) method might be the following for a classic OpenEdge Web Services Adapter (WSA) connection:

"-WSDL http://host:port/wsa/wsa1/wsdl?targetURI=urn:CustomerSvc"

The equivalent SOAP connection parameter for a PAS for OpenEdge connection might be the following:

"-WSDL http://host:port/soap/wsdl?targetURI=urn:CustomerSvc"

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.

Note: This example uses the same WAR file name as in the previous example of a classic AIA URL migration (see Migrate AIA URLs to use the APSV transport), instead of using a file name that reflects the original name of the WSA instance, 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 and Manage SOAP transports.

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.