The 20 Minute E-mail Solution!
TOC PREV NEXT INDEX

Configuring the Web Calendaring Server


The Web Calendaring server is installed on the host where the IMail Server software is installed. You can change the default port number and Web directory, set SSL options, set other Web server options, and start and stop the Web server. (Some of these options can also be set in the iwebcal.ini file in the winnt folder.)

  1. Expand the Services folder in the left panel and select Web Calendaring. The Web Calendaring Server tab appears in the right panel.

  1. Change any of the Web server properties. See the previous sections for more information about the Web server port and SSL.
Web Server Port. The port on which the Web Calendaring server operates. If you change the port, the Web Calendaring server must be stopped and restarted.
Note: If you use a non-standard port number (anything other than 80), users will need to specify the port in the logon Web address. For more information, see "By default, the IMail Web Calendaring server is assigned a Web address that consists of the host name of the IMail Server host and a Web server port number. The default port number is 8484. For example, if your mail host had a name of host1.ipswitch.com, then the address is: http://host1.ipswitch.com:8484".
Web Files Directory. This directory contains the files used to create Web pages for Web Calendaring. If you change this directory, stop and restart the Web server.
Ignore source address in security check. Before displaying a page, the Web server checks the IP address requesting the page against the IP address from which the user logged on. If you select this option, the Web server does not check the IP address. This is useful with firewalls and service providers using dynamic IP addresses (such as AOL).
Enable Keep Alive. Select this option to create a persistent TCP connection between the Web Calendaring server and a browser (if the browser supports it.) If this option is cleared, the server closes the TCP connection after each response.
Normally, the connection between a browser and a Web server is valid only for a single request/response pair. Turning on Enable Keep Alive can improve performance by reducing overhead per request, but it also means that fewer resources are available for other processes, such as creating new connections.
Auto Restart Server on Apply. If this is selected, the Web server will be stopped and restarted automatically when you click Apply (if you changed anything). We recommend that you select this option.
  1. Optionally, set SSL options. For information about SSL, see "Using Secure Sockets Layer (SSL)".
Enable SSL. Select this option if you are using the Secure Sockets Layer (SSL) utility to encrypt communications with the Web Messaging client. This sets the Web Calendaring server to accept SSL connections in addition to normal connections.
Web SSL Port. The TCP port on which Web Calendaring listens for an SSL-based HTTP request. If you used the default Web Server Port for Web Calendaring (8484), then you can assign any TCP port number here, the default is 8485. The standard SSL port is 443.
Note: If you use a non-standard port number (anything other than 443), users will need to specify the SSL port in the logon Web address.
Force SSL. Turn this option on if you want the Web Calendaring server to accept only SSL-based HTTP connections; normal HTTP connections are not accepted.
  1. Optionally, set Thread Pooling options.
Web Calendaring can create a thread pool for handling HTTP requests (from the browser) on this TCP port. Using thread pooling reduces the overhead involved in creating and closing threads. However, if all threads in the pool are in use (in other words, your server is seeing heavy use), then an additional HTTP request will be denied. Also, threads reserved for use by Web Calendaring are not available to other processes running on your server. You need to determine if thread pooling is appropriate for your Web Calendar server.
Enable Thread Pooling. Select this option to create a thread pool for handling HTTP requests from clients. Web Calendaring creates 64 work threads to process requests. If this option is cleared, Web Calendaring creates a thread to handle each request (either persistent or normal) and after handling the request, destroys the thread.
Thread Exit. Select this option to close a thread after the HTTP request is processed completely. Web Calendaring will create a replacement for closed threads on next poll time (set in Thread Check Time). Clear this option to keep the thread open and available for another request. This option is used only when Enable Thread Pooling is turned on.
Thread Check Time. This is the interval (in seconds) used by Web Calendaring to check the status of the thread pool. This option is used only when Enable Thread Pooling is turned on. The default value is 10 seconds.
  1. Click Apply.
  2. Stop and restart the Web Calendaring server in order to save your changes.


Ipswitch, Inc.
http://www.ipswitch.com
TOC PREV NEXT INDEX
©Ipswitch 2005