SPECIFYING DATA IN A STANDARDS STYLE PATTERN OF SERVICE-ORIENTED ARCHITECTURE (SOA) ENVIRONMENTS

• US 20160210122A1
• Filed: 03/31/2016
• Published: 07/21/2016
• Est. Priority Date: 03/12/2012
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: IYER, Sreekanth R., PATIL, Sandeep R., RAMANATHAN, Sri, SIVAKUMAR, Gandhi, TREVATHAN, Matthew B.
• Granted Patent: US 10,067,748 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/31 Programming languages or programming paradigms
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

An approach for specifying data in a standards style pattern of Service-Oriented Architecture (SOA) environments is provided. The approach implemented in a computer infrastructure, includes defining an interface including one or more local data elements and one or more references to one or more common data elements, of a service, the one or more common data elements being defined in a library for a plurality of services. The approach further includes configuring a data definition file (DDF) which indicates whether each of the one or more local data elements and the one or more common data elements is mandatory for the service. The approach further includes validating one or more data elements from a consumer as mandatory for the service based on the configured DDF.

Claims

1. A method implemented in a computer infrastructure including a computing device, comprising:

defining an interface comprising one or more local data elements and one or more references to one or more common data elements, of a service, the one or more common data elements being defined in a library for a plurality of services, wherein the one or more common data elements are not defined in the library as being mandatory for any of the plurality of services;

configuring a data definition file (DDF), the configuring comprising defining an optionality attribute for each of the one or more local data elements and the one or more common data elements as mandatory for the service; and

validating the one or more common data elements from the service message as mandatory for the service based on the interface and the configured DDF.

2. The method of claim 1, wherein the configuring of the DDF is performed after the defining of the interface.

3. The method of claim 1, wherein in the DDF comprises a Web Services Description Language (WSDL) file.

4. The method of claim 1, further comprising connecting the one or more common data elements to the DDF based on the one or more virtual links.

5. The method of claim 1, further comprising invalidating the one or more common data elements as optional for the service based on the interface and the configured DDF.

6. The method of claim 1, wherein a service provider at least one of creates, maintains, deploys, and supports a computer infrastructure operable to the steps of claim 1.

7. The method of claim 1, wherein the steps of claim 1 are provided by a service provider on a subscription, advertising, and/or fee basis.

8. The method of claim 1, wherein the validating comprises determining that one or more virtual links exists between the one or more references to the one or more common data elements in the interface and the one or more common data elements defined in the DDF.

9. The method of claim 8, further comprising creating the one or more virtual links via a consumer device coupled to the computing device.

10. The method of claim 9, further comprising creating a value via the consumer device for at least one of the one or more local data elements and at least one of the one or more common data elements.

11. The method of claim 9, wherein a reception layer is located between the computing device and a service layer of the service.

12. The method of claim 11, wherein the validating is performed in the reception layer of the service that receives the one or more data elements from the computing device.