On Monday 28th March 2011 the WSInterProScan service was decommissioned and replaced by the following services:

• InterProScan (REST)
• InterProScan (SOAP)

The service documentation and clients below are historical and provided solely for reference purposes.

InterProScan is a tool that combines different protein signature recognition methods native to the InterPro member databases into one resource with look up of corresponding InterPro and GO annotation. This service allows you to query your protein sequence against InterPro.

For more information about this tool see:

• EMBL-EBI Tools:
  • InterProScan
  • InterProScan (REST)
  • InterProScan (SOAP)
• Stand-alone InterProScan
  • Readme
  • FAQs
• InterPro
  • User manual
  • Help pages
• Web service registry entries:
  • BioCatalogue
  • seekda!

We kindly ask all users of SOAP Web Services to submit jobs in batches of up to 25 sequences at a time and to not submit more until the results and processing has completed for these. This should enable the users as well as the EBI maintainers to deal more easily with local and remote network outages as well as scheduled or unscheduled downtime.

Service provision happens on a fair-share basis. Overzealous usage of a particular resource will be dealt with in accordance to the EBI's Terms of Use.

Due to resource limitations the InterProScan service no longer accepts nucleotide sequence submissions.

To process nucleotide sequences using InterProScan:

1. Translate your nucleotide sequence
The standalone version of InterProScan uses EMBOSS sixpack to perform the translation and filter the resulting open reading frame (ORF) sequences by length. Alternative tools such as EMBOSS transeq are also available, but may require an additional filtering process to limit the ORF sequences to those above a certain length. These tools are available as part of our EMBOSS webservices, Soaplab and as part of the EMBOSS package.

2. Filter ORFs by sequence length.
Short sequences (<80 aa) are unlikely to have any signature matches, so unless there is additional evidence that the sequence occurs, short sequences can be discarded. The EMBOSS sixpack tool provides an option to do length filtering when performing the translation.

3. Significant hits from sequence similarity searches.
The signatures used by InterProScan are based on known protein sequences so a filtering step by performing a BLAST or FASTA sequence similarity search with the ORF translations against the UniProtKB or UniParc protein sequence databases and only keeping sequences which have hits with e-values <0.001. In the case where an exact match is found to the sequence, you can go directly to the InterPro Matches databases to get the signature matches for the sequence.

Note: the standalone version of InterProScan can perform the translation and ORF length filtering as part of the submission and is recommended if you need to perform large numbers of analysis and have access to the required resources. See InterProScan Readme for details.

Sample clients are provided for a number of programming languages. For details of how to use these clients, download the client and run the program without any arguments.

For further details see WSInterProScan Clients.

http://www.ebi.ac.uk/Tools/webservices/wsdl/WSInterProScan.wsdl

Get details of the available signature methods available in InterProScan.

Arguments: none

Returns: an array of outData objects describing the available options.

Submits a InterProScan job to the service.

Arguments:

• params an instance of the inputParams data structure.
• content a list of data data structures describing the query sequence data.

Returns: a string containing the job ID (jobid).

Get the status of a job.

Arguments:

• jobid the job identifier of the job to check status of.

Returns: a string indicating the status of the job. Current values are:

• DONE: job has finished, and the results can then be retrieved.
• ERROR: the job failed or no results where found
• NOT_FOUND: the job id is no longer available (job results are deleted after 24 h)
• PENDING: the job is in a queue waiting processing
• RUNNING: the job is currently being processed

Get details of the result types available.

Arguments:

• jobid the job identifier of the job to get result types for.

Returns: an array of WSFile structures describing the available result types for the job.

Wait until the job has finished and get the specified type of result data.

Arguments:

• jobid the job identifier of the job to get result from.
• type a string specifying the type of result to retrieve. See getResults(jobid) and WSFile for details of how to obtain valid values.

Returns: a base64 encoded string containing the result data. Depending on the SOAP library and programming language used the result may be returned in decoded form.

Deprecated. Use runInterProScan(params, content) instead.

Deprecated. Use poll(jobid, type) instead.

Structure containing option descriptions for a parameter.

Structure containing the input data for the job

For example to specify an input sequence in Java:

Data inSeq = new Data();
inSeq.setType = "sequence";
inSeq.setContent = ">TestSequence\nASAMPLESEQ\n";

A structure containing the parameters required to run the job.

Structure describing a result type. Returned by the getResults(jobid) method.

If you have any questions or comments, or you plan to use this service as part of a course or for a high number of submissions, please contact us EBI Support.