Specifying data in a standards style pattern of service-oriented architecture (SOA) environments
First Claim
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,the validating being performed by a parser in a reception layer of a service tool, which reception layer receives the one or more data elements from the computing device and service messages from a consumer device, to prevent incomplete or incorrect service messages received by the reception layer from percolating down to a mediation layer and a service layer which are lower level layers of the service tool,wherein the parser invalidates common data elements referred to in the service messages as optional based on the optionality attribute of the DDF.
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
17 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, the validating being performed by a parser in a reception layer of a service tool, which reception layer receives the one or more data elements from the computing device and service messages from a consumer device, to prevent incomplete or incorrect service messages received by the reception layer from percolating down to a mediation layer and a service layer which are lower level layers of the service tool, wherein the parser invalidates common data elements referred to in the service messages as optional based on the optionality attribute of the DDF. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13)
-
-
14. 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), 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 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, the validating being performed in a reception layer of a service tool, which reception layer receives the one or more data elements from the computing device and service messages from a consumer device, to prevent incomplete or incorrect service messages received by the reception layer from percolating down to a mediation layer and a service layer which are lower level layers of the service tool, wherein the reception layer includes a parser structured to validate the common data elements as mandatory or to invalidate the common data elements as optional based on the optionality attribute defined by the DDF. - View Dependent Claims (15)
-
-
16. A computer program product comprising a tangible computer usable storage medium having readable program code embodied in the tangible computer usable storage medium, wherein the tangible computer usable storage medium is not a transitory signal per se, 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; 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; and 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, the validating being performed by a parser in a reception layer of a service tool, which reception layer receives the one or more data elements from the computing device and service messages from a consumer device, to prevent incomplete or incorrect service messages received by the reception layer from percolating down to a mediation layer and a service layer which are lower level layers of the service tool, wherein the parser invalidates common data elements referred to in the service messages as optional based on the optionality attribute of the DDF. - View Dependent Claims (17)
-
Specification