Kbase 17694: How PROPATH works in WebSpeed 2.x for NT
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
How PROPATH works in WebSpeed 2.x for NT
The use of PROPATH in WebSpeed 2.x for NT is often a
confusing issue. This knowledge base will atttempt to
explain how PROPATH is implemented in WebSpeed 2.x.
The most important point to remember when trying to understand
how PROPATH works is who installed WebSpeed. This user is
considered to be the "Current User", regardless of who
happens to be logged into the machine at any given time.
It is also important to understand that during the
installation, there is a question "Do you want this
installation to be the default for all users?" The answer
you give to this question will affect the way PROPATH
works.
When WebSpeed selects a PROPATH, it first looks in the NT
Registry under HKEY_CURRENT_USER. It then looks in
HKEY_LOCAL_MACHINE. Finally, if there is no entry in
either registry location, it looks in
%DLC%\bin\progress.ini. The PROPATHs shown in the WebSpeed
Configuration Utility are "Application PROPATH for Current
User" which is taken from HKEY_CURRENT_USER, and
"Application PROPATH for All Users" which is taken from
HKEY_LOCAL_MACHINE. It is important to remember that the
only user that will have a PROPATH in HKEY_CURRENT_USER is
the user that installed WebSpeed. If you make the
installation the default for all users, there will also be
a registry entry for HKEY_LOCAL_MACHINE.
First, let's assume that during the installation, you made
the installation the default for all users. In this case,
there will be a PROPATH registry entry in
HKEY_LOCAL_MACHINE, and two PROPATHS will show up in the
Configuration Utility - "Application PROPATH for Current
User" and "Application PROPATH for All Users". Which
PROPATH will be used depends on who owns the WebSpeed
service. This can be determined by checking the user on
the "General" tab of the Configuration Utility. If the
user that owns the service is the same as the user that
installed WebSpeed, there will be an entry in
HKEY_CURRENT_USER and WebSpeed agents will use the
"Application PROPATH for Current User". If the user that
owns the service is different than the user that installed
WebSpeed, there will be no entry in HKEY_CURRENT_USER, and
WebSpeed agents will use the "Application PROPATH for All
Users".
Now let's assume that you did NOT make the installation the
default for all users. In this case, there is no entry for
HKEY_LOCAL_MACHINE, and you will see that the "Application
PROPATH for All Users" fill-in in the Configuration
Utility is disabled. In this case, the only way to change
the PROPATH from the configuration utility is to be sure
the service is owned by the user that installed WebSpeed,
and change the "Application PROPATH for Current User".
What happens in the case where the installer did not make
the installation the default for all users, and the owner
of the service is not the installer? In this case, there
is no PROPATH entry in either HKEY_CURRENT_USER or
HKEY_LOCAL_MACHINE. This situation should be avoided,
because the choice of PROPATH in this case is not obvious
and cannot be changed from the Configuration Utility. You
will only be able to change the "Application PROPATH for
Current User", but since the service owner is not the
installer, this PROPATH will actually be ignored. Instead,
the PROPATH will be taken from %DLC%\bin\progress.ini.
For more information on using network drives in PROPATH,
see kbase 17336, "Using Networked Drives in PROPATH with
WebSpeed 2.0 on NT".
JHD - 2/13/98
Progress Software Technical Support Note # 17694