Product DocsMenu

Pre-Loading a .NET Search Page to Prevent Display Delays

You can configure CES to continuously send wake up requests to a .NET search application. The purpose of this configuration is to keep the Coveo .NET search application alive in IIS and prevent a significant delay to display a .NET search page when the application has to be reloaded (see Why does the Initial .NET Search Page Take Much Longer to Appear?).

When you perform the first-time setup of a Coveo .NET Front-End search interface, this search page is automatically registered to be warmed up in the Pre-loading page of the Administration Tool (see Coveo .NET Front-End First Time Setup). You may still need to manually add a .NET search interface for pre-loading in some cases.

Examples:

  • When you use a Coveo JavaScript Search interface, the pre-loading configuration must be done manually.

  • When your Coveo .NET Front-End servers are accessed through a network load balancer (NLB), the first time setup adds the NLB URL. You need to manually add the URL of each front-end server.

The configuration schedules the CES service to send an HTTP GET request with a wake up query argument (&wakeup=1) to the search page URL every 60 seconds. The request warms up all skins of the /Web/Coveo/Skins folder on the Coveo Front-End server.

When your Coveo configuration includes more than one Front-End server in an NLB cluster or not, repeat the following procedure to enter the URL of each server, not the address of a NLB cluster. Similarly, when a Front-End server has more than one application serving search pages, repeat this procedure to enter the URL of each application.

Notes:

  • When you get error messages like the following: 

    An error occurred while warming up search page [URL]: class CGLNetwork::NetworkAccessDenied: The login information of server (SERVER NAME) is invalid.

    follow the procedure in this topic and ensure that you properly configure the Address and the Authentication parameters, or when the search page no longer exists, delete its address (see Removing a Pre-Loaded Search Page).

  • The search page warm up feature also triggers the tagging refresh processes that are often used in customer service solutions. Tags are fields that are populated with information gathered by post-indexing processes.

    When your customer solution takes advantage of tagging, you must set one search page to be warmed up to ensure that the tags remain up-to-date.

    When your Coveo instance includes more than one Front-End server, avoid warming up search pages from several servers as they will trigger duplicate tagging refresh processes that can waste Master server resources.

To pre-load a search page to prevent initial display delays

  1. On the Coveo server, access the Administration Tool (see Opening the Administration Tool).

  2. Click the Configuration tab, and then click the Pre-loading menu.

  3. In the Pre-loading page, click Add.

  4. In the Edit Search Page page:

    1. In the Name box, enter a name describing the search page that you want to automatically warm up.

      This name only appears in the Pre-loading page.

    2. In the Address box, enter the URL of one search that you want to automatically warm up. Ensure to enter a URL that the Back-End server can resolve.

      Examples:

      • Enter the URL of your default Coveo web search page: https://Coveo.MyOrganization.com/Default.aspx

      • Enter the URL of a search page on a SharePoint server: https://intranet.mycompany.com/CoveoSearch.aspx

      • When Coveo .NET Front-End and Coveo Enterprise Search are installed on different servers, do not use http://localhost:8080, because the page is not available from the Back-End server.

    3. When the search page cannot be accessed anonymously, in Authentication, select a user identity that has access to the search page.

      Note: If the password of this account changes, you must update the password in the user identity to prevent warm up errors.

      You can modify an existing user identity or create a new one respectively by clicking Edit or Add (see Adding a User Identity).

    4. Click Test Search Page to validate the connection to the search page.

      When the connection cannot be established, modify your settings and test again.

    5. When the connection is successful, click Apply Changes.

Removing a Pre-Loaded Search Page

  1. On the Coveo server, access the Administration Tool (see Opening the Administration Tool).

  2. Click the Configuration tab, and then click the Pre-loading menu.

  3. In the Pre-loading page, under Pre-loading, select the check box of the search page for which you want to stop the warm up, and then click Delete.

    Note: When your customer solution takes advantage of tagging, ensure to leave one search page to be warmed up so that the tags remain up-to-date.

People who viewed this topic also viewed