Index Server Search Plug-in
Alterian Content Manager
Corporate Edition 6.3
1 November 2010
www.alterian.com
Information in this document is subject to change without notice and does not represent a commitment on the part of the vendor or its representatives.
Copyright © Alterian. All rights reserved.
Documentation feedback and comments: [email protected]
Alterian Content Manager and the Alterian Content Manager logo are trademarks of Alterian. Windows XP, SQL Server, ASP.NET, Visual Studio .NET and C# are trademarks of Microsoft Corporation. All other products named herein may be trademarks of their respective manufacturers and are hereby recognized. Trademarked names are used editorially, to the benefit of the trademark owner, with no intent to infringe on the trademark.
www.alterian.com
Document Control
The following table details the revision history of this Installation and User Guide. It details significant changes to the text and the software version to which the changes apply.
Version History
Date Author Version Change reference
November 10 Jordanka Balkanska 6.3 Initial Release
Distribution List
Who Position
Jordanka Balkanska Technical Author
Index Server Search Plug-in i of iii
Table of Contents
1 Introduction ...... 1
1.1 Overview ...... 1
1.1.1 Sample Output 1
1.1.2 Query Syntax and Filtering 2
1.2 Known Issues ...... 2
2 Compatibility ...... 3
2.1 Windows Server Compatibility ...... 3
2.2 Multi-Language Compatibility ...... 3
3 Installation ...... 4
3.1 Pre-requisites ...... 4
3.2 Installation Overview ...... 4
3.3 Step 1 – Configuration of Website Folders ...... 5
3.3.1 Overview 5
3.3.2 Configuration 5
3.4 Step 2 - Configuration of Windows Indexing Service ...... 5
3.4.1 Overview 5
3.4.2 Configuration 5
3.5 Step 3 - Installation of PDF IFilter and HTML IFilter on Server ...... 8
3.5.1 Installation on Windows Server 2003 8
3.5.2 Installation on Windows Server 2008 8
3.6 Step 4 – Configure Alterian CMC to Create Index-able Web Pages ...... 8
3.7 Step 5 - Configure Search Logging ...... 9
3.7.1 Create the Log File 9
3.7.2 Modify the Web.Config File 10
3.8 Step 6 - Configuring the Plug-in with the Editor ...... 10
3.8.1 Adding the Plug-in to a Page 10
3.9 Step 7 - Finalization and Testing the Configuration ...... 14
3.9.1 Re-Index the Site 14
Index Server Search Plug-in ii of iii
3.9.2 Start Windows Indexing Service 15
3.9.3 Categorize Custom Catalog Properties 15
4 Appendix A – Detailed Plug-in Configuration ...... 17
5 Appendix B - Searching External Information or Sites ...... 19
5.1 Custom Properties ...... 19
5.1.1 Multi-Site Searching 19
6 Appendix C – Resolving Configuration Issues ...... 20
7 Appendix D - Advanced Testing ...... 21
Index Server Search Plug-in iii of iii
1 Introduction
1.1 Overview
The Alterian CMC Index Server Search plug-in provides fast and accurate searching of your site*. It ranks pages by relevance and can limit searches based on categories and document content types. An optional advanced search mode enables searching by date last updated and also allows results to be ordered by relevance, date and title. The plug-in integrates with the Indexing Service facilities provided natively by Windows in order to index and locate documents.
For link pages to be returned in search results, the configuration option Note needs to be enabled in the CMC Admin application, Configuration Indexing.
1.1.1 Sample Output
Example output from the plug-in is shown in the screenshot, below:
Index Server Search Plug-in 1 of 21
1.1.2 Query Syntax and Filtering
A range of query filtering and syntax options are available in the Index Server Search plug-in to constrain the query results. Options include: • Constraining the query text to words, phrases and complete sentences • Boolean operators for document content or property values (such as AND, OR, NOT, AND NOT) • Restricting matches to a range of dates within which documents were last updated • Document types (such as only .DOC or .XLS) • Category-based search boundaries
The plug-in includes the ability to search most common types of documents including Microsoft Office and PDF documents together with HTML pages from your website.
Content is automatically re-indexed by the Windows Indexing Service whenever it is updated, meaning that minimal administration is required once setup and configuration is complete.
1.2 Known Issues
Known issues exist within Index Server - in particular with its handling of multilingual content which uses foreign characters: • If a published HTML page contains content which uses a character different to the set used by the Index Server's machine locale, for example a Chinese title in an HTML page indexed on a server with an English locale, that data will be incorrectly indexed and results based on matching queries will show corrupt data, or may not show the corrupted page at all. • Foreign characters cannot be used as part of a search query unless the locale of the search is specifically set to the correct locale of the search characters. This means that queries containing mixtures of characters from different locales are not possible.
Index Server Search Plug-in 2 of 21
2 Compatibility
The Index Server Search plug-in applies to Alterian CMC 6.3.
2.1 Windows Server Compatibility
The Index Server Search plug-in integrates with Windows Indexing Service for both Windows Server 2003 and Windows Server 2008. Configuration is slightly different on each server. This document highlights where different configuration is required.
The default indexing service for Windows Server 2008 is Windows Search. This plug-in is applicable only to the Windows Indexing Service role service which is an alternative and optional service provided within Windows Warning Server 2008. It is important to note that the Windows Indexing Service cannot be installed side-by-side with the Windows Search – the two are mutually exclusive services.
2.2 Multi-Language Compatibility
Note that version 6.3 plug-ins include multi-lingual capability for both the Editor-specific user- interface and the generated website output. All examples in this document are in English.
The process of adding language translations to a plug-in are described in a Note separate document.
Index Server Search Plug-in 3 of 21
3 Installation
3.1 Pre-requisites
In order to configure the Windows Indexing Service additional files are required and are available in the following zip archive: • IndexServerSearch.zip
For Windows Server 2008, if .pdf files are to be indexed, version 8.1.2 or Note above of Acrobat Reader should be installed. This is supplied on the Alterian CMC installation CD.
3.2 Installation Overview
Seven key steps are involved in installing and configuring the system to support the Index Server Search plug-in. These steps are as follows: 1. Creation/configuration of folders to allow Windows Indexing Service to index required website files; 2. Configuration of Windows Indexing Service to identify the above folders for indexing including:
a. Creation of a folder that Windows Indexing Service will use to manage its “Catalog” (a catalog being a specification of folders etc. that may be indexed);
b. Specification of the different website folders which may be indexed;
3. Specification of the filters which allow non-default file-types to be indexed (for example .doc file types are indexed by default whereas .pdf and .htm files are not). 4. Configuring Alterian CMC so that it generates index-able web pages. 5. Configuring Search Logging. 6. Configuring the plug-in within the Editor; 7. Finalization and testing the configuration.
The following sections explain the steps involved to complete the configuration process after which it should be possible to use the Index Server Search plug-in.
This document does not explain the intricacies of Windows Indexing Service or how to administer it - merely, it describes how to configure it for use with the Index Server Search plug-in.
Index Server Search Plug-in 4 of 21
3.3 Step 1 – Configuration of Website Folders
3.3.1 Overview
Once configured, Windows Indexing Service will index folders you have specified for your site. Typically, these folders may contain documents such as .doc files or .pdf files. In addition, your website pages will also need to be indexed. For this to be possible, additional configuration is required.
In order for site pages to be indexed it is necessary to create a folder which will contain .htm files. These .htm files are, in essence, a representation of your site which is created automatically by the Alterian CMC Service so that the Windows Indexing Service may use them.
3.3.2 Configuration 1. Create a directory called “Publish” outside of the webroot folder on the hard drive of the web server. A possible location would be as a sibling folder to the webroot – e.g: C:\Program Files\Alterian\CMC 6.3\CMS\Websites\PublicSector\Publish 2. Ensure that this folder has been given the appropriate permissions for CMC. For both Windows Server 2003 and Windows Server 2008 the folder requires the NETWORK SERVICE user to be granted Modify access. 3. It will also be necessary to ensure that the Windows Indexing Service can index this folder. To do this: • Select the folder in Windows Explorer; • Right-click and open the Properties dialog; • Within this dialog, click the Advanced… button; • In the “Advanced Attributes” dialog that is displayed, ensure that the checkbox for fast searching within Indexing Service is enabled – select it if it is not. 4. Note that it will also be necessary to set the fast searching option for all other folder which may require indexing (e.g. pdf, files, docs etc.).
3.4 Step 2 - Configuration of Windows Indexing Service
3.4.1 Overview
We now need to configure the Windows Indexing Service so that it knows which of the website folders to index. We do this by creating a new “Catalog” within the Windows Indexing Service which we will configure to reference the required folders.
3.4.2 Configuration
First, open the user interface for the Windows Indexing Service by: 1. Opening:
Start All Programs Control Panel Administrative Tools Computer Management 2. Within the Computer Management Console, expand the Services and Applications node, then expand the Indexing Service node.
Index Server Search Plug-in 5 of 21
The following screenshot gives an example of what will be displayed:
Each node underneath the Indexing Service node is a “Catalog”. We will need to create a new site-specific catalog for use by the Index Server Search plug-in.
Create the Catalog
To create the catalog, two steps are required:
1. Create a directory called “Catalog” in the same location as the publish directory for the Index Server catalog. For example: C:\Program Files\Alterian\CMC 6.3\CMS\Websites\PublicSector\Catalog
We will not be concerned with the content of this folder – it will be used by Windows Indexing Service for its management of the Catalog we are about to create. 2. Select the Indexing Service node in the Computer Management console, right-click and create a new catalog. When prompted, specify the “Name” as the site name (e.g. PublicSector), and the “Location” as the path of the catalog directory created in the previous step.
If you wish Index Server to generate summaries of the documents, you need Note to select the Generate abstracts checkbox under the Generation tab of the catalog's properties.
Index Server Search Plug-in 6 of 21
Add Directories to the Catalog
Now that we have a catalog for the website, we need to specify which folders within the site we wish to be indexed by the Windows Indexing Service. To do this: 1. Right-click on the directories pane of the newly created catalog and select New Directory. 2. Create a new directory entry for each site folder of interest specifying a “UNC Alias” for each (this is usually just a “name” but refer to the note in the following section for more details). For example, if you wish to index the website pages, your pdf and docs folder then create the following Indexing Service directories within the console:
UNC Alias Directory
publish C:\Program Files\Alterian\CMC 6.3\CMS\Websites\PublicSector\publish docs C:\Program Files\Alterian\CMC 6.3\CMS\Websites\PublicSector\webroot\docs pdf C:\Program Files\Alterian\CMC 6.3\CMS\Websites\PublicSector\webroot\pdf
You may also wish to add other directories to search as well.
If you wish to add further directories at a later date, the Index Server Service should be stopped before adding directories with large numbers of Warning files. Failure to do this may result in the Index Server catalog becoming corrupted.
A side note regarding Directories and Aliases
Where possible, the Index Server Search plug-in will attempt to provide a relative URL from the current site to any "found" files. Where this is not possible it will use the value in the Alias/UNC field for the directory. This allows network shares or separate HTTP virtual directory paths to be specified, e.g
Directory D:\Data\Documents\
UNC Alias \\servername\documentshare\ or:
Directory D:\Data\Documents\
UNC Alias http://servername/documents/ (where the Virtual Directory is setup in IIS to point to the physical directory path)
If this is not specified, it will simply provide a relative link to the filename, which is unlikely to work. It is your responsibility when setting up Index Service directories to ensure that the UNC Aliases specified are correct and that adequate folder and sharing permissions on the file system are applied to enable indexed documents reported in search results to be accessible.
Index Server Search Plug-in 7 of 21
3.5 Step 3 - Installation of PDF IFilter and HTML IFilter on Server
In order for pdf and htm files to be searchable, dedicated filters need to be installed. The process of installation is slightly different for Windows Server 2003 and Windows Server 2008 so the steps required are described separately.
Refer to the .zip file specified at the start of this document to obtain specified files.
3.5.1 Installation on Windows Server 2003
HTML IFilter 1. Copy the htmlprop.dll and htmlprop.ini files to the %windir%\system32 directory on your server. 2. Register the dll by entering the following at the command-line prompt: regsvr32.exe "%windir%\System32\HtmlProp.dll" 3. Enable automatic registration of the filters by adding the paths and filenames of the DLLs to the MULTI_SZ value of the 'DLLsToRegister' entry. This can be found in the registry under the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ContentInd ex
PDF IFilter 1. Run the ifilter60.exe program on the server. This will install the PDF filtering component.
3.5.2 Installation on Windows Server 2008
HTML IFilter 1. Copy the htmlprop.dll and htmlprop.ini files to the %windir%\system32 directory on your server.
PDF IFilter 1. In order to install an appropriate PDF IFilter, ensure that an appropriate version of Adobe Acrobat Reader is installed on the server. Version 8.1.2 as supplied on the CMC installation disk will suffice.
3.6 Step 4 – Configure Alterian CMC to Create Index-able Web Pages
In order for the website pages to be accessed and indexed by the Windows Indexing Service, the website pages are written out to the “Publish” folder created earlier. This process is performed by the Alterian CMC Service and, in order for this service to know whether and where to write these files, we must provide additional configuration to Alterian CMC.
To do this open the Alterian CMC Admin application and go to Configuration Site Options. You will need to add a new option group depending on whether the searches are performed on a live or staging server. The required options are shown in the table below:
Index Server Search Plug-in 8 of 21
Key Value Group
enabled yes or no SQLDataPublishStaging
path SQL publishing directory SQLDataPublishStaging
siteurl Absolute URL to site default page minus the page ID* SQLDataPublishStaging
enabled yes or no SQLDataPublishLive
path SQL publishing directory SQLDataPublishLive
siteurl Absolute URL to site default page minus the page ID* SQLDataPublishLive
Note that, for a single installation, only the SQLDataPublishStaging options need be specified. In such a configuration, for example, specify the following options: 1. Enabled – set this to “yes” 2. Path – set this to the fully-qualified path to the “Publish” folder created earlier – this value will be used by the Alterian CMC Service to create the index-able website files. 3. Siteurl – This option is used by the plug-in to construct links from search results to the “found” webpage. It represents a query using the absolute URL to the site default page but without specifying a page id. This is usually of the following form:
http:// yoursiterooturl /default.aspx?page=
E.g.
http://server1/PublicSector/default.aspx?page=
The plug-in will append the appropriate page id to this URL when the search results are rendered.
3.7 Step 5 - Configure Search Logging
A log directory will be used to store comma-separated value (CSV) files of the search terms used by the site visitors.
3.7.1 Create the Log File 1. Create a directory on the server for storing search logs, for example:
C:\Program Files\Alterian\CMC 6.3\CMS\Websites\PublicSector\iss_logs 2. Ensure that this folder has been given the appropriate permissions. For both Windows Server 2003 and Windows Server 2008 the folder requires the NETWORK SERVICE user to be granted Modify access.
Index Server Search Plug-in 9 of 21
3.7.2 Modify the Web.Config File
The site web.config file must be modified to register the log directory: 1. Modify the web.config file by adding the following line to the bottom of the
2. Add the following section to the web.config as a child node of the
Where the value is the path to the directory created earlier in this step.
The system should now be in a state such that the Index Server Search plug-in can be configured within the CMC Editor.
3.8 Step 6 - Configuring the Plug-in with the Editor
3.8.1 Adding the Plug-in to a Page
Start by adding the plug-in to a page as follows: 1. Log in to the Alterian CMC Editor. 2. Browse to the designated search page (create a new page if necessary). 3. Insert a new Index Server Search plug-in by selecting the “Plug-ins” toolbar item and then select “Search -> Index Server Search” from the plug-ins dialog.
The GUI interface for the plug-in will appear allowing a number of options to be set, as shown below:
Index Server Search Plug-in 10 of 21
Index Server Search Plug-in Configuration Dialog
The user interface has three panels, each of which are described below: 1. Categories to exclude from the search This option allows pages marked with a particular category that would otherwise have matched the query, to be excluded from search results. This is useful for pages which are meant to remain private or hidden (system pages, for example). Multiple items can be selected by holding down the CTRL key whilst selecting the required categories. Note that categories excluded from the search are not excluded from the category drop-down list (when the search control is rendered on the website) - this needs to be set in “Categories to hide from the user”. 2. Categories to hide from the user This option allows control over which categories will appear in the category drop-down list on the website search page. This is useful for categories that are system-specific or of use for site Editors but not visitors.
An example of such a category could be “Hide from Menu”. Multiple items can be selected by holding down the CTRL key whilst selecting the required categories. Please note that categories hidden from the user are not excluded from the search results - this needs to be set in “Categories to exclude from the search”. 3. Advanced Search Options These options determine whether or not the Advanced search options should be shown on the website search page and, if they are not shown, whether they can be displayed via a “More Search Options” link. The advanced search options allow site visitors to add further search predicates to their search, allowing for the date last updated to be restricted, and the results to be ordered by relevance, date, and title:
Index Server Search Plug-in 11 of 21
Advanced Search Options Hidden
Advanced Search Options Shown
Index Server Search Plug-in 12 of 21
Index Server Options
This set of options connects the search plug-in to the “Catalog” created in Windows Indexing Service configuration steps explained earlier and also enables the specification of document types to be shown in results together with various formatting options.
Catalog
This is the catalog created within the Windows Indexing Service for the site. This is not the name of the directory created to contain the catalog but rather the name of the catalog created within the Indexing Service console.
If an incorrect catalog name is specified, the plug-in may return files Note from other parts of the system.
It is this option which connects the plug-in to the indexed items produced by Windows Indexing Service. In essence, this option specifies where the plug-in will actually search to obtain its results.
'All Other' Document Types
This option is used to specify which default document types should be searched for when no document type has been specified by the website search user.
The format of this option is a comma-delimited list of document file type extensions, using question marks (?) as wildcards.
For example, to query .txt and .bat files, the value should be:
txt,bat
The inclusion of '?' as a wildcard allows for multiple doc types - for example Word templates and documents (doc, dot).
Layout Options
The layout options determine how the search box will appear, how many results to display per page, and the color in which to render the search box and border: • Items per Page
This must be a positive integer to represent how many search result items to display per page, before pagination “Previous” and “Next” links are created:
• Pagination Spacing
This must be a positive integer to represent how many spaces to display between the “Previous” and “Next” pagination links when showing results. • Border Color
This color is used for the border around the search plug-in and defaults to black when none is specified. The value must be a valid HTML-based color, beginning with a # symbol, e.g.
Index Server Search Plug-in 13 of 21
#RRGGBB
• Box Color
This color is used for the filled color of the search plug-in and defaults to a pale grey when none is specified. The value must be a valid hexadecimal color code, such as #000000 for black.
The Index Server Search Plug-in Configured in the Editor
Once the options have been entered press the OKOKOK button to apply the changes. The plug-in will then be displayed in the Editor with its options displayed:
Refer to Appendix A for details regarding further configuration of the plug-in and search results.
3.9 Step 7 - Finalization and Testing the Configuration
Once the above configuration is complete, the following final steps are required to ensure that documents and pages can be appropriately searched.
3.9.1 Re-Index the Site
Approved pages will appear as a .htm files within the “Publish” folder when the site is next re- indexed. To force an immediate re-index (thus making pages available to the Windows Indexing
Index Server Search Plug-in 14 of 21
Service), within the Alterian CMC Admin application navigate to the Admin Add-ins Search ReIndex page and press the “ReIndex Now” button.
Once re-indexing is complete, check the “Publish” folder for the existence of .htm files. Note that at this point, the Windows Indexing Service itself will not have indexed the .htm files.
3.9.2 Start Windows Indexing Service
Start the Windows Indexing Service (or restart, as appropriate). Ensure that all pages and documents have been indexed before proceeding. To determine that the Windows Indexing Service has completed indexing the site pages and documents, perform the following steps: 1. Start the Indexing Service user interface (where the catalog was created earlier) and select the Indexing Service node. The catalog you created will be listed together with the total number of documents and the documents remaining to be indexed. 2. Ensure that “Total Docs” is greater than 0 and that “Docs to Index” is equal to 0. If “Docs to Index” is not yet 0 wait a while – it may take some time to index all of the site documentation.
3.9.3 Categorize Custom Catalog Properties
By indexing the site, the Windows Indexing Service will have read the content of the .htm files and will have created the following custom catalog properties within your catalog: • lastsavedtm • comments • categories • Alterian CMC URL • access rights • characterisation • window
It is necessary to ensure that each of these are in the Windows Indexing Server secondary cache and are of type VT_LPWSTR4. To do this: 1. Start the Indexing Service user interface and select the Indexing Service node. 2. Select the Properties sub-node of your Catalog. 3. If the new properties are not listed, right-click on the Properties node and select All Tasks -> Refresh List. 4. Right-click on each of the above and select the secondary cache option (i.e. make them searchable). 5. Ensure that the type of each is VT_LPWSTR4. 6. Restart Index Server Service – you need to restart this in order for the changes to be picked up.
It should now be possible to perform searches within a website page containing the Index Server Search plug-in.
If results are not shown it may be necessary to tell the Indexing Service to re-scan with the new properties. To do this:
Index Server Search Plug-in 15 of 21
• Navigate to the “Directories” list in your site catalogue within the Indexing Service user interface (from within the Computer Management console);
• Right-click on the “Publish” directory that you have created;
• Select All Tasks->Rescan (Full);
This will instruct the Indexing Service to rescan the generated .htm file using the properties defined above. This process can also be performed with any additional directories (such as pdf, files, docs etc.).
Index Server Search Plug-in 16 of 21
4 Appendix A – Detailed Plug-in Configuration
When the plug-in is configured within a page in the Editor, the appropriate properties are inserted into the page source. An example of this is shown below:
The properties which may be specified are:
(A) NoSearchMetaIds This should be a dash delimited list of the IDs of the meta categories, for example 1-2-3
(B) IgnoreMetaId This should be a dash delimited list of the IDs of the meta categories, for example 1-2-3
(C) AdvancedLink To show advanced options, value should be 'show' To hide advanced options, value should be 'none' To display a link to advanced options, value should be 'link'
(D) IndexServerCatalog The name of the catalog in Index Server setup for the site
(E) AllOtherDocTypes See GUI description
(F) ItemsPerPage Integer value for number of search results to display per page
(G) PaginationSpacing Integer value for number of spaces to insert between Previous and Next pagination links
(H) BorderColor HTML-based color, e.g. #000000
(I) BoxColor HTML-based color, e.g. #000000
Template for Search Results
The Index Server Search plug-in is a templated control. An example of the ItemTemplate is shown below:
Index Server Search Plug-in 17 of 21
The template definition can be edited in the Editor using the “Edit Source” option. In order to verify the properties of the plug-in have been correctly chosen, the page should be viewed using the Alterian CMC Editor “Preview” feature. If the page does not appear correctly, then the configuration steps in the document should be referenced to make sure that everything has been correctly configured.
Index Server Search Plug-in 18 of 21
5 Appendix B - Searching External Information or Sites
The Windows Indexing Service cannot search databases. This makes it necessary to publish data to the file system in order for database records to be read. This is exactly what is done when Alterian CMC web pages are transformed into .htm files within the “Publish” directory.
If you wish to search data of an external application using the Index Server Search plug-in, start by referring to one of the generated .htm files within the “Publish” directory for an example of how such content generated content should be structured. Particular attention should be given to the Custom Properties contained therein.
5.1 Custom Properties
The following “custom” properties exist and can be used so that any external data may be published and searched by the Index Server Search plug-in. • Alterian CMCurl
The URL to go to when this document is selected from the search results. • AccessRights
A comma-separated list of roles that are allowed to access this document. This list must also start and end with a comma. • Categories
A comma separated list of categories that apply to this document. Must also start and end with a comma. • LastSavedTm
The time the document was last modified stored as a double floating point number (although written out as a string).
The above functionality means that you could for example “spider” an external website or legacy application, “publish” the content to a directory somewhere on your server including the above values in the published content and then include the publish directory into your index server catalog. The Index Server Search plug-in will be able to direct users to the appropriate URL.
5.1.1 Multi-Site Searching
One additional feature of the search is that it is possible to add various directories (e.g. PDF, docs, files, publish) from more than one web site into a given index server catalog. This effectively provides a multi-site search capability.
The limitation with this is that the search does not know the categories and permissions for the other site. In such circumstances it will use the roles and category ids from the “base“ site. If you have used exactly the same roles and categories across all the sites in a catalog then this is not an issue. However, if this is not the case, it will be necessary to consider the effect this will have on the search results.
Index Server Search Plug-in 19 of 21
6 Appendix C – Resolving Configuration Issues
Should you have any issues configuring the required setup for the Index Server Search plug-in, Alterian support site contains details regarding the following configuration issues. • PRB: "No Catalog defined" error occurs when searching for values with Index Server Search • PRB: Index Server Search does not return any HTML files for the site • PRB:Documents are not retrieved by the Index Server Search facility • PRB: Recently updated documents/pages are not retrieved by the search facility
Index Server Search Plug-in 20 of 21
7 Appendix D - Advanced Testing
It may be of use to use the “Query the Catalog” functionality (which is provided with the Windows Indexing Service) to test the Windows Index Server Search configuration in detail. If this is required, then the HTM file it is run from needs modification (note - these changes are not supported by Microsoft or Alterian CMC). To do this: 1. Locate the ciquery.htm file found within %windir%\Help\ 2. Take a backup copy of the file and store it in a location from where it can be restored at a later time if required. 3. Open the original file within an HTML or text editor 4. Find the following line in the HTML source code of the file:
Q.DefineColumn "Unfiltered(DBTYPE_BOOL, 1) = 49691c90-7e17- 101a-a91c-08002b2ecda9 7"
5. Add the following lines underneath it:
Q.DefineColumn "accessrights(DBTYPE_STR | DBTYPE_BYREF) = d1b5d3f0-c0b3-11cf-9a92-00a0c908dbf1 accessrights" Q.DefineColumn "categories(DBTYPE_STR | DBTYPE_BYREF) = d1b5d3f0-c0b3-11cf-9a92-00a0c908dbf1 categories" Q.DefineColumn "Alterian CMCurl(DBTYPE_STR | DBTYPE_BYREF) = d1b5d3f0-c0b3-11cf-9a92-00a0c908dbf1 Alterian CMCurl" Q.DefineColumn "comments(DBTYPE_STR | DBTYPE_BYREF) = d1b5d3f0-c0b3-11cf-9a92-00a0c908dbf1 comments" Q.DefineColumn "language(DBTYPE_STR | DBTYPE_BYREF) = d1b5d3f0-c0b3-11cf-9a92-00a0c908dbf1 language"
6. Find the following line in the HTML source code of the file:
7. Modify the MAXLENGTH value to 100000, then save the file:
Modifying the file in this way will allow Trace output Query text of the Index Server Search plug-in to be copied and pasted into the “Query The Catalog” page and run directly against index server.
Index Server Search Plug-in 21 of 21
Corporate and North American European Headquarters Headquarters
Alterian Plc Alterian Inc. The Spectrum Building 35 E. Wacker Drive Bond Street Suite 200 Bristol Chicago, Il 60601 BS1 3LG USA UK T +1 312 704 1700 T +44 117 970 3200 F +1 312 704 1701 F +44 117 970 3201
Other Offices
Alterian Alterian Alterian Insight House 1010 Washington Blvd. Building 34 Newbury Business Park 9th Floor Suakin Drive London Road Stamford Mosman Newbury, Berkshire CT 06901 NSW 2088 RG14 2QA USA Sydney UK T +1 203 653 9090 Australia T +1635 262000 F +1 203 653 9095 T +61 2 9968 2449 F +1635 262001 F +61 2 9969 1163
Alterian Alterian B.V. Alterian Technologies India Pvt. Ltd. Branksome House Naarderweg 16 3rd Floor Discovery Court Business Park 1217 GL Hilversum H.M. Rochester Wallisdown Road Postbus 371 197 Double Road Poole, Dorset 1200 AJ Hilversum Indiranagar BH12 5AG The Netherlands Bangalore – 560 038 UK T +31 35 625 7890 T +91 80 2521 0740 T +44 1202 250000 F +31 35 625 7899 F +44 1202 250001
Alterian Alterian Alterian Deutschland 25152 Springfield Court 125-B Sully’s Trail Theresienstra βe 6-8 Suite 360 Pittsford, NY 14534 80333 München Valencia, CA 91355 USA Germany USA T +1 585 586 0160 T +49 89 288 90 164 T +1 661 367 9970 F +1 866 537 1533 F +49 89 288 90 45 F +1 661 367 9969
Alterian Nordics Sjöhagsvägen 6 721 32 Västerås Sweden T +46 21 495 01 40
E [email protected] W www.alterian.com Copyright © 2010 Alterian Technology Ltd.
www.alterian.com