Skip to main content
Compatible with Fusion version: 4.0.0 through 5.12.0
The Web V1 connector discovers pages through links such as href attributes and sitemaps up to your configured depth, then indexes those pages.
V1 deprecation and removal noticeStarting in Fusion 5.12.0, all V1 connectors are deprecated. This means they are no longer being actively developed and will be removed in Fusion 5.13.0.The replacement for this connector is the Web V2 connector.If you are using this connector, you must migrate to the replacement connector or a supported alternative before upgrading to Fusion 5.13.0. We recommend migrating to the replacement connector as soon as possible to avoid any disruption to your workflows.
If you migrate to the Web V2 connector instead of the Web V1 connector, you’ll get better Java SDK-based performance, distributed fetching, upgrades to the plugin as new versions are released, and built-in OAuth token support. Fusion 5.x uses the Open Graph Protocol metadata such as og:title and og:description as the default configuration for fields. Deviation from that standard configuration may exclude information from indexing during the crawl.

​
Prerequisites

Perform these prerequisites to ensure the connector can reliably access, crawl, and index your data. Proper setup helps avoid configuration or permission errors, so use the following guidelines to keep your content available for discovery and search in Fusion. Network connectivity requires that your Fusion server or remote connector host be able to reach the target site over HTTP/HTTPS on the required ports.

​
Authentication

Setting up the correct authentication according to your organization’s data governance policies helps keep sensitive data secure while allowing authorized indexing. The Web V1 connector supports many HTTP-level authentication methods. You configure these under Crawl Authentication Properties in your datasource. The supported authentication schemes include the following:
  • Basic HTTP Authentication: Provide host, port, realm (if any), username, and password.
  • Digest HTTP Authentication: Same parameters as Basic, but using the Digest challenge/response scheme.
  • Form Authentication: Post to a login form URL with whatever name/value pairs the site expects, plus a TTL for the session.
  • SAML/Smart Form Authentication: For multi-step or SAML-backed form logins, submit a sequence of forms until you’re authenticated.
  • NTLM Authentication for Windows-style authentication: Provide domain, workstation, host, port, realm (if any), username, and password.
Once you’ve picked your scheme, Fusion will maintain cookies and session state automatically for the duration of the crawl.

​
Crawl options

  • If you’re crawling a website protected by a login or SmartForm, see Crawl an Authenticated Website with the Web Connector.
  • If you’re crawling a CMS or ecommerce site, you may want to Deduplicate Web Content using Canonical Tags.
  • To prevent unbounded crawls or to only crawl a portion of your website, see Limit the Crawl Scope for Web Sites.
This article explains how to use the Web V1 connector to crawl a website that is protected by SSO, SAML, or OAuth.

​
Overview

This example uses SharePoint Online, a website that uses the Microsoft identity platform.To crawl a website behind a login, configure the Web connector to authenticate with valid login credentials. In this example, there is also a final prompt to stay signed in. Configure the connector to use the SAML/Smart Form authentication method.Microsoft sign inThe Microsoft identity platform also requires JavaScript to authenticate, which means you must also configure the connector to use JavaScript Evaluation.

​
Prerequisites

Before you can configure the Web connector, you must locate and copy the login parameters from the website you’re trying to crawl.
  1. Open a private or incognito window in your internet browser. This example uses Google Chrome.
  2. Navigate to the site that you want to crawl with authentication.
  3. Identify the URL for the login page. For example, from http://some-website-with-auth.com, navigate to the page that displays the login form, then copy the page URL, such as http://some-website-with-auth.com/sso/login. Use this URL as the value of the loginUrl parameter (URL in the Fusion UI).
  4. On the login page, identify the fields used for inputting the username and password. You can do this by right-clicking on the form fields and selecting Inspect element to open the developer tools, where the corresponding HTML element is highlighted. In most cases it is an <input> element that has a name attribute and you can specify the field as this name value. For example: 
    <input id="resolving_input" name="login" class="signin-textfield" autocorrect="off" autocapitalize="off" type="text">
  5. Add the username field as a parameter to the authentication section of the Web connector. The Property Name is login and the Property Value is the username the connector will use to log in.
  6. Add the password field name as the passwordParamName (Password Parameter in the Fusion UI).
  7. On the site login page, right-click Submit (or equivalent) and select Inspect element.
    • If the button is an <input type="submit"/>, then the SmartForm login picks it up automatically.
    • If the button is another element (such as <button>, <a>, <div>, and so on) then you must add a parameter with the special prefix ::submitButtonXPath::, then add an XPath expression that points to the submit button. For example: ::submitButtonXPath:://button[@name='loginButton']
  8. If there is no name attribute on the <input> elements, then you must specify a parameter to tell the Web connector how to find the input element. You can use any of these special selector formats for the parameter name: 
    ;;BY_XPATH;;//input[@id='someId']
