1. ChannelFinder Client Kunal Shroff EPICS Spring Collaboration Meeting, October 2010 BNL

2. ChannelFinder:  A Directory Service  Generic No dependency on installation and local conventions  Simple and Fast Use standards wherever possible  Provides “query-by-functionality”

3. ChannelFinder  REST style web service URI specifies the data element to operate on HTTP method specifies the operation Payload (XML, JSON) contains object representation  RDB Contains directory data  Use LDAP to query user-group relations

4. ChannelFinderAPI  http://channelfinder.sourceforge.net/ http://channelfinder.sourceforge.net/  Pure Java API library Query Add/Remove channels, Properties, Tags Set/Update channels, Properties, Tags  RESTful web service client - Jersey  Test Driven Development Junit corbertura

5. ChannelFinderAPI  Benchmark tests 2K channel Directory5k Channel Directory (+ SSL) Query 1 Channel15 ms93 ms Query 10 Channel16 ms39 ms Query 100 Channel23 ms39.5 ms Query 500 Channel31 ms70 ms Query 1000 Channel47 ms86.5 ms Query 2000 Channel94 ms125 ms

6. Channels

7. ChannelFinder Viewer  CSS  Display  ChannelFinderViewer  Searching Name, Property value, Tags Regular Expressions using “*”, “?”

8. ChannelFinder Viewer

9. Acknowledgement  Ralph Lange (Directory Service)  Gabriele Carcassi (App/Build Servers, IRMIS)  Don Dohan (IRMIS)

10. Questions