Google Search Appliance Connectors Administration Guide Manual do Utilizador Página 1

Google Search Appliance Connectors Administration Guide Google Search Appliance Connectors software version 4.0.3 Google Search Appliance software

3 General Information This section contains general information about Connectors 4.0, including: ● Supported connectors ● Supported Google Sear

Configuration properties file Configuration is handled in the adaptor-config.properties file. Each connector installation procedure in this document

Secure crawling and serving configurations Connectors 4.0 support the authentication and authorization configurations for crawling and serving that

ACLs are stored in the search appliance’s group database. Mark all documents as public Adding the variable adaptor.markAllDocsAsPublic=true to

Download the connector software All connectors 4.0 must be installed on a host machine. This connector version does not support installing connector

To register a connector as a service: 1. Download and extract prunsrv.exe from the latest Windows binary download of Apache Commons Daemon. If you

com.google.enterprise.adaptor.sharepoint.SharePointUserProfileAdaptor com.google.enterprise.adaptor.fs.FsAdaptor com.google.enterprise.adaptor.ad.Ad

Use the ServicePassword to specify the password for the account designated by the ServiceUser parameter, as shown in the following example: --S

Where <CONNECTOR-NAME> is the internal name of the connector: ● SharePoint: adaptor-sharepoint ● SharePoint User Profiles: adaptor-sharepoi

4 Enable Connector Security In secure mode, the connectors communicate with the Google Search Appliance over HTTPS. You can enable security for an

Table of Contents About this Guide 1 About Connectors 4.0 The Lister/Retriever model 2 What’s New in Connectors 4.0? Resiliency Easy monitoring and

● Exchange certificates ● Turn on security with the server.secure property Create a self-signed certificate for the GSA For information about cre

Create a self-signed certificate for the connector Generate a self-signed certificate for the connector and export the newly created certificate.

2. Under Add more Certificate Authorities, click Browse. 3. Navigate to the connector’s directory and select adaptor.crt. 4. Click Save. Turn o

(Linux / Unix systems): java \ -Djava.util.logging.config.file=src/logging.properties \ -Djavax.net.ssl.keyStore=keys.jks \ -Djavax.n

You must include server.secure=true in the connector configuration before enabling these stricter features. To enable stricter security, perform t

5 Configure Connector Logs The connectors log processing messages, including exceptions and warnings. Log messages appear in the Connector Dashboar

java.util.logging.FileHandler.count=20 java.util.logging.ConsoleHandler.formatter=com.google.enterprise.adaptor.CustomFormatter com.google.enterpris

To change the size of log files, edit the java.util.logging.FileHandler.limit value in the logging.properties file: java.util.logging.FileHandler.l

6 Monitor Connectors with the Dashboard The Dashboard is a web-based interface that provides information about the connector’s operation, with easy

where: ● HTTP or HTTPS--If you run the connector in secure mode, use HTTPS to log in to the Dashboard. ● <CONNECTOR_HOST> is the hostname

Stop running a connector 4 Enable Connector Security Certificate Authorities Self-signed certificates Create a self-signed certificate for the GSA F

For each item, a signal indicates the status by color: ● Green for OK. The item is functioning. ● Yellow for alert. The item is not currently fu

Encode sensitive values You can encode passwords and other sensitive configuration values and copy them to the adaptor-config.properties file. Value

Download rich data about the connector The Diagnostics zip archive contains rich data about the connector, including: ● Current configuration sett

7 Troubleshoot Connectors Connectors 4.0 provide several options for troubleshooting issues, including: ● Connector Dashboard for checking the st

2. Make sure GSA crawling is not paused by using the Content Sources > Diagnostics > Crawl Status page. 3. Check the Connector status and re

documents:The server sent HTTP status code 503: Service unavailable reduce host load Feeds are not coming through ● Make sure GSA can accept feeds

Crawling is slow Use the Dashboard to find: ● What is the mean duration of a request (Response Time)? A couple hundred milliseconds would be good.

8 Common configuration options The following table lists common configuration options, which are used by all connectors. If the administrator doesn

documents are marked as “public.” Take note that if this option is set to “true” for the Connector for Active Directory, the connector does not sen

feed.noRecrawlBitEnabled Send bit telling the GSA to crawl your documents only once. false gsa.version Version number used to configure expected GSA

About this Guide This Administration Guide is intended for anyone who needs to understand how to manage Google Search Appliance (GSA) Connectors 4.

server.docIdPath Part of URL preceding encoded document ids. /doc/ server.fullAccessHosts Hosts allowed access without authentication (certificate

checking. server.useCompression Compress retrieval responses. true transform.acl.X Where X is an integer, match and modify principals as describe

1 About Connectors 4.0 Google Search Appliance connectors enable the Google Search Appliance to acquire content from external repositories and prov

The Lister/Retriever model Connectors 4.0 are based on the lister/retriever model. In this model, the lister notifies the search appliance of the na

2 What’s New in Connectors 4.0? In release 4.0, connectors work seamlessly with more search appliance features than previous releases. Noteworthy fe

Off-Board installation All Connectors 4.0 are installed on a separate host server rather than the search appliance itself. For more details on this

SAML security messages In this release, SAML is the communication protocol between the search appliance and the connector for user authentication an