Specifying data in a standards style pattern of service-oriented architecture (SOA) environments
First Claim
1. A method implemented in a computer infrastructure, 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, wherein;
the validating comprises determining that one or more virtual links exists between 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; and
the validating is performed in a reception layer of the service that receives the one or more data elements from a computing device.
1 Assignment
0 Petitions
Accused Products
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.
-
Citations
19 Claims
-
1. A method implemented in a computer infrastructure, 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, wherein; the validating comprises determining that one or more virtual links exists between 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; and the validating is performed in a reception layer of the service that receives the one or more data elements from a computing device. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. A system implemented in hardware, comprising:
a computer infrastructure operable to; define 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; configure a data definition file (DDF) comprising one or more data optionality attributes which indicate whether each of the one or more local data elements and the one or more common data elements is optional for the service; and invalidate the one or more common data elements from the service message as optional for the service based on the interface and the configured DDF, wherein; the invalidation comprises determining that the one or more references to the one or more common data elements in the interface is not defined in the DDF; and the invalidation is performed in a reception layer of the service that receives the one or data elements from the consumer device. - View Dependent Claims (12, 13, 14, 15)
-
16. A computer program product comprising a non-transitory tangible computer usable storage medium having readable program code embodied in the tangible computer usable storage medium, the computer program product includes at least one component operable to:
-
define 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; and configure 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; validate the one or more common data elements from the service message as mandatory for the service based on the interface and the configured DDF, wherein; the validating comprises determining that one or more virtual links exists between 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; and the validation is performed in a reception layer of the service that receives the one or more data elements from a computing device. - View Dependent Claims (17, 18, 19)
-
Specification