After you start the eXtreme Scale REST data service, you can use any HTTP client to interact with it. A Web browser, PHP client, Java client or WCF Data Services client can be used to issue any of the supported request operations.
The REST service implements a subset of the Microsoft Atom Publishing Protocol: Data Services URI and Payload Extensions specification, Version 1.0 which is part of OData protocol. This chapter describes which of the features of the specification are supported and how they are mapped to eXtreme Scale.
Microsoft WCF Data Services typically defines a service per data source or entity model. The eXtreme Scale REST data service defines a service per defined ObjectGrid. Each ObjectGrid that is defined in the eXtreme Scale ObjectGrid client override XML file is automatically exposed as a separate REST service root.
The URI for the service root is:
http://<host>:<port>/<contextroot>/restservice/<gridname>
Where contextroot is defined when the REST data service application is deployed, and is dependent on the application server, and gridname is the name of the ObjectGrid.
Request types
The following list describes the Microsoft WCF Data Services request types which the eXtreme Scale REST data service supports.
For details on each request type that WCF Data Services supports, see:
http://msdn.microsoft.com/en-us/library/dd541602%28PROT.10%29.aspx
For additional information, see:
http://msdn.microsoft.com/en-us/library/dd541376(PROT.10).aspx
For additional information, see:
http://msdn.microsoft.com/en-us/library/dd541376(PROT.10).aspx
Clients can delete resources using the DELETE HTTP verb with the following limitations:
For additional information, see:
http://msdn.microsoft.com/en-us/library/dd541534(PROT.10).aspx
Clients can retrieve resources using the GET HTTP verb with the following limitations:
For additional information, see:
http://msdn.microsoft.com/en-us/library/dd541450(PROT.10).aspx
For additional information, see:
http://msdn.microsoft.com/en-us/library/dd541320(PROT.10).aspx
Partition routing is based on the root entity. A request URI infers a root entity if its resource path starts with a root entity or with an entity that has a direct or indirect association to the entity.
In a partitioned environment, any request that cannot infer a root entity will be rejected. Any request that infers a root entity will be routed to the correct partition.
For additional information on defining a schema with associations and root entities, see section in this document and the partitioning topic in the Product Overview of the WebSphere eXtreme Scale documentation.
Invoke request
Invoke requests are not supported.
For additional information, see:
http://msdn.microsoft.com/en-us/library/dd541482(PROT.10).aspx
Batch request
Clients can batch multiple Change Sets or Query Operations within a single request. This can reduce the number of round trips to the server and allows multiple requests to participate in a single transaction.
For additional information, see:
http://msdn.microsoft.com/en-us/library/dd541539(PROT.10).aspx
Tunneled requests
Tunneled requests are not supported.
For additional information, see:
http://msdn.microsoft.com/en-us/library/dd541243(PROT.10).aspx