| SAS/IntrNet 9.2: Application Dispatcher | 
The following are required:
- The end user must have a Web browser.
- The site must have a machine that has a Web server.
- The site must have a SAS server for SAS 9.2 with an 
Application Server installed.
These requirements (a Web browser, a Web server, and an Application 
Server) can reside on one machine or on three separate machines.
You must install both the Application Broker and the Application Server 
components of the Application Dispatcher. Install the Application Server on 
a machine that has SAS software running, and install the Application Broker 
on the machine that has your Web server running. A third component of the Application 
Dispatcher, the Application Load Manager, is not required for a typical setup. 
SAS software is not required on the Web server or the local desktop. The 
installation requirements are
- Because the Application Broker is invoked by the Web server, the Web server must 
already be installed on the machine where you plan to install the Application Broker.
- You must have WRITE access to the directory where your CGI scripts and 
programs are stored.
- You must have already installed at least one Application Server.
- The machine on which you install the Application Broker must
have access by means of a TCP/IP-based network to the machine on which you 
installed the Application Server.
- For pool services, a Load Manager must be running on the network. A 
SAS spawner is also required if servers are to be started by using user name or 
passwords.
- You must have access to a Web browser to test your installation.
This documentation describes the Application Server for SAS 9.2.  If your SAS server is an earlier version, refer to the documentation for that version.
- You must install the Application Server on a machine where SAS 9.2 is installed, because the Application Server is a SAS program. 
- If you want to use a launch service, both the Web server and the SAS 
server must reside on the same machine. This is because the Web server 
invokes the Application Broker and the Application Broker invokes the SAS server.
- A socket service can be configured by using the Web server and the SAS 
server on the same or on different machines.
- For increased functionality, you can take advantage of other SAS 
software you already have installed, such as SAS/GRAPH, SAS/SHARE, 
SAS/ACCESS, or SAS/EIS software.
- The machine on which the Application Server is installed must have 
access to all of the data that is necessary to run the Application Dispatcher applications. 
This data can be stored in local SAS data sets, in third-party databases 
accessed through SAS/ACCESS software, or on remote servers
accessed through SAS/SHARE software.
- You must install both the Application Broker and the Application Server in order 
to use Load Manager.
- Load Manager must have access to the Web server and the Application 
Server by means of a TCP/IP-based network. You can install Load Manager on 
your Web server machine, your SAS server machine, or any other machine 
on your network.
- You can run Load Manager as an unattended, background process, or 
you can start it as a system service.
Copyright © 2007 by SAS Institute Inc., Cary, NC, USA. All rights reserved.