Application Integration (On-Premises) : Service Development : Working with REST
Working with REST
 
Creating a REST Resource
About the REST Resource Folder
REST (Representational State Transfer) is an architectural style that requires web applications to support the HTTP GET, POST, PUT, and DELETE methods and to use a consistent, application-independent interface. Integration Server can act as a REST server or a REST client.
When Integration Server acts as a REST client, Integration Server sends specifically formatted requests to the REST server.
For Integration Server to act as a REST server, it must host services that perform the GET, PUT, POST, and DELETE functions. These services perform functions that are specific to your application. At a minimum, these services must:
*Be located in a REST resource folder whose fully qualified name is unique across the entire Integration Server namespace.
*Be named _get, _put, _post, _delete, or _default.
*Accept certain predefined input parameters that are passed in through the REST request.
Note:  
While the services _get, _put,_post, _delete, or _default might appear to be regular services, it is the naming convention and location of the services that instruct Integration Server to treat them as a REST resource.
When Integration Server acts as a REST client, Integration Server sends specifically formatted requests to the REST server.
Note:  
For more information about working with REST services in Integration Server, see the REST Developer’s Guide.
Copyright © 2015- 2016 Software AG, Darmstadt, Germany.
Product LogoContact Support   |   Community   |   Feedback