IP Library Patent Application 13212641
Patent Application
App. No. 13/212,641

MODEL-DRIVEN REST CONSUMPTION FRAMEWORK

Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US None
App. No.
13/212,641
Abstract

The present disclosure describes methods, systems, and computer program products for implementing web services. One method includes identifying a REST service for integration with a business application, identifying a set of metadata associated with the REST service, and generating a REST client proxy object associated with the REST service for use in consuming the REST service with the business application, where an instantiation of the REST client proxy object is consumable via the business application. In some instances, the method may include consuming the REST service using an instantiation of the generated REST client proxy object associated with the REST service. Further, the identified set of metadata associated with the REST service may include a service structure document and a metadata document. Generating the REST client proxy object may include generating at least one business configuration object and/or at least one authentication proxy artifact associated with the REST service.

Claims (38)

1 . A computer program product for implementing web services, the computer program product comprising computer readable instructions embodied on tangible, non-transitory media, the instructions operable when executed to:

identify a REST service for integration with a business application;

identify a set of metadata associated with the REST service; and

generate a REST client proxy object associated with the REST service for use in consuming the REST service with the business application, where an instantiation of the REST client proxy object is consumable via the business application.

2 . The product of claim 1 , the operations further operable when executed to consume the REST service using an instantiation of the generated REST client proxy object associated with the REST service.

3 . The product of claim 1 , wherein the REST service is available at a web-accessible location (URL).

4 . The product of claim 1 , wherein the identified set of metadata associated with the REST service includes a service structure document and a metadata document.

5 . The product of claim 2 , wherein generating the REST client proxy object includes generating at least one business configuration object associated with the REST client proxy object, each business configuration object defining at least one option for consuming the REST service.

6 . The product of claim 5 , wherein consuming the REST service using the instantiation of the generated REST client proxy object associated with the REST service includes selecting a particular business configuration object to consume the REST service with the at least one defined option associated with the particular business configuration object selected.

7 . The product of claim 5 , wherein each business configuration object identifies a particular URL associated with the at least one option for consuming the REST service.

8 . The product of claim 2 , wherein generating the REST client proxy object includes generating at least one authentication proxy artifact associated with the REST service, each authentication proxy artifact defining at least one authentication method accepted by the REST service.

9 . The product of claim 8 , wherein consuming the REST service using the instantiation of the generated REST client proxy object associated with the REST service includes using a particular authentication proxy artifact by the REST client proxy object to satisfy at least one authentication requirement associated with the REST service.

10 . The product of claim 2 , wherein consuming the REST service using the instantiation of the generated REST client proxy object associated with the REST service includes:

receiving input from the business application associated with the REST client proxy object; and

calling the REST service using the REST client proxy object and the received input.

11 . The product of claim 1 , the instructions operable when executed to:

receive a set of output data from the REST service via the REST client proxy object; and

integrating the received set of output data into operations of the business application.

12 . A computer-implemented method for implementing web services, the method comprising:

identifying a REST service for integration with a business application;

identifying a set of metadata associated with the REST service; and

generating a REST client proxy object associated with the REST service for use in consuming the REST service with the business application, where an instantiation of the REST client proxy object is consumable via the business application.

13 . The method of claim 12 , the method further comprising to consuming the REST service using an instantiation of the generated REST client proxy object associated with the REST service.

14 . The method of claim 12 , wherein the identified set of metadata associated with the REST service includes a service structure document and a metadata document.

15 . The method of claim 13 , wherein generating the REST client proxy object includes generating at least one business configuration object associated with the REST client proxy object, each business configuration object defining at least one option for consuming the REST service.

16 . The method of claim 15 , wherein consuming the REST service using the instantiation of the generated REST client proxy object associated with the REST service includes selecting a particular business configuration object to consume the REST service with the at least one defined option associated with the particular business configuration object selected.

17 . The method of claim 15 , wherein each business configuration object identifies a particular URL associated with the at least one option for consuming the REST service.

18 . The method of claim 13 , wherein generating the REST client proxy object includes generating at least one authentication proxy artifact associated with the REST service, each authentication proxy artifact defining at least one authentication method accepted by the REST service.

19 . The method of claim 18 , wherein consuming the REST service using the instantiation of the generated REST client proxy object associated with the REST service includes using a particular authentication proxy artifact by the REST client proxy object to satisfy at least one authentication requirement associated with the REST service.

20 . The method of claim 13 , wherein consuming the REST service using the instantiation of the generated REST client proxy object associated with the REST service includes:

receiving input from the business application associated with the REST client proxy object; and

calling the REST service using the REST client proxy object and the received input.

21 . A system comprising:

one or more computers; and

a computer-readable medium coupled to the one or more computers having instructions stored thereon which, when executed by the one or more computers, cause the one or more computers to perform operations comprising:

identifying a REST service for integration with a business application;

identifying a set of metadata associated with the REST service; and

generating a REST client proxy object associated with the REST service for use in consuming the REST service with the business application, where an instantiation of the REST client proxy object is consumable via the business application.

Assignments (2)
CHANGE OF NAME Recorded Aug 26, 2014
From: SAP AG
To: SAP SE
Reel/Frame 033625/0223 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 9, 2011
From: SAID, BARE; BAEUERLE, STEFAN; HERTER, KLAUS; ERBE, LARS
To: SAP AG
Reel/Frame 026882/0406 →