|
Overview Service Description Client proxy Methods Init DeleteJob AddFile AddTextFile GetFile GetZipedFile GetTextFile SubmitPoy IsDoneYet Methods for binding PoyServiceSoap12 Init DeleteJob AddFile AddTextFile GetFile GetZipedFile GetTextFile SubmitPoy IsDoneYet |
WSDL document for namespace "supramap" Download <?xml version="1.0" encoding="utf-8"?>
<definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:s0="supramap" name="PoyService" targetNamespace="supramap" xmlns="http://schemas.xmlsoap.org/wsdl/"> <types> <xs:schema elementFormDefault="qualified" targetNamespace="supramap" xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:element name="Init"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" maxOccurs="1" name="passPhase" type="xs:string"/> <xs:element minOccurs="0" maxOccurs="1" name="resource" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="InitResponse"> <xs:complexType> <xs:sequence> <xs:element minOccurs="1" maxOccurs="1" name="InitResult" type="xs:int"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="DeleteJob"> <xs:complexType> <xs:sequence> <xs:element minOccurs="1" maxOccurs="1" name="jobId" type="xs:int"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="DeleteJobResponse"> <xs:complexType> <xs:sequence> <xs:element minOccurs="1" maxOccurs="1" name="DeleteJobResult" type="xs:boolean"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="AddFile"> <xs:complexType> <xs:sequence> <xs:element minOccurs="1" maxOccurs="1" name="jobId" type="xs:int"/> <xs:element minOccurs="0" maxOccurs="1" name="fileData" type="xs:base64Binary"/> <xs:element minOccurs="0" maxOccurs="1" name="fileName" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="AddFileResponse"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" maxOccurs="1" name="AddFileResult" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="AddTextFile"> <xs:complexType> <xs:sequence> <xs:element minOccurs="1" maxOccurs="1" name="jobId" type="xs:int"/> <xs:element minOccurs="0" maxOccurs="1" name="fileData" type="xs:string"/> <xs:element minOccurs="0" maxOccurs="1" name="fileName" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="AddTextFileResponse"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" maxOccurs="1" name="AddTextFileResult" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="GetFile"> <xs:complexType> <xs:sequence> <xs:element minOccurs="1" maxOccurs="1" name="jobId" type="xs:int"/> <xs:element minOccurs="0" maxOccurs="1" name="fileName" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="GetFileResponse"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" maxOccurs="1" name="GetFileResult" type="xs:base64Binary"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="GetZipedFile"> <xs:complexType> <xs:sequence> <xs:element minOccurs="1" maxOccurs="1" name="jobId" type="xs:int"/> <xs:element minOccurs="0" maxOccurs="1" name="fileName" type="xs:string"/> <xs:element minOccurs="0" maxOccurs="1" name="compressionType" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="GetZipedFileResponse"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" maxOccurs="1" name="GetZipedFileResult" type="xs:base64Binary"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="GetTextFile"> <xs:complexType> <xs:sequence> <xs:element minOccurs="1" maxOccurs="1" name="jobId" type="xs:int"/> <xs:element minOccurs="0" maxOccurs="1" name="fileName" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="GetTextFileResponse"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" maxOccurs="1" name="GetTextFileResult" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="SubmitPoy"> <xs:complexType> <xs:sequence> <xs:element minOccurs="1" maxOccurs="1" name="jobId" type="xs:int"/> <xs:element minOccurs="1" maxOccurs="1" name="numberOfNodes" type="xs:int"/> <xs:element minOccurs="1" maxOccurs="1" name="wallTimeHours" type="xs:int"/> <xs:element minOccurs="1" maxOccurs="1" name="wallTimeMinutes" type="xs:int"/> <xs:element minOccurs="0" maxOccurs="1" name="postBackURL" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="SubmitPoyResponse"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" maxOccurs="1" name="SubmitPoyResult" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="IsDoneYet"> <xs:complexType> <xs:sequence> <xs:element minOccurs="1" maxOccurs="1" name="jobId" type="xs:int"/> <xs:element minOccurs="0" maxOccurs="1" name="command" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="IsDoneYetResponse"> <xs:complexType> <xs:sequence> <xs:element minOccurs="1" maxOccurs="1" name="IsDoneYetResult" type="xs:boolean"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="int" type="xs:int"/> <xs:element name="boolean" type="xs:boolean"/> <xs:element name="string" nillable="true" type="xs:string"/> <xs:element name="base64Binary" nillable="true" type="xs:base64Binary"/> </xs:schema> </types> <message name="InitSoapIn"> <part name="parameters" element="s0:Init"/> </message> <message name="InitSoapOut"> <part name="parameters" element="s0:InitResponse"/> </message> <message name="DeleteJobSoapIn"> <part name="parameters" element="s0:DeleteJob"/> </message> <message name="DeleteJobSoapOut"> <part name="parameters" element="s0:DeleteJobResponse"/> </message> <message name="AddFileSoapIn"> <part name="parameters" element="s0:AddFile"/> </message> <message name="AddFileSoapOut"> <part name="parameters" element="s0:AddFileResponse"/> </message> <message name="AddTextFileSoapIn"> <part name="parameters" element="s0:AddTextFile"/> </message> <message name="AddTextFileSoapOut"> <part name="parameters" element="s0:AddTextFileResponse"/> </message> <message name="GetFileSoapIn"> <part name="parameters" element="s0:GetFile"/> </message> <message name="GetFileSoapOut"> <part name="parameters" element="s0:GetFileResponse"/> </message> <message name="GetZipedFileSoapIn"> <part name="parameters" element="s0:GetZipedFile"/> </message> <message name="GetZipedFileSoapOut"> <part name="parameters" element="s0:GetZipedFileResponse"/> </message> <message name="GetTextFileSoapIn"> <part name="parameters" element="s0:GetTextFile"/> </message> <message name="GetTextFileSoapOut"> <part name="parameters" element="s0:GetTextFileResponse"/> </message> <message name="SubmitPoySoapIn"> <part name="parameters" element="s0:SubmitPoy"/> </message> <message name="SubmitPoySoapOut"> <part name="parameters" element="s0:SubmitPoyResponse"/> </message> <message name="IsDoneYetSoapIn"> <part name="parameters" element="s0:IsDoneYet"/> </message> <message name="IsDoneYetSoapOut"> <part name="parameters" element="s0:IsDoneYetResponse"/> </message> <message name="InitHttpGetIn"> <part name="passPhase" type="s:string"/> <part name="resource" type="s:string"/> </message> <message name="InitHttpGetOut"> <part name="Body" element="s0:int"/> </message> <message name="DeleteJobHttpGetIn"> <part name="jobId" type="s:int"/> </message> <message name="DeleteJobHttpGetOut"> <part name="Body" element="s0:boolean"/> </message> <message name="AddFileHttpGetIn"> <part name="jobId" type="s:int"/> <part name="fileData" type="s:base64Binary"/> <part name="fileName" type="s:string"/> </message> <message name="AddFileHttpGetOut"> <part name="Body" element="s0:string"/> </message> <message name="AddTextFileHttpGetIn"> <part name="jobId" type="s:int"/> <part name="fileData" type="s:string"/> <part name="fileName" type="s:string"/> </message> <message name="AddTextFileHttpGetOut"> <part name="Body" element="s0:string"/> </message> <message name="GetFileHttpGetIn"> <part name="jobId" type="s:int"/> <part name="fileName" type="s:string"/> </message> <message name="GetFileHttpGetOut"> <part name="Body" element="s0:base64Binary"/> </message> <message name="GetZipedFileHttpGetIn"> <part name="jobId" type="s:int"/> <part name="fileName" type="s:string"/> <part name="compressionType" type="s:string"/> </message> <message name="GetZipedFileHttpGetOut"> <part name="Body" element="s0:base64Binary"/> </message> <message name="GetTextFileHttpGetIn"> <part name="jobId" type="s:int"/> <part name="fileName" type="s:string"/> </message> <message name="GetTextFileHttpGetOut"> <part name="Body" element="s0:string"/> </message> <message name="SubmitPoyHttpGetIn"> <part name="jobId" type="s:int"/> <part name="numberOfNodes" type="s:int"/> <part name="wallTimeHours" type="s:int"/> <part name="wallTimeMinutes" type="s:int"/> <part name="postBackURL" type="s:string"/> </message> <message name="SubmitPoyHttpGetOut"> <part name="Body" element="s0:string"/> </message> <message name="IsDoneYetHttpGetIn"> <part name="jobId" type="s:int"/> <part name="command" type="s:string"/> </message> <message name="IsDoneYetHttpGetOut"> <part name="Body" element="s0:boolean"/> </message> <message name="InitHttpPostIn"> <part name="passPhase" type="s:string"/> <part name="resource" type="s:string"/> </message> <message name="InitHttpPostOut"> <part name="Body" element="s0:int"/> </message> <message name="DeleteJobHttpPostIn"> <part name="jobId" type="s:int"/> </message> <message name="DeleteJobHttpPostOut"> <part name="Body" element="s0:boolean"/> </message> <message name="AddFileHttpPostIn"> <part name="jobId" type="s:int"/> <part name="fileData" type="s:base64Binary"/> <part name="fileName" type="s:string"/> </message> <message name="AddFileHttpPostOut"> <part name="Body" element="s0:string"/> </message> <message name="AddTextFileHttpPostIn"> <part name="jobId" type="s:int"/> <part name="fileData" type="s:string"/> <part name="fileName" type="s:string"/> </message> <message name="AddTextFileHttpPostOut"> <part name="Body" element="s0:string"/> </message> <message name="GetFileHttpPostIn"> <part name="jobId" type="s:int"/> <part name="fileName" type="s:string"/> </message> <message name="GetFileHttpPostOut"> <part name="Body" element="s0:base64Binary"/> </message> <message name="GetZipedFileHttpPostIn"> <part name="jobId" type="s:int"/> <part name="fileName" type="s:string"/> <part name="compressionType" type="s:string"/> </message> <message name="GetZipedFileHttpPostOut"> <part name="Body" element="s0:base64Binary"/> </message> <message name="GetTextFileHttpPostIn"> <part name="jobId" type="s:int"/> <part name="fileName" type="s:string"/> </message> <message name="GetTextFileHttpPostOut"> <part name="Body" element="s0:string"/> </message> <message name="SubmitPoyHttpPostIn"> <part name="jobId" type="s:int"/> <part name="numberOfNodes" type="s:int"/> <part name="wallTimeHours" type="s:int"/> <part name="wallTimeMinutes" type="s:int"/> <part name="postBackURL" type="s:string"/> </message> <message name="SubmitPoyHttpPostOut"> <part name="Body" element="s0:string"/> </message> <message name="IsDoneYetHttpPostIn"> <part name="jobId" type="s:int"/> <part name="command" type="s:string"/> </message> <message name="IsDoneYetHttpPostOut"> <part name="Body" element="s0:boolean"/> </message> <portType name="PoyServiceSoap"> <operation name="Init"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">The 'Init' method basically creates a directory on the super computer it returns a token that must be used on all subsequent method calls as the jobId parameter.Note this token will only work with the ipaddress that was used to call this method. Note it is not enforced but it highly encouraged to use this method over https. to get a pass prase to use this web service please vist http://glenn-webservice.bmi.ohio-state.edu/Application.aspx The current to option for resource are Glenn and supradev</wsdl:documentation> <input message="s0:InitSoapIn"/> <output message="s0:InitSoapOut"/> </operation> <operation name="DeleteJob"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">This method removes all files on the super computer for this job</wsdl:documentation> <input message="s0:DeleteJobSoapIn"/> <output message="s0:DeleteJobSoapOut"/> </operation> <operation name="AddFile"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">The 'AddFile' method is used to basically put a file on the super computer. It should be called once to a load a .poy script. Plus it should be called for each file that the POY script references. It is the responsibility of the downstream client developer to generate the POY scripts this places more work in there hands but also give them great flexibility to design web apps that can use POY for anything. Note: there is a bug and the method won't work if there is a space in any of the file names </wsdl:documentation> <input message="s0:AddFileSoapIn"/> <output message="s0:AddFileSoapOut"/> </operation> <operation name="AddTextFile"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">The AddTextFile method is an alternative to the Add File command. This function allows the permissioned user to add a file as a simple string instead of using binary data in the fileData field.</wsdl:documentation> <input message="s0:AddTextFileSoapIn"/> <output message="s0:AddTextFileSoapOut"/> </operation> <operation name="GetFile"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">The GetFile method is utilized to retrieve the output files specified in the Poy script. This function is called once per file </wsdl:documentation> <input message="s0:GetFileSoapIn"/> <output message="s0:GetFileSoapOut"/> </operation> <operation name="GetZipedFile"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">The GetZipedFile is a second method that can be used to retrieve an output file. This command allows the user to compress the file prior to retrieving it. </wsdl:documentation> <input message="s0:GetZipedFileSoapIn"/> <output message="s0:GetZipedFileSoapOut"/> </operation> <operation name="GetTextFile"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">The basically 'GetFile' but returns a string instead of binary data should only be used on text files</wsdl:documentation> <input message="s0:GetTextFileSoapIn"/> <output message="s0:GetTextFileSoapOut"/> </operation> <operation name="SubmitPoy"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"> The 'SubmitPoy' method start a job on the super computer that start the POY job. When running a job on a super computer you have to request a what resource you need like how many processors, how many nodes, how much memory and how long it will take. If you ask for a lot of resources your job could get scheduled for a future date instead of running immediately. So it would not be suitable for realtime-ish apps. On the other hand if you request to little resources your job might not finish. Also we could extend the web service by adding new method that are similar to this one but only use other back-end Linux tools. These methods could take advantage of all of the existing infrastructure. </wsdl:documentation> <input message="s0:SubmitPoySoapIn"/> <output message="s0:SubmitPoySoapOut"/> </operation> <operation name="IsDoneYet"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"> The client must periodically poll the service after it submits its job so it knows when its job is done. The 'IsDoneYet' method does just that and returns true if the job is done and false if the job is not done yet. The command value can ether be 'poy' or 'GenPhen' </wsdl:documentation> <input message="s0:IsDoneYetSoapIn"/> <output message="s0:IsDoneYetSoapOut"/> </operation> </portType> <portType name="PoyServiceSoap12"> <operation name="Init"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">The 'Init' method basically creates a directory on the super computer it returns a token that must be used on all subsequent method calls as the jobId parameter.Note this token will only work with the ipaddress that was used to call this method. Note it is not enforced but it highly encouraged to use this method over https. to get a pass prase to use this web service please vist http://glenn-webservice.bmi.ohio-state.edu/Application.aspx The current to option for resource are Glenn and supradev</wsdl:documentation> <input message="s0:InitSoapIn"/> <output message="s0:InitSoapOut"/> </operation> <operation name="DeleteJob"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">This method removes all files on the super computer for this job</wsdl:documentation> <input message="s0:DeleteJobSoapIn"/> <output message="s0:DeleteJobSoapOut"/> </operation> <operation name="AddFile"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">The 'AddFile' method is used to basically put a file on the super computer. It should be called once to a load a .poy script. Plus it should be called for each file that the POY script references. It is the responsibility of the downstream client developer to generate the POY scripts this places more work in there hands but also give them great flexibility to design web apps that can use POY for anything. Note: there is a bug and the method won't work if there is a space in any of the file names </wsdl:documentation> <input message="s0:AddFileSoapIn"/> <output message="s0:AddFileSoapOut"/> </operation> <operation name="AddTextFile"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">The AddTextFile method is an alternative to the Add File command. This function allows the permissioned user to add a file as a simple string instead of using binary data in the fileData field.</wsdl:documentation> <input message="s0:AddTextFileSoapIn"/> <output message="s0:AddTextFileSoapOut"/> </operation> <operation name="GetFile"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">The GetFile method is utilized to retrieve the output files specified in the Poy script. This function is called once per file </wsdl:documentation> <input message="s0:GetFileSoapIn"/> <output message="s0:GetFileSoapOut"/> </operation> <operation name="GetZipedFile"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">The GetZipedFile is a second method that can be used to retrieve an output file. This command allows the user to compress the file prior to retrieving it. </wsdl:documentation> <input message="s0:GetZipedFileSoapIn"/> <output message="s0:GetZipedFileSoapOut"/> </operation> <operation name="GetTextFile"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">The basically 'GetFile' but returns a string instead of binary data should only be used on text files</wsdl:documentation> <input message="s0:GetTextFileSoapIn"/> <output message="s0:GetTextFileSoapOut"/> </operation> <operation name="SubmitPoy"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"> The 'SubmitPoy' method start a job on the super computer that start the POY job. When running a job on a super computer you have to request a what resource you need like how many processors, how many nodes, how much memory and how long it will take. If you ask for a lot of resources your job could get scheduled for a future date instead of running immediately. So it would not be suitable for realtime-ish apps. On the other hand if you request to little resources your job might not finish. Also we could extend the web service by adding new method that are similar to this one but only use other back-end Linux tools. These methods could take advantage of all of the existing infrastructure. </wsdl:documentation> <input message="s0:SubmitPoySoapIn"/> <output message="s0:SubmitPoySoapOut"/> </operation> <operation name="IsDoneYet"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"> The client must periodically poll the service after it submits its job so it knows when its job is done. The 'IsDoneYet' method does just that and returns true if the job is done and false if the job is not done yet. The command value can ether be 'poy' or 'GenPhen' </wsdl:documentation> <input message="s0:IsDoneYetSoapIn"/> <output message="s0:IsDoneYetSoapOut"/> </operation> </portType> <portType name="PoyServiceHttpGet"> <operation name="Init"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">The 'Init' method basically creates a directory on the super computer it returns a token that must be used on all subsequent method calls as the jobId parameter.Note this token will only work with the ipaddress that was used to call this method. Note it is not enforced but it highly encouraged to use this method over https. to get a pass prase to use this web service please vist http://glenn-webservice.bmi.ohio-state.edu/Application.aspx The current to option for resource are Glenn and supradev</wsdl:documentation> <input message="s0:InitHttpGetIn"/> <output message="s0:InitHttpGetOut"/> </operation> <operation name="DeleteJob"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">This method removes all files on the super computer for this job</wsdl:documentation> <input message="s0:DeleteJobHttpGetIn"/> <output message="s0:DeleteJobHttpGetOut"/> </operation> <operation name="AddFile"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">The 'AddFile' method is used to basically put a file on the super computer. It should be called once to a load a .poy script. Plus it should be called for each file that the POY script references. It is the responsibility of the downstream client developer to generate the POY scripts this places more work in there hands but also give them great flexibility to design web apps that can use POY for anything. Note: there is a bug and the method won't work if there is a space in any of the file names </wsdl:documentation> <input message="s0:AddFileHttpGetIn"/> <output message="s0:AddFileHttpGetOut"/> </operation> <operation name="AddTextFile"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">The AddTextFile method is an alternative to the Add File command. This function allows the permissioned user to add a file as a simple string instead of using binary data in the fileData field.</wsdl:documentation> <input message="s0:AddTextFileHttpGetIn"/> <output message="s0:AddTextFileHttpGetOut"/> </operation> <operation name="GetFile"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">The GetFile method is utilized to retrieve the output files specified in the Poy script. This function is called once per file </wsdl:documentation> <input message="s0:GetFileHttpGetIn"/> <output message="s0:GetFileHttpGetOut"/> </operation> <operation name="GetZipedFile"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">The GetZipedFile is a second method that can be used to retrieve an output file. This command allows the user to compress the file prior to retrieving it. </wsdl:documentation> <input message="s0:GetZipedFileHttpGetIn"/> <output message="s0:GetZipedFileHttpGetOut"/> </operation> <operation name="GetTextFile"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">The basically 'GetFile' but returns a string instead of binary data should only be used on text files</wsdl:documentation> <input message="s0:GetTextFileHttpGetIn"/> <output message="s0:GetTextFileHttpGetOut"/> </operation> <operation name="SubmitPoy"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"> The 'SubmitPoy' method start a job on the super computer that start the POY job. When running a job on a super computer you have to request a what resource you need like how many processors, how many nodes, how much memory and how long it will take. If you ask for a lot of resources your job could get scheduled for a future date instead of running immediately. So it would not be suitable for realtime-ish apps. On the other hand if you request to little resources your job might not finish. Also we could extend the web service by adding new method that are similar to this one but only use other back-end Linux tools. These methods could take advantage of all of the existing infrastructure. </wsdl:documentation> <input message="s0:SubmitPoyHttpGetIn"/> <output message="s0:SubmitPoyHttpGetOut"/> </operation> <operation name="IsDoneYet"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"> The client must periodically poll the service after it submits its job so it knows when its job is done. The 'IsDoneYet' method does just that and returns true if the job is done and false if the job is not done yet. The command value can ether be 'poy' or 'GenPhen' </wsdl:documentation> <input message="s0:IsDoneYetHttpGetIn"/> <output message="s0:IsDoneYetHttpGetOut"/> </operation> </portType> <portType name="PoyServiceHttpPost"> <operation name="Init"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">The 'Init' method basically creates a directory on the super computer it returns a token that must be used on all subsequent method calls as the jobId parameter.Note this token will only work with the ipaddress that was used to call this method. Note it is not enforced but it highly encouraged to use this method over https. to get a pass prase to use this web service please vist http://glenn-webservice.bmi.ohio-state.edu/Application.aspx The current to option for resource are Glenn and supradev</wsdl:documentation> <input message="s0:InitHttpPostIn"/> <output message="s0:InitHttpPostOut"/> </operation> <operation name="DeleteJob"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">This method removes all files on the super computer for this job</wsdl:documentation> <input message="s0:DeleteJobHttpPostIn"/> <output message="s0:DeleteJobHttpPostOut"/> </operation> <operation name="AddFile"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">The 'AddFile' method is used to basically put a file on the super computer. It should be called once to a load a .poy script. Plus it should be called for each file that the POY script references. It is the responsibility of the downstream client developer to generate the POY scripts this places more work in there hands but also give them great flexibility to design web apps that can use POY for anything. Note: there is a bug and the method won't work if there is a space in any of the file names </wsdl:documentation> <input message="s0:AddFileHttpPostIn"/> <output message="s0:AddFileHttpPostOut"/> </operation> <operation name="AddTextFile"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">The AddTextFile method is an alternative to the Add File command. This function allows the permissioned user to add a file as a simple string instead of using binary data in the fileData field.</wsdl:documentation> <input message="s0:AddTextFileHttpPostIn"/> <output message="s0:AddTextFileHttpPostOut"/> </operation> <operation name="GetFile"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">The GetFile method is utilized to retrieve the output files specified in the Poy script. This function is called once per file </wsdl:documentation> <input message="s0:GetFileHttpPostIn"/> <output message="s0:GetFileHttpPostOut"/> </operation> <operation name="GetZipedFile"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">The GetZipedFile is a second method that can be used to retrieve an output file. This command allows the user to compress the file prior to retrieving it. </wsdl:documentation> <input message="s0:GetZipedFileHttpPostIn"/> <output message="s0:GetZipedFileHttpPostOut"/> </operation> <operation name="GetTextFile"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">The basically 'GetFile' but returns a string instead of binary data should only be used on text files</wsdl:documentation> <input message="s0:GetTextFileHttpPostIn"/> <output message="s0:GetTextFileHttpPostOut"/> </operation> <operation name="SubmitPoy"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"> The 'SubmitPoy' method start a job on the super computer that start the POY job. When running a job on a super computer you have to request a what resource you need like how many processors, how many nodes, how much memory and how long it will take. If you ask for a lot of resources your job could get scheduled for a future date instead of running immediately. So it would not be suitable for realtime-ish apps. On the other hand if you request to little resources your job might not finish. Also we could extend the web service by adding new method that are similar to this one but only use other back-end Linux tools. These methods could take advantage of all of the existing infrastructure. </wsdl:documentation> <input message="s0:SubmitPoyHttpPostIn"/> <output message="s0:SubmitPoyHttpPostOut"/> </operation> <operation name="IsDoneYet"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"> The client must periodically poll the service after it submits its job so it knows when its job is done. The 'IsDoneYet' method does just that and returns true if the job is done and false if the job is not done yet. The command value can ether be 'poy' or 'GenPhen' </wsdl:documentation> <input message="s0:IsDoneYetHttpPostIn"/> <output message="s0:IsDoneYetHttpPostOut"/> </operation> </portType> <binding name="PoyServiceSoap" type="s0:PoyServiceSoap"> <soap:binding transport="http://schemas.xmlsoap.org/soap/http"/> <operation name="Init"> <soap:operation soapAction="supramap/Init" style="document"/> <input> <soap:body use="literal"/> </input> <output> <soap:body use="literal"/> </output> </operation> <operation name="DeleteJob"> <soap:operation soapAction="supramap/DeleteJob" style="document"/> <input> <soap:body use="literal"/> </input> <output> <soap:body use="literal"/> </output> </operation> <operation name="AddFile"> <soap:operation soapAction="supramap/AddFile" style="document"/> <input> <soap:body use="literal"/> </input> <output> <soap:body use="literal"/> </output> </operation> <operation name="AddTextFile"> <soap:operation soapAction="supramap/AddTextFile" style="document"/> <input> <soap:body use="literal"/> </input> <output> <soap:body use="literal"/> </output> </operation> <operation name="GetFile"> <soap:operation soapAction="supramap/GetFile" style="document"/> <input> <soap:body use="literal"/> </input> <output> <soap:body use="literal"/> </output> </operation> <operation name="GetZipedFile"> <soap:operation soapAction="supramap/GetZipedFile" style="document"/> <input> <soap:body use="literal"/> </input> <output> <soap:body use="literal"/> </output> </operation> <operation name="GetTextFile"> <soap:operation soapAction="supramap/GetTextFile" style="document"/> <input> <soap:body use="literal"/> </input> <output> <soap:body use="literal"/> </output> </operation> <operation name="SubmitPoy"> <soap:operation soapAction="supramap/SubmitPoy" style="document"/> <input> <soap:body use="literal"/> </input> <output> <soap:body use="literal"/> </output> </operation> <operation name="IsDoneYet"> <soap:operation soapAction="supramap/IsDoneYet" style="document"/> <input> <soap:body use="literal"/> </input> <output> <soap:body use="literal"/> </output> </operation> </binding> <binding name="PoyServiceSoap12" type="s0:PoyServiceSoap12"> <soap12:binding transport="http://schemas.xmlsoap.org/soap/http"/> <operation name="Init"> <soap12:operation soapAction="supramap/Init" style="document"/> <input> <soap12:body use="literal"/> </input> <output> <soap12:body use="literal"/> </output> </operation> <operation name="DeleteJob"> <soap12:operation soapAction="supramap/DeleteJob" style="document"/> <input> <soap12:body use="literal"/> </input> <output> <soap12:body use="literal"/> </output> </operation> <operation name="AddFile"> <soap12:operation soapAction="supramap/AddFile" style="document"/> <input> <soap12:body use="literal"/> </input> <output> <soap12:body use="literal"/> </output> </operation> <operation name="AddTextFile"> <soap12:operation soapAction="supramap/AddTextFile" style="document"/> <input> <soap12:body use="literal"/> </input> <output> <soap12:body use="literal"/> </output> </operation> <operation name="GetFile"> <soap12:operation soapAction="supramap/GetFile" style="document"/> <input> <soap12:body use="literal"/> </input> <output> <soap12:body use="literal"/> </output> </operation> <operation name="GetZipedFile"> <soap12:operation soapAction="supramap/GetZipedFile" style="document"/> <input> <soap12:body use="literal"/> </input> <output> <soap12:body use="literal"/> </output> </operation> <operation name="GetTextFile"> <soap12:operation soapAction="supramap/GetTextFile" style="document"/> <input> <soap12:body use="literal"/> </input> <output> <soap12:body use="literal"/> </output> </operation> <operation name="SubmitPoy"> <soap12:operation soapAction="supramap/SubmitPoy" style="document"/> <input> <soap12:body use="literal"/> </input> <output> <soap12:body use="literal"/> </output> </operation> <operation name="IsDoneYet"> <soap12:operation soapAction="supramap/IsDoneYet" style="document"/> <input> <soap12:body use="literal"/> </input> <output> <soap12:body use="literal"/> </output> </operation> </binding> <binding name="PoyServiceHttpGet" type="s0:PoyServiceHttpGet"> <http:binding verb="GET"/> <operation name="Init"> <http:operation location="/Init"/> <input> <http:urlEncoded/> </input> <output> <mime:mimeXml part="Body"/> </output> </operation> <operation name="DeleteJob"> <http:operation location="/DeleteJob"/> <input> <http:urlEncoded/> </input> <output> <mime:mimeXml part="Body"/> </output> </operation> <operation name="AddFile"> <http:operation location="/AddFile"/> <input> <http:urlEncoded/> </input> <output> <mime:mimeXml part="Body"/> </output> </operation> <operation name="AddTextFile"> <http:operation location="/AddTextFile"/> <input> <http:urlEncoded/> </input> <output> <mime:mimeXml part="Body"/> </output> </operation> <operation name="GetFile"> <http:operation location="/GetFile"/> <input> <http:urlEncoded/> </input> <output> <mime:mimeXml part="Body"/> </output> </operation> <operation name="GetZipedFile"> <http:operation location="/GetZipedFile"/> <input> <http:urlEncoded/> </input> <output> <mime:mimeXml part="Body"/> </output> </operation> <operation name="GetTextFile"> <http:operation location="/GetTextFile"/> <input> <http:urlEncoded/> </input> <output> <mime:mimeXml part="Body"/> </output> </operation> <operation name="SubmitPoy"> <http:operation location="/SubmitPoy"/> <input> <http:urlEncoded/> </input> <output> <mime:mimeXml part="Body"/> </output> </operation> <operation name="IsDoneYet"> <http:operation location="/IsDoneYet"/> <input> <http:urlEncoded/> </input> <output> <mime:mimeXml part="Body"/> </output> </operation> </binding> <binding name="PoyServiceHttpPost" type="s0:PoyServiceHttpPost"> <http:binding verb="POST"/> <operation name="Init"> <http:operation location="/Init"/> <input> <mime:content type="application/x-www-form-urlencoded"/> </input> <output> <mime:mimeXml part="Body"/> </output> </operation> <operation name="DeleteJob"> <http:operation location="/DeleteJob"/> <input> <mime:content type="application/x-www-form-urlencoded"/> </input> <output> <mime:mimeXml part="Body"/> </output> </operation> <operation name="AddFile"> <http:operation location="/AddFile"/> <input> <mime:content type="application/x-www-form-urlencoded"/> </input> <output> <mime:mimeXml part="Body"/> </output> </operation> <operation name="AddTextFile"> <http:operation location="/AddTextFile"/> <input> <mime:content type="application/x-www-form-urlencoded"/> </input> <output> <mime:mimeXml part="Body"/> </output> </operation> <operation name="GetFile"> <http:operation location="/GetFile"/> <input> <mime:content type="application/x-www-form-urlencoded"/> </input> <output> <mime:mimeXml part="Body"/> </output> </operation> <operation name="GetZipedFile"> <http:operation location="/GetZipedFile"/> <input> <mime:content type="application/x-www-form-urlencoded"/> </input> <output> <mime:mimeXml part="Body"/> </output> </operation> <operation name="GetTextFile"> <http:operation location="/GetTextFile"/> <input> <mime:content type="application/x-www-form-urlencoded"/> </input> <output> <mime:mimeXml part="Body"/> </output> </operation> <operation name="SubmitPoy"> <http:operation location="/SubmitPoy"/> <input> <mime:content type="application/x-www-form-urlencoded"/> </input> <output> <mime:mimeXml part="Body"/> </output> </operation> <operation name="IsDoneYet"> <http:operation location="/IsDoneYet"/> <input> <mime:content type="application/x-www-form-urlencoded"/> </input> <output> <mime:mimeXml part="Body"/> </output> </operation> </binding> <service name="PoyService"> <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"> The Application to use the following web service can be found <a href='http://poyws.osc.edu/Application.aspx'>here</a> <br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>( Note: do not use space in any of the file names) </wsdl:documentation> <port name="PoyServiceSoap" binding="s0:PoyServiceSoap"> <soap:address location="http://poyws.osc.edu/PoyService.asmx"/> </port> <port name="PoyServiceSoap12" binding="s0:PoyServiceSoap12"> <soap12:address location="http://poyws.osc.edu/PoyService.asmx"/> </port> <port name="PoyServiceHttpGet" binding="s0:PoyServiceHttpGet"> <http:address location="http://poyws.osc.edu/PoyService.asmx"/> </port> <port name="PoyServiceHttpPost" binding="s0:PoyServiceHttpPost"> <http:address location="http://poyws.osc.edu/PoyService.asmx"/> </port> </service> </definitions> |