Common System Designs¶
Introduction¶
This chapter is being written right now.
purpose/how to use this
mapping of OE to FWD components
logical vs physical separation
TBD: add configurations for each design
Simplistic Designs¶
ChUI¶
multi-user database
shared memory database access
UNIX/Linux
Batch Processes¶
multi-user database
shared memory database access
UNIX/Linux
GUI¶
Simple GUI¶
multi-user database
TCP/IP connections
single GUI client with direct database access
ADM/ADM2
Split GUI¶
multi-user database
shared memory database access on the server side
appserver running the non-interactive parts of the ADM/ADM2 framework (all database access occurs on the server side)
Linux
Windows clients (possibly on a Windows Terminal Server/Citrix)
GUI client running the interactive parts of the ADM/ADM2 framework, no direct access to the database
calls appserver entry points to execute the server-side portions of the ADM/ADM2 framework, the server handles the database acccess and returns any results back to the client using temp-tables
Appserver/PASOE¶
multi-user database
shared memory database access on the server side
appserver/PASOE agents exposing some external procedures, internal procedures and functions
Linux or Windows
4GL clients
Java Open Client
.NET Open Client
WebSpeed / Web Handler¶
SOAP and REST¶
Combined (More Realistic) Designs¶
ChUI with Batch Processes¶
one database instance¶
multiple database instances, different schemata¶
multiple database instances, same schemata¶
"Split GUI" with Appserver and Batch Processes¶
Web Services and Batch Processes¶
© 2021 Golden Code Development Corporation. ALL RIGHTS RESERVED.