The OCLC SiteSearch suite supports IIS for only the Windows NT operating system.

1. Open the IIS Internet Service Manager.

2. Add the WebZ extension for IIS as an ISAPI filter for the IIS master server:

• Right-click the icon for the master server.
• Select Properties from the context menu.
• On the Internet Information Server dialog tab, click the Edit button beside Master Properties.
• Click the ISAPI Filters tab.
• Click the Add button.
• On the Filter Properties dialog box, enter a name for the WebZ extension and the name and location of its executable file (<WebZ_root>/isapi/isapiwebz.dll). Click OK.
• On the ISAPI Filters tab, click Apply.

3. Add the SSPI filter as an ISAPI filter for the IIS master server. From its ISAPI Filters tab (the tab open at the end of step 2):

• Click the Add button.
• On the Filter Properties dialog box, enter a name for the SSPI filter and the name and location of its executable file (C:\Winnt\System32\inetbay\sspifilt.dll). Click OK.
• On the ISAPI Filters tab, click Apply. Then click OK.

5. Add the WebZ extension for IIS as an ISAPI filter for WebZ.

• Click the + sign beside the master server to display the Web servers defined for Web sites and FTP sites.
• Right-click the icon for the Web server you are using for WebZ.
• Select Properties from the context menu.
• Click the ISAPI Filters tab.
• Click the Add button.
• On the Filter Properties dialog box, enter a name for the WebZ extension and the name and location of its executable file (<WebZ_root>\isapi\isapiwebz.dll). Click OK.
• On the ISAPI Filters tab, click Apply.
• Click OK.

6. Add information about the WebZ extension to the Windows registry:

• Use Windows Explorer to go to the <WebZ_root>\scripts directory.
• Double-click the webz.reg file.
• You receive a message confirming that information from webz.reg has been entered into the registry. Click OK.

8. Restart your NT system and IIS to read in the configuration changes you made to the registry.

12. Start the WebZ System and test access to the system through IIS using a Web browser.

1. Follow the IIS configuration procedure for SiteSearch 4.1.2/4.1.2a for WebZ on the machine on which you plan to run IIS with Record Builder. Verify that WebZ functions properly under IIS.

6. Add the WebZ extension for IIS as an ISAPI filter for Record Builder.

• Click the + sign beside the master server to display the Web servers defined for Web sites and FTP sites.
• Right-click the icon for the Web server you are using for Record Builder.
• Select Properties from the context menu.
• Click the ISAPI Filters tab.
• Click the Add button.
• On the Filter Properties dialog box, enter a name for the WebZ extension and the name and location of its executable file (<WebZ_root>\isapi\isapiwebz.dll). Click OK.
• On the ISAPI Filters tab, click Apply.
• Click OK.

7. Use the Windows Control Panel to stop the IIS Administrative Service and the World Wide Publishing service.

8. Edit <WebZ_root>\ini\WebSvrExt.ini file:

• Review the values defined in this file to ensure that they are accurate and edit them if necessary.
• Add this line to the end of the file. Remember to add a carriage return at the end of the line.

  ServerType1 = jassirb

9. Do you want to prevent WebZ's servers (JaSSI, ZBase, and Access) from starting when you start Record Builder? Since you cannot run WebZ and Record Builder simultaneously on the same machine with IIS, there is no need for them to start when you are running Record Builder.

• Yes. Edit the [ServerType] section of <WebZ_root>\ini\OpServe_rb.ini.
  • Comment out or remove the JaSSI, ZBase, and Access lines.
  • Renumber the remaining lines so that the section looks like this:

    [ServerType]
    ServerType1 = OpServe
    ServerType2 = Lock
    ServerType3 = JaSSIRB
    ServerType4 = ZBaseRB
    ServerType5 = AccessRB

• No. Go directly to step 10.

12. Start Record Builder and test access to Record Builder through IIS using a Web browser.

1. From the Start menu, select Run.

2. Type "regedt32" in the Run window and click OK. The Registry Editor window will appear.

3. From the HKEY_LOCAL_MACHINE on Local Machine screen, open the following directories and subdirectories on the left portion of the screen: HKEY_LOCAL_MACHINE -> SYSTEM -> CurrentControlSet -> Services -> W3SVC -> Parameters.

4. Review the variables contained in the Parameters subdirectory listed on the right-hand side of the screen. Double click on the Filter DLLs variable and add the following line of text below to the value of the variable in the String Editor:

<WebZ_root>\isapi\isapiWebZ.dll

Note:

If the Filter DLLs variable does not exist in the Parameters subdirectory, you will need to add the variable. From the Edit menu, select Add Key. In the Add Key window, type "Filter DLLs" in the Key Name field and add the value shown above. Click OK and check to see if the variable now shows up in the list with the correct value.

Make sure to separate multiple paths with a comma (","). For example, after you make the changes above, the value of Filter DLLs may look similar to the following:

D:\WINNT\System32\inetsrv\sspifilt.dll,
D:\Inetpub\wwwroot\scripts\isapiWebZ.dll

The second value reflects the location of the WebZ Extension DLL. Notice that the path names included above are separated by a comma.

5. Click OK to close the String Editor. Make sure that the changes you made are now visible in the right-hand portion of the HKEY_LOCAL_MACHINE screen.

6. Exit the Registry Editor.

7. Open the <WebZ_root>\ini\WebSvrExt.ini file in a text editor. Review the values defined in this file to ensure that they are accurate. Make any necessary changes. Save and close the file.

8. In your IIS configuration, define the <WebZ_root\/htdocs\obiv1 directory (or another directory under <WebZ_root>\htdocs that contains your customized HTML files) under as your document root.

9. Restart your NT system and IIS to read in the configuration changes you made to the registry.

10. Start the WebZ System and test access to the system through IIS using a Web browser.