Query Windows Search from Java

Question

I would like to get to query Windows Vista Search service directly ( or indirectly ) from Java.

I know it is possible to query using the search-ms: protocol, but I would like to consume the result within the app.

I have found good information in the Windows Search API but none related to Java.

I would mark as accepted the answer that provides useful and definitive information on how to achieve this.

Thanks in advance.

EDIT

Does anyone have a JACOB sample, before I can mark this as accepted? :)

Answer 1

Any reason why you couldn't just use Runtime.exec() to query via search-ms and read the BufferedReader with the result of the command? For example:

public class ExecTest {
    public static void main(String[] args) throws IOException {
        Process result = Runtime.getRuntime().exec("search-ms:query=microsoft&");

        BufferedReader output = new BufferedReader(new InputStreamReader(result.getInputStream()));
        StringBuffer outputSB = new StringBuffer(40000);
        String s = null;

        while ((s = output.readLine()) != null) {
            outputSB.append(s + "\n");
            System.out.println(s);
        }

        String result = output.toString();
    }
}

Answer 2

You may want to look at one of the Java-COM integration technologies. I have personally worked with JACOB (JAva COm Bridge):

• http://danadler.com/jacob/

Which was rather cumbersome (think working exclusively with reflection), but got the job done for me (quick proof of concept, accessing MapPoint from within Java).

The only other such technology I'm aware of is Jawin, but I don't have any personal experience with it:

• http://jawinproject.sourceforge.net/

Update 04/26/2009: Just for the heck of it, I did more research into Microsoft Windows Search, and found an easy way to integrate with it using OLE DB. Here's some code I wrote as a proof of concept:

public static void main(String[] args) {
 DispatchPtr connection = null;
 DispatchPtr results = null;
 try {
  Ole32.CoInitialize();
  connection = new DispatchPtr("ADODB.Connection");
  connection.invoke("Open",
   "Provider=Search.CollatorDSO;" +
   "Extended Properties='Application=Windows';");
  results = (DispatchPtr)connection.invoke("Execute",
   "select System.Title, System.Comment, System.ItemName, System.ItemUrl, System.FileExtension, System.ItemDate, System.MimeType " +
   "from SystemIndex " +
   "where contains('Foo')");
  int count = 0;
  while(!((Boolean)results.get("EOF")).booleanValue()) {
   ++ count;
   DispatchPtr fields = (DispatchPtr)results.get("Fields");
   int numFields = ((Integer)fields.get("Count")).intValue();

   for (int i = 0; i < numFields; ++ i) {
    DispatchPtr item =
     (DispatchPtr)fields.get("Item", new Integer(i));
    System.out.println(
     item.get("Name") + ": " + item.get("Value"));
   }
   System.out.println();
   results.invoke("MoveNext");
  }
  System.out.println("\nCount:" + count);
 } catch (COMException e) {
  e.printStackTrace();
 } finally {
  try {
   results.invoke("Close");
  } catch (COMException e) {
   e.printStackTrace();
  }
  try {
   connection.invoke("Close");
  } catch (COMException e) {
   e.printStackTrace();
  }
  try {
   Ole32.CoUninitialize();
  } catch (COMException e) {
   e.printStackTrace();
  }
 }
}

To compile this, you'll need to make sure that the JAWIN JAR is in your classpath, and that jawin.dll is in your path (or java.library.path system property). This code simply opens an ADO connection to the local Windows Desktop Search index, queries for documents with the keyword "Foo," and print out a few key properties on the resultant documents.

Let me know if you have any questions, or need me to clarify anything.

Update 04/27/2009: I tried implementing the same thing in JACOB as well, and will be doing some benchmarks to compare performance differences between the two. I may be doing something wrong in JACOB, but it seems to consistently be using 10x more memory. I'll be working on a jcom and com4j implementation as well, if I have some time, and try to figure out some quirks that I believe are due to the lack of thread safety somewhere. I may even try a JNI based solution. I expect to be done with everything in 6-8 weeks.

Update 04/28/2009: This is just an update for those who've been following and curious. Turns out there are no threading issues, I just needed to explicitly close my database resources, since the OLE DB connections are presumably pooled at the OS level (I probably should have closed the connections anyway...). I don't think I'll be any further updates to this. Let me know if anyone runs into any problems with this.

Update 05/01/2009: Added JACOB example per Oscar's request. This goes through the exact same sequence of calls from a COM perspective, just using JACOB. While it's true JACOB has been much more actively worked on in recent times, I also notice that it's quite a memory hog (uses 10x as much memory as the Jawin version)

public static void main(String[] args) {
 Dispatch connection = null;
 Dispatch results = null;

 try {
  connection = new Dispatch("ADODB.Connection");
  Dispatch.call(connection, "Open",
   "Provider=Search.CollatorDSO;Extended Properties='Application=Windows';");
  results = Dispatch.call(connection, "Execute",
   "select System.Title, System.Comment, System.ItemName, System.ItemUrl, System.FileExtension, System.ItemDate, System.MimeType " +
   "from SystemIndex " +
   "where contains('Foo')").toDispatch();
  int count = 0;
  while(!Dispatch.get(results, "EOF").getBoolean()) {
   ++ count;
   Dispatch fields = Dispatch.get(results, "Fields").toDispatch();
   int numFields = Dispatch.get(fields, "Count").getInt();

   for (int i = 0; i < numFields; ++ i) {
    Dispatch item =
     Dispatch.call(fields, "Item", new Integer(i)).
     toDispatch();
    System.out.println(
     Dispatch.get(item, "Name") + ": " +
     Dispatch.get(item, "Value"));
   }
   System.out.println();
   Dispatch.call(results, "MoveNext");
  }
 } finally {
  try {
   Dispatch.call(results, "Close");
  } catch (JacobException e) {
   e.printStackTrace();
  }
  try {
   Dispatch.call(connection, "Close");
  } catch (JacobException e) {
   e.printStackTrace();
  }
 }
}

Answer 3

There are several libraries out there for calling COM objects from java, some are opensource (but their learning curve is higher) some are closed source and have a quicker learning curve. A closed source example is EZCom. The commercial ones tend to focus on calling java from windows as well, something I've never seen in opensource.

In your case, what I would suggest you do is front the call in your own .NET class (I guess use C# as that is closest to Java without getting into the controversial J#), and focus on making the interoperability with the .NET dll. That way the windows programming gets easier, and the interface between Windows and java is simpler.

If you are looking for how to use a java com library, the MSDN is the wrong place. But the MSDN will help you write what you need from within .NET, and then look at the com library tutorials about invoking the one or two methods you need from your .NET objects.

EDIT:

Given the discussion in the answers about using a Web Service, you could (and probably will have better luck) build a small .NET app that calls an embedded java web server rather than try to make .NET have the embedded web service, and have java be the consumer of the call. For an embedded web server, my research showed Winstone to be good. Not the smallest, but is much more flexible.

The way to get that to work is to launch the .NET app from java, and have the .NET app call the web service on a timer or a loop to see if there is a request, and if there is, process it and send the response.

Answer 4

As few posts here suggest you can bridge between Java and .NET or COM using commercial or free frameworks like JACOB, JNBridge, J-Integra etc.. Actually I had an experience with with one of these third parties (an expensive one :-) ) and I must say I will do my best to avoid repeating this mistake in the future. The reason is that it involves many "voodoo" stuff you can't really debug, it's very complicated to understand what is the problem when things go wrong.

The solution I would suggest you to implement is to create a simple .NET application that makes the actual calls to the windows search API. After doing so, you need to establish a communication channel between this component and your Java code. This can be done in various ways, for example by messaging to a small DB that your application will periodically pull. Or registering this component on the machine IIS (if exists) and expose simple WS API to communicate with it.

I know that it may sound cumbersome but the clear advantages are: a) you communicate with windows search API using the language it understands (.NET or COM) , b) you control all the application paths.