MaxHits in ODWEK

[Steve C]

Hi All,

   We our server running on z/OS and also have a websphere server running on z/OS. We have a simple java interface written to run in this websphere server and
  this code then uses the  ODWEK APIs to access our OD server. As of September 06 we were up to date with all the latest PTFs.

   We appear to be having the following problem.....

When running a folder query against a very application group (hundreds of millions of documents) then if the query is open and has no real constraints we would expect
that the maxHits limit would be reached.
For us this is set to 1000 in the arswww.ini file.
Instead we pay IBM 100K Swiss Francs for the MIPS we use in creating an online hitlist result set of the 100 Million documents.

Is anyone else experiencing such problems?

We will be setting the maxhits on the folder level as of Monday and testing that this fixes the problem. (Are there other alternatives?)
If not we will have to implement requirements on the search entry mask to ensure a minimum set of search criteria (our old GUI interface has this but our new 'better' one does not!!)

If the old CGI interface can have the maxHits limit set as part of the call - why is there not a set method for MaxHits in the ODWEK Java APIs?!!!

   

[markwilliams]

in the arswww.ini file there is a maxhits parm

we run ondemand on zOS and the odwek APIs on AIX. The maxhits works perfect for us.

[javed.khan]

The MaxHits property is also present at the CMOD server side. Ideally the property set in CMOD takes priority over the ODWEK peoperty.

[ewirtz]

Hi Steve,

if DB2 p.e. needs an internal sort, max hits will not help at all to reduce costs even if max hits work fine. So database / index design is very important also in case of Ondemand.

regards

Egon

[Alessandro Perucchi]

Hello Steve,

if you're doing some Java development using the API, then the "trick" to modify the arswww.ini doesn't work anymore. Well it might work, but that was deprecated since a few versions.

Normally you need to tell in your java code what is the limit, if you haven't put in the AG itself.

for example:

Code Select Expand


 ODConfig config = new ODConfig();
 ODServer server = new ODServer(config);
 server.initialize("test");
 server.setPort(0);
 server.logon("127.0.0.1", "admin", "password");
 ODFolder folder = server.openFolder("System Log");
 // Define the number of max hit in the folder.
 folder.setMaxHits(1000);
 // ...
 folder.close();
 server.logoff();
 server.terminate();


You can also find using the method ODFolder.getMaxHits() how many hits you will get in return. And that before doing your search.

Here is the documentation of the method ODFolder.setMaxHits:

Set the Maximum Hits allowed to be returned during a search. The search call will be stopped if MaxHits is encountered, and depending on ODFolder.getSortLocation(),the sort order of the hitlist returned may be affected.
The default ODWEK setting for MaxHits is 200, or the OnDemand Folder definitions as set by the OnDemand Administrator, whichever is less.
MaxHits can be reset between searches as necessary.

Of course you can define with the constructor of ODConfig the whole set of parameters (general scope) from the connection you want to make:

public ODConfig(java.lang.String afpViewer,
               java.lang.String lineViewer,
               java.lang.String metaViewer,
               long maxHits,
               java.lang.String appletDir,
               java.lang.String language,
               java.lang.String tempDir,
               java.lang.String traceDir,
               int traceLevel,
               java.util.Properties props)
        throws ODException

Of course, this is only if you do some development in Java. If you use the CGI/Servlet, then the arswww.ini trick should work.

I hope that helps a bit.

Sincerely yours,
Alessandro