Enabling the NSAPI Web Connector

When you installed the Web Connector, the setup.sh script generated the following configuration files that are customized for your installation of Crystal Enterprise:

• mime.types.conf
• obj.conf

These files are located in the crystal/enterprise/PLATFORM_PATH/wcs/conf directory of your Web Connector installation. Copy the information from these files into the appropriate iPlanet configuration files, as described in the following procedures.

Note:    The iPlanet configuration files are usually located in the servers/https-servername/config directory of your iPlanet installation. Here, https-servername represents the name of the web server that you want to configure for use with Crystal Enterprise. The relevant iPlanet files differ, depending upon which version of iPlanet Enterprise Server you are running.

To enable the NSAPI Web Connector

1. On the web server machine, open the mime.types.conf file from the crystal/enterprise/PLATFORM_PATH/wcs/conf directory of your Web Connector installation.

   The file contains the following lines:

   type=magnus-internal/rpt exts=rpt
   

   type=magnus-internal/csp exts=csp
   

   type=magnus-internal/cri exts=cri
   

   type=magnus-internal/cwr exts=cwr
   

2. Copy these lines from mime.types.conf to the bottom of the iPlanet mime.types file.
3. Open the obj.conf file from the crystal/enterprise/PLATFORM_PATH/wcs/conf directory of your Web Connector installation.

   Note the customized Init lines that correspond to the following example:

   # Add to init part
   

   Init fn="load-modules" funcs=req_handler,req_init shlib="INSTALL_ROOT/enterprise/PLATFORM_PATH/wcs/lib/libnsapi.so"
   

   # For connecting to WCS
   

   Init fn="req_init" WCSHosts="WCSLIST" ClientPool="5" ConnectorTimeout="600000" WCSPathMap="/crystal;.rpt;INSTALL_ROOT/webcontent,/crystal;.cwr;INSTALL_ROOT/webcontent,/crystal;.csp;INSTALL_ROOT/webcontent,/crystal;.cri;INSTALL_ROOT/webcontent"
   

4. Add the two Init lines to the appropriate iPlanet configuration file. Add these lines immediately after any Init lines that are already in the iPlanet file.

   Note:    

   • If you are running iPlanet Enterprise Server version 6.x, add these lines to the magnus.conf file. If you are running iPlanet Enterprise Server version 4.1, add these lines to the obj.conf file.
   • If the Init fn="req_init" line is commented out, be sure to remove the preceding # symbol when you add the line to the iPlanet magnus.conf file.
5. Return to the wcs/conf/obj.conf file and note the customized NameTrans lines that correspond to the following template:

   # Add to NameTrans part
   

   NameTrans fn=pfx2dir from=/crystal dir="INSTALL_ROOT/webcontent"
   

   NameTrans fn=pfx2dir from=/viewer dir="INSTALL_ROOT/viewers"
   

6. Add the NameTrans lines to the <Object name="default"> section of the iPlanet obj.conf file. Be sure to add these lines before the NameTrans fn="document-root" line.
7. Return to the wcs/conf/obj.conf file and note the Service lines:

   # Add to Service part
   

   Service fn="req_handler" method="(GET|POST)" type="magnus-internal/rpt"
   

   Service fn="req_handler" method="(GET|POST)" type="magnus-internal/csp"
   

   Service fn="req_handler" method="(GET|POST)" type="magnus-internal/cri"
   

   Service fn="req_handler" method="(GET|POST)" type="magnus-internal/cwr"
   

8. Add the Service lines to the <Object name="default"> section of the iPlanet obj.conf file, after any existing Service lines.
9. Return to the wcs/conf/obj.conf file and note the <Object> section that corresponds to the following template:

   # Add to the end of the file
   

   <Object ppath="INSTALL_ROOT/viewers/*.exe">
   

   ObjectType fn="force-type" type="application/octet-stream"
   

   Service fn="send-file"
   

   </Object>
   

10. Add the <Object> section to the end of the iPlanet obj.conf file.
11. Restart your iPlanet Enterprise Server.
12. Connect to Crystal Enterprise by opening your web browser and going to:

    http://webserver/crystal/enterprise/

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