Microsoft IIS 7 or Later

Registering the Native Modules

DLLs: CSPms.dll and CSPmsSys.dll

Before these modules can be used they must be registered with IIS. This is done in the Internet Information Services (IIS) Manager control panel.

1. Open the Internet Information Services (IIS) Manager window.

2. In the left panel, highlight: [MACHINE_NAME] ([machine_name]\[user_name])

3. In the middle panel, double-click the Modules icon.

4. In the right panel, select Add Native Module (or Configure Native Modules).The precise wording depends on the build of IIS in use.

5. Select Register and enter the following in the Register Native Module dialogue:

   Name: CSPms

   Path: C:\inetpub\CSPGateway\CSPms.dll

   Select OK.

6. In the left panel, expand the top level and expand Web Sites, and Default Web Site. Highlight Default Web Site:

   [MACHINE_NAME] ([machine_name]\[user_name])
               Web Sites
                       Default Web Site
   

   

7. In the right panel, select Add Native Module.

8. Select CSPms and select OK.

Mapping the CSP File Extensions

Map the CSP file extensions to the CSP Gateway Native Modules as follows:

1. Open the Internet Information Services (IIS) Manager window.

2. In the left panel, expand the top level and expand Web Sites, then the Default Web Site section. Highlight Default Web Site:

   [MACHINE_NAME] ([machine_name]\[user_name])
               Web Sites
                       Default Web Site
   

   
   Note:

   This activates CSP for the whole web site. To restrict the use of CSP to specific virtual sub-directories (such as /csp/) focus control on the appropriate subdirectory (under Default Web Site) before creating the mappings. Repeat the process for each virtual subdirectory from which CSP content is to be served.

3. In the middle panel, double-click the Handler Mappings icon.

4. In the right panel, select Add Module Mapping.

5. In the Add Module Mappings dialogue, enter the following details:

   Request Path: *.csp

   Module: (select CSPms from the dropdown)

   Name:CSPGateway_csp

6. Select Request Restrictions and ensure that the box is not checked next to Invoke handler only if request is mapped to. This action sets the value of Path Type to Unspecified, as shown in the Handler Mappings table.

7. Select OK to return to the Add Module Mappings dialogue and select OK again.

8. Repeat the above process to add the following Module Mappings:

   Request Path: *.cls

   Module: (select CSPms from the list)

   Name:CSPGateway_cls

   Request Path: *.zen

   Module: (select CSPms from the list)

   Name:CSPGateway_zen

   Request Path: *.cxw

   Module: (select CSPms from the list)

   Name: CSPGatewayManagement

Registering Additional File Types with CSP

To configure additional file types to be processed by CSP, replicate the configuration created for the usual file extensions (that is, .csp,. .cls, .zen) for the new file extension(s).

If you need to serve other static files through the CSP Gateway, add mappings for the needed file types so that those files can be loaded. In particular, if you need to access the Management Portal through this web server, add mappings for file types .jpg, .gif, .png, .css, and .js. If you do not do so, the Management Portal will be missing its images.

To map requests for all files to CSP for a given path, set up the following wildcard entry for that path:

Operating and Managing the Gateway

To access the CSP Gateway’s systems management suite, point your browser at the following location:

http://<ip_address>/csp/bin/Systems/Module.cxw

The CSP engine is automatically invoked for requested files that contain a .csp, .cls, or .zen extension. For example:

http://<ip_address>/csp/samples/menu.csp

If you see an unauthorized user error message, refer to the security notes in the section “CSP Gateway and Security”.