The Active X and Java Viewers allow clients to view graphs and embedded maps, utilize the navigation "trees," drill down, export reports, search for values, view sub-reports, and drill down on sub-reports. The other viewers offer less functionality. You should carefully consider what your end user environment is like before choosing a viewer for your organization. Oftentimes this decision is made based on existing corporate standards (for example, the company runs IE internally). Reports should be designed with this issue in mind. I personally have found the Active X viewer to be quite stable, and it has all the available features.

The last piece of the Reporting Web Server is the Web component connectors, of which there are two types, the WCS CGI connector (complies to CGI standard) and WCS ISAPI\NSAPI. The connector used depends entirely on the type of Web Server running within your organization. Since we are running Domino, we would be using the WCS CGI connector application, whose filename is WCSCGI.EXE.

Configuring your Domino Server
After you've installed the Seagate Software and completed the configuration steps listed above on the Windows NT side, you're ready to configure your Domino Server. As I mentioned earlier, Domino supports CGI, so we will be using the CGI component connector. The instructions below are for Domino R5. If you're running Domino 4.x, consult the Seagate Web site for modified instructions.

Step 1: WCSCGI.EXE
The first step is very simple. You'll want to copy the WCSCGI.EXE file into your Domino CGI directory on the server.

Step 2: Virtual Directories
The second step will require that you have proper rights to modify the NAB, particularly the server document for the server that'll act as your reporting server.

Essentially, we'll be creating virtual directories on the Domino Web server. In R4, this was done via a configuration database. In R5, there's no longer such a database, so we add the mappings directly in the NAB or via the Domino Administrator client.

As you can see in my example below in Figure A, I've created a total of five mappings for my server.

FIGURE A


I've created five mappings for my server. Roll over picture for a larger image.

The first four mappings are all URL->Directory Mappings, as follows:

URL Path: /scrsamples
This is an optional mapping to the sample reports that come with the Seagate software. It's pictured in Figure B.

FIGURE B


This is an optional mapping to the sample reports. Roll over picture for a larger image.

URL Path: /scrreports
This is another optional mapping to the sample reports that come with the Seagate software. You can see it in Figure C.

FIGURE C


Here's another optional mapping to the sample report. Roll over picture for a larger image.

URL Path: /viewer/*
This points to the directory where all viewers reside and is required in order for the Web Components Server to serve up the reports to the browser properly. It's pictured in Figure D.

FIGURE D


This points to the directory where all viewers reside. Roll over picture for a larger image.

URL Path: /reports
This is the actual directory where all your pre-designed Crystal reports sit. These are files with a .rpt extension and are, of course, required. You can see it in Figure E.