What is REST?

REST abstract:

• REST is the short form of Representational State Transfer.
• REST is architectural style web service which is based on web standards and http protocols (get, post, put, delete).
• REST was invented by Roy Fielding in 2000. 
• In REST architecture, everything are consider as resource, these resources access could be access by common interface based on the HTTP standard methods (get, post, put, delete).
• In REST architecture, there is server & client relationship. Server provides and controls the access to the resources; where as client access and modify the resources. 
• REST support all the common HTTP operations and resources are accessed by URI. 
• REST allow that resources to have different representational styles such as TEXT, HTML, XML, JSON, etc. 
• We can create RESTFUL web service using follow methods:
• Jersey
• REST Easy

Configuration of a REST message

A REST message contains the following elements:

• Endpoint: is the URL of the data to be retrieved, updated or deleted. The endpoint can be defined at the top level of the message, at the function level, or in the REST message workflow activity. The endpoint configured in the activity takes precedence over the other endpoints defined. 
• Headers: The HTTP headers in REST messages carry the information about the data format. They apply to all functions in that message unless the header is overridden  in the function definitions. Headers cannot be set in the REST message workflow activity. 
• Functions: REST message functions are the HTTP functions (put, post, get, delete) that interact with the data at the endpoint. Use the function definitions to override either the endpoint of header defined in the REST message. Each REST message workflow activity calls a single function to perform work on the endpoint.

Integration between HP ALM and ServiceNow (draft)

The objective of this post is simple, discuss the integration between HP ALM (version 11) and Service Now.

HP ALM v11 - Integration Overview / API:

• ALM 11.00 provides 2 methods of integration - OTA (Open Test Architecture) & REST (Representational State Transfer).  
• ALM 11.00 can use Client-Side Deployment so that a client can connect to more than one ALM platform. This affects OTA in following ways:
• The OTA type library is no longer registered automatically in the client machine. Before connecting to an ALM Platform with an OTA application, register the library for the server by running HP ALM Client Registration from the ALM Add-ins page. (refer Registering ALM on a Workstation in the HP ALM Installation Guide for more info.)
• The installation of custom test types has changed. (refer HP ALM Custom Test Type Guide for more info.)

• ALM 11.00 can now support REST. (refer HP ALM REST API reference.)

Service Now (SNOW) - Integration Overview / API:

• 
  

Reference URL: Click here