Is it possible to configure the Web Services Adapter (WSA) to communicate with a PASOE instance ? - Progress Community

Loading

Skip to Main Content

Is it possible to configure the Web Services Adapter (WSA) to communicate with a PASOE instance ?

This article explains why the Web Services Adapter (WSA) is unable to communicate with the PASOE. It also provides information on how to maintain the same distributed configuration as the WSA in a DMZ with the Classic AppServer, using a reverse proxy.

Mar 24, 2021
Knowledge

Title

Is it possible to configure the Web Services Adapter (WSA) to communicate with a PASOE instance ?

URL Name

How-to-configure-the-WebServices-Adapter-WSA-to-communicate-with-the-PASOE

Article Number

000188966

Environment

Product: Progress Application Server for OpenEdge (PASOE) Version: 11.6 and later, 12.x OS: All Supported platforms Other: Web Services

Question/Problem Description

Is it possible to configure the Web Services Adapter (WSA) to communicate with a PASOE instance ?

How to configure the Web Services Adapter (WSA) to communicate with a PASOE instance ?

Steps to Reproduce

Clarifying Information

Error Message

Defect Number

Enhancement Number

Cause

Resolution

The WSA can only communicate with the Classic AppServer. This is because the target URL for the classic and PASOE are different. The reason it's 'forbidden' is there's no such thing as a 'wsa' PAS Transport

The WSA allows the target AppServer information to be specified by changing parameters in the .props file:

appServiceProtocol
appServiceHost
appServicePort
appServiceName

Based on this information the WSA builds the target URL for the classic AppServer, for instance: AppServer://localhost:5162/asbroker1
Hypothetically, the Classic configuration would be as follows for PAS: http://localhost:8810/apsv

appServiceProtocol http [ psc.as.http.port ]
appServiceHost localhost [psc.as.hostname ]
appServicePort 8810 [ psc.as.http.port ]
appServiceName apsv transport : What are the PASOE transports?

wsaURL is configured in the openedge.properties:
wsaUrl=http://${psc.as.host.name}:${psc.as.http.port}/soap

In Classic UBroker Secure environments, the AppServer is isolated from the Internet and the WSA runs in the DMZ section of the network.
PASOE uses the SOAP transport to replace the WSA (Web Services Adapter): How to deploy .wsm file in PASOE from proenv

When deployed to ROOT: http://localhost:8810/soap/wsdl?targetURI=<NameSpace>
Otherwise the Web app name: http://localhost:8810/<Web Application>/soap/wsdl?targetURI=<NameSpace>

Configure the SOAP Endpoint in the <PASOE instance>\conf\openedge.properties file. The property is called: wsaUrl

Since OpenEdge 12.2, http://localhost:8810/soap not only shows if the instance is responding, but also shows the list of deployed SOAP services (comparable to the classic WSA)

What is the meaning of the PASOE REST/SOAP transport 'status enabled' parameter ?

The URL used in the application code is not the URL to the WSDL document. Run bprowsdldoc against your WSDL document to get the code to call your web service:

How to consume a Web Service from an OpenEdge client ?

Unlike the classic model, a PASOE instance cannot be 'split' between the DMZ and the firewalled network. The architected solution therefore is to connect from the Web Server in DMZ (IIS or Apache httpd) using mod_jk or any similar connector with the PASOE AJP13 connector:

With PASOE integrating the SOAP transport, you can configure a reverse proxy server in replacement of the WSA.
This DMZ-based http proxy will forward the incoming client requests directly to the PASOE.
Apache, NGINX, IIS can all be configured as reverse proxy servers.

This is outlined in the following Article, which also provides related Documentation References:

How to configure PASOE to run in a DMZ?

Workaround

Notes

References to Documentation:

Migrate Classic AppServer Applications to PAS for OpenEdge: ABL Application Code Migration, Migrate client connections to PAS for OpenEdge - Migrate WSA URLs to use the SOAP transport
https://docs.progress.com/bundle/openedge-migrate-classic-appserver-128/page/Migrate-WSA-URLs-to-use-the-SOAP-transport.html

OpenEdge Development: Web Services: Exposing AppServer Applications as OpenEdge SOAP Web Services, Distributing your WSDL file:
https://docs.progress.com/bundle/develop-openedge-webservices-122/page/Distributing-your-WSDL-file.html

Keyword Phrase

Last Modified Date

5/13/2026 1:08 PM

OpenEdge DeploymentOpenEdge ArchitectureOpenEdge DevelopmentOpenEdge General DiscussionsOpenEdge Pro2OpenEdge RDBMS

Drop Files

Upload FilesOr drop files

Disclaimer

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.

Loading

Is it possible to configure the Web Services Adapter (WSA) to communicate with a PASOE instance ? - Progress Community