Kbase P84757: Deploying a database on the same machine as a Terminal Server hosting the clients
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
26/06/2009 |
|
Status: Verified
GOAL:
Deploying a database on the same machine as a Terminal Server hosting the clients
GOAL:
How to configure Progress in a terminal server environment so everything runs on the same machine.
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.x
Windows
FIX:
Especially for smaller sites using Terminal Server, it may be more efficient to have everything run on the same server machine.
The benefits of such an environment are:
1. Only one server machine. This is easier to administrate and usually more cost-effective than having to maintain multiple machines.
2. The possibility to use shared memory connections to the database. This eliminates the networking layer of the database connection, which will usually result in a significant performance boost.
3. As the database product includes the client software required for point 2, no installation for Client Networking is required if no further components of the Client Networking product are required (such as ODBC client software).
To configure such an environment:
1. Install the relevant Progress products on the server machine hosting the terminal services. As usual, take care to insure this is done in installation mode.
2. Configure the database(s) to start in multi-user mode as usual.
3. Configure the clients so they make a Shared Memory connection to the database by specifying the pathname to the .db file, and omitting the -H, -S, -N networking parameters. Also, make sure each user uses it's own directory for temporary files.
A typical command line to start a GUI client will look like:
prowin32 -db C:\application\databases\main.db -T %TEMP% -p program.p
Note that the path to the database can either be fully qualified as above, or relative to the clients' working directory.
The -T parameter ensures the general temporary directory as set in the user profile is used.
Further points to keep in mind:
1. Because of known issues with Microsoft's file sharing system, the application code should be stored on the same machine as the rest. Also, this is usually desirable as it will help avoid networking overhead.
2. The server machine should have enough resources available. Especially available memory may become a bottleneck; make sure there is enough available to have both the database and the multiple clients run comfortably.