Server configuration
The Crystal Web Server includes an application called the Web Components Manager, pictured in Figure A, that allows you to modify the server's configuration for performance and security reasons.

FIGURE A


The Web Components Manager allows you to modify the server's configuration. Roll over picture for a larger image.

The Page Server tab includes an option to specify a database refresh interval, basically telling the Page Server how often to refresh the data in cached reports. You can use this setting to minimize the frequency of end-user requests on your server for new data. This is a much better alternative to allowing your user population to have control over how often report data is refreshed. If you specify 0, (as I have in this example), the data will get refreshed each time a report request is sent to the server. There's also an option to decide whether a database gets hit when a user refreshes from his or her browser.

You can also specify a maximum number of threads for processing of reports. The Web server is designed as a multi-threaded application, so it will generate a new thread each time a report request comes through. By limiting the maximum number of concurrent threads, you can cut down on system resource usage and increase overall performance. By default, this option is set to Unlimited.

In addition to the cached reports options I discussed above, there's an interface for maintaining the caching specifics of your reports server. It's found in the Cache Settings tab of the Web Components Manager, pictured in Figure B.

FIGURE B


In the Cache Settings tab, there's an interface for maintaining the caching specifics. Roll over picture for a larger image.

If you've configured some of your reports to save data with the report, you can move them to a specific directory on your server, which is noted in the Cache Directory. You can also specify a maximum cache size used for report caching. Once this maximum is reached, older pages will be deleted from the cache so newer pages can be stored.

Security: take control
In addition to performance considerations, there are other items that can be configured which affect end-users. The manner in which reports are viewed and displayed can also be modified by the developer or server administrator through the Report Viewing tab, pictured in Figure C.

FIGURE C


The Report Viewing tab modifies the manner in which reports are viewed and displayed. Roll over picture for a larger image.

There are essentially three parts to the Report Viewing tab, one for all possible Crystal Viewers, a second for Active X and Java viewers, and a third for standard HTML pages.

By default, end-users can perform searches and use drilldowns and group trees within any report served up by the reports server. It's worthwhile to note that disabling group trees can be another way to enhance performance for your Web reports server. Group trees need the server to pass through the data another time to create the trees. However, you can disable any of these items through this Report Viewing tab.

You also have the ability to disable report printing, exporting, and zooming within Active X and Java viewers, if needed.