Progress/400
Product Guide
Native 4GL and Progress/400 AppServer Architecture
The Native 4GL Client and the Progress/400 AppServer architectures make it possible for Progress 4GL code to be compiled and executed on the AS/400.
Progress applications operating on the AS/400 can access data in DB2/400 database files locally using the Native 4GL Client as well as the Progress/400 AppServer. In this configuration, both the database and the application code reside on the AS/400. This architecture can exist simultaneously with the Progress/400 client/server architecture. The Native 4GL Client is available in a run-time-only version with the Progress/400 DataServer. The Progress/400 Native 4GL Compiler product allows the Native 4GL Client to compile Progress 4GL code directly on the AS/400.
Figure 1–2 shows the Progress/400 Native 4GL Client and the Progress/400 AppServer in the host-based architecture on the AS/400.
Figure 1–2: Progress/400 Host-based Architecture
![]()
With the host-based Progress/400 architecture, the Progress Native 4GL Client as well as the Progress/400 AppServer can run the Progress 4GL application on the AS/400. This takes advantage of the AS/400 server performance and reduces the network load. These clients can connect to multiple databases as long as they reside on the same AS/400. They are also compatible with all of the supported client/server configurations for accessing data. However, they do not have interactive capabilities.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |