Kbase P78175: Seeing change in behavior between 9.1B and 9.1D with PROPATH and Ubroker.properties Environment.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
29/04/2004 |
|
Status: Unverified
SYMPTOM(s):
PROPATH is not working as it did in 9.1B.
CHANGE:
Upgraded from 9.1B to 9.1D
CAUSE:
Bug# 20000803-022 in 9.1B using environment var's in PROPATH prevented a defining an environment variable in the ubroker.properties [Environment] section and referencing that var in PROPATH.
FIX:
Upgrade to 9.1D where is environment variables defined in the ubroker.properties Environment section may be used in the PROPATH.
jvmStart handles the environment variables. The variables from the ubroker.properties file are sent to jvmStart and thus are able to be set before PROPATH is set so the environment variables are picked up.
Example:
In 9.1D if the [Environment.test] section the PROPATH is set:
PROPATH=/usr/dlc/scr/custom
Then in the Ubroker.AS.test PROPATH is defined as follows:
PROPATH=${PROPATH}:/usr1/appl/etc/appserver
The AS.test PROPATH will pick up the PROPATH from the [Environment.test] and appends it to the PROPATH in AS.test at startup of the AdminService.
AS.test PROPATH should be /usr/dlc/scr/custom:/usr1/appl/etc/appserver
Environment.test PROPATH should be /usr/dlc/scr/custom