System and method for supporting representational state transfer services natively in a service bus runtime

Patent metadata

Field	Value
Publication number	US-9652269-B2
Application number	US-201615088772-A
Country	US
Kind code	B2
Filing date	Apr 1, 2016
Priority date	Apr 3, 2015
Publication date	May 16, 2017
Grant date	May 16, 2017

Abstract

In accordance with an embodiment, described herein is a system and method for supporting REST services natively in a service bus runtime. The service bus runtime can include one or more native REST proxy services, one or more native REST pipelines, and one or more native REST reference services. A native REST proxy service can deliver a message payload of a REST native format into a native REST pipeline, which can process the payload without converting the payload to or from an XML-based Simple Object Access Protocol (SOAP) format. JavaScript code can be supported in the pipeline to manipulate the message payload. A REST branch node can be used in the service bus runtime to route a message based on an HTTP verb or a relative URL path in a header of the message.

First claim

What is claimed is:

1. A system for supporting representational state transfer (REST) services in a service bus runtime, comprising:
a computer including one or more microprocessors;
a service bus runtime, executing on an application server on the computer, that includes a native REST reference service, a native REST proxy service, a native REST pipeline associated with the native REST proxy service, and a processing engine;
wherein the native REST pipeline defines an action that retrieves and updates message context variables, and a REST branch node for implementing a branching logic for message routing;
wherein the processing engine provides bindings for the message context variables and executes code in the action;
wherein the REST branch node is configured with a plurality of branches, each branch with a branch label specifying one or more of an HTTP verb or a URL path; and
wherein the service bus runtime operates to
receive a message of a particular REST native format, wherein a header of the message includes an HTTP verb and a relative URL path, and
process the message, including using the defined action to manipulate the message context variables and using the REST branch node to route the message to a particular branch based on a mapping between the information in the message header and a particular branch label.

2. The system of claim 1 , wherein the particular REST native format is one of JavaScript Notation (JSON), XML, text, or binary.

3. The system of claim 1 , wherein the action is a JavaScript action, and the processing engine is a JavaScript engine.

4. The system of claim 3 , wherein an instance of the JavaScript engine is instantiated in the service bus runtime, and wherein a global object is provided in the JavaScript engine instance to be bound to the JavaScript action, to facilitate the JavaScript action retrieving and updating the context variables.

5. The system of claim 1 , wherein each of the native REST proxy service, the native REST pipeline and the native REST reference service is a typed native REST service, or a un-typed REST service.

6. The system of claim 1 , wherein the service bus runtime is an enterprise service bus runtime.

7. The system of claim 1 , wherein at least one branch label includes a parameterized path expression comprising one or more message context variables, wherein the one or more message context variables are automatically created by the service bus runtime and defined with values extracted from metadata in an inbound transport layer of the service bus runtime.

8. The system of claim 1 , wherein the native REST proxy service includes a routing options action for use by a user to specify one or more arguments selected from the group consisting of an HTTP verb, a relative path, a query parameter, and an accept header value, wherein the one or more arguments are used to invoke a REST service.

9. A method for supporting representational state transfer (REST) services in a service bus runtime, comprising:
providing a service bus runtime on an application server executing on a computer including one or more microprocessors, wherein the service bus runtime includes a native REST reference service, a native REST proxy service, and a native REST pipeline associated with the native REST proxy service;
configuring the native REST pipeline to define an action for use in retrieving and updating message context variables, and a REST branch node for implementing a branching logic for message routing, wherein the REST branch node is configured with a plurality of branches, each branch with a branch label specifying one or more of an HTTP verb or a URL path;
instantiating an instance of a processing engine that provides bindings for the message context variables, and executes code in the defined action; and
processing a message of a particular REST native format, wherein a header of the message includes an HTTP verb and a relative URL path, including using the defined action to manipulate the message context variables and using the REST branch node to route the message to a particular branch based on a mapping between the information in the message header and a particular branch label.

10. The method of claim 9 , wherein the particular REST native format is one of JavaScript Notation (JSON), XML, text, or binary.

11. The method of claim 9 , wherein the action is a JavaScript action, and the processing engine is a JavaScript engine.

12. The method of claim 11 , wherein an instance of the JavaScript engine is instantiated in the service bus runtime, and wherein a global object is provided in the JavaScript engine instance to be bound to the JavaScript action, to facilitate the JavaScript action retrieving and updating the context variables.

13. The method of claim 9 , wherein each of the native REST proxy service, the native REST pipeline and the native REST reference service is a typed native REST service, or a un-typed REST service.

14. The method of claim 9 , wherein the service bus runtime is an enterprise service bus runtime.

15. The method of claim 9 , wherein at least one branch label includes a parameterized path expression comprising one or more message context variables, wherein the one or more message context variables are automatically created by the service bus runtime and defined with values extracted from metadata in an inbound transport layer of the service bus runtime.

16. A non-transitory computer-readable storage medium storing a set of instructions for supporting representational state transfer (REST) services in a service bus runtime, said instructions, when executed by one or more processors, causing the one or more processors to perform steps comprising:
providing a service bus runtime on an application server executing on a computer including one or more microprocessors, wherein the service bus runtime includes a native REST reference service, a native REST proxy service, and a native REST pipeline associated with the native REST proxy service;
configuring the native REST pipeline to define an action for use in retrieving and updating message context variables, and a REST branch node for implementing a branching logic for message routing, wherein the REST branch node is configured with a plurality of branches, each branch with a branch label specifying one or more of an HTTP verb or a URL path;
instantiating an instance of a processing engine that provides bindings for the message context variables, and executes code in the defined action; and
processing a message of a particular REST native format, wherein a header of the message includes an HTTP verb and a relative URL path, including using the defined action to manipulate the message context variables and using the REST branch node to route the message to a particular branch based on a mapping between the information in the message header and a particular branch label.

17. The non-transitory computer-readable storage medium of claim 16 , wherein the particular REST native format is one of JavaScript Notation (JSON), XML, text, or binary.

18. The non-transitory computer-readable storage medium of claim 16 , wherein the action is a JavaScript action, and the processing engine is a JavaScript engine.

19. The non-transitory computer-readable storage medium of claim 18 , wherein an instance of the JavaScript engine is instantiated in the service bus runtime, and wherein a global object is provided in the JavaScript engine instance to be bound to the JavaScript action, to facilitate the JavaScript action retrieving and updating

Assignees

• Oracle Int Corp

Inventors

• Prabhakar Kiran
• Fichtenholtz Greg
• Laloue Dimitri

Classifications

• G06F9/45529 Primary

  Embedded in an application, e.g. JavaScript in a Web browser · CPC title

• G06F9/546 Primary

  Message passing systems or structures, e.g. queues · CPC title

• G06F9/547

  Remote procedure calls [RPC]; Web services · CPC title

• G06F9/54

  Interprogram communication · CPC title