;;BY_ID;;someid
;;BY_NAME;;somename
;;BY_CLASS_NAME;;someCssClassName
;;BY_CSS_SELECTOR;;.div#selector
Sometimes your web page asks you a random question, such as What is the name of your first dog?In this case add another special parameter:
::WhenXPath::XPath of element to check against::Either @attributeToCheckAgainst or text to check against the text of the element::Value To Match::Field selector to set the value of only if the conditional check matched
Here is an example of three different parameters where your site might ask one of three questions randomly:
::WhenXPath:://div[@tag='Your question']::text::What is the name of your first dog?::;;BY_ID;;answer
::WhenXPath:://div[@tag='Your question']::text::In what city were you born?::;;BY_ID;;answer
::WhenXPath:://input[@id='Your question']::@value::In what city were you born?::;;BY_ID;;answer

​
Configure Web connector

Configure the connector to use login credentials and JavaScript to successfully authenticate through your website.
  1. In Fusion, navigate to Indexing > Datasources.
  2. Click Add, then select Web (v1) (in Fusion 5.12, select Web (Deprecated)) from the dropdown.
  3. Configure the datasource and fill in required fields.
  4. Expand Crawl Authorization, scroll down to SAML/Smart Form Authentication, then click Add.
    1. Enter the URL of the website that requires authentication.
    2. Enter the password to use for the authentication request.
    3. Set the TTL (ms) so there is enough time to load the form pieces on the page before Fusion attempts to run the Smart Form step.
    4. Add Parameters as needed. For example, if the login page requires you to enter your name in addition to a password, add a parameter, specifying the Property Name and Property Value. Add a parameter for every required field on the login page. SAML authentication
    5. If applicable, create a SAML/Smart Form Authentication for every subsequent login page. These steps trigger from top to bottom.
  5. Expand the JavaScript Evaluation section and enable Evaluate JavaScript during SmartForm Authentication. Enable Evaluate Javascript if you would like to use a JavaScript evaluation engine for all requests, not just the authentication. JavaScript Evaluation
You can find the Property Name and Property Value for any given step on the login page. Use your browser’s Developer Tools to inspect the input field, then copy the XPath.

​
Install Chromium dependencies (Fusion 4.x only)

This section only applies to 4.x.x releases. For 5.x.x releases, Chrome dependencies are already installed in the Docker container.
To enable high-performance JavaScript evaluation, you must install some dependencies, then set f.crawlJS/“Evaluate JavaScript” and f.useHighPerfJsEval/“High Performance Mode” to “true”.Enable high-performance mode with Chromium
  1. Install the dependencies, using one of the scripts packaged with Fusion:
    • Windows: https://FUSION_HOST:FUSION_PORT/bin/install-high-perf-web-deps.ps1
    • Linux and OSX: https://FUSION_HOST:FUSION_PORT/bin/install-high-perf-web-deps.sh
    When the script finishes a confirmation message displays: 
    Successfully installed high-performance JS eval mode dependencies for Lucidworks Fusion web connector.
  2. In the Fusion UI, configure your Web data source:
    1. Set Evaluate Javascript to “true”.
    2. Set High Performance Mode to “true”.
    An additional f.headlessBrowser parameter can be set to “false” to display the browser windows during processing. It is “true” by default. Non-headless mode is available only using the “High-performance” mode.
  3. Save the datasource configuration.
