Project

General

Profile

PASOE application conversion

Added by Deividas Varzgalys about 3 years ago

I am trying to convert Progress PASOE based application which doesn't have an entry procedure. It is possible to convert? Or it does not support this type(REST) transport.
Does your tool support all (APSV, REST, SOAP, WEB) transports? Or just APSV?
Can you provide more info about application server implementations on converted PASOE based application?
(More detailed configuration process to convert PASOE based application to your suggested application server)


Replies (1)

RE: PASOE application conversion - Added by Greg Shah about 3 years ago

I am trying to convert Progress PASOE based application which doesn't have an entry procedure. It is possible to convert?

Our conversion process is not dependent upon have a specific entry procedure or procedures. The input for the conversion is either a REGEX specification of procedure/class files to process OR it is driven by a file containing include or exclude specfications. Either way, so long as the conversion know what procedures/classes to convert, it will do so. It is not dependent upon PASOE or the transports used in PASOE.

Or it does not support this type(REST) transport.
Does your tool support all (APSV, REST, SOAP, WEB) transports? Or just APSV?

We've had support for classic appserver in prior versions (since FWD v2). Most of PASOE is supported in v4 (see #3854).

We support APSV, REST (see #3855) and SOAP (see #3310) all nearly 100%. WEB is partial (see #3855). We support a basic form of the WebHandler and have some front end (parsing) support for webspeed code but the core traditional webspeed support is not yet there. It can be added for a given project as needed.

More detailed configuration process to convert PASOE based application to your suggested application server

  • Make sure that the procedures/classes (and all includes) are present and that the conversion is configured to process all of the procedures/classes which will be needed, including anything that is a dependency of the code being called via any mechanism (interactive code, REST, SOAP... whatever).
  • APSV usage does not have special requirements for converting the 4GL code, but for the runtime configuration please see Setup of a FWD Appserver
  • Steps for configuring conversion can be found in Converting REST and SOAP.
  • Steps for configuring the runtime can be found in Runtime Configuration for REST and SOAP

You will details about our WebHandler support in those same REST/SOAP chapters.

For your current testing, do you need details on replacing Open Client usage?

    (1-1/1)