To deploy or publish an ABL WebApp project with WebSpeed feature, follow the steps:

Note: The instance directory will be referenced using the environment variable CATALINA_BASE in the steps below.
  1. Copy static files used by the WebSpeed application to ${CATALINA_BASE}/webapps/<webapp>/static/webspeed (the default location), or another directory under ${CATALINA_BASE}/webapps/<webapp>.
  2. If you've made any modifications to web/objects/web-util.p to support your WebSpeed application, migrate them to the newer version of web/objects/web-util.p where significant changes have been implemented to support running in a multi-session agent (_mproapsv)
  3. In ${CATALINA_BASE}/conf/openedge.properties, locate the [<CATALINA_BASE>.<webapp>.WEB] node, where <CATALINA_BASE> is the instance name and <webapp> is the name of the named webapp or ROOT for the ROOT webapp.
    1. Modify the wsRoot property to specify the directory where the static files are located. Make sure the directory specification begins with / and is relative to ${CATALINA_BASE}/webapps/<webapp> (<webapp> may be ROOT).
    2. Confirm that the defaultHandler property is set to OpenEdge.Web.CompatibilityHandler.
  4. The url to run the WebSpeed application on PAS for OpenEdge will be in one of the following forms:
    • For the ROOT webapp:
      http://<host>[:port]/web/<path to r-code>
    • For a named webapp:
      http://<host>[:port/<webapp>/web/<path to r-code>
    Note: The path to the r-code is relative to the PROPATH.
    WebSpeed applications that use the following features cannot be migrated in this way:
    • WebSpeed applications that use HTML mapping are not supported.
    • WebSpeed applications with a modified web-disp.p and supporting files will need the custom Web Handler, web-handler.p, to implement the necessary customizations. This file can be found in $DLC/src/web/objects/web-handler.p.