ARCHIVED: Can I access CLSD as a Web Service?

The Indiana University Centralized Life Sciences Data (CLSD) service was retired June 18, 2010.

To access the Centralized Life Science Data (CLSD) service at Indiana University as a Web Service, access the Web Service function, queryCLSD (exposed for use from within the Java class CLSDservice), at:

This service accepts a query and associated authentication parameters, and uses the Java API for DataBase Connectivity (JDBC) to access the CLSD service at IU. As a result, routines that call it do not have to use JDBC.

The script for this service was developed using AXIS running over a TomCat servlet engine, and should interoperate with any (JAX-RPC) Web Service client, including those developed using AXIS, and those developed using Perl's SOAP::Lite module.

An example Web Service client written in Perl is described in Perl examples for accessing CLSD on the IU Research Technologies web site.

For more about using Java to access CLSD using both JDBC and Java-based Web Services, see Using Java to access CLSD on the IU Research Technologies web site. For the Web Services approach, that page provides links to:

• The Java source code for the Web Service, which itself uses JDBC to get to CLSD
  
  
• The Java source code for a very simple command-line client that calls the Web Service
  
  
• The Java source code for a servlet that invokes the Web Service method in place of making JDBC calls

Note: Java clients developed to access this CLSD resource require several JAR files to compile and run, as do all Java-based Web Service clients.

This document was developed with support from the National Science Foundation (NSF) under Grant No. 0503697 to the University of Chicago and subcontracted to Indiana University. Additional support was provided by IU through its participation in the TeraGrid, which is supported by the NSF under Grants No. 0833618, SCI451237, SCI535258, and SCI504075. Any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the NSF.

Comments/Questions/Corrections