M
Michael Jacobs
Guest
To expand on Irfan's response: The server instance's conf/openedge.properties is a single point of configuring all of the OpenEdge related components, which can run in either the PAS [java] web server or in the multi-session agent. Every property for components running in the PAS [java] web server resolves Java system properties ( like ${psc....}, and every property used by the multi-session agent resolves OS process environment variables ( like ${DLC} ). I try to remember that if the group begins with [AppServer.Agent... ] I use OS process environment variables and for everything else I use Java system properties. PAS will automatically execute the instance's /bin directory's *_setenv.sh ( *_setenv.bat for that Windows thing ) scripts at startup. So for instance I like to create a 'myapp_setenv.sh' in the /bin directory and place all of the OS process environment variable definitions there. The standard OS process environment variable ${CATALINA_BASE} will resolve to the PASOE instance's root directory path and is handy in the ABL Agent for getting at the work and temp directories. Mike J. From: Irfan bounce-isyed@community.progress.com Reply-To: " TU.OE.General@community.progress.com " TU.OE.General@community.progress.com Date: Friday, March 13, 2015 at 12:10 PM To: " TU.OE.General@community.progress.com " TU.OE.General@community.progress.com Subject: RE: [Technical Users - OE General] How to use (environment) variables in PASOE propath RE: How to use (environment) variables in PASOE propath Reply by Irfan You can define environment variables in PASOE, but setting a _setenv.sh or _setenv.bat file in the instance bin directory and get the variable value in the server logic by OS-GETENV("name of the the variable"). Stop receiving emails on this subject. Flag this post as spam/abuse.
Continue reading...
Continue reading...