Web Connector virtual path mappings

Crystal Enterprise may require a third level of path mapping that establishes a virtual path between the Web Connector and the Web Component Server (WCS). Rather than passing entire files back and forth across the network, Crystal Enterprise increases overall efficiency and response time by duplicating its "web content" directory structure on both the web server and the WCS machines. For instance, when a user requests an HTML page that refers to ./logon.csp, the Web Connector does not send the logon.csp file across the network. Instead, the Web Connector instructs the WCS to evaluate its own local copy of the logon.csp file. The path to the logon.csp file on the web server may not match the absolute path to the corresponding logon.csp file on the WCS; therefore, the Web Connector uses a virtual path mapping in order to translate a path on the web server to an absolute path on the WCS.

The WCS must be able to locate its own local copy of each .csp file that it is asked to process. Thus, you must define virtual path mappings for .csp files (one virtual path mapping for the /crystal virtual directory, and one virtual path mapping for the /crystalreportviewers10 virtual directory).

Depending upon your web environment, you configure this virtual path mapping in the Web Connector or in your web server's configuration files. On Windows, this virtual path mapping is typically required only when the Web Connector and the Web Component Server are installed on separate machines.

Note:    

• The WCS also responds to .cwr and .cri requests, but it generates these files itself, so it does not have to find its own local copy first. In other words, the .cwr and .cri file types file types are handled by application mappings alone.
• If a firewall separates your web server from the WCS or from other Crystal Enterprise components, you will need to make additional changes to your configuration. For details, see the firewalls section in the Crystal Enterprise Administrator's Guide.

For more information on Web Connector path mappings, see Web Connector virtual path mappings.