If Fusion is running on Docker, you must either mount an shm directory using the argument -v /dev/shm:/dev/shm or use the flag --shm-size=2g to use the host’s shared memory. The default shm size 64m will result in failing crawls with logs showing error messages like org.openqa.selenium.WebDriverException: Failed to decode response from marionette. See Geckodriver issue 1193 for more details.

​
Test the configuration

  1. In Fusion, navigate to Indexing > Datasources.
  2. Click on the web connector you configured.
  3. Set your Fetch Threads and Emit Threads. It simplifies testing when only one thread is trying to authenticate at a time.
    1. Expand Crawl Performance.
    2. Set Fetch Threads and Emit Threads to 1.
  4. Enable Diagnostic logging. Diagnostic mode will allow the HTML contents to print out in the logs for each step of the log on process, so you can use that to see what the browser doing. This can be useful because you can see where the browser was when/if you got into a bad state.
    1. Toggle Advanced to view advanced settings.
    2. Enable Diagnostic mode.
  5. Headless mode (Fusion 4.x only). If you are on a Windows Server or have the ability to install Fusion somewhere an active desktop environment is available, such as Mac or Linux with Desktop, you can use headless mode = false to test with an actual web browser.
    1. Expand JavaScript Evaluation.
    2. Disable Headless Browser.
    3. When you run the crawl, a browser window opens and performs the log in process.
  6. Click Run to start the datasource job. Review results in the Query Workbench.
The Web V1 connector retrieves data from a Web site using HTTP and starting from a specified URL.In content management and online shopping systems, it is common for the same content to be accessed through multiple URLs. Content syndication helps you distribute content to different URLs and domains, consolidate link signals for the duplicate or similar content, and track metrics for a single product or topic. But it creates some challenges when people use search engines to reach your page.The Fusion Web connector can leverage canonical meta tags in your website’s HTML to deduplicate web pages.
  1. When configuring your Web datasource, toggle Advanced at the top of the page.
  2. Under Dedupe, click Dedupe documents.
  3. Make sure Deduplication via canonical tag is checked.
The Web V1 connector retrieves data from a Web site using HTTP and starting from a specified URL.The connector works by going to the seed page (the startURIs specified in the configuration form), collecting the content for indexing, and extracting any links to other pages. It then follows those links to collect content on other pages, extracting links to those pages, and so on.When creating a Web data source, pay attention to the Max crawl depth and Restrict To Tree parameters (c.depth and c.restrictToTree in the REST API). These properties limit the scope of your crawl to prevent an unbounded crawl that could continue for a long time, particularly if you are crawling a site with links to many pages outside the main site. An unbounded crawl can also cause memory errors in your system.The connector keeps track of URIs it has seen, and many of the properties relate to managing the resulting database of entries. If the connector finds a standard redirect, it tracks that the redirected URI has an alias, and does not re-evaluate the URI on its next runs until the alias expiration has passed. If deduplication is enabled, documents that were found to be duplicates are also added to the alias list and are not re-evaluated until the alias expiration has passed.Regular expressions can be used to restrict the crawl either by defining URI patterns that should be followed or URI patterns that should not be followed.Additionally, specific patterns of the URI can be defined to define URIs that should not be followed.
The sitemap_incremental_crawling configuration parameter processes and crawls URLs found in the sitemap. Set to true to remove documents from the index when they can no longer be accessed as unique documents. For example, if the page is removed from the sitemap and cannot be accessed. In addition, if the page is not in the sitemap, the connector classifies the missing page as unbounded and removes the page from the index.

​
Learn more

