Abstract: Network services may include data associated with one or more entities. An aggregator service may host respective application programming interfaces (APIs) of the services at a single endpoint of the network such that the entities, including associations and relationships between entities, may be federated. For example, the services may register the entities of which the data of each of the services is associated with through a declarative entity model to establish an API schema for each of the services, which may be published at the aggregator service. In response to receipt of a request for entity related data from a client, the aggregator service may employ the declarative entity model to determine which of the services are associated with the entity related data such that a query may be submitted to the services, and how to aggregate responses to the query received from the services for transmission to the client.

Abstract: The present disclosure is directed to preserving running sessions during a side-by-side upgrade of system resources. Example aspects include deploying a first version and a second version of a system resource to a server within a network, the first version and the second version of the system resource both maintained within the system network and accessible via a version agnostic Application Programming Interface. Example aspects can receive, at a front-end server, a request for interaction with the system resource from a first client system, the request from the first client system including a header including version-identifying information. The systems and methods can determine, at a session version redirector, that the client system should be provided the first version and not the second version based on the version-identifying information in the header.

Abstract: The present disclosure is directed to preserving running sessions during a side-by-side upgrade of system resources. Example aspects include deploying a first version and a second version of a system resource to a server within a network, the first version and the second version of the system resource both maintained within the system network and accessible via a version agnostic Application Programming Interface. Example aspects can receive, at a front-end server, a request for interaction with the system resource from a first client system, the request from the first client system including a header including version-identifying information. The systems and methods can determine, at a session version redirector, that the client system should be provided the first version and not the second version based on the version-identifying information in the header.

Abstract: Network services may include data associated with one or more entities. An aggregator service may host respective application programming interfaces (APIs) of the services at a single endpoint of the network such that the entities, including associations and relationships between entities, may be federated. For example, the services may register the entities of which the data of each of the services is associated with through a declarative entity model to establish an API schema for each of the services, which may be published at the aggregator service. In response to receipt of a request for entity related data from a client, the aggregator service may employ the declarative entity model to determine which of the services are associated with the entity related data such that a query may be submitted to the services, and how to aggregate responses to the query received from the services for transmission to the client.

Abstract: The present invention relates to a system and methodology providing an Application Programming Interface (API) and framework that supports a meta-object model for application design and operating system interactions. The API includes an input component that receives data and/or instructions. The input component processes a meta-data model that interrelates data via a class hierarchy, wherein the class hierarchy includes relationship descriptions between class objects, attributes, rules, and/or behavioral descriptions. Another aspect includes a data management system that includes a component to receive an item having meta-data annotations. An analysis component determines at runtime a structure for the item via deployment of the meta-data annotations. The system can also include a framework component that defines meta-data class derivations, meta-data classes, meta-data integrity rules, and/or meta-data class behavior.

Abstract: A system and method facilitating asset composition based, at least in part, upon metadata (e.g., asset specification) describing compositional property(ies) of the asset(s) is provided. Asset specification(s) (e.g., metadata) that describe asset(s) to efficiently search and/or match asset(s) are employed. The system can facilitate matching (e.g., automatically) the particular software component to available server(s). Thus, the system can provide a flexible manner of describing asset(s) and an efficient way of locating matching description(s).

Abstract: A system and method facilitating asset composition based, at least in part, upon metadata (e.g., asset specification) describing compositional property(ies) of the asset(s) is provided. Asset specification(s) (e.g., metadata) that describe asset(s) to efficiently search and/or match asset(s) are employed. The system can facilitate matching (e.g., automatically) the particular software component to available server(s). Thus, the system can provide a flexible manner of describing asset(s) and an efficient way of locating matching description(s).

Abstract: The present invention relates to a system and methodology providing an Application Programming Interface (API) and framework that supports a meta-object model for application design and operating system interactions. The API includes an input component that receives data and/or instructions. The input component processes a meta-data model that interrelates data via a class hierarchy, wherein the class hierarchy includes relationship descriptions between class objects, attributes, rules, and/or behavioral descriptions. Another aspect includes a data management system that includes a component to receive an item having meta-data annotations. An analysis component determines at runtime a structure for the item via deployment of the meta-data annotations. The system can also include a framework component that defines meta-data class derivations, meta-data classes, meta-data integrity rules, and/or meta-data class behavior.

Abstract: The present invention relates to a system and methodology providing an Application Programming Interface (API) and framework that supports a meta-object model for application design and operating system interactions. The API includes an input component that receives data and/or instructions. The input component processes a meta-data model that interrelates data via a class hierarchy, wherein the class hierarchy includes relationship descriptions between class objects, attributes, rules, and/or behavioral descriptions. Another aspect includes a data management system that includes a component to receive an item having meta-data annotations. An analysis component determines at runtime a structure for the item via deployment of the meta-data annotations. The system can also include a framework component that defines meta-data class derivations, meta-data classes, meta-data integrity rules, and/or meta-data class behavior.

Abstract: Generating coverage information identifying tested elements of a declarative data structure. A method includes exercising a first element of a declarative data structure. Information is gathered about the effects of exercising a first element of a declarative data structure on other elements of the declarative data structure. The information gathered about the effects of exercising a first element of a declarative data structure on other elements of the declarative data structure is collated and analyzed. The information gathered about the effects of exercising a first element of a declarative data structure on other elements is reported in a human understandable format.

Abstract: A system and method facilitating asset composition based, at least in part, upon metadata (e.g., asset specification) describing compositional property(ies) of the asset(s) is provided. Asset specification(s) (e.g., metadata) that describe asset(s) to efficiently search and/or match asset(s) are employed. The system can facilitate matching (e.g., automatically) the particular software component to available server(s). Thus, the system can provide a flexible manner of describing asset(s) and an efficient way of locating matching description(s).

Abstract: The present invention relates to a system and methodology providing an Application Programming Interface (API) and framework that supports a meta-object model for application design and operating system interactions. The API includes an input component that receives data and/or instructions. The input component processes a meta-data model that interrelates data via a class hierarchy, wherein the class hierarchy includes relationship descriptions between class objects, attributes, rules, and/or behavioral descriptions. Another aspect includes a data management system that includes a component to receive an item having meta-data annotations. An analysis component determines at runtime a structure for the item via deployment of the meta-data annotations. The system can also include a framework component that defines meta-data class derivations, meta-data classes, meta-data integrity rules, and/or meta-data class behavior.

Abstract: A system and method facilitating asset composition based, at least in part, upon metadata (e.g., asset specification) describing compositional property(ies) of the asset(s) is provided. Asset specification(s) (e.g., metadata) that describe asset(s) to efficiently search and/or match asset(s) are employed. The system can facilitate matching (e.g., automatically) the particular software component to available server(s). Thus, the system can provide a flexible manner of describing asset(s) and an efficient way of locating matching description(s).