Kbase P11892: Variables are not populated when calling proset.env from ubu
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/03/2003 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.1X
FACT(s) (Environment):
UNIX
SYMPTOM(s):
Variables defined in proset.env called by asbman are not populated
Variables defined in proset.env called by wtbman are not populated
Variables defined in proset.env called by ubutil are not populated
Unable to use environment variables defined in proset.env with WebSpeed
Unable to use environment variables defined in proset.env with AppServer
CAUSE:
Unified broker is started as a child process of the AdminServer, so if those variables are not set during the AdminServer startup, unified broker will not be aware about those variables, even if they are set using proset.env called by ubutil (asbman, wtbman).
When AdminServer is started, the java process(es) is(are) spawned. When the new unified broker is started using the command line utilities (e.g. asbman, wtbman etc.), java process that is started connects to the AdminServer's java process using Java RMI, it sends the message containing the instruction as which instance of the unified broker AdminServer should start, it awaits for acknowledgment and then it disconnects and shuts down itself. AdminServer will then spawn a new java process which represents the instance of the unified broker and which inherits all the environment from it's parent process i.e. AdminServer. Therefore the environment set when issuing the command (asbman, wtbman etc.) will not be known to the new instance of unified broker spawned by the AdminServer.
FIX:
Put all your needed variable definitons into proset.env executed by proadsv.