The Web V1 connector retrieves data from a Web site using HTTP and starting from a specified URL.You can optionally add custom headers to all http get requests from the Web connector. For example, you might want to add a header that includes Connection: keep-alive to prevent the connector from timing out while crawling your Web site.To add a custom header, use the configuration parameter f.addedHeaders. To send multiple headers, use the following format:
Header1: Value1
Header2: Value2
  1. Click Indexing > Datasources.
  2. Click Add+, then Web.
  3. Enter a datasource ID and a start link.
  4. Click Link discovery.
  5. Fill in the Headers to add to HTTP requests field.
    • Add each header in the format HeaderName: HeaderValue.
    • To add multiple headers to all HTTP requests, put each header on a new line.
  6. Fill in any remaining options to configure the datasource.
  7. Click Save.
JavaScript-enabled web sites require a different crawling configuration than plain HTML web sites do.

​
Enable JavaScript evaluation

To enable JavaScript evaluation, set the f.crawlJS/“Evaluate Javascript” parameter to “true”. When this option is enabled, the connector crawls links rendered from JavaScript evaluation, using a headless browser by default (see below).JavaScript evaluation is fastest when using High Performance JavaScript Evaluation mode, which uses the Chromium browser with the Web connector. There is also a High Performance Mode parameter, which uses the Chromium web browser to crawl web sites.How is “High performance JavaScript evaluation” different than the non-high performance mode? In high performance mode, the following are true:
  • JavaScript evaluation is faster.
  • JavaScript evaluated content is more accurate.
  • You can run in “non-headless” mode to watch the browser crawl your content on a desktop, for debugging purposes.
  • You can save screenshots of pages and index them as base64 along with your other web page content.
  • The process uses more RAM.
  • The process uses more CPU.

​
Dependencies for High Performance JavaScript Evaluation

IMPORTANT: This section only applies to 4.x.x releases. For 5.x.x releases, Chrome dependencies are already installed in the Docker container.To enable high-performance JavaScript evaluation, you must install some dependencies, then set f.crawlJS/“Evaluate JavaScript” and f.useHighPerfJsEval/“High Performance Mode” to “true”.Enable high-performance mode with Chromium
  1. Install the dependencies, using one of the scripts packaged with Fusion:
    • Windows: https://FUSION_HOST:FUSION_PORT/bin/install-high-perf-web-deps.ps1
    • Linux and OSX: https://FUSION_HOST:FUSION_PORT/bin/install-high-perf-web-deps.sh
    When the script finishes a confirmation message displays: 
    Successfully installed high-performance JS eval mode dependencies for Lucidworks Fusion web connector.
  2. In the Fusion UI, configure your Web data source:
    1. Set Evaluate Javascript to “true”.
    2. Set High Performance Mode to “true”.
    An additional f.headlessBrowser parameter can be set to “false” to display the browser windows during processing. It is “true” by default. Non-headless mode is available only using the “High-performance” mode.
  3. Save the datasource configuration.
If Fusion is running on Docker, you must either mount an shm directory using the argument -v /dev/shm:/dev/shm or use the flag --shm-size=2g to use the host’s shared memory. The default shm size 64m will result in failing crawls with logs showing error messages like org.openqa.selenium.WebDriverException: Failed to decode response from marionette. See Geckodriver issue 1193 for more details.

​
Screenshots with High Performance Mode

To enable screenshots, configure these parameters:
  • f.takeScreenshot - Enable screenshots. Default: false.
  • f.screenshotFullscreen - Take full-screen screenshots. Default: false.
These additional viewport parameters exist mainly to support screenshots, but the viewport settings can also affect the overall output:
  • f.viewportWidth - View port width in pixels. Default: 800.
  • f.viewportHeight - View port height in pixels. Default: 600.
  • f.deviceScreenFactor - Device screen factor. Default: 1 (no scaling). See the Android Screen compatibility overview for a description about device displays.
  • f.simulateMobile - (advanced property) Tell the browser to “emulate” a mobile browser. Default: false.
  • f.mobileScreenWidth - (advanced property) Only applicable with f.simulateMobile. Sets the screen width in pixels.
  • f.mobileScreenHeight - (advanced property) Only applicable with f.simulateMobile. Sets the screen height in pixels.

​
Authentication with JavaScript Evaluation

