Web Service Interface Sample Clauses

Web Service Interface. According to the WP6 design philosophy the Pipeline Service has been designed around a Service Oriented Architecture (SOA). A preliminary draft Web Service interface has been presented in the Year 1 WP6 design deliverable D6. 1. This interface has been enhanced in response to the feedback from project partners. The webservice binding enables clients to interact with the Pipeline Service and perform various functions such as submission of workflows, tracking progress and various control functions. There are essentially four types of methods supported in the Pipeline Service. Submission methods expose functionality that enables a user to submit a workflow. Workflow Control methods expose functionality that enable interaction with currently executing workflows. The Pipeline Service Initialisation method is invoked to initialise a session with the Pipeline Service. Finally the Pipeline Service Internal methods are methods that enable interaction with internal components of the Pipeline Service. Specific parameters are required for various Pipeline Service methods. The following four parameters are generally used: SessionID, Workflow, UserCredentials and WorkflowID. The SessionID denotes the identifier used internally by the Pipeline Service to identity a specific user session. The Workflow argument denotes the actual workflow submitted by the user. The userCredentials argument denotes a credential provided by the user to identify the user. The WorkflowID argument used in the Workflow Control methods is the middleware-specific unique identifier for the workflow. The Pipeline Service API methods are as follows. Details of each method are provided in subsequent sections. • batch_submit(SessionID, Workflow) • int_submit(SessionID, Workflow)