Tour 3: Designing Your Environment

SAS/IntrNet software can be installed in multiple systems on your network. You can either have separate machines for your Web server and SAS server or use the same machine for both.

The following diagrams shows the systems and components that make up typical SAS/IntrNet installations. The subsequent discussions describe the parts of the diagram in more detail.

Typical SAS/IntrNet Configuration for CGI Applications

Web Browser	Web Server Application Broker Load Manager htmSQL	Base SAS Software Application Server Load Manager SAS/SHARE Software

Typical SAS/IntrNet Configuration for Java Applications

Java Tools	SAS/CONNECT Software SAS/SHARE Software

Typical SAS/IntrNet Configuration for Java Applets

Web Browser Java Tools	Web Server Tunnel Feature	Base SAS Software SAS/CONNECT Software SAS/SHARE Software

The thin client is the machine on which the user runs a Web browser or other Web applications. Install the Java Tools on the client system if you want to eliminate the time spent downloading Java classes from the Web server or if you develop Java applets or applications on the client. Otherwise, you do not need to install any SAS/IntrNet software on most client systems.

The Java Tools package contains SAS/SHARE for JDBC and SAS/CONNECT for Java classes, which are used for accessing SAS servers from a Java applet or application.

The Web server is the machine on which your Web server software is installed. This can be the same machine as your SAS server, but is often a different machine and can even be of a different platform type. Several SAS/IntrNet components can be installed on your Web server:

• The Application Broker component of the Application Dispatcher can be installed on the Web server and connected to an Application Server.

• The Load Manager component of the Application Dispatcher can be installed on either the SAS server machine or the Web server machine.

• htmSQL allows a browser to connect to a SAS/SHARE server and perform SAS/IntrNet data services.

• The tunnel feature for Java Tools is required only if you are using the Java Tools package and want to install your SAS server on a machine other than your Web server machine. If the SAS server and the Web server reside on the same machine, then your applet can communicate directly with the SAS server without tunneling.

The SAS server is the machine or machines where SAS (including SAS/IntrNet components such as the Application Server and the MDDB Report Viewer) is installed. Servers that can be installed and run on this system are listed below. If you have the appropriate licenses for these products, then the servers are included when you install SAS from the SAS media.

• The Application Server component of the Application Dispatcher provides a CGI-based compute service capability.

• The Load Manager component of the Application Dispatcher can be installed on either the SAS server machine or the Web server machine.

• The SAS/CONNECT server can provide compute services for Java applets and applications using the SAS/CONNECT Driver for Java. You must license the SAS/CONNECT product to use this server.

• The SAS/SHARE server can provide data services for htmSQL applications and Java applets and applications using the SAS/SHARE Driver for JDBC. You must license the SAS/SHARE product to use this server.

A development machine is a machine that a developer uses to create and test programs and applications. A development machine is frequently used to emulate multiple machines in the production system and might have any or all of the following components installed:

• SAS/IntrNet components (including SAS Design-Time Controls)

• Web server

• SAS server

Development machines enable you to develop and test changes without affecting the production environment.