- Informatica ActiveVOS
- All Products
<?xml version="1.0" encoding="UTF-8"?> <ns2:RESTRequest xmlns:ns2="http://schemas.activebpel.org /REST/2007/12/01/aeREST.xsd"> <ns2:subdomain>Search</ns2:subdomain> <ns2:method>GET</ns2:method> <ns2:pathInfo>V1</ns2:pathInfo> <ns2:params> <ns2:param name="temp" value="50"/> <ns2:param name="windchill" value="40"/> </ns2:params> <ns2:payload contentType="text/xml">lookUpWeather/mass/waltham?temp=50&windchill=40</ns2:payload> </ns2:RESTRequest>
Optional for partner service (invoke). The part that identifies one of the REST-based services that a domain can offer. For example Yahoo offers search, news, and other services. You can use the subdomain part to specify the service you want to use. In the endpoint reference for the partner link, you can add a logical subdomain value that can be replaced by the subdomain specified:
The HTTP method to execute. See the
HTTP Methodstable below.
Optional for partner service (invoke). Parts that extends the resource details defined in WS-Address. For example, in
search.yahooapis.com, you can specify the path info for the search service, version number, and specific type of search:
(Optional) Query parameters specified by the REST service you want to address.
(Optional). HTTP headers containing connection, host, content type and other request details.
(Optional) The representation of the resource. This data can be character data or XML data. If it is character data, you should include the
(Optional) The string shown as it is formatted in the request. Contains parameters in the order they are specified.
(Optional) Value populated for inbound requests (receives). This value is equivalent to the value returned by
The value can be one of the following: BASIC, FORM, CLIENT_CERT or DIGEST
(Optional) Boolean. True if the request is sent as https.
(Optional) The application called in the request.
(Optional) The location of the service where the request is made.
(Optional). The ISO 639 Codes for country and languages. For example,
<locale country="US" lang="en">en_US </locale>
Asks for the response identical to the one that would correspond to a GET request, but without the response body. This is useful for retrieving meta-information written in response headers, without having to transport the entire content.
Requests a representation of the specified resource
Submits data to be processed (for example, from an HTML form) to the identified resource. The data is included in the body of the request. This can result in the creation of a new resource or the updates of existing resources or both.
Uploads a representation of the specified resource
Deletes the specific resource.
(Not supported for receives) Echoes back the received request so that a client can see what intermediate servers are adding or changing in the request.
Returns the HTTP methods the server supports. This can be used to check the functionality of a web server.
(CURRENTLY NOT SUPPORTED) Converts the request connection to a transparent TCP/IP tunnel, usually to facilitate SSL-encrypted communication (HTTPS) through an unencrypted HTTP proxy.
<rest:RESTResponse xmlns:rest="http://schemas.activebpel.org/REST/2007/12/01/aeREST.xsd" statusCode="1"> <!--Optional:--> <rest:headers> <!--Optional:--> <rest:header name="string" value="string"/> </rest:headers> <!--Optional:--> <rest:payload contentType="string"> <!-- Payload information --> </rest:payload> </rest:RESTResponse>
<rest:RESTFault xmlns:rest="http://schemas.activebpel.org/REST/2007/12/01/aeREST.xsd" errorType="transport"> <rest:errorCode>400</rest:errorCode> <rest:message>Bad Request</rest:message> <rest:messageDetails>The request cannot be fulfilled due to bad syntax</rest:messageDetails> </rest:RESTFault>