This sample topology delivers
static HTML content to clients from an HTTP server that is configured
as a reverse proxy. This strategy reduces the work load on the Web
application server. Examples of HTTP servers that can be configured
as reverse proxies are Apache HTTP Server and Microsoft Internet Information
Services (IIS).
When a browser makes
a request for a SAS Web application, a part of the request is for
static content such as HTML files, images, cascading style sheets,
and JavaScript scripts. The SAS Themes Web application provides this
static content. For Web applications that use Flex, there is static
content that is provided by SAS Themes for Flex Applications. In this
scenario, the static content for SAS Themes and SAS Themes for Flex
Applications is unpacked and delivered by the reverse proxy. The reverse
proxy simply returns the requested content to the browser, and the
browser displays the document.
Note: If you unpack and deploy
the static content on the reverse proxy, then you must redeploy this
content if you later install a SAS software upgrade or apply maintenance
that includes new files for the static content.
If the reverse proxy
can be configured to cache content, then the performance improvement
is even greater. The portion of the request that is for dynamic content
still requires some type of data manipulation by the SAS Web applications
and the Web application server must perform that work before returning
the requested page.
In a typical configuration,
the HTTP server is configured with a module or plug-in that enables
the reverse proxy function of communicating with the Web application
server. By having the reverse proxy as the single point of contact
for browser requests, the Web application server is not directly exposed
to clients. The reverse proxy provides a layer of security for the
SAS Web applications.
Although this topology
must be manually configured and maintained, here are the advantages
and disadvantages of this topology:
Scenario 2 Advantages and Disadvantages
|
|
|
|
The reverse proxy provides
a layer of security.
The network on the middle-tier
server can be configured to reject HTTP packets that do not originate
from the reverse proxy.
SSL can be enabled on
the client side of the reverse proxy without affecting the work load
on the Web application server or the performance of the SAS Web applications.
The Web application
server and SAS Web applications can be configured to perform Web authentication
for single sign-on to SAS Web applications and other Web resources
in the network.
|
Adding firewalls to
the network is a good next step.
|
|
Response time is improved
because processing static content is offloaded from the Web application
server to the reverse proxy.
|
As with scenario 1,
all of the SAS Web applications are deployed to a single Web application
server instance. However, a second managed server instance can be
configured, as mentioned in the scenario 1 section.
|
|
There are no advantages
in this scenario, but the topology provides an upward path to clustering
Web application servers.
|
This topology does not
support hundreds of concurrent users.
|
|
|
This topology has no
provision for planned or unplanned down time.
|
|
The SAS Deployment Wizard
can still automate the configuration and deployment of the Web application
server and the SAS Web applications.
|
After manual or automatic
installation and configuration with the SAS Deployment Wizard, there
are manual steps to perform.
The reverse proxy must
be configured with the connection information for the SAS Web applications.
|