CallSite Server Installation
 
 

Section: II. D. 5

Starting the CallSite Server (Firewall enabled)

You can launch the CallSite server as a Java Servlet (using any compliant servlet engine, such as Tomcat or iPlanet). This allows your CallSite system to be 100% firewall proof, since the client applet can use the HTTP protocol through the port 80, which is usually not blocked by firewalls.

The servlet installation is not easy and is recommended only for experienced users. You can also contact our Professional service team to help you with firewall installation.

1. Servlet engine installation:

First, your Web server needs to be servlet enabled.
For Netscape or Microsoft servers, you can install a third party servlet engines, such as JRun or ServletExec. To have a complete list, you can consult the Sun Microsystem servlet homepage : http://java.sun.com/products/servlet/

For Apache, there is a free servlet engine (Tomcat) available at: http://jakarta.apache.org/tomcat/. The Tomcat servlet engine works fine with most web servers like IIS and Netscape in addition to the Apache web server.

2. Servlet engine configuration:

Add the file callsite/server/WeMessageServer.jar to the CLASSPATH that is used by your servlet engine (restart the servlets engine if necessary).

For example, the environment variables needed for Tomcat on Unix/Linux:
JAVA_HOME=/usr/jdk1.5; export JAVA_HOME CLASSPATH=.:/home/httpd/html/wemeeting/server/WeMessageServer.jar:/home/httpd/html/wemeeting/server/mysql_comp.jar; export CLASSPATH
TOMCAT_HOME=/home/httpd/jakarta-tomcat-5.5.16; export TOMCAT_HOME

You need to specify the following initialization parameters in the servlets properties file. Given below is the sample configuration of the Tomcat servlet engine (typically the file web.xml for the Tomcat servlet engine):

<servlet>
   <servlet-name>
     callsite
   </servlet-name>
   <servlet-class>
     com.netdive.servlet.WMServlet
   </servlet-class>
   <init-param>
     <param-name>product</param-name>
     <param-name>CallSite</param-value>
   </init-param>
   <init-param>
     <param-name>version</param-name>
     <param-value>7.5</param-value>
   </init-param>
   <init-param>
     <param-name>fullVersion</param-name>
     <param-value>7.5.1</param-value>
   </init-param>
   <init-param>
     <param-name>port</param-name>
     <param-value>36680</param-value>
   </init-param>
   <init-param>
     <param-name>config</param-name>
     <param-value>/home/httpd/html/callsite/server</param-value>
   </init-param>
   <init-param>
     <param-name>dirClass</param-name>
     <param-value>com.netdive.server.sqldir.SQLDatabaseDirectory</param-value>
   </init-param>
</servlet>

The Tomcat default web.xml file is located in the directory:
jakarta-tomcat-5.5.16/webapps/examples/WEB-INF/web.xml

The servlet initialization parameters used in this sample configuration are explained below:

product parameter: the name of the product - CallSite
version parameter: the version of the product - 7.5
fullVersion parameter: the full version of the product - 7.5.1
port parameter: the default TCP/IP port for the server (default way to communicate, if it does not work the client automatically switches to HTTP port 80).
config parameter: the full path to your CallSite server directory
dirClass parameter: the directory service class (containing the user list). If you are connecting to the CallSite server using a SQL database via the bridge.cfg file, you will need to mention here the class that enables you to connect to the database. In case you are connecting your CallSite users to the CallSite server using the users.cfg file (i.e. you are not connecting to the CallSite server using a SQL database), you do not need to mention this parameter in this file at all.

3. Restart the servlet engine:

You will probably need to restart the servlet engine after you made these changes.

In order to restart Tomcat, go to the the directory:
jakarta-tomcat-5.5.16/bin/
To stop Tomcat, type the following command:
./shutdown.sh
To start Tomcat, type the command:
./startup.sh

4. Client side configuration:

When you are done with this, you need to make sure that these parameters are properly set on the client side (they need to connect the client to the right ports and the servlet). These parameters need to be set by the Agents in the agent.cfg file which is located in the CallSite directory of the Agent application.

The following are the parameters that your Agents will need to set for the sample configuration shown above in the agent.cfg file:

port=6680
httpPort=80
ConfPort=6682
ConfHttpPort=80
servletBase=tomcat/servlet/callsite

The parameter "servletBase" needs to be the URL that accesses the web server and the servlet engine. For example: if the complete URL to access the CallSite servlet in your server is: "http://your-server/tomcat/servlet/callsite", then you should specify the value of the parameter "servletBase" as follows: servletBase=tomcat/servlet/callsite.

You will also need to mention the parameter "servletBase" in the server.cfg file (located in the '/callsite/server/' directory. For example, in the server.cfg file, you will need to mention servletBase=tomcat/servlet/callsite

In order to launch the CallSite server (TCP and HTTP), access the CallSite servlet with a web browser.
For example, type the URL:

http://your-server/servlets/callsite

The server is also launched automatically the first time you run the CallSite application.