Initially, the term "Web server" was used to mean an HTTP server that
simply managed Web page requests from the browser and delivered HTML
documents, or Web pages, in response. As the technology progressed, Web
servers began to be used for server-side processing in the form of CGI
scripts and Active Server Pages (ASPs), which provided functions such
as database searching.
The next-generation, Java-based Web servers of today use Java servlets and JavaServer Pages (JSPs) to perform the processing, but also support CGI and ASPs. JSP and servlet-enabled Web servers are sometimes referred to as Application Servers.
The term Application Server has also evolved. In a client/server environment, an Application Server could have been added to perform business logic in a middle tier. Today, the term Application Server is used to mean the server that sits along with or between the Web server and the
databases and legacy applications, enabling a browser-based application
to link to multiple sources of information via servlets, JSPs, and Enterprise
JavaBeans (EJBs).
Many Application Servers are also Web servers; however, in large sites,
separate Application Servers may be linked to one or more Web servers
to provide load balancing and fault tolerance for high-volume traffic.
For smaller Web sites, the Application Server may be used as the Web
server.
When running MQL from CGI, you must add the HOME parameter to the
MQL scripts. The value for the HOME parameter should be the home directory
of the user running the current session. It can be any valid path, for example,
ENOVIA HOME/.