Kbase P79621: RTB - What are the advantages of having an AppServer partition setup for Roundtable 9.1D?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
18/10/2004 |
|
Status: Unverified
GOAL:
What are the advantages of having an AppServer partition setup for Roundtable 9.1D?
GOAL:
Where does the AppServer come into play with Roundtable 9.1D?
GOAL:
Is the Check-in/out functionality affected by having a remote AppServer partition setup for Roundtable 9.1D?
FACT(s) (Environment):
Windows
FIX:
As with any distributed Progress application, defining a remote "roundtable" partition enables a portion of the application logic to run on a remote computer. In the case of RTB, a remote AppServer partition causes all repository database access to occur on the remote partition. Depending upon the remote computer and the network, application performance may increase. RTB 9.1D requires that the remote partition runs on a Windows machine.
The advantages of running RTB with a remote partition are:
- Asynchronous Selective Compile is enabled.
- Reports are run asynchronously.
- Remote development is possible using Task directories.
Without a client connection to the repository database, some client features are disabled, including Module Load and Schema Load.
Check-in functionality is not affected. An object cannot be checked in unless it resides physically in the Workspace (Share-status of "Central"). The Workspace root path defined for a Workspace must be valid for both the AppServer partition and the client (typically a UNC path).
Check-out functionality remains the same for objects checked-out with a Share-status of "Central". Again, the Workspace root path must be valid for both the remote partition and the client. If objects are checked-out with a Share-status other than "Central", the client need not have access to the Workspace root path. The object source will be extracted into the specified Task Directory on the client machine.