Declarative configuration of enterprises services
First Claim
1. A method comprising:
- providing, to a client program being executed on a processor of a computer, a definition of an object class representing attributes of a first collection of data elements, a list of possible operations on the first collection, and a request syntax, each data element having attributes and possible operations in common with other data elements from the first collection, wherein the definition and the request syntax are provided using metadata stored in a repository;
customizing a usage policy of the first collection for a first configuration of the client program;
receiving from the client program a first request to execute an operation from the list on one or more data elements from the first collection, wherein the first request comprises configuration data specifying the first configuration of the client program;
checking the first request and the configuration data against the definition, the usage policy, and the request syntax by using the metadata;
executing the operation on the one or more data elements of the first collection;
providing to the client program a definition of a module representing a second collection of data elements, the second collection including the first collection; and
customizing a module usage policy for a second configuration of the client program, wherein;
the definition of the module comprises a query on the second collection of data elements and the module usage policy specifies a deactivation of the query such that a second request, that is based on the second configuration and is received from the client program to execute a query on the second collection of data elements, is rejected;
the module usage policy specifies a usage of the first collection of data elements included in the second collection, the module usage policy being one of mandatory, deactivated, and read only; and
the deactivated module usage policy specifies that the first collection of the data elements included in the second collection are not usable by the client program having the second configuration, the read-only module usage policy specifies that the first collection of the data elements included in the second collection cannot be changed by the client program having the second configuration, and the configuration module usage policy specifies a third configuration that the client program, having the second configuration, must have to use the first collection of the data elements included in the second collection.
3 Assignments
0 Petitions
Accused Products
Abstract
Methods and apparatus, including computer program products, that include providing to a client a definition of an object class representing attributes of a first collection of data elements and a list of possible operations on the first collection, each data element having attributes and possible operations in common with other data elements from the first collection. The method also includes customizing a usage policy of the first collection for a configuration of the client, receiving from the client a first request to execute an operation from the list on one or more data elements from the first collection, checking the first request against the definition and the usage policy, and executing the operation on the one or more data elements of the first collection.
-
Citations
19 Claims
-
1. A method comprising:
-
providing, to a client program being executed on a processor of a computer, a definition of an object class representing attributes of a first collection of data elements, a list of possible operations on the first collection, and a request syntax, each data element having attributes and possible operations in common with other data elements from the first collection, wherein the definition and the request syntax are provided using metadata stored in a repository; customizing a usage policy of the first collection for a first configuration of the client program; receiving from the client program a first request to execute an operation from the list on one or more data elements from the first collection, wherein the first request comprises configuration data specifying the first configuration of the client program; checking the first request and the configuration data against the definition, the usage policy, and the request syntax by using the metadata; executing the operation on the one or more data elements of the first collection; providing to the client program a definition of a module representing a second collection of data elements, the second collection including the first collection; and customizing a module usage policy for a second configuration of the client program, wherein; the definition of the module comprises a query on the second collection of data elements and the module usage policy specifies a deactivation of the query such that a second request, that is based on the second configuration and is received from the client program to execute a query on the second collection of data elements, is rejected; the module usage policy specifies a usage of the first collection of data elements included in the second collection, the module usage policy being one of mandatory, deactivated, and read only; and the deactivated module usage policy specifies that the first collection of the data elements included in the second collection are not usable by the client program having the second configuration, the read-only module usage policy specifies that the first collection of the data elements included in the second collection cannot be changed by the client program having the second configuration, and the configuration module usage policy specifies a third configuration that the client program, having the second configuration, must have to use the first collection of the data elements included in the second collection. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A system comprising:
-
a first computer comprising a computer-readable storage medium and a processor configured to execute a client program; a second computer configured to execute a server program; and a network linking the first and second computers, the server program configured to; provide to the client program a definition of an object class representing attributes of a first collection of data elements, a list of possible operations on the first collection, and a request syntax, each data element in the first collection having attributes and possible operations in common with other data elements from the first collection, wherein the definition and the request syntax are provided using metadata stored in a repository; provide to the client program a usage policy of the first collection for a first configuration of the client program for a client; receive from the client program a first request to execute an operation from the list on one or more data elements from the first collection, wherein the first request comprises configuration data specifying the first configuration of the client program; check the first request and the configuration data against the definition, the usage policy, and the request syntax by using the metadata; execute the operation on the one or more data elements of the first collection; provide to the client program a definition of a module representing a second collection of data elements, the second collection including the first collection; and customizing a module usage policy for a second configuration of the client program, wherein; the definition of the module comprises a query on the second collection of data elements and the module usage policy specifies a deactivation of the query such that a second request, that is based on the second configuration and is received from the client program to execute a query on the second collections of data elements, is rejected by the server program; the module usage policy specifies a usage of the first collection of data elements included in the second collection, the module usage policy being one of mandatory, deactivated, and read only; and the deactivated usage policy specifies that the first collection of the data elements included in the second collection are not usable by the client program having the second configuration, the read-only module usage policy specifies that the first collection of the data elements included in the second collection cannot be changed by the client program having the second configuration, and the configuration module usage policy specifies a third configuration that the client program, having the second configuration, must have to use the first collection of the data elements. - View Dependent Claims (11, 12, 13, 14, 15, 16, 17, 18, 19)
-
Specification