Web Calendaring Settings (Old)
How to get here
- From the home page, click the > tab. The page appears.
After making changes, click . Navigate to the Service Administration page and restart the service.
Use to specify the Web Server Port , Directory, Maximum Work Threads, SSL and Thread Pooling Settings for the Web Calendaring Server.
- Enter the port on which the Web Calendaring server operates. By default the web port is set to 8484, but you can change it to any unused port. If you change the port, the Web Calendaring server must be stopped and restarted. If you do not have another web server on the same system, you can use the normal web port of 25.
If you use a non-standard port number (anything other than 25), users will need to specify the SSL port in the logon web address.
- Enter the the path to the Web Files Directory. This directory contains the files used to create web pages for IMail Web Calendaring. If you change this directory, you must stop and restart the web server. Useto locate the directory if it resides locally.
- Enter the value to set the maximum number of work threads that can be simultaneously used by IMail Web Calendaring. This setting to constrains the load on your web server. If an HTTP request requires a work thread and the maximum has already been reached, Web Calendaring returns a "server not available" message. This option does not require to be selected.
- Select this check box if you want the web server to ignore the IP address that requested the page. This is useful with firewalls and service providers that use dynamic IP addresses (such as AOL). (Normally, the web server checks the IP address that requested the page against the IP address from which the user logged on.)
- Select this check box to stop and restart the server automatically when you click . We recommend that you select this option.
- Select this check box if you want 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. Using Enable Keep Alive can improve performance by reducing overhead per request, but it also means that fewer resources are available for other processes.
If you use and , then the number of simultaneous connections allowed to the server will equal the . Thus, you will be limiting the number of connections allowed.
SSL Settings
- Select this check box to use Secure Sockets Layer to encrypt communications with clients, and to accept SSL connections in addition to normal connections.
- Enter the Web SSL Port on which the Web Calendaring server listens for an SSL-based HTTP request if you enabled SSL. If you used the default Web Server Port (8484), you can assign any TCP port number here -- the default is 8485. If you used the standard web server port (port 80), then set the SSL port to the standard SSL port 443.
- Select this check box to set the Web Calendaring server to accept only SSL- based HTTP connections; normal HTTP connections are not accepted.
Thread Pooling Settings
- Select this check box to create a thread pool for handling HTTP requests from clients. IMail Web Calendaring creates up to 64 Max Work Threads to process requests. If this option is cleared, IMail Web Calendaring creates a thread to handle each request (either persistent or normal) and after handling that request, destroys the thread. IMail 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, then additional HTTP requests are denied. Also, threads reserved for use by IMail Web Calendaring are not available to other processes running on your server.
- Enter the interval (in seconds) used by IMail Web Calendaring to check the status of the thread pool. If the current number of work threads is less than Max Work Threads, new threads are created. This option is used only when thread pooling is enabled. The default value is 10 seconds.
- Select this check box to close a thread after the HTTP request is processed completely. This option is used only when thread pooling is enabled. IMail Web Calendaring creates a replacement for closed threads on the next poll time, which is set in Thread Check Time. When this option is cleared, the thread is kept open and made available to process another request.
- Click to save your settings. An "Update Successful" message and the time of the update appear.