BiBiServ Logo
Attention:
Due to technical maintenance some tools might be unavailable.
See maintenance information.
BiBiServ -
                                    Bielefeld         University Bioinformatic Service
Tools
Education
Administration
Tools
Genome Comparison
Gecko
REPuter
...more
Alignments
PoSSuMsearch2
ChromA
...more
Primer Design
GeneFisher2
RNA Studio
RNAshapes
KnotInFrame
RNAhybrid
...more
Evolutionary Relationship
ROSE
...more
Others
XenDB
jPREdictor
...more

ChromA - WebService

This is a short introduction on how to use the ChromA WebService offered by BiBiServ. If you're not familiar with using webservices in general you should have a closer look to our webservice related linklist.

WSDL - methods, parameters and datatypes

If you have a closer look at the WSDL file describing the ChromA webservice, you can see two methods belonging together.

request_orig and response_orig

Bioinformatic programs often perform computation on large data sets and therefore require much CPU time. This can cause problems like http connection timeouts (usually after 5 minutes) during online usage. To avoid such problems when using ChromA WebService we use a technique called Request and Reply with polling based on BiBiWS. First the client side (e.g. your program) requests a ChromA job submitting the necessary data (parameter and data) and gets an id after the job is started. Afterwards the client can request the result by calling the corresponding response method with the id returned earlier. If the ChromA job is not finished, the user gets a status code with an enhanced description of current status back (see HOBIT status codes for more information).

request_orig
The request_orig method ... (see table below for an example param array - default values in bold) and returns either a unique id or in case of an error a fault message.

key value description
array_params impl:ArrayOf_xsd_anyType serialized map of parameters {key1=value1,key2=value2} => [key1,value1,key2,value2]
key value description
email optional Email address for result notification (currently disabled)
alignmentAlgorithmDistance required; one of Lp,Cos,Corr,TICSq; default: Lp Which local distance/similarity to use for alignment
alignmentAlgorithm required; one of MZIDTW,TICDTW; default: MZIDTW Which algorithm to use for alignment, TICDTW only works with TICSq!
anchors1 optional; String of space separated integers, e.g.: "10 50 300"; default: "" Scans within file1 to be used as anchors
anchors2 optional; String of space separated integers, e.g.: "10 50 300"; default: "" Scans within file2 to be used as anchors
filteredMasses optional; String of space separated mass bins, e.g.: "71 72 73"; default: "" Mass channels whose intensites are removed
neighborhood optional; Integer number as String, e.g.: "10"; default: "0" Neighborhood around anchors to be considered
band optional; Float number as String, e.g.: "0.01"; default: "0" Band constraint along the diagonal, width is value*max(|chromA|,|chromB|)
file1 soapenc:base64Binary First file compressed with GZip and Base64 encoded
filename1 soapenc:string Filename of file1 without path prefix, but with endings .gz.b64
file2 soapenc:base64Binary Second file compressed with GZip and Base64 encoded
filename2 soapenc:string Filename of file2 without path prefix, but with endings .gz.b64

response_orig
The response_orig method gets the id returned by the request method as input parameter and returns the calculated result as a base64 encoded zip-Archive.

Welcome
Submission
WebService
WebStart
References
Manual
Download
Contact
Report a Bug
Fri Dec 14 12:49:15 2012