To use authentication when JavaScript evaluation is enabled, use the SmartForm (SAML) option because it can log in to a web site like a typical browser user.SmartForm login functionality is more powerful when JavaScript evaluation is enabled:
  • You can perform login on forms that might be JavaScript rendered.
  • You can use a variety of HTML selectors to find the elements to enter as login information. By contrast, when JavaScript evaluation is disabled, you can only provide inputs using the name attribute of <input> elements.
Configure authentication for JavaScript-enabled crawling
  1. Open a private or incognito window in your internet browser. This example uses Google Chrome.
  2. Navigate to the site that you want to crawl with authentication.
  3. Identify the URL for the login page. For example, from http://some-website-with-auth.com, navigate to the page that displays the login form, then copy the page URL, such as http://some-website-with-auth.com/sso/login. Use this URL as the value of the loginUrl parameter (URL in the Fusion UI).
  4. On the login page, identify the fields used for inputting the username and password. You can do this by right-clicking on the form fields and selecting Inspect element to open the developer tools, where the corresponding HTML element is highlighted. In most cases it is an <input> element that has a name attribute and you can specify the field as this name value. For example: 
    <input id="resolving_input" name="login" class="signin-textfield" autocorrect="off" autocapitalize="off" type="text">
  5. Add the username field as a parameter to the authentication section of the Web connector. The Property Name is login and the Property Value is the username the connector will use to log in.
  6. Add the password field name as the passwordParamName (Password Parameter in the Fusion UI).
  7. On the site login page, right-click Submit (or equivalent) and select Inspect element.
    • If the button is an <input type="submit"/>, then the SmartForm login picks it up automatically.
    • If the button is another element (such as <button>, <a>, <div>, and so on) then you must add a parameter with the special prefix ::submitButtonXPath::, then add an XPath expression that points to the submit button. For example: ::submitButtonXPath:://button[@name='loginButton']
  8. If there is no name attribute on the <input> elements, then you must specify a parameter to tell the Web connector how to find the input element. You can use any of these special selector formats for the parameter name: 
    ;;BY_XPATH;;//input[@id='someId']
;;BY_ID;;someid
;;BY_NAME;;somename
;;BY_CLASS_NAME;;someCssClassName
;;BY_CSS_SELECTOR;;.div#selector
Sometimes your web page asks you a random question, such as What is the name of your first dog?In this case add another special parameter:
::WhenXPath::XPath of element to check against::Either @attributeToCheckAgainst or text to check against the text of the element::Value To Match::Field selector to set the value of only if the conditional check matched
Here is an example of three different parameters where your site might ask one of three questions randomly:
::WhenXPath:://div[@tag='Your question']::text::What is the name of your first dog?::;;BY_ID;;answer
::WhenXPath:://div[@tag='Your question']::text::In what city were you born?::;;BY_ID;;answer
::WhenXPath:://input[@id='Your question']::@value::In what city were you born?::;;BY_ID;;answer

​
Debug the JavaScript Evaluation Stage using Non-headless Chromium

