Moving Open Text Delivery Server to Common Search

As part of the small team behind the Solution Exchange, I was somewhat dreading the day when I had to change the internal search engine over to Open Text Common Search on the Web Site Management Delivery Server.

However, in absolute honesty, this was not the issue of complex configuration that I was expecting and I will explain the steps I took.

The Delivery Server Common Search Connector

  1. The first step is to install the Open Text Common Search product.  I was fortunate enough to have this already in our infrastructure so didn’t need to do this step.
  2. Assuming the Common Search is installed, you can log into Delivery Server, navigate to connectors > Search Engines > Administer and click the import button.  Version 10.1 of Delivery Server has a pre-configured connector that you can use.  Click the OTCommonSearch link to import the connector.
  3. Change the URL of the Common Search Server to the IP of your Common Search machine.
  4. Change the “Incoming directory of indexing jobs” to a shared folder.  This is a path as seen by the Delivery Server.  I’ve chosen to place this on the local machine of the Delivery Server and share that with the Common Search machine.
  5. Change the “Incoming directory of Common Search server” to point to the same directory as above but from the perspective of the Common Search machine.  I initially had problems here as the Delivery Server and Common Search were on different Domains.  We changed this anyhow to reflect better practice in our setup.
  6. Create the shared folder if you haven’t already and make sure both the Delivery Server and Common Search have read/write access.
  7. You’re done!

It was really that easy! (well, if I discount the delays due to not being able to share directories effectively across Windows Domains at first).

Finally, it is worth pointing out the tweaks I made to my queries for the new Search Engine.

When searching specific groups, you can now use the syntax:

group:<ds_group_name>

and

attributeName:'[#request:attributeExample#]'

for attributes.

Admittedly, I didn’t need to do anything more complex than this so there were not a lot of queries to change.

There may be more complex example out there but the key message is to start planning your changeover now as it might just be easier than you think!

As always, please leave your questions or comments.

8 thoughts on “Moving Open Text Delivery Server to Common Search

  1. Herdy

    Thanks for the post, very useful. I was wondering if you can do a follow up post on the administrative side of OTCS, e.g. how to trigger the indexing, basic troubleshooting process, notable OTCS features…

    Reply
  2. Danny Baggs

    Hi Herdy,

    Thanks for the comment. Are you referring to some guidance on the pure OTCS interface and setting that up or something more specific with the integration that this post is about?

    If the former, I’ll try and encourage some of my colleague to comment here.

    Regards,

    Dan

    Reply
  3. Herdy

    More specific to the integration actually. When I went through the DS training (June 2010), we learnt about the things I mention: triggering index etc. using the Verity search engine.

    Reply
  4. Pingback: Troubleshooting Common Search with Delivery Server [Best Practice Project] « Miss Integration

  5. Mark Yuan

    With Common Search, how do you get more detail in the search results for PDF files? We’re basically getting just the filename, no document title, no first few lines of content. In other words, nothing like the results from an HTML page.

    Reply
    1. Danny Baggs

      Hi Mark,

      I have to say that I’m not too experienced on this subject apart from the basic configuration that I did and reported in this post. For further details and questions, I would encourage you to take part within our online community platform Solution Exchange and perhaps register and post your question in the forum – http://www.solutionexchange.info/forum.htm

      Regards,

      Dan

      Reply
  6. Joo

    Hi,

    We have recently migrated our search function from K2 Verity to Open Text Common Search. One challenge we are having now is tunning relevancy of the search result.

    It seems like tunning the search relevancy is related with doing some configuration in the live link admin – ie: ranking.

    I posed this question in solutionexchange.info, but I haven’t heard from anyone yet.

    Can you please advise me on tunning/configuring search relevancy?

    Hope to hear from you.

    Joo

    Reply

Leave a Reply to Mike Unwalla Cancel reply

Your email address will not be published. Required fields are marked *