Google Search Appliance User Experience Guide Instrukcja Użytkownika Strona 29

  • Pobierz
  • Dodaj do moich podręczników
  • Drukuj
  • Strona
    / 31
  • Spis treści
  • BOOKMARKI
  • Oceniono. / 5. Na podstawie oceny klientów
Przeglądanie stron 28
29
Appendix More Information
Technical solutions for common challenges
This appendix presents some technical solutions for common challenges in the following areas of search
appliance deployment.
Interfaces and Front End Customization
Document Relevancy
Interfaces and Front End Customization
I just changed my front end but when I view my results, they still show the old one. What is
wrong?
A front end will only reload itself into memory every 15 minutes (or even longer). Therefore, in
order to force a reload of the front end, you must use the parameter proxyreload=1 in the
query URL at least once after the style sheet has been modified. This parameter should only be
used for a refresh during development and not in production, as it negatively impacts the
performance of the Google Search Appliance.
How can I give developers access to the front end so that they can make changes without being
able to affect my KeyMatches, and so on?
You can create two front ends, using some naming convention. For example, use the one called
"my_frontend" to manage KeyMatches, related queries, filters, remove URLs, and OneBoxes
(collectively known as "client"). Then create another one called "my_frontend_ss" to manage
the user interface (or output as it is denoted in the Admin Console), which is referred to as
"proxystylesheet."
Give the UI developer access to "my_frontend_ss" only so they can update their style sheet
there.
Retain control over "my_frontend" where user's search experience is managed by a non-UI
developer.
Make a modification to the application so it uses two front ends:
client=my_frontend&proxystylesheet=my_frontend_ss. By default, it would be
client=my_frontend&proxystylesheet=my_frontend.
How can I reuse some Front End configuration?
If you want to use most configurations in a front end for different user interfaces, while you want
to have different options for query expansion policies and/or result biasing policies, do not create
multiple front ends for this. Use entqr and entsp instead.
Przeglądanie stron 28
1 2 ... 24 25 26 27 28 29 30 31

Komentarze do niniejszej Instrukcji

Brak uwag