TS.Census Web Console

coldwaterphewServers

Nov 17, 2013 (3 years and 8 months ago)

84 views



1

of
2

www.tallysystems.com



Tally Systems is an affil
iate of TS.Census International, Ltd





2003 Tally Systems Corp. All rights reserved.


TS.Census Web Console

Running the Web Console in your existing web server environment




The TS.Census Web Console (version 3.0+) and Web Reports (version 2.2) use Java servlet
technology to handle communications between web browsers and the TS.Census database. The
core Java servlet technology is based around Tomcat, which is an o
pen source servlet container
from the Apache Software Foundation. Tomcat can be implemented with your existing web server
software (Microsoft Internet Information Services [IIS] or Apache) or as a stand
-
alone server
process. This document describes various

configuration options for Tomcat. For detailed
instructions for installing Tomcat with Microsoft IIS, please refer to utility 22+ALUISAPIFilter.


Overview

TS.Census Web functionality is implemented using Java servlet technology based around
Apache Tomca
t. Servlets are programs that run on a server and act as a middle layer between
requests coming from a Web browser and databases or applications on the server. They are
designed to:




Read requests sent by a browser



Generate results from a request by commu
nicating with a database or running an application



Format the results inside a document (normally a Web page)



Send the document back to the browser


The features within TS.Census built as a servlet include the Web Console: Inventory Reports;
Network Discov
ery user interface; Software Compliance Module, and Web Reports. We have
chosen Java servlets because they provide a powerful development environment and good
performance. They also use proven component technologies.


Tomcat

is a Java servlet container use
d to run servlets. Servlets can't communicate directly with
a browser; they need an environment to run within and a method for handling browser requests.
Tomcat provides the necessary environment by executing servlets and passing requests from
browsers to
the servlets and returning the result of the requests to the browser.





2

of
2

www.tallysystems.com



Tally Systems is an affil
iate of TS.Census International, Ltd





2003 Tally Systems Corp. All rights reserved.



Tomcat and IIS

When Tomcat is configured to work with IIS browser requests go directly to IIS, which then
passes them onto Tomcat. A servlet running under Tomcat processes the reques
t, constructs a
document, and returns the document to IIS, which then relays the document back to the browser.
The browsers never communicate directly with Tomcat.


The integration of Tomcat and IIS is accomplished using an ISAPI filter. Figure 1 shows T
omcat
configured with either IIS or Apache.



Figure 1

Tomcat and Apache

The integration between Tomcat and the Apache web server is similar to the IIS integration. The
Apache server handles browser requests, passes them on to Tomcat, which processes the
request and passes the result back to Apache, which then returns it to the browser. The actual
technology used to integrate the two can include connecting port numbers by URLs, proxying
requests from Apache HTTP’d to Tomcat or using a Connector module.


To
mcat development is part of the Jakarta project of the Apache Software Foundation
(
http://jakarta.apache.org
).


Stand
-
alone Tomcat

Tomcat itself is a server process. It can be configured to run as a stand
-
alone We
b server (with or
without SSL) or it can be configured to work with IIS or Apache Web servers. Figure 2 shows
Tomcat configured as a stand alone Web Server.



Figure 2