# US 2006/0069791 A1 · Service oriented architecture with interchangeable transport protocols

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

- Number: US 2006/0069791 A1
- Document ID: US20060069791A1
- Status: Published application
- Kind: A1
- Application number: 11/131,838
- Filed: 2005-05-18
- Published: 2006-03-30
- Earliest claimed: 2004-05-21
- Assignees: BEA Systems, Inc.
- Inventors: Paul Patrick; Ashok Aletty; Jayaram Kasi; Chet Kapoor; Tolga Urhan; Matthew Mihic
- Web page: https://patentgrep.com/patent/US20060069791A1

## CPC

- H04L 67/565: Conversion or adaptation of application format or content (adding application control or application functional data H04L67/561)
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/56: Provisioning of proxy services (store-and-forward switching systems in data switching networks H04L12/54)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A system, method and media for a service oriented architecture. This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects and objects of the invention can be obtained from a review of the specification, the figures and the claims.

## Claims

### Claim 1

A method for a service proxy, comprising:
accepting a message in a first representation from a first transport protocol;
converting the first representation to a second representation;
affording at least one message processing node the opportunity to process the second representation;
wherein the at least one message processing node implements an interface and/or a protocol that is compatible with the service proxy; and
wherein the first transport protocol supports at least one of: File Transport Protocol (FTP), Hypertext Transfer Protocol (HTTP), HTTP/Secure (HTTP/S), Simple Object Access Protocol (SOAP), Java Message Service (JMS), Web Services Reliable Messaging (WS-RM).

### Claim 2 (depends on 1)

The method of claim 1 wherein:
the service proxy is an intermediary between a client and one of: a service and another service proxy.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
converting the second representation to a third representation; and
providing via a second transport protocol the second representation to one of:
a service and another service proxy.

### Claim 4 (depends on 1)

The method of claim 1 wherein:
a transport protocol can be configured to follow a service level agreement.

### Claim 5 (depends on 1)

The method of claim 1 wherein:
a transport protocol can be configured for one of: asynchronous communication and synchronous communication.

### Claim 6 (depends on 1)

The method of claim 1 wherein:
a message processing node in the at least one message processing node can be added to or removed from then service proxy dynamically.

### Claim 7 (depends on 1)

The method of claim 1 wherein:
a transport protocol can be configured dynamically.

### Claim 8 (depends on 1)

The method of claim 1 wherein:
a message processing node in the at least one message processing node is capable of performing at least one of the following: message authentication, message authorization, message validation, message transformation, message routing, performance monitoring, message tracking, message archiving, message logging, message publication, error reporting, and a user-defined process.

### Claim 9 (depends on 1)

The method of claim 1 wherein:
the first transport protocol is provides communication between the service proxy and an endpoint.

### Claim 10

A machine readable medium having instructions stored thereon to cause a system to:
accept a message in a first representation from a first transport protocol;
convert the first representation to a second representation;
afford at least one message processing node the opportunity to process the second representation;
wherein the at least one message processing node implements an interface and/or a protocol that is compatible with a service proxy; and
wherein the first transport protocol supports at least one of: File Transport Protocol (FTP), Hypertext Transfer Protocol (HTTP), HTTP/Secure (HTTP/S), Simple Object Access Protocol (SOAP), Java Message Service (JMS), Web Services Reliable Messaging (WS-RM).

### Claim 11

A service proxy, comprising:
a first transport layer capable of accepting a message in a first representation over a first transport protocol;
a first component capable of converting the first representation to a second representation;
at least one message processing node capable of processing the second representation;
wherein the at least one message processing node implements an interface and/or a protocol that is compatible with the service proxy; and
wherein the first transport protocol supports at least one of: File Transport Protocol (FTP), Hypertext Transfer Protocol (HTTP), HTTP/Secure (HTTP/S), Simple Object Access Protocol (SOAP), Java Message Service (JMS), Web Services Reliable Messaging (WS-RM).

### Claim 12 (depends on 11)

The service proxy of claim 11 wherein:
the service proxy is an intermediary between a client and one of: a service and another service proxy.

### Claim 13 (depends on 11)

The service proxy of claim 11, further comprising:
a second component capable of converting the second representation to a third representation; and
a second transport layer capable of providing the third representation over a second transport protocol to one of: a service and another service proxy.

### Claim 14 (depends on 11)

The service proxy of claim 11 wherein:
a transport layer can be configured to follow a service level agreement.

### Claim 15 (depends on 11)

The service proxy of claim 11 wherein:
a transport protocol can be configured for one of: asynchronous communication and synchronous communication.

### Claim 16 (depends on 11)

The service proxy of claim 11 wherein:
a message processing node in the at least one message processing node can be added to or removed from then service proxy dynamically.

### Claim 17 (depends on 11)

The service proxy of claim 11 wherein:
a message processing node in the at least one message processing node can be configured dynamically.

### Claim 18 (depends on 11)

The service proxy of claim 11 wherein:
a message processing node in the at least one message processing node is capable of performing at least one of the following: message authentication, message authorization, message validation, message transformation, message routing, performance monitoring, message tracking, message archiving, message logging, message publication, error reporting, and a user-defined process.

### Claim 19 (depends on 11)

The service proxy of claim 11 wherein:
the first transport protocol is provides communication between the service proxy and an endpoint.
