source: fedd/wsdl/fedd_messages.wsdl @ 61c71bf

axis_examplecompt_changesinfo-opsversion-1.30version-2.00version-3.01version-3.02
Last change on this file since 61c71bf was 338e9a7, checked in by Ted Faber <faber@…>, 16 years ago

Move wsdl stuff to its own directory

  • Property mode set to 100644
File size: 5.3 KB
Line 
1<?xml version="1.0"?>
2<definitions name="fedd"
3  targetNamespace="http://www.isi.edu/faber/fedd_messages"
4  xmlns:tns="http://www.isi.edu/faber/fedd_messages"
5  xmlns:xsd1="http://www.isi.edu/faber/fedd_types"
6  xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
7  xmlns="http://schemas.xmlsoap.org/wsdl/">
8
9  <!--
10  The message definitions are all simple embeddings of one of the types
11  from fedd_types.xsd
12  -->
13  <message name="RequestAccessRequestMessage">
14    <part name="RequestAccessRequestBody" type="xsd1:requestType"/>
15  </message>
16
17  <message name="RequestAccessResponseMessage">
18    <part name="RequestAccessResponseBody" type="xsd1:responseType"/>
19  </message>
20
21  <message name="ReleaseAccessRequestMessage">
22    <part name="ReleaseAccessRequestBody" type="xsd1:releaseRequestType"/>
23  </message>
24
25  <message name="ReleaseAccessResponseMessage">
26    <part name="ReleaseAccessResponseBody" type="xsd1:releaseResponseType"/>
27  </message>
28  <message name="CreateRequestMessage">
29    <part name="CreateRequestBody" type="xsd1:createRequestType"/>
30  </message>
31
32  <message name="CreateResponseMessage">
33    <part name="CreateResponseBody" type="xsd1:createResponseType"/>
34  </message>
35
36  <message name="VtopoRequestMessage">
37    <part name="VtopoRequestBody" type="xsd1:vtopoRequestType"/>
38  </message>
39
40  <message name="VtopoResponseMessage">
41    <part name="VtopoResponseBody" type="xsd1:vtopoResponseType"/>
42  </message>
43
44  <message name="VisRequestMessage">
45    <part name="VisRequestBody" type="xsd1:visRequestType"/>
46  </message>
47
48  <message name="VisResponseMessage">
49    <part name="VisResponseBody" type="xsd1:visResponseType"/>
50  </message>
51
52  <message name="InfoRequestMessage">
53    <part name="InfoRequestBody" type="xsd1:infoRequestType"/>
54  </message>
55
56  <message name="InfoResponseMessage">
57    <part name="InfoResponseBody" type="xsd1:infoResponseType"/>
58  </message>
59
60
61  <message name="TerminateRequestMessage">
62    <part name="TerminateRequestBody" type="xsd1:terminateRequestType"/>
63  </message>
64
65  <message name="TerminateResponseMessage">
66    <part name="TerminateResponseBody" type="xsd1:terminateResponseType"/>
67  </message>
68
69  <message name="FaultMessage">
70    <part name="FaultBody" type="xsd1:faultType"/>
71  </message>
72
73  <portType name="feddPortType">
74    <operation name="RequestAccess">
75      <documentation>
76        Request access to a testbed.  The request includes the various
77        resources needed (loosely), the identity of the requester, access
78        credentials andscheduling information.  A successful response includes
79        enough information for the federation system to access the testbed and
80        actually request resources.
81      </documentation>
82      <input message="tns:RequestAccessRequestMessage"/>
83      <output message="tns:RequestAccessResponseMessage"/>
84      <fault name="FeddFault" message="tns:FaultMessage"/>
85    </operation>
86    <operation name="ReleaseAccess">
87      <documentation>
88        Release an allocation of access to a testbed. This informs the testbed
89        that it is no longer necessary to allow the access mthods negotiated by
90        a RequestAccess cal.
91      </documentation>
92      <input message="tns:ReleaseAccessRequestMessage"/>
93      <output message="tns:ReleaseAccessResponseMessage"/>
94      <fault name="FeddFault" message="tns:FaultMessage"/>
95    </operation>
96    <operation name="Create">
97      <documentation>
98        A request to create a federated experiment from the included
99        description.  Credentials and access information is also provided.  On
100        success a logical description of the experiment is returned as well as
101        the information about federated testbeds needed to access local
102        services.
103      </documentation>
104      <input message="tns:CreateRequestMessage"/>
105      <output message="tns:CreateResponseMessage"/>
106      <fault name="FeddFault" message="tns:FaultMessage"/>
107    </operation>
108    <operation name="Vtopo">
109      <documentation>
110        A request for the virtual topology of the experiment.  Requesters with
111        different access rights may receive different information.
112      </documentation>
113      <input message="tns:VtopoRequestMessage"/>
114      <output message="tns:VtopoResponseMessage"/>
115      <fault name="FeddFault" message="tns:FaultMessage"/>
116    </operation>
117    <operation name="Vis">
118      <documentation>
119        A request for the visualization of the experiment.  This is really a
120        legacy interface for visual tools that cannot generate their own
121        visualization.  Requesters with different access rights may receive
122        different information.
123      </documentation>
124      <input message="tns:VisRequestMessage"/>
125      <output message="tns:VisResponseMessage"/>
126      <fault name="FeddFault" message="tns:FaultMessage"/>
127    </operation>
128    <operation name="Info">
129      <documentation>
130        A one-stop request for meta-data on the experiment.  Includes all the
131        info from a Vtopo and a Vis request.
132      </documentation>
133      <input message="tns:InfoRequestMessage"/>
134      <output message="tns:InfoResponseMessage"/>
135      <fault name="FeddFault" message="tns:FaultMessage"/>
136    </operation>
137    <operation name="Terminate">
138      <documentation>
139        Stop this experiment and deallocate its resources.
140      </documentation>
141      <input message="tns:TerminateRequestMessage"/>
142      <output message="tns:TerminateResponseMessage"/>
143      <fault name="FeddFault" message="tns:FaultMessage"/>
144    </operation>
145  </portType>
146</definitions>
Note: See TracBrowser for help on using the repository browser.