Interfacing between a caller application and a service module

• US 10,169,117 B2
• Filed: 06/02/2015
• Issued: 01/01/2019
• Est. Priority Date: 04/14/2008
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Berry, Charles F., Godoy, Glenn C., Snavely, Amy J.
• Primary Examiner(s): Anya, Charles E
• Application Number:
  US14/727,949
• Publication Number:
  US 20150261589A1
• Time in Patent Office: 1,309 Days
• CPC Class Codes: G06F 9/466 Transaction processing
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 30/0633 Lists, e.g. purchase orders, compilation or processing

Abstract

A method and system for interfacing between a caller application and a service module. A request for performing a transaction from the caller application is received. The request includes at least one caller application attribute describing the request. A service module data structure is built pursuant to the received request. The service module data structure includes a generic service document and at least one service module attribute. Each service module attribute is stored in a relational table of the service module data structure. The request is serviced within the service module data structure, which results in instantiating the generic service document. The generic service document is returned to the caller application.

Claims

1. A method for interfacing between a caller application and a service module, said method comprising:

receiving, by a processor of a computer system, a request for performing a transaction from the caller application, wherein the request comprises at least one caller application attribute describing the request;

subsequent to said receiving the request, said processor building a service module data structure pursuant to the received request, wherein the service module data structure comprises a generic service document and at least one service module attribute, and wherein said building the service module data structure comprises;

creating one or more containers in the generic service document, wherein each container of the one or more containers is respectively associated with each service module attribute of the at least one service module attribute in each mapping of the at least one mapping in a mapping table of the service module data structure, wherein each container comprises a data value for each service module attribute of the at least one service module attribute; and

subsequent to said creating the one or more containers in the generic service document, naming each container of said at least one container in the generic service document after each mapping of said at least one mapping in the mapping table;

subsequent to said building the service module data structure, said processor storing each service module attribute in a relational table of the service module data structure;

subsequent to said storing each service module attribute, said processor servicing the request within the service module data structure, wherein said servicing results in instantiating the generic service document, and wherein said servicing comprises;

performing the transaction, retrieving each mapping of at least one mapping in the mapping table of the service module data structure, and reloading each container of at least one container from the relational table into respective containers of the generic service document according to each retrieved mapping; and

subsequent to said servicing, said processor returning the generic service document to the caller application.

2. The method of claim 1, said building the service module data structure comprising:

defining the at least one service module attribute of the service module data structure, wherein each service module attribute of the at least one service module attribute either corresponds to one caller application attribute of the at least one caller application attribute or is created by the service module;

subsequent to said defining the at least one service module attribute, configuring a caller identifier that uniquely identifies the caller application which had sent the request and the service module data structure pursuant to the received request; and

subsequent to said configuring the caller identifier, constructing the generic service document, wherein the generic service document is configured to contain a result of the performed transaction.

3. The method of claim 1, said storing comprising:

determining a category of a first service module attribute of the at least one service module attribute, wherein a configuration table comprises a respective category of each service module attribute, wherein the category is either an extended-category that is recognized only by the caller application or a basic-category that is recognized by both the caller application and the service module;

subsequent to said determining the category, determining a level of the first service module attribute, wherein the configuration table further comprises a respective level of each service module attribute, wherein the level is either a header-level that is applicable for all service module attributes represented in the generic service document or an item-level that is applicable only for the first service module attribute;

subsequent to said determining the level, storing in the relational table a first container of at least one container, said first container being pursuant to the category and the level of the first service module attribute that is associated with the first container, wherein the relational table is selected from the group consisting of a first table for service module attributes determined to be in the basic-category and in the header-level, a second table for service module attributes determined to be in the basic-category and in the item-level, a third table for service module attributes determined to be in the extended-category and in the header-level, and a fourth table for service module attributes determined to be in the extended-category and in the item-level; and

subsequent to said storing the first container, repeating said determining the category, said determining the level, and said storing the first container after setting the first container with a next container in the relational table until all containers are stored in the relational table.

4. The method of claim 1, wherein the caller application is a member of a group comprising at least two caller applications, and wherein the service module is shared by each member of the group.

5. The method of claim 1, said method further comprising:

providing at least one support service for at least one of creating, integrating, hosting, maintaining, and deploying computer-readable program code in the computer system, said program code being executed by the processor to implement said receiving the request, said building the service module data structure, said storing each service module attribute, said servicing the request, and said returning the generic service document to the caller application.

6. A computer program product, comprising a computer readable hardware storage device storing computer readable program code which, upon being executed by a processor of a computer system, said storage device not being a signal and not including a transmission medium, implements a method for interfacing between a caller application and a service module, said method comprising:

receiving, by a processor of a computer system, a request for performing a transaction from the caller application, wherein the request comprises at least one caller application attribute describing the request;

subsequent to said receiving the request, said processor building a service module data structure pursuant to the received request, wherein the service module data structure comprises a generic service document and at least one service module attribute, and wherein said building the service module data structure comprises;

creating one or more containers in the generic service document, wherein each container of the one or more containers is respectively associated with each service module attribute of the at least one service module attribute in each mapping of the at least one mapping in a mapping table of the service module data structure, wherein each container comprises a data value for each service module attribute of the at least one service module attribute; and

subsequent to said creating the one or more containers in the generic service document, naming each container of said at least one container in the generic service document after each mapping of said at least one mapping in the mapping table;

subsequent to said building the service module data structure, said processor storing each service module attribute in a relational table of the service module data structure;

subsequent to said storing each service module attribute, said processor servicing the request within the service module data structure, wherein said servicing results in instantiating the generic service document, and wherein said servicing comprises;

performing the transaction, retrieving each mapping of at least one mapping in a mapping table of the service module data structure, and reloading each container of at least one container from the relational table into respective containers of the generic service document according to each retrieved mapping; and

subsequent to said servicing, said processor returning the generic service document to the caller application.

7. The computer program product of claim 6, said building the service module data structure comprising:

defining the at least one service module attribute of the service module data structure, wherein each service module attribute of the at least one service module attribute either corresponds to one caller application attribute of the at least one caller application attribute or is created by the service module;

subsequent to said defining the at least one service module attribute, configuring a caller identifier that uniquely identifies the caller application which had sent the request and the service module data structure pursuant to the received request; and

subsequent to said configuring the caller identifier, constructing the generic service document, wherein the generic service document is configured to contain a result of the performed transaction.

8. The computer program product of claim 6, said storing comprising:

determining a category of a first service module attribute of the at least one service module attribute, wherein a configuration table comprises a respective category of each service module attribute, wherein the category is either an extended-category that is recognized only by the caller application or a basic-category that is recognized by both the caller application and the service module;

subsequent to said determining the category, determining a level of the first service module attribute, wherein the configuration table further comprises a respective level of each service module attribute, wherein the level is either a header-level that is applicable for all service module attributes represented in the generic service document or an item-level that is applicable only for the first service module attribute;

subsequent to said determining the level, storing in the relational table a first container of at least one container, said first container being pursuant to the category and the level of the first service module attribute that is associated with the first container, wherein the relational table is selected from the group consisting of a first table for service module attributes determined to be in the basic-category and in the header-level, a second table for service module attributes determined to be in the basic-category and in the item-level, a third table for service module attributes determined to be in the extended-category and in the header-level, and a fourth table for service module attributes determined to be in the extended-category and in the item-level; and

subsequent to said storing the first container, repeating said determining the category, said determining the level, and said storing the first container after setting the first container with a next container in the relational table until all containers are stored in the relational table.

9. The computer program product of claim 6, wherein the caller application is a member of a group comprising at least two caller applications, and wherein the service module is shared by each member of the group.

10. A computer system comprising a processor, a memory coupled to the processor, and a computer readable storage device coupled to the processor, said storage device containing program code configured to be executed by the processor via the memory to implement a method for interfacing between a caller application and a service module, said method comprising:

said processor receiving a request for performing a transaction from the caller application, wherein the request comprises at least one caller application attribute describing the request;

subsequent to said receiving the request, said processor building a service module data structure pursuant to the received request, wherein the service module data structure comprises a generic service document and at least one service module attribute, and wherein said building the service module data structure comprises;

creating one or more containers in the generic service document, wherein each container of the one or more containers is respectively associated with each service module attribute of the at least one service module attribute in each mapping of the at least one mapping in a mapping table of the service module data structure, wherein each container comprises a data value for each service module attribute of the at least one service module attribute; and

subsequent to said creating the one or more containers in the generic service document, naming each container of said at least one container in the generic service document after each mapping of said at least one mapping in the mapping table;

subsequent to said building the service module data structure, said processor storing each service module attribute in a relational table of the service module data structure;

subsequent to said storing each service module attribute, said processor servicing the request within the service module data structure, wherein said servicing results in instantiating the generic service document, and wherein said servicing comprises;

performing the transaction, retrieving each mapping of at least one mapping in a mapping table of the service module data structure, and reloading each container of at least one container from the relational table into respective containers of the generic service document according to each retrieved mapping; and

subsequent to said servicing, said processor returning the generic service document to the caller application.

11. The computer system of claim 10, said building the service module data structure comprising:

defining the at least one service module attribute of the service module data structure, wherein each service module attribute of the at least one service module attribute either corresponds to one caller application attribute of the at least one caller application attribute or is created by the service module;

subsequent to said defining the at least one service module attribute, configuring a caller identifier that uniquely identifies the caller application which had sent the request and the service module data structure pursuant to the received request; and

subsequent to said configuring the caller identifier, constructing the generic service document, wherein the generic service document is configured to contain a result of the performed transaction.

12. The computer system of claim 10, said storing comprising:

determining a category of a first service module attribute of the at least one service module attribute, wherein a configuration table comprises a respective category of each service module attribute, wherein the category is either an extended-category that is recognized only by the caller application or a basic-category that is recognized by both the caller application and the service module;

subsequent to said determining the category, determining a level of the first service module attribute, wherein the configuration table further comprises a respective level of each service module attribute, wherein the level is either a header-level that is applicable for all service module attributes represented in the generic service document or an item-level that is applicable only for the first service module attribute;

subsequent to said determining the level, storing in the relational table a first container of at least one container, said first container being pursuant to the category and the level of the first service module attribute that is associated with the first container, wherein the relational table is selected from the group consisting of a first table for service module attributes determined to be in the basic-category and in the header-level, a second table for service module attributes determined to be in the basic-category and in the item-level, a third table for service module attributes determined to be in the extended-category and in the header-level, and a fourth table for service module attributes determined to be in the extended-category and in the item-level; and

subsequent to said storing the first container, repeating said determining the category, said determining the level, and said storing the first container after setting the first container with a next container in the relational table until all containers are stored in the relational table.

13. The computer system of claim 10, wherein the caller application is a member of a group comprising at least two caller applications, and wherein the service module is shared by each member of the group.