# US 2017/0251075 A1 · Enterprise service bus sequencer

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0251075 A1
- Document ID: US20170251075A1
- Status: Published application
- Kind: A1
- Application number: 15/500,926
- Filed: 2015-01-28
- Published: 2017-08-31
- Earliest claimed: 2015-01-28
- Assignees: Hewlett Packard Enterprise Development LP
- Applicants: Hewlett Packard Enterprise Development LP
- Inventors: Scott LOPEZ; Jeff KALIBJIAN
- Web page: https://patentgrep.com/patent/US20170251075A1

## CPC

- H04L 67/60: Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources (admission control or resource allocation H04L47/70)
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

In one example, an Enterprise Service Bus (ESB) Sequencer may receive a request token that includes a plurality of ESB requests. The request token may be parsed into a plurality of service frames. Verification confirms a) each of the plurality of ESB requests are valid and corresponding services available and b) sufficient computing resources are available to complete each of the plurality of ESB requests. For each of the plurality of service frames an ESB may be called using a requested input source and format provided in the request token for the service frame. The respective output source from the ESB is received and stored. The respective output source may be used as an input source for one or more other service frames. One or more service frame output sources as requested by the request token may be sent to a calling application.

## Claims

### Claim 1

A method to process a sequence of Enterprise Service Bus (ESB) requests for an ESB, comprising:
receiving from a calling application a request token that includes a plurality of ESB requests parsable into multiple service frames and a temporal target instance;
verifying the request token by:
confirming that each the plurality of ESB requests are valid and corresponding services available,
confirming that sufficient computing resources are available to complete each the plurality of ESB requests, and
confirming the entire plurality of ESB requests can be completed by the temporal target instance, if present;
for each of the multiple service frames, calling the ESB using a requested input source and format specified in the request token for the service frame, receiving an output source from the ESB, and storing the output source from the ESB in a requested format wherein the output source stored may be used as an input source for one or more other service frames; and
sending one or more service frame output sources as requested by the request token to the calling application.

### Claim 2 (depends on 1)

The method of claim 1 wherein the step of verifying the request token comprises validating over the set of multiple service frames a digital signature.

### Claim 3 (depends on 1)

The method of claim 1 wherein storing the output source from the ESB comprises storing the result output source in an independent ESB result manager to protect the output source to allow it to be securely propagated forward as an input source to a subsequent service frame.

### Claim 4 (depends on 1)

The method of claim 1 further comprising the step of logging the request token, the ESB requests and their respective input sources and output sources in an ESB Audit system.

### Claim 5 (depends on 1)

The method of claim 1 further comprising the step of providing tracking and monitoring of the plurality of ESB requests based on the request token.

### Claim 6

An Enterprise Service Bus (ESB) Sequencer to process a sequence of ESB requests for an ESB, comprising:
a communication interface to receive a request token from a calling application that includes a plurality of ESB requests;
a parser module to parse the request token into a plurality of service frames and a temporal target instance, if present;
a verification module to confirm a) each of the plurality of ESB requests are valid and corresponding services available, b) sufficient computing resources are available to complete each of the plurality of ESB requests, and c) if present, that the entire plurality of ESB request can be completed by the temporal target instance; and
a sequencer module to a) call the ESB for each of the plurality of service frames using a requested input source and format provided in the request token for the service frame, b) receive an output source from the ESB, and c) store the output source, wherein the output source may be used as an input source for one or more other service frames and wherein the communication interface is to send one or more service frame output sources as requested by the request token to the calling application.

### Claim 7 (depends on 6)

The system of claim 6, wherein the verification module is also to validate over the plurality of service frames a digital signature.

### Claim 8 (depends on 6)

The system of claim 6 further comprising an ESB result manager to protect the output source to allow it to be securely propagated forward as an input source to a subsequent service frame.

### Claim 9 (depends on 6)

The system of claim 6 further comprising an ESB audit system to log the request token, the ESB requests and their respective input sources and output sources.

### Claim 10 (depends on 6)

The system of claim 6 further comprising a tracking and monitoring module to communicate the current state of the sequence module calls to the ESB based on the request token.

### Claim 11

A non-transitory computer readable memory (CRM) comprising instructions executable by a processor to:
parse a request token having a plurality of Enterprise Service Bus (ESB) requests into a plurality of service frames;
for each service frame,
verify that a) each of the plurality of ESB requests are valid and that corresponding ESB services are available, and b) sufficient computing resources are available to complete each of the plurality of ESB requests,
call the ESB using a requested input source and format provided in the request token for the service frame,
receive a respective service frame output source from the ESB wherein the respective output source may be used as an input source for one or more other service frames; and
send one or more service frame output sources as requested by the request token to a calling application.

### Claim 12 (depends on 11)

The CRM of claim 11 wherein the instructions are also executable to validate a digital signature over the plurality of service frames.

### Claim 13 (depends on 11)

The CRM of claim 11 wherein the instructions are also executable to send to an ESB result manager the respective output source to protect it and allow it to be securely propagated forward as an input source to a subsequent service frame.

### Claim 14 (depends on 11)

The CRM of claim 11 wherein the instructions are also executable to log the request token, the ESB requests and their respective input sources and respective output sources to an ESB audit system.

### Claim 15 (depends on 11)

The CRM of claim 11 wherein the instructions are also executable to confirm that the entire plurality of ESB request can be completed by a temporal target instance, if present.
