Federate Search - Configuring Google

Products

• SUPPORT AUTOMATION- SERVER
• CA Service Desk Manager - Unified Self Service
• KNOWLEDGE TOOLS
• CA Service Management - Asset Portfolio Management
• CA Service Management - Service Desk Manager

Issue/Introduction

Federate Search is usually configured to utilize SharePoint. If you need to configure Google as the default one needs to follow slightly different instructions.

How do I configure Federate Search to utilize Google instead of SharePoint?

Environment

Release: SDMU0M99000-14.1-Service Desk Manager-Full License
Component:

Resolution

1.   Verify what Custom Google search engines you have via this URL: https://cse.google.com/cse/all


2.   You can get (create) a Custom Search Engine from Google - by accessing: https://cse.google.com/cse/create/new 

- create a custom search engine
- in the Basics tab -> Details -> Search engine ID button reveals the Search Engine ID value
- This is what you need in the C:\Program Files (x86)\CA\Service Desk Manager\samples\cafedsearch\adapters.properties file's google_googleCx field's value:

#Start of Google configuration parameters

google_googleCx=

Note: its of format: 1234213123231232:abcdef1234

 

3.   Next step is to get a google API key. To get a search API key go to: https://developers.google.com/custom-search/json-api/v1/overview 

- get a key, normally you get prompted for a project name followed by enabling a key that you copy/paste.
(see what projects/APIs you have: https://console.developers.google.com/apis/dashboard )

- The key you obtain above goes to: C:\Program Files (x86)\CA\Service Desk Manager\samples\cafedsearch\adapters.properties file's google_googleApiKey field's value:

google_googleApiKey=
Note: APIKey is of format: abcd1234xyz1234def

4.   Once you have done this, you need to follow rest of the steps:

https://docops.ca.com/ca-service-management/14-1/en/using/knowledge-management/integrating-multiple-search-engines-using-federated-search/how-to-configure-federated-search

5.   NX_ROOT/bin/fs_adapters_cli -i -k Google -b GoogleSearchAdapter -t "google-tmpl.xml" -o "google.xml"


6.   Check: $NXROOT\log\jfedsearch.log for any errors

7.   Copy C:\Program Files (x86)\CA\Service Desk Manager\samples\cafedsearch\adapters-config.xml and google.xml to the following CA SDM directory:

$NX_ROOT\bopcfg\www\CATALINA_BASE_FS\webapps\cafedsearch\WEB-INF


8.   Restart the Federated Search Tomcat instance:

pdm_tomcat_nxd - c STOP - t FS

Wait for 1 minute

pdm_tomcat_nxd - c START - t FS

 

 

9.    Verify and check the error log files in $NX_ROOT\log\jfedsearch.log

10.   Try to do your search now, if you continue to face the same problem, here's what is recommended 

a) $NX_ROOT\bopcfg\www\CATALINA_BASE_FS\webapps\cafedsearch\WEB-INF\log4j.properties
b) look for log4j.rootCategory=info, jfedsearch
c) change it to log4j.rootCategory=debug, jfedsearch
d) save the file and restart tomcat

pdm_tomcat_nxd - c STOP - t FS

Wait for 1 minute

pdm_tomcat_nxd - c START - t FS

11.   Reproduce the issue and send CA Support the following: $NX_ROOT\log\jfedsearch.log