P
Peter Judge
Guest
PASOE's multisession agent still uses PROPATH in the same way that any AVM does. So if ABL code is on PROPATH, then normal rules apply. If you have ABL code in the instance's directory structure that's in a directory that's not on PROPATH, it won't run. There are 3 places in a PASOE instance that are provided for ABL code by default: /openedge /webapps/ /WEB-INF/openedge $DLC/tty/** (1) is for code that is common to all the ABL apps and ABL webapps in an instance. that would be a good place for code that is comon to all - stuff like framework or util code. This folder is on the PROPATH for all the ABL apps in an instance. (2) is for ABL code that is used for service interfaces - code that lets a client "in" to the ABL application. (3) is for ABL code that Progress ships, inclding the webhandlers in $DLC/tty/netlib/OpenEdge.Net.pl You can see that there's no place for code that's specific to an ABL application: I would suggest you create a /ablapps/ /openedge directory and add code in there. You will need to manually do this and also manually add that path to PROPATH. You can, of course, also have that code anywhere on PROPATH. PROPATH is not limited to the instance's directories, but having it all in an instance means that it is easier to package/zip and deploy to another host/machine. I would not recommend having the db in the instance folder staructure, since we may want to be able to scale a number of these instances to handle load, and they all need to be able to write to a single (set of) database(s). You can see the PROPATH values in /conf/openedge.properties in the [AppServer.Agent. ] sections. HTH, -- peter
Continue reading...
Continue reading...