Apologies if this is too simple a question, but these two DFS services appear similar, is there information available to help me determine which one I should use?
If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.
Very simply,
QueryService is about executing DQL queries and obtaining results, generally from metadata
SearchService is about executing full text queries and searching the content of files
So if executing metadata queries use QueryService, if you want to search the full text use SearchService.
The DFS reference guide has some further explanation of these
Thanks for that, could you point me towards the "DFS reference guide"
I have the following .chm files from "emc-dfs-sdk-6.0"
They dont do the explaining of how to do things though.
It's in the standard content server documentation set, a pdf named (for 6.7 anyhow)
Documentum Enterprise Content Services 6.7 Reference.pdf
The .chm files are the .NET equivalent of the JavaDocs, they desribe what the API calls are and the parameters but noit the how/when to use, that's what the PDF documents are for. There is the guide above along with the more general development guide
One more difference is that in SearchService you can issue searches asynchronously, and poll whether the result has been gathered/returned yet - and if the search has been runnning for too long, you can cancel it.
Besides that, SearchService has a limit for the resultset, by default it is 350 (you can change it at DFS server level - in dfc.properties).
So if you need complete result sets, then use QueryService, if you need just a "document search" like functionality, which may be incomplete, then use SearchService.
