Rebuildable service-oriented applications

• US 9,524,145 B2
• Filed: 03/16/2009
• Issued: 12/20/2016
• Est. Priority Date: 03/28/2008
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Jin, Ge, Tan, Jia, Zhou, Zhi Rong
• Primary Examiner(s): Dao, Thuy
• Assistant Examiner(s): BUI, HANH THI MINH
• Application Number:
  US12/404,986
• Publication Number:
  US 20090249288A1
• Time in Patent Office: 2,836 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/24 Object-oriented
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: G06F 8/36 Software reuse
• CPC Class Codes: G06F 8/72 Code refactoring
• CPC Class Codes: G06F 9/44521 Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
• CPC Class Codes: G06N 5/00 Computing arrangements using knowledge-based models

Abstract

A method includes receiving a selection of a predefined implementation variation for a variable service component in at least one computing device configured to implement a service-oriented application; and executing source code associated with the variable service component in response to receiving the selection, wherein the source code performs a predetermined rebuilding of at least a portion of the service-oriented application such that the variable service component is redefined according to the selected implementation variation.

Claims

1. A method comprising:

receiving confirmation, from a customer, that functional and non-functional variable service components of a service-oriented application comprise variability point information that supports an acceptable variation of the service-oriented application;

in which the variability point information defines how and to what extent a variable service component may be varied by a customer of the variable service component; and

in which the variable service components are predefined in an interface variation protocol defining the selectable variation point information related to the variable service component prior to the customer accepting the variation of the service-oriented application; and

receiving, from the customer, a selection of the variability point information defining how and to what extent the variable service components are to be varied in at least one computing device configured to implement a service-oriented application;

executing source code associated with said variable service component in said at least one computing device in response to receiving said selection, and

receiving at least one parameter associated with said selection from said predetermined set of available variations in said service component;

said source code performing a predetermined rebuilding of at least a portion of said service-oriented application such that said variable service component is redefined according to said selected variability point information; and

where a non-functional variable service component is the only component selected by the customer to be variable, modifying only a service model representing the service-oriented application and a deployment script of the service-oriented application.

2. The method of claim 1, in which said variable service component comprises at least one of:

a service, a process implemented by a service, a service description, a service communication protocol, and a service communication transmission.

3. The method of claim 1, in which said variable service component is a component of a service contract for a service in said service-oriented application.

4. The method of claim 1, in which said variability point information defining how and to what extent a variable service component may be varied comprises at least one of:

adding at least one message field to an input/output message definition associated with said variable service component, removing at least one message field from said input/output message definition, and modifying at least one message field in said input/output message definition.

5. The method of claim 1, in which said variability point information defining how and to what extent a variable service component may be varied comprises adding a service operation to a service, removing a service operation from a service, modifying a service operation associated with a service, adding a non-functional requirement of a service, removing a non-functional requirement of a service, and modifying a non-functional requirement of a service.

6. A method for providing a rebuilding solution for a service-oriented application, said service-oriented application comprising a service model and service model source code associated with said service model, said method comprising:

defining functional and non-functional variable portions of a service component in a service model associated with said service-oriented application;

providing source code, via a graphical component, describing the functional and non-functional variable portions of the service component, the functional and non-functional variable portions each comprising a predefined variation;

receiving confirmation from a customer that the functional and non-functional variable portions of the service component in the service model are sufficient to rebuild the service-oriented application,

in which the functional and non-functional variable portions in the service component are predefined in an interface variation protocol prior to the customer confirming the functional and non-functional variable portions of the service component are sufficient; and

in which the source code describing the functional and non-functional variable portions of the service component define how and to what extent the variable service component may be varied by a customer of the variable service component; and

receiving, from the customer, a selection of the functional and non-functional variable portions of the service component defining how and to what extent the variable service component is to be varied in at least one computing device configured to implement a service oriented application;

performing, by said source code, a predetermined rebuilding process on said service component in said service-oriented application implemented by said computing device, using said selection of the functional and non-functional variable portions as an input; and

receiving at least one parameter associated with said selection from said predetermined set of available variable portions in said service component;

wherein, where a non-functional variable service component is the only component selected by the customer to be variable, only a service model representing the service-oriented application and a deployment script of the service-oriented application is modified.

7. The method of claim 6, wherein said predetermined rebuilding process is based on a variation definition in said source code.

8. The method of claim 6, wherein said service component comprises at least one of:

a service, a process implemented by a service, a service description, a service communication protocol, and a service communication transmission.

9. The method of claim 6, wherein said predetermined rebuilding process comprises:

modifying a service model;

modifying a deployment script; and

modifying at least one of;

a service component implementation at a code level, a service implementation at a configuration level, an affected business process, a service invocation client stub in the service-oriented application, and a user interface component.

10. The method of claim 9, wherein said variable portions comprises at least one of a message field to be added, a message field to be removed, and a message field to be modified.

11. The method of claim 10, wherein said message field is a component of an existing input/output message definition associated with said variable service component.

12. A computer program product for rebuilding a service-oriented application, said computer program product comprising:

a computer readable storage memory device comprising computer usable program code embodied therewith, wherein the computer usable program code comprises computer usable program code to;

receive confirmation from a customer of a variable service component in the service-oriented application that variability information that defines how and to what extent functional and non-functional variable service components may be varied by a customer is accepted by the customer, in which the variable service components are predefined in an interface variation protocol defining selectable variation point information related to the variable service component prior to the customer accepting the variability information;

receive, from the customer, a selection of a predefined implementation variation for a variable service component in a service-oriented application, the predefined implementation variation defining how and to what extent the variable service component is to be varied;

perform a predetermined rebuilding of at least a portion of said service-oriented application in response to receiving said selection such that said variable service component is redefined according to said selected implementation variation; and

receive at least one parameter associated with said selection from said predetermined set of available variations in said service component;

wherein, where a non-functional variable service component is the only component selected by the customer to be variable, modifying only a service model representing the service-oriented application and a deployment script of the service-oriented application.

13. The computer program product of claim 12, wherein said variable service component comprises at least one of:

a service, a process implemented by a service, a service description, a service communication protocol, and a service communication transmission.

14. The computer program product of claim 12, further comprising computer usable code comprising variability information that defines how and to what extent said variable service component may be modified.

15. The computer program product of claim 12, wherein said predefined implementation variation comprises:

adding a message field, removing a message field, modifying a message field, adding a service operation, removing a service operation, modifying a service operation, adding a non-functional requirement of a service, removing a non-functional requirement of a service, and modifying a non-functional requirement of a service.

16. The computer program product of claim 15, wherein said message field is a component of an existing input/output message definition associated with said variable service component.

17. A method for providing a rebuilding solution for a service-oriented application, said service-oriented application comprising a service model and service model source code associated with said service model, the method comprising:

identifying functional and non-functional variable service components in said service model and, based on the functional and non-functional variable service components, a variation model for defining selectable variation point information related to said variable service component, wherein said variation point information related to the functional and non-functional variable service components comprises variability information defining whether and to what extent the service component is variable, and

creating source code that supports variation implementation of the service model, wherein said source code that supports said variation implementation defines variations of the service model and the service model source code for realizing the variation point information related to the functional and non-functional variable service components and is used for performing a predetermined rebuilding process on said service model and said service model source code according to a variation definition that supports implementation of the variation point in said source code, using a selection of variation point information related to the functional and non-functional variable service components in said variation model as an input; and

receiving at least one parameter associated with said selection from said predetermined set of available variations in said service component;

wherein, where a non-functional variable service component is the only component selected by the customer to be variable, modifying only a service model representing the service-oriented application and a deployment script of the service-oriented application.