BLOG: Web Content Management

Welcome to Oshyn’s Web Content Management Blog where our experts discuss the latest developments and best practices in the Content Management industry with a focus on several leading platforms: Drupal, EPiServer, Jahia, Open Text and Sitecore.

Open Text Web Solutions Delivery Server / LiveServer and Google Search Appliance (GSA)

Open Text Web Solutions Delivery Server / LiveServer and Google Search Appliance (GSA)

Marcelo Davalos... - Friday, February 26, 2010

Even though Live Server comes integrated with Verity as a search engine, it is possible to use Google Search Appliance (GSA) as a search engine on a Live Server site.

The Advantages we have for using GSA are:

  • Independent administration console.
  • User search familiarity.
  • Fast search engine with an inbox server.
  • Google custom searches and weights for pages.
  • Google technical support.

Now how would we pass the request to GSA.  First GSA lives in a separated server which will be connected to Live Server by, if possible, a gigabit infrastructure.

GSA is nothing more than a web application that gets http requests and based on the parameters returns an html or xml response.

Knowing this, to integrate GSA with Live server we will need to create a dynament which will include the xml response from GSA and then format with a traditional xslt similar to the ones we use for the rest of the site.

So in brief the steps to integrate GSA will be:

  1. 1.    Set up GSA and index the site (see GSA)
  1. 2.    Create a simple sample GSA http query and test; for instance we will search the word product and the query will be: http://192.168.1.10/search?q=product&output=xml&client=default_frontend&site=default_collection&filter=0
Note: For your query you will need to replace the ip address 192.168.1.10 to your GSA server ip address.  

  1. 3.    Copy the google.dtd file to the following location C:\Program Files\RedDot\LiveServer\tomcat\bin\google.dtd.  This file permits Live Server to process the xml response from Google.  Please note that we are considering the default installation of Live Server on a Windows Server

  1. 4.    Create a dynament like GSASearch.xml and include the following content:

<dynaments-GsaSearch>

<rde-dm:attribute mode="write" source="request" attribute="gsaHost" value="192.168.1.10" />

<rde-dm:include tag="generalResults"  content="http://[#request:gsaHost#]/search?q=[#request:param#].encode()&amp;output=xml&amp;client=default_frontend&amp;site=default_collection&amp;filter=0" rde-id="01"/>

</dynaments-GsaSearch >

  1. 5.    Test the dynament calling with the parameter param to see the results, for instance GSASearch.xml?param=product.  This should return the same result from step 2 but from a live server request.
  1. 6.    Create an xslt file to format the results from Google.
ajax rotator
Recent Posts

RSS feeds
Tag cloud
keyword selection concrete5 LDAP sitecore meetup Actionscript 3 social media VPP cms whitepaper web evolution Marketing Automation theming design patterns ipc SMM GSA php5 sitecore user group web marketing redundant database structure Active Directory RFP opentext integration optimization mobile new sites html open text cms los angeles Jahia ajax content mangement inbound marketing profile box geographical ajax push open text web solutions editing content LS url keywords website design los angeles reddot whitepaper profile tab code design content authoring content management los angeles css HubSpot sitecore online marketing suite, online marketing suite Database open source development cookie-free domain VB content management white paper Flash search engine project management cluster EPiServer WCM Design Patterns .net CRM Business Users release management lead management Ubercart lucene asp CMS Training content authors webcomponent liferay architecture presentation layer target dynament software design design open-source sitecore ECM web design los angeles mysql online marketing CMS usability oshyn Acquia Ubuntu Server php multisite ASP.NET spatial LiveServer Maven call to action configuration management linux lead generation data access modules IT Investment wcm APC boost marketing EPiServer Active Directory Live Server content management systems reddot white paper Velocity CMS higher education postgis web marketing for dummies VS2010 memcache multilingual SEO web2.0 E-commerce javascript sitecore email campaign manager jquery facebook app, OS 3.0, three20 google analytics patterns cms los angeles, content management los angeles, web development los angeles, website design los angeles, web design los angeles, sitecore meetup, sitecore user group sitecore oms open text cms cloud computing open text delivery server java consulting ui google rdbs licencing content management whitepaper web development los angeles tuckey drools mashups mashup mashware twitter reddot cms foursquare Visual Studio web content management plugin jquery, jquery plugin communicating campaigns sitecore devices templating scalability deployment search suggest social network geo ubuntu portlets thoughts print command line MVC google maps JSR-168 web3.0 reddot facebook developers Delivery Server CTA management open text management server sales 2.0 Dynamic Data jahia cms jahia wcm enterprise industry challenges Web development fbml cloud missing images friendly url template design icefaces portal oms social 2.0 tools facebook Solr reddot higher education IIS Sharepoint google search appliance OO Development iphone cms white paper frontend optimization Sitecore web services GIS web design reddot cms higher education AS3 ASP.NET MVC tuning Navigation Sitecore Active Directory Drupal location google appEngine dynament drush sitecore layout open text liveserver jsp performance Visual Basic
2010 Copyright Oshyn. All rights reserved.