next up previous
Next: Dublin Core Terms Set Up: Quick User's Guide Previous: 3.3 Map

4 Testing the agent

The simplest way to check is Searchy is correctly listening is by the test action in the init script, just execute 'SEARCHY.SH TEST' or 'SEARCHY.BAT TEST' and if the agent is running, its name must be displayed.

Searchy has not been designed to be used by final users, but by other applications like servlets, PHP pages or heavy applications. So, a custom client should be developed, but a generic client for testing proposes has been included in the distribution of Searchy.

To use the generic client, set the classpath to include the jar files LIB/LOG4J-1.2.4.JAR, LIB/JAVA-GETOPT-1.0.9.JAR, LIB/SPHEON-JSOAP.JAR, the CLASSES folder and execute the class es.rediris.searchy.client.SearchyLocator, it accepts three arguments:

q,query
The query to be submitted.
n,name
To query the agent's name.
e,element
The DC element for which we query.
a,agent
The address of the agent we are querying, if not given, it will use localhost:33333.
h,help
Help
For example, to ask for a DC element creator with valour Homer in the localhost:

java es.rediris.searchy.client.SearchyLocator -e creator -q Homer


next up previous
Next: Dublin Core Terms Set Up: Quick User's Guide Previous: 3.3 Map
2004-05-20