Is there a way to set a different persistent super procedure for different Webspeed webApps running on the same PAS instance?

There are 3 webspeed applications on one PASOE instance.

The application need to specify a SUPER_PROC environment variable for every webpeed app with a different value e.g.:

• wsccs: SUPER_PROC="proc/procs.p"; export SUPER_PROC
• wscfn: SUPER_PROC="utils/utilsproc-1.p"; export SUPER_PROC
• wsrep: SUPER_PROC="utils/utilsproc-2.p"; export SUPER_PROC

Can this be done with a single PASOE instance?

The openedge.properties Agent 'sessionStartupProc' property could be used to do this for a single webApp, but it cannot be used with three webApps that have different startup procedure requirements.  There isn't a way to do this out of the box with a single PAS instance. 

To work around this limitation there are two possible options:

• Create three different ABLApps, one for each webspeed application
• Define a Custom Webspeed Compatibility Handler for each webApp and specify any custom code in the HandleRequest method, for example:

openedge.properties:

# Transport properties for the WEB protocol
[Webspeed.Webspeed.WEB]
    adapterEnabled=1
    defaultCookieDomain=
    defaultCookiePath=
    defaultHandler=CustomCompatibilityHandler
    handler1=WebspeedHandler: /Webspeed
    srvrAppMode=development
    srvrDebug=0
    wsRoot=/Webspeed/static/webspeed

USING Progress.Lang.*.
USING OpenEdge.Web.CompatibilityHandler.

BLOCK-LEVEL ON ERROR UNDO, THROW.

CLASS CustomCompatibilityHandler INHERITS CompatibilityHandler: 

    METHOD OVERRIDE PUBLIC INTEGER HandleRequest(  ):
        MESSAGE " Custom Compatibility Handler " view-as alert-box.  
        RETURN SUPER:HandleRequest().
    END METHOD.
END CLASS.

Progress Article(s):

Where to place code to create DB Aliases in order for it to execute prior to requests?

How to create multiple ABL applications in one single PASOE instance.

Must oeabl.war be deployed multiple times when multiple ABL applications run in a single PASOE instance