Progress/400
Product Guide
The Progress/400 AppServer Instance
The Progress/400 AppServer instance contains the same components as the AppServer instance on other Progress platforms. It includes both the Application Broker and the Application Server. On the AS/400, these components run as OS/400 jobs.
Every Application Broker on the AS/400 is made up of two OS/400 jobs. The Application Broker jobs follow a specific naming convention. Progress/400 gives the first job the same name as the name of the Application Broker, for example ASBROKER1, and it controls the Java Virtual Machine. The second job, the actual Java Virtual machine, always takes the name QJVACMDSRV. These two jobs together make up one Application Broker.
Every Application Broker can start a predefined number of Application Servers. Each Application Server on the AS/400 is made up of two AS/400 jobs that also follow a specific naming convention. The first job, named QZSHSH, binds together the Application Broker and the Application Server that the broker controls. The second job, named QZP0SPWT, is the actual server job. This job executes the Progress/400 AppServer program called PROAPPSVR.
If any of these jobs within the Application Broker or the Application Server ends, its corresponding partner job will end as well.
Figure 7–2 diagrams the Application Broker and a single Application Server with their required jobs.
Figure 7–2: Progress/400 AppServer Instance Architecture
![]()
As shown in Figure 7–2, the Application Broker and Application Server jobs make up one Progress/400 AppServer instance. A Progress/400 AppServer instance runs in the subsystem specified at install time.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |