If you are writing a generic repository browsing application, you will need perform searches to discover the objects in the repository. There are two styles of searches, a listing search (listObjects) and a fetching search (getObjects). A listing search retrieves the name and a few attributes of the object, but does not bring the entire object into memory. A fetching search loads the entire object into memory.
You should always use listing searches when querying IDMXUser objects, because there can be a large number of users in the directory.
The listObjects, getObjects, and deleteObjects methods recognize an options map argument, in which search criteria and other options may be specified. When building an options map, it is recommend that you use a set of constant string objects. The following table lists the valid query option names and their corresponding constant object.
Option Name |
Object |
---|---|
orderBy |
LighthouseContext.OP_ORDER_BY |
maxRows |
LighthouseContext.OP_MAX_ROWS |
subject |
LighthouseContext.OP_SUBJECT |
attributes |
LighthouseContext.OP_ATTRIBUTES |
conditions |
LighthouseContext.OP_CONDITIONS |
Service Provider enforces a maximum number of results that a query can return. This maximum is specified by the maxRows option.