Google Search Appliance Connectors Deploying the Connector for File Systems Google Search Appliance Connector for File Systems software version 4.0.3 Google Search Appliance software version 7.
Table of Contents About this Guide Overview of the GSA Connector for File Systems Automatic updates every 15 minutes Supported operating systems for the connector Supported file system protocols Known limitations File System limitation Distributed File System limitations Before you deploy the Connector for File Systems Windows account permissions Deploy the Connector for File Systems Step 1 Specify the IP address of the host computer Step 2 Install the Connector for File Systems Step 3 Configure adaptor-con
About this Guide This guide is intended for anyone who needs to deploy the Google Search Appliance Connector 4.0.3 for File Systems. The guide assumes that you are familiar with Windows operating systems, file systems, and configuring the Google Search Appliance by using the Admin Console. See the Google Search Appliance Connectors Administration Guide 4.0.3 for general information about the connectors, including: ● What’s new in Connectors 4.
Overview of the GSA Connector for File Systems The Connector for File Systems enables the Google Search Appliance to crawl and index content from Windows shares. A single connector instance can support a single Windows share. The share can be a UNC path or a mapped drive. DFS links are fully supported by the connector. The Connector For File Systems submits URLs identifying files in the file system repository to the GSA.
In addition to the directed graph traversal described above, the Connector For File Systems registers a file system change notification handler. This handler receives notifications when files or folders are added, removed, moved, modified, or have changes in metadata (including ACLs). The connector generates DocIds for the changed files and folders, constructs URLs from those DocIds, and sends them to the GSA in a metadata-and-URL feed.
Supported file system protocols The following table lists file system protocols used to communicate with file shares and indicates if the connector supports them.
Before you deploy the Connector for File Systems Before you deploy the Connector for File Systems, ensure that your environment has all of the following required components: ● GSA software version 7.2.0.G.90 or higher To download GSA software, visit the Google for Work Support Portal (password required). ● Java JRE 1.7 update 6 or higher installed on computer that runs the connector ● Connector for File Systems 4.0.
Membership in one of the following groups grants a Windows account the sufficient permissions needed by the connector: ● Administrators ● Power Users ● Print Operators ● Server Operators Note: It is not sufficient for the user to be a member of one of these groups at the domain level. The user must be a member of one of these groups on the local machine that exports the Windows share.
Deploy the Connector for File Systems Because the Connector for File Systems is installed on a separate host, you must establish a relationship between the connector and the search appliance. To deploy the Connector for File Systems, perform the following tasks: 1. Specify the IP address of the host computer 2. Install the Connector for File Systems 3. Optionally, configure adaptor-config.properties variables 4.
3. Visit the connector 4.0.3 software downloads page at http://googlegsa.github.io/adaptor/index.html. 4. Download the exe file by clicking on Microsoft Windows Shares in the Windows Installer table. You are prompted to save the single binary file, fs-install-4.0.3.exe. 5. Save the file to the host. 6. Start installing the file by double clicking fs-install-4.0.3. 7. On the Introduction page, click Next. 8.
16. To enable the search appliance to crawl the repository’s content, add the URL provided by the connector to the search appliance’s crawl configuration follow patterns: a. In the search appliance Admin Console, click Content Sources > Web Crawl > Start and Block URLs. b. Under Follow Patterns, add the URL that contains the hostname of the machine that hosts the connector and the port where the connector runs. For example, you might enter http://connector.example.com:5678/doc/ where connector.example.
adaptor.incrementalPollPeriodSecs Time between incremental crawls. 300 seconds adaptor.namespace Namespace used for ACLs sent to GSA Default filesystemadaptor. supportedAccounts Accounts that are in the supportedAccounts will be included in ACLs regardless if they are builtin or not. BUILTIN\\Administrators,\\E veryone,BUILTIN\\Users, BUILTIN\\Guest,NT AUTHORITY\\INTERACTIVE, NT AUTHORITY\\Authenticated Users filesystemadaptor.
hidden files and folders to be crawled by the search appliance. filesystemadaptor. lastAccessedDate Disables crawling of files whose time of last access is earlier than a specific date. The cutoff date is specified in ISO8601 date format, YYYY-MM-DD. Setting disabled filesystemadaptor.la stAccessedDate to 2010-01-01 would only crawl content that has been accessed since the beginning of 2010. Only one of filesystemadaptor. lastAccessedDate or filesystemadaptor.la stAccessedDays may be specified.
Setting filesystemadaptor.la stAccessedDays to 365 would only crawl content that has been accessed in the last year. Only one of filesystemadaptor. lastAccessedDate or filesystemadaptor.la stAccessedDays may be specified. filesystemadaptor. lastModifiedDate Disables crawling of files whose time of last access is earlier than a specific date. The cutoff date is specified in ISO8601 date format, YYYY-MM-DD. Setting disabled filesystemadaptor.
property can be used to expire previously indexed content if it has not been modified in a while. The expiration window is specified as a positive integer for number of days. Setting filesystemadaptor.la stModifiedDays to 365 would only crawl content that has been modified in the last year. Only one of filesystemadaptor.la stModifiedDate or filesystemadaptor.la stModifiedDays may be specified.
Note: By default the Connector for File Systems service runs using the Windows Local System account. This should be fine in most cases but this can cause issues if access to documents is restricted through ACLs. In cases where the Connector for File Systems service is not able to crawl documents due to ACL restrictions, you would need to specify a user for the Connector for File Systems service through the Windows Service Control Manager that has sufficient access to crawl the documents.
Uninstall the Google Search Appliance Connector for File Systems To uninstall the Connector for File Systems: 1. Click the Change GSA_FS_Adaptor Installation icon on your desktop. The Uninstall GSA_FS_Adaptor page appears. 2. Click Next. Files are uninstalled. 3. Click Done.
Troubleshoot the Connector for File Systems For information about troubleshooting the Connector for File Systems, see “Troubleshoot Connectors,” in the Administration Guide.