When testing the Web connector with Chromium, it helps to access Fusion through a GUI-enabled browser. Configure a Web data source with your website, enable advanced mode, set the Crawl Performance > Fetch Threads to 1, and uncheck Javascript Evaluation > Headless Browser.This results in the Web fetcher using a single instance of Chromium in a window where you can see the fetch documents. This is helpful if you are getting an unexpected result from the Chromium evaluation stage.
The Web V1 connector retrieves data from a Web site using HTTP and starting from a specified URL.The connector supports several approaches to extracting and filtering content from pages. When analyzing the HTML of a page, the connector can specifically include or exclude elements based on the HTML tag, the tag ID, or the tag class (such as a div tag, or the #content tag ID).Specific tags can be selected to become fields of the document if needed. For example, all content from <h1> tags can be pulled into an h1 field, and with field mapping be transformed into document titles.For other advanced capabilities, you can use jsoup selectors to find elements in the content to include or exclude from the content.While field mapping is generally a function of the index pipeline, you can define some initial mappings to occur during the crawl. The “initial mappings” property for each web datasource is predefined with three mappings: to move fetchedDates to a fetchedDates_dts field, to move lastModified to a lastModified_dt field, and to move length to a length_l field.Finally, the crawler can deduplicate crawled content. You can define a specific field to use for this deduplication (such as title, or another field), or you can use the full raw content as the default. In the Fusion UI, when you are defining your datasource, toggle Advanced to access the Dedupe settings.
The Web V1 connector retrieves data from a Web site using HTTP and starting from a specified URL.Crawling sitemaps is supported. Simply add the URL(s) of the sitemap to the f.sitemapURLs property (Sitemap URLs in the UI) and all of the URLs found in a sitemap are added to the list of URLs to crawl. Sitemap indexes (that is, a sitemap that points to other sitemaps) are also supported. The URLs found through each sitemap are added to the list of URLs to crawl.To configure your datasource to crawl only the sitemap file, add the sitemap URL to both the startLinks property (because that is a required property for a datasource) and also to the f.sitemapsURL property so it is properly treated as a sitemap by the connector when it starts.

​
Incremental crawls and deleted documents

Crawling a website with a sitemap.xml adds the links in the sitemap to crawlDB.To remove deleted documents during reindexing, you must remove the links from the sitemap.xml.The Datasources API contains information on how to work with crawlDB and removing items.

​
Diagnostic logging

Diagnostic logging allows the HTML contents to print out in the logs for each step of the crawl, so you can use that to see what the browser is doing. This can be useful because you can see the browser’s state if any part of a crawl fails.To enable diagnostic logging:
  1. Open the Web connector.
  2. Toggle Advanced. You should now see new fields become active next to Cookie Spec.
  3. Select Diagnostic mode.
This article describes how to crawl REST API endpoints associated with Web connectors using Fusion.Before crawling a REST API endpoint, the following prerequisites must be met:
  • All endpoints are available using bulk start links or a sitemap
  • The response data is in a parseable format (JSON, XML, etc.)

​
Options

If you have a small number of endpoints you want to crawl, enter each endpoint as a bulk start link.To crawl the API endpoints using bulk start links:
  1. Add a new Web connector datasource. To learn how to configure a new datasource, see Configure a New Datasource.
  2. Under Start links, enter the main domain that contains the sitemap. For example, http://www.restapiendpoint.com.
  3. In the Link discovery section under Bulk Start Links, enter the URLs you want to crawl. Separate links with a new line. For example: 
    http://www.restapiendpoint.com/?apikey=user-token&amp;s=dark%20knight&amp;type=movie&amp;page=1
http://www.restapiendpoint.com/?apikey=user-token&amp;s=superman&amp;type=movie&amp;page=1
http://www.restapiendpoint.com/?apikey=user-token&amp;s=superman&amp;type=movie&amp;page=2
  4. Save and run the job.
  5. Once complete, check the results in the Index Workbench. Web connector configuration using start links

​
Using a sitemap

If you have a large number of endpoints you want to crawl, use a sitemap containing the API endpoint locations. This is also helpful if someone without access to Fusion maintains the list of endpoint URLs. An example sitemap:
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
    <url>
        <loc>http://www.restapiendpoint.com/?apikey=user-token&amp;s=dark%20knight&amp;type=movie&amp;page=1</loc>
        <lastmod>2021-07-21</lastmod>
        <changefreq>daily</changefreq>
        <priority>0.8</priority>
    </url>
    <url>
        <loc>http://www.restapiendpoint.com/?apikey=user-token&amp;s=superman&amp;type=movie&amp;page=1</loc>
        <lastmod>2021-07-21</lastmod>
        <changefreq>daily</changefreq>
        <priority>0.8</priority>
    </url>
    <url>
        <loc>http://www.restapiendpoint.com/?apikey=user-token&amp;s=superman&amp;type=movie&amp;page=2</loc>
        <lastmod>2021-07-21</lastmod>
        <changefreq>daily</changefreq>
        <priority>0.8</priority>
    </url>
    <url>
        <loc>http://www.restapiendpoint.com/?apikey=user-token&amp;s=superman&amp;type=movie&amp;page=3</loc>
        <lastmod>2021-07-21</lastmod>
        <changefreq>daily</changefreq>
        <priority>0.8</priority>
    </url>
    <url>
        <loc>http://www.restapiendpoint.com/?apikey=user-token&amp;s=batman&amp;type=movie&amp;page=1</loc>
        <lastmod>2021-07-21</lastmod>
        <changefreq>daily</changefreq>
        <priority>0.8</priority>
    </url>
</urlset>
To crawl the API endpoints using the sitemap:
  1. Add a new Web connector datasource. To learn how to configure a new datasource, see Configure a New Datasource.
  2. Under Start links, enter the main domain that contains the sitemap. For example, http://www.restapiendpoint.com.
  3. In the Link discovery section under Sitemap URLs, click the Add button.
  4. Enter the URL of the sitemap. For example, http://www.restapiendpoint.com/sitemap.xml.
  5. Save and run the job.
  6. Once complete, check the results in the Index Workbench. Web connector configuration using sitemap

​
Results

Both options above achieve the same result. Fusion indexes the JSON response provided at the endpoints. If an array of JSON objects is available, Fusion indexes each object and an individual document.For example, Fusion creates three documents from the JSON response below:
{
    "Search": [{
        "Title": "Batman v Superman: Dawn of Justice",
        "Year": "2016",
        "imdbID": "tt2975590",
        "Type": "movie",
        "Poster": "https://m.media-amazon.com/images/M/MV5BYThjYzcyYzItNTVjNy00NDk0LTgwMWQtYjMwNmNlNWJhMzMyXkEyXkFqcGdeQXVyMTQxNzMzNDI@._V1_SX300.jpg"
    }, {
        "Title": "Superman Returns",
        "Year": "2006",
        "imdbID": "tt0348150",
        "Type": "movie",
        "Poster": "https://m.media-amazon.com/images/M/MV5BNzY2ZDQ2MTctYzlhOC00MWJhLTgxMmItMDgzNDQwMDdhOWI2XkEyXkFqcGdeQXVyNjc1NTYyMjg@._V1_SX300.jpg"
    }, {
        "Title": "Superman",
        "Year": "1978",
        "imdbID": "tt0078346",
        "Type": "movie",
        "Poster": "https://m.media-amazon.com/images/M/MV5BMzA0YWMwMTUtMTVhNC00NjRkLWE2ZTgtOWEzNjJhYzNiMTlkXkEyXkFqcGdeQXVyNjc1NTYyMjg@._V1_SX300.jpg"
    }],
    "totalResults": "3",
    "Response": "True"
}

​
chromeBinaryPath values

If Google Chrome was installed via package installation manager, specify the Chrome binary in the chromeBinaryPath. Example locations are /usr/bin/google-chrome or /path/to/customlocation/of/google-chrome.For RHEL builds, run:
wget https://dl.google.com/linux/direct/google-chrome-stable_current_x86_64.rpm
yum -y install redhat-lsb libXScrnSaver
yum -y localinstall google-chrome-stable_current_x86_64.rpm
Then use which google-chrome to find where it installs and use that in the chromeBinaryPath.

​
Troubleshooting Chrome binary errors

Steps to verify:
  • Make sure Chrome is installed properly on the system and google-chrome --version returns successfully.
  • If a custom Chrome binary path is set in the datasource configuration, make sure is it valid.
  • If bundled Chromium is used, where is it located? The Chrome install script puts it inside var/connectors/connectors-classic/chrome-linux, but Fusion looks for it inside var/connectors/connectors-classic/chrome-linux64.
  • Ensure proper permissions are set for the Fusion user.
  • If running Fusion locally, try unchecking the Headless Browser option. This allows Chrome to open to the page the crawler is indexing and lets you know that Chrome is being reached by Fusion.

​
Configuration

When entering configuration values in the UI, use unescaped characters, such as \t for the tab character. When entering configuration values in the API, use escaped characters, such as \\t for the tab character.
If you experience CrawlDB errors such as “File is already opened and is locked”, then raise the Alias Expiration setting.
⌘I