Progress/400
Product Guide
Client/Server, Web-based, or N-tier Architecture
The Progress/400 product allows Progress applications operating in a client/server, Web-based, or n-tier mode to access data in DB2/400 database files. The primary difference between a host-based architecture and a client/server architecture is the location of the application code. In a client/server architecture, the application code resides on the PC or workstation client and the database resides on the host AS/400. A Web-based or n-tier architecture requires the use of a middle-tier platform; however, this middle tier appears as just another client to the DataServer.
With the Progress/400 product, the Progress client (MS-Windows or UNIX) contains the Progress application logic, and requests database records from the AS/400. The DataServer retrieves database requests from the AS/400 and delivers them to the client. Each Progress client starts its own DataServer.
Figure 1–1 shows the Progress/400 client and server components.
Figure 1–1: Progress/400 Client/Server Architecture
![]()
Note that in Figure 1–1:
- A connection can also be made from the middle-tier platform of a WebSpeed Transaction Server or an AppServer instead of a Progress client.
- You can connect through TCP or SNA network protocols. The SNA connection requires the use of specific routers. See the "SNA Communications Protocol" section in "Remote Access to Progress/400 DataServer," for details.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |