Kbase P41394: What should @{WorkPath} refer to under Working Directory, wh
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/09/2003 |
|
Status: Unverified
GOAL:
What should @{WorkPath} refer to under Working Directory, when defining the WebSpeed Broker properties with Progress Explorer?
GOAL:
What should be the working directory for the WebSpeed broker?
FACT(s) (Environment):
Windows
FACT(s) (Environment):
Progress 9.1D
FIX:
The properties for WebSpeed brokers can be defined using the Progress Explorer. Right-click on the broker and select Properties. Under Broker - General, there is a fill-in for the Working Directory. By default the value for this is @{WorkPath}, but can be explicitly specified using the Progress Explorer.
The @{WorkPath} variable refers to the value for the Progress working directory that is stored in the registry and ini file; this is the default value that is set during the installation of Progress.
If changed in the registry, the value will be taken over by all other instances of the @{WorkPath} variable. If changed only in a fill-in, the changed value will only apply to the property that the fill-in refers to. However, the value can be changed in the fill-ins under Progress Explorer to reference another directory; any instances of @{WorkPath} that shouldn't reference the registry entry have to be defined manually.
For example, if @{WorkPath} is changed for wsbroker1 under Broker - General - Working Directory to C:\wswork\wsbroker1, then the associated temp files appear in this directory. The wsbroker1.broker.log, however, will not appear in this directory since the broker log for wsbroker has its own property settings, defined under Broker - Logging - Setting. By default broker.log file will use @{WorkPath} and will pick up the registry value. If the broker log file should also use the working directory defined for wsbroker1, then this has to be explicitly specified, as indicated above.