Reliable updating for a service oriented architecture

• US 20060031431A1
• Filed: 05/19/2005
• Published: 02/09/2006
• Est. Priority Date: 05/21/2004
• Status: Abandoned Application

• Current Assignee: BEA Systems Incorporated (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Kasi, Jayaram, Mihic, Matthew, Urhan, Tolga, Kapoor, Chet, Aletty, Ashok, Patrick, Paul B.
• Application Number:
  US11/132,557
• Publication Number:
  US 20060031431A1
• Time in Patent Office: Days
• US Class Current: 709/220
• CPC Class Codes: H04L 41/06 Management of faults, events, alarms or notifications
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 41/5003 Managing SLA; Interaction between SLA and QoS
• CPC Class Codes: H04L 41/5009 Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
• CPC Class Codes: H04L 41/5074 Handling of user complaints or trouble tickets
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

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

1. A method for configuring at least one service proxy, comprising:

providing a configuration to at least one managed server;

accepting a response from the at least one managed server wherein the response indicates whether or not the configuration can be applied to a managed server that provided the response;

instructing the at least one managed server to either commit the configuration or to cancel the configuration; and

wherein the commit instruction is provided if each accepted response indicates success.

2. The method of claim 1 wherein:

the configuration is a delta.

3. The method of claim 1, further comprising:

applying the configuration to a service proxy in the at least one service proxy if the commit instruction is provided.

4. The method of claim 1 wherein:

the configuration includes at least one action to configure at least one component associated with a service proxy.

5. The method of claim 4 wherein:

an action is an instruction to;

delete a component, create a component, modify a component and rename a component.

6. The method of claim 4 wherein:

a component is one of;

a service definition for a service proxy, a message transformation, a message processing pipeline, a message processing stage in a message processing pipeline, a routing table, a message validation process, a message logging process, a message tracking process, a performance monitor, an error handler, a message authorization process, and a message authentication process.

7. The method of claim 1 wherein:

a service proxy is an intermediary between a client and one of;

a service and another service proxy.

17. The method of claim 1 wherein:

a service proxy is an intermediary between a client and one of;

a service and another service proxy.

8. A machine readable medium having instructions stored thereon to cause a system to:

provide a configuration to at least one managed server;

accept a response from the at least one managed server wherein the response indicates whether or not the configuration can be applied to a managed server that provided the response;

instruct the at least one managed server to either commit the configuration or to cancel the configuration; and

wherein the commit instruction is provided if each accepted response indicates success.

9. A system for configuring at least service proxy, comprising:

at least one component capable of performing the following steps;

providing a configuration to at least one managed server;

accepting a response from the at least one managed server wherein the response indicates whether or not the configuration can be applied to a managed server that provided the response;

providing to the at least one managed server one of the following instructions;

commit and cancel; and

wherein the commit instruction is provided if each accepted response indicates success otherwise the cancel instruction is provided.

10. A method for configuring a service proxy, comprising:

accepting a first configuration wherein the first configuration includes at least one action for configuring the service proxy;

performing the at least one action;

detecting an error in the performing; and

rolling back the at least one action.

11. The method of claim 10, further comprising:

providing an indication of failure to an administrative server; and

accepting a second configuration from the administrative server.

12. The method of claim 11 wherein:

the second configuration is a delta.

13. The method of claim 11 wherein:

the first configuration includes at least one component associated with the service proxy.

14. The method of claim 13 wherein:

an action is an instruction to;

delete a component, create a component, modify a component and rename a component.

15. The method of claim 13 wherein:

a component is one of;

a service definition for a service proxy, a message transformation, a message processing pipeline, a message processing stage in a message processing pipeline, a routing table, a message validation process, a message logging process, a message tracking process, a performance monitor, an error handler, a message authorization process, and a message authentication process.

16. The method of claim 11 wherein:

rolling back includes one of;

performing at least one inverse action, and reverting to a state prior to the performing of the at least one action.

18. A machine readable medium having instructions stored thereon to cause a system to:

accept a first configuration wherein the first configuration includes at least one action for configuring a service proxy;

perform the at least one action;

detect an error in the performing; and

roll back the at least one action.

19. A system for configuring a service proxy, comprising:

at least one component capable of performing the following steps;

accepting a first configuration wherein the first configuration includes at least one action for configuring the service proxy;

performing the at least one action;

detecting an error in the performing; and

rolling back the at least one action.