Enabling the ASAPI Web Connector

Before configuring Apache to use the ASAPI Web Connector, ensure that your version of Apache supports DSOs. Note also that you can use a version of the Web Connector that uses the AP13 Apache API, or EAPI.

Follow the procedure for enabling the Web Connector by including the asapi.conf file in your web server's httpd.conf file. The asapi.conf file was generated when you installed the Web Connector; it is located in the crystal/enterprise/platform/wcs/conf directory of your Web Connector installation.

To enable the ASAPI Web Connector
  1. On the web server machine, open the asapi.conf file from the crystal/enterprise/platform/wcs/conf directory of your Web Connector installation.
  2. By default, the AP13 API is selected in the asapi.conf file:

    LoadModule wcs_connector_module crystal_root/enterprise/platform/wcs/lib/mod_wcs.ap13.so

    #LoadModule wcs_connector_module crystal_root/enterprise/platform/wcs/lib/mod_wcs.eapi.so

    To select the EAPI Web Connector, place a # in front of the line specifying the AP13 API Web Connector, and remove the # at the beginning of the line specifying the EAPI web connector.

  3. The WCSHosts directive indicates the list of WCS hosts to connect to. The WCSHosts directive should be followed by the full list of WCS hosts, and there should be only one WCSHosts directive per virtual server:

    # List of WCS hosts to connect to.

    WCSHosts machinename:port machinename:port

    Verify that the WCHosts list provides the name and port number for each of your WCS machines. The default port number for the WCS is 6401.

  4. The Alias directives define the virtual directories that allow your web server to serve up Crystal Enterprise web content.

    # Alias the crystal and viewer directories

    Alias /crystal /crystal_root/webcontent

    Alias /viewer /crystal_root/viewers

    Alias /crystalreportviewers10 /crystal_root/viewers

    Ensure that /crystal_root/webcontent and /crystal_root/viewers point to the webcontent and viewers directories on your web server machine.

    Note:    Alias directives are valid only if the mod_alias module is enabled on your installation of Apache. (This module is typically enabled at runtime, in the httpd.conf file.)

  5. Ensure that the path mapping directives map the virtual directories on the web server to the actual Web Content and crystalreportviewers10 directories on your Windows WCS machine:

    # Path Mapping

    AddPathMap /crystal csp "C:\Program Files\Crystal Decisions\Enterprise 10\Web Content"

    AddPathMap /crystalreportviewers10 csp "C:\Program Files\Common Files\Crystal Decisions\2.5\crystalreportviewers10"

  6. On the web server machine, open the Apache httpd.conf file in a text editor such as vi.
  7. Add the following line to the file:

    Include /crystal_root/enterprise/platform/wcs/conf/asapi.conf

  8. Restart the Apache daemon using the command appropriate to the version that you are running.
  9. Connect to Crystal Enterprise by opening your web browser and going to:

    http://webserver/crystal/enterprise10/

    Here, the term webserver represents the name of the web server machine.

    Note:    If mod_wcs.so does not match your version of Apache, you will see the following error message when you attempt to restart the server.

    "API module structure 'wcs_connector_module' in file mod_wcs.so is garbled - perhaps this is not an Apache module DSO?"



Crystal Decisions
http://www.crystaldecisions.com/
Support services
http://support.crystaldecisions.com/