P
Peter Judge
Guest
It was a bit of a challenge to work thru this stuff. First of all, when multiple ABL applications and multiple ABL webapps are in play, the PDSOE does the *least* helpful thing it can possibly do when it publishes your code modules into "catalina.base"\openedge. Essentially this causes all code, whether related or not, to be "flattened" out into the same massive code directory without any organization. That particular directory is shared for the entire PAS instance. Agreed. We have plans/backlog items to make this better. You can do a couple of things in the interim - In your instances, there should be an ablapps/ / folder already (in 11.7 something, maybe .0). I’d add an openedge/ folder to that, and add that folder to PROPATH in the instance config. Now you should have a default propath that looks something like ${CATALINA_BASE}/webapps/ROOT/WEB-INF/openedge, ${CATALINA_BASE}/ablapps/oepas1/openedge, ${CATALINA_BASE}/openedge, ${DLC}/tty (assuming an ablapp of oepas1 and the default ROOT webapp) The ${CATALINA_BASE}/openedge directory is for common libraries/code like framework code. The ${CATALINA_BASE}/ablapps/oepas1/openedge folder is for this-application’s code (business logic) The ${CATALINA_BASE}/webapps/ROOT/WEB-INF/openedge folder is for service interfaces into that business logic - In PDSOE set your publish location to ${CATALINA_BASE}/ablapps/oepas1/openedge for the ABL Service projects/ - You may need to manually deploy the code into the instance’s openedge/ folder.
Continue reading...
Continue reading...