PAS for OpenEdge is available as a host for WebSpeed applications. You can migrate existing WebSpeed applications to PAS for OpenEdge, or you can use the Progress Developer Studio for OpenEdge to develop new WebSpeed applications that run on PAS for OpenEdge.

This topic describes migrating an existing (classic) WebSpeed applications. For information about developing new web applications for PAS for OpenEdge using the WEB transport, see Application servers, web applications, and services.

This task-based video reviews the most common steps needed to migrate WebSpeed applications to PAS for OpenEdge.

To migrate a WebSpeed application to a PAS for OpenEdge instance, you must do the following:
  1. Move the application's static files to a specific folder in the instance.
  2. Update the PROPATH for the instance to include the folders that contain the application's r-code.
  3. Enable the WEB transport on the instance and use the compatibility handler in the openedge.properties file.

Static files

A PAS for OpenEdge instance requires the static files that support a WebSpeed application to be in a particular location in the instance's directory structure. Static files include images and HTML files.

The location of the static files for the default web application is:

instance_name/webapps/ROOT/static

If you deploy another application, then the default location for its static files is: 

instance_name/webapps/webapp_name/static

where webapp_name is the name of the WebSpeed application or ABL web application.

r-code

To enable a PAS for OpenEdge instance to find a WebSpeed application's r-code, add any folders that contain WebSpeed application r-code files to the instance agent's PROPATH.

The default location for r-code is:

instance_name/openedge

PROPATH is set in the instance_name/conf/openedge.properties file. For example:

[AppServer.Agent]
	PROPATH=${CATALINA_BASE}/openedge,${DLC}/tty,${DLC}/tty/netlib/OpenEdge.Net.pl
Note: CATALINA_BASE is an environment variable that resolves to instance_path.

Update openedge.properties to enable WEB transport

Ensure that the instance-name/conf/openedge.properties has the WEB transport enabled and the defaultHandler is set to OpenEdge.Web.CompatibilityHandler. For example:

[abl_app_name.ROOT.WEB]    
	adapterEnabled=1    
	defaultCookieDomain=    
	defaultCookiePath=    
	defaultHandler=OpenEdge.Web.CompatibilityHandler

Migration Notes

Before you migrate an existing WebSpeed application to an instance of PAS for OpenEdge, note the following:
  • A PAS for OpenEdge instance must be created from an OpenEdge 11.6 or later release because that is when the OpenEdge.Web.CompatibilityHandler was introduced.

    For information about creating, starting, and stopping instances, see Create and Configure PAS for OpenEdge instances.

  • R-code should be located on the same machine where the PAS for OpenEdge instance is running. R-code on network-mapped drives can cause issues with performance and permissions.
  • Recompile r-code only if it was generated in OpenEdge 10.x or earlier releases.
  • WebSpeed applications that use HTML mapping are not supported.
  • WebSpeed applications with a modified web-disp.p and supporting files will not run without making changes to the default WebHandler.
  • WSASP, WSISA, NSAPI, and CGIIP messengers are not necessary. They are not supported and cannot be configured in a PAS for OpenEdge instance. Because there is no Messenger, the application connection URL changes.

    In classic WebSpeed, the URL path included the Messenger in the scripts directory of the web server, and then the path to the code. For example:

     http://hostname:port/cgi/wspd_cgi.sh/. . .
    In PAS for OpenEdge, the default URL references the WebSpeed transport (WEB) and not the Messenger. For example:
     http://hostname:port/web/. . .