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

• US 10,210,029 B2
• Filed: 04/10/2017
• Issued: 02/19/2019
• Est. Priority Date: 04/03/2015
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Prabhakar, Kiran, Fichtenholtz, Greg, Laloue, Dimitri
• Primary Examiner(s): Truong, Lechi
• Application Number:
  US15/483,136
• Publication Number:
  US 20170212795A1
• Time in Patent Office: 680 Days
• Field of Search: 719328
• CPC Class Codes: G06F 9/45529 Embedded in an application, e.g. JavaScript in a Web browser
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services

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.

Claims

1. A system for supporting end-to-end JavaScript Notation (JSON) messages in a service bus runtime, the system comprising:

a microprocessor; and

a service bus runtime executing on the microprocessor, wherein the service bus runtime comprises;

a plurality of representational state transfer (REST) services comprising a REST proxy service and a REST pipeline service;

a JavaScript Action; and

a JavaScript engine configured to execute javaScript code in the JavaScript action, wherein the service bus runtime, when receiving a JSON message having a JSON format and comprising a payload operates to;

receive the JSON message by the REST proxy service;

forward the JSON message by the REST proxy service to the REST pipeline service;

invoke the JavaScript engine to process the JSON message by manipulating the payload of the JSON message;

use the JavaScript action by the REST pipeline service to retrieve and update context variables associated with the JSON message; and

route the JSON message through the plurality of REST services while maintaining the JSON format of the message without converting the payload by the manipulating to or from a format other than a REST native type.

2. The system of claim 1, wherein the plurality of REST services further comprises a REST reference service.

3. The system of claim 1, wherein the JSON message is received by the REST proxy service, and forwarded by the REST proxy service to the REST pipeline service for the manipulating.

4. The system of claim 1, wherein:

the plurality of REST services further comprises a processing engine;

the processing engine provides bindings of the context variables associated with the JSON message and executes code in the JavaScript action; and

the service bus runtime operates to;

receive the JSON message of a particular REST native format, wherein a handler of the JSON message of the particular REST native format comprises an HTTP verb and a relative URL path; and

process the JSON message of the particular REST native format using the JavaScript action to manipulate the context variables.

5. The system of claim 1, wherein the REST proxy service comprises a routing options action for use by an associated 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 selected REST service.

6. The system of claim 1, wherein the REST pipeline service further comprises 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.

7. The system of claim 6, wherein the service bus runtime operates to use the REST branch node to route the JSON message to a particular branch based on a mapping between information in a message header and a particular branch label.

8. The system of claim 1, wherein the service bus runtime operates to route the JSON message through the plurality of REST services while maintaining the JSON format of the message without converting the payload to or from a format other than:

the JSON format;

an XML format;

a text format;

or a binary format.

9. The system of claim 1, wherein the service bus runtime operates to route the JSON message through the plurality of REST services while maintaining the JSON format of the message without converting the payload to or from an XML-based Simple Object Access Protocol (SOAP) format.

10. A method for supporting end-to-end JavaScript Notation (JSON) messages in a service bus runtime, the method comprising:

providing a service bus runtime executing on a microprocessor, wherein the service bus runtime comprises;

a plurality of representational state transfer (REST) services comprising a REST proxy service and a REST pipeline service;

a JavaScript Action; and

a JavaScript engine configured to execute javaScript code in the JavaScript action;

receiving a JSON message at the REST proxy service of the service bus runtime, the JSON message having a JSON format and comprising a payload;

forwarding the JSON message by the REST proxy service to the REST pipeline service;

processing the JSON message using the JavaScript engine to manipulate the payload of the JSON message;

using the JavaScript action by the REST pipeline service to retrieve and update context variables associated with the JSON message; and

routing the JSON message through the plurality of REST services while maintaining the JSON format of the message without converting the payload by the manipulating to or from a format other than a REST native type.

11. The method of claim 10, wherein the plurality of REST services further comprises a REST reference service.

12. The method of claim 10, wherein the JSON message is received by the REST proxy service, and forwarded by the REST proxy service to the REST pipeline service for the manipulating.

13. The method of claim 10, wherein:

the plurality of REST services further comprises a processing engine;

the processing engine provides bindings of the context variables associated with the JSON message and executes code in the JavaScript action; and

the service bus runtime operates to;

receive the JSON message of a particular REST native format, wherein a handler of the JSON message of the particular REST native format comprises an HTTP verb and a relative URL path; and

process the JSON message of the particular REST native format using the JavaScript action to manipulate the context variables.

14. The method of claim 10, wherein the REST proxy service comprises a routing options action for use by an associated 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 selected REST service.

15. The method of claim 10, wherein the REST pipeline service further comprises 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.

16. The method of claim 15, wherein the service bus runtime operates to use the REST branch node to route the JSON message to a particular branch based on a mapping between information in a message header and a particular branch label.

17. A non-transitory computer-readable storage medium storing a set of instructions for supporting end-to-end JavaScript Notation (JSON) messages 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 executing on a microprocessor, wherein the service bus runtime comprises;

a plurality of representational state transfer (REST) services comprising a REST proxy service and a REST pipeline service;

a JavaScript Action; and

a JavaScript engine configured to execute javaScript code in the JavaScript action;

receiving a JSON message at the REST proxy service of the service bus runtime, the JSON message having a JSON format and comprising a payload;

forwarding the JSON message by the REST proxy service to the REST pipeline service;

processing the JSON message using the JavaScript engine to manipulate the payload of the JSON message; and

using the JavaScript action by the REST pipeline service to retrieve and update context variables associated with the JSON message;

routing the JSON message through the plurality of REST services while maintaining the JSON format of the message without converting the payload by the manipulating to or from a format other than a REST native type.

18. The non-transitory computer-readable storage medium of claim 17, wherein the plurality of REST services further comprises a REST reference service.

19. The non-transitory computer-readable storage medium of claim 17, wherein the JSON message is received by the REST proxy service, and forwarded by the REST proxy service to the REST pipeline service for the manipulating.

20. The non-transitory computer-readable storage medium of claim 17, wherein:

the plurality of REST services further comprises a processing engine;

the processing engine provides bindings of the context variables associated with the JSON message and executes code in the JavaScript action; and

the service bus runtime operates to;

receive the JSON message of a particular REST native format, wherein a handler of the JSON message of the particular REST native format comprises an HTTP verb and a relative URL path; and

process the JSON message of the particular REST native format using the JavaScript action to manipulate the context variables.

21. The non-transitory computer-readable storage medium of claim 17, wherein the REST proxy service comprises a routing options action for use by an associated 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 selected REST service.

22. The non-transitory computer-readable storage medium of claim 17, wherein the REST pipeline service further comprises 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.