Skip to main content

Successfully installed and implemented Google Mini

Google Mini is Google's integrated hardware and software solution to index your organization's digital assets. You can learn more about Google Mini here http://www.google.com/enterprise/mini/.

Earlier our client, was using Microsoft's Index Server to index their digital assets. This index server was shared by several websites and is slowing things a bit. The server, I guess reached its capacity and could not crawl and index any new files added. We were looking at alternative solutions and stumbled upon the Mini.

Google Mini is a powerful search appliance in a blue box of the size of a large Pizza Hut pizza box. It is very easy to set it up and configure. The whole things takes around an hour or so to have the basic search solution up and running. All you have to do, is to tell the Mini what URL paths it has to index and bang, the Mini is on its feet crawling the site.

Things get a little tough and confusing when you start to change the look and feel of the results. To change the look and feel of the search results, we got to modify the style sheet (XSLT) that Google Appliance uses. In that we can configure our own header, menu and footer to integrate the search solution within the corporate website. This might take a while but trust me it is easy if you know how to tweak the XSLT. We can have more than one look and feel( front end) for our search results. Google Mini also lets us define our own collections to have pointed searches. A collection is a set of URL paths.

You can find the solution we implementd here http://search.dcoz.dc.gov/.

Overall, we are extremely satisfied with the end result. The search is very fast and the Return on Investment is huge.

If you have any questions on Google Mini, please leave a comment and I'll be glad to help you out.

Comments

Popular posts from this blog

Clear Validation Errors and Validation Summary messages

ASP.net built in validation does not provide us a straight forward to clear all the validation errors. This would be really helpful while resetting a form. The reset html button would simply reset the form values but will not clear the validation errors. The following javascript code snippet can be used to clear the validation error messages. Have a reset button on your form and call the following js function onclick. <input type="reset" onclick="HideValidationErrors();" /> function HideValidationErrors() { //Hide all validation errors if (window.Page_Validators) for (var vI = 0; vI < Page_Validators.length; vI++) { var vValidator = Page_Validators[vI]; vValidator.isvalid = true; ValidatorUpdateDisplay(vValidator); } //Hide all validaiton summaries if (typeof (Page_ValidationSummaries) != "undefined") { //hide the validation summaries

Kill a remote user session remotely

When trying to connect to your Windows 2000/2003 server remotely, you may receive the following error. "The terminal server has exceeded the maximum number of allowed connections." You could kill one or more of those connections by using PsExec tool that can be downloaded from the following link. This tool and a bunch of others were developed by SysInternals which was bought by Microsoft. http://www.microsoft.com/technet/sysinternals/utilities/pstools.mspx Open your command prompt and from the directory that contains the psexec utility, do the following 1) psexec \\x.x.x.x -u user -p password cmd (this will give you access to the cmd prompt on the server) Example: psexec \\127.0.0.1 -u admin -p password cmd 2) once you get the command prompt run the command qwinsta to get a list of all Terminal Services connections. Each connection has an Id Number. 3) Run the command logoff [id# of session to quit] /v (this will kill the connection with that id #) Example: logoff 2 /v Once

Creating a Windows Task Scheduler Service

Recently, one of my friends asked me for help in creating a windows service for scheduling some tasks. He said that he could not use the task scheduler that comes with Windows as the Task Scheduler expects each task to be a stand alone executable file. All his tasks were in a single class library and it would be a lot of work to separate each task into its own executable. Also he said that that the schedule for the tasks could change from time to time and it would be nice if he could configure the tasks in an XML file. To Recap, the requirements for the windows service are 1) The tasks should be loaded from a class library 2) The schedule information for the tasks should be configurable in an XML file. We googled (binged :)) for the solution and found an excellent article by Ajit Kumar Application Scheduler Service Using C#.Net And XML to base our solution upon. We took some good points like configuring the task information from the above mentioned article. This is how we to