Programming Guides › Connector Programming Guide › Endpoint Objects › How You Search for an Object › How you Test the Search Operation

How you Test the Search Operation

Your connector and directory object load correctly after implementing the doSearch method. To test the doSearch function, you also have to implement the doAdd function first so you can add some objects within the Provisioning Manager.

Assuming there are some account and group objects in the system, you can do the following searches for testing:

1. Test searching all type of object types.

   Issue a one-level search under the connector (or appropriate virtual containers where your connector uses them), by providing filters of the form (objectclass=<class1>) for each object type. One level searches are important as the Provisioning Server favors their use.

2. Test searching objects with filtering, for example, using a filter of the form (namingAttribute=a*).

   For unsupported filters, your connector should throw com.ca.jcs.LdapNotSupportedException.

3. Test search objects with return attributes.

   Try to establish a search by specifying some specific attributes you want to return.

4. Test the streaming search.

   Turn on the streaming search and start a subtree level search under the connector.

If no user interface is available at the time you do the testing, you can use JXplorer or other LDAP clients to issue the search requests.