Abstract: The disclosure generally describes methods, software, and systems for cross-application protocols describing integration dependencies. A request is received to synchronize customer data from multiple system instances. The system instances include one or more application programming interfaces. A semantic description of an integration process configured to synchronize the customer data from the plurality of system instances is generated. The semantic description defines integration dependencies between system instances. The integration process is executed to synchronize the customer data from the plurality of system instances to generate synchronized customer data. The synchronized customer data are provided for storage.

Abstract: The disclosure generally describes methods, software, and systems for open resource discovery protocol describing entity types. An identifier of a first entity type is received. The first entity type defines a relation between an application programming interface (API) and event information. A reference for the first entity type is generated based on the identifier of the first entity type. The reference links the first entity type to the API. A description of the first entity type is provided for storage using the reference for the first entity type. the description includes a structure of an underlying data model. A request to provide the first entity type based on the description of the first entity type is received. The first entity type is provided using an exposed API and the reference for the first entity type.

Abstract: The disclosure generally describes methods, software, and systems for cross-application protocols describing integration dependencies. A request is received to synchronize customer data from multiple system instances. The system instances include one or more application programming interfaces. A semantic description of an integration process configured to synchronize the customer data from the plurality of system instances is generated. The semantic description defines integration dependencies between system instances. The integration process is executed to synchronize the customer data from the plurality of system instances to generate synchronized customer data. The synchronized customer data are provided for storage.

Abstract: In an example embodiment, three roles are defined for each of the following: resource discovery: provider, aggregator, and consumer. The provider is the one whose resource information will be shared. Rather than the provider needing to implement the complicated API, however, an aggregator may provide that role. The aggregator defines the API and is able to gather resource information from potentially multiple providers (and also, in some embodiments, other aggregators). The consumer then accesses the aggregator to obtain resource information rather than directly accessing the provider.

Abstract: The present disclosure relates to computer-implemented methods, software, and systems for importing metadata between applications. One example method includes obtaining, at a data warehouse application, metadata for relevant entities in response to a query defined for querying metadata from a metadata source associated with a source application. A service at the source application is queried to identify a set of programming interfaces associated with the relevant entities for acquiring data objects corresponding to the obtained metadata from the source application. Instructions are generated that can be used to configure the database associated with the data warehouse application to acquire a data object based on executing a call to a corresponding programming interface. The generated instructions are provided to the database to configure the database to automatically execute the call to acquire the data object from the source application.

Abstract: In an example embodiment, three roles are defined for each of the following: resource discovery: provider, aggregator, and consumer. The provider is the one whose resource information will be shared. Rather than the provider needing to implement the complicated API, however, an aggregator may provide that role. The aggregator defines the API and is able to gather resource information from potentially multiple providers (and also, in some embodiments, other aggregators). The consumer then accesses the aggregator to obtain resource information rather than directly accessing the provider.

Abstract: In an example embodiment, a technique is disclosed to describe generic capabilities in the ORD standard. In addition, this new ORD resource type may be explicitly supported by a Central ORD aggregator (or Central Management Plane), which can be used to discover and retrieve the information centrally. Having a central metadata service also eliminates the need for many point-to-point integrations.

Abstract: In an example embodiment, a technique is disclosed to describe generic capabilities in the ORD standard. In addition, this new ORD resource type may be explicitly supported by a Central ORD aggregator (or Central Management Plane), which can be used to discover and retrieve the information centrally. Having a central metadata service also eliminates the need for many point-to-point integrations.

Abstract: In an example embodiment, three roles are defined for each of the following: resource discovery: provider, aggregator, and consumer. The provider is the one whose resource information will be shared. Rather than the provider needing to implement the complicated API, however, an aggregator may provide that role. The aggregator defines the API and is able to gather resource information from potentially multiple providers (and also, in some embodiments, other aggregators). The consumer then accesses the aggregator to obtain resource information rather than directly accessing the provider.

Abstract: In an example embodiment, three roles are defined for each of the following: resource discovery: provider, aggregator, and consumer. The provider is the one whose resource information will be shared. Rather than the provider needing to implement the complicated API, however, an aggregator may provide that role. The aggregator defines the API and is able to gather resource information from potentially multiple providers (and also, in some embodiments, other aggregators). The consumer then accesses the aggregator to obtain resource information rather than directly accessing the provider.

Abstract: The present disclosure relates to computer-implemented methods, software, and systems for importing metadata between applications. One example method includes obtaining, at a data warehouse application, metadata for relevant entities in response to a query defined for querying metadata from a metadata source associated with a source application. A service at the source application is queried to identify a set of programming interfaces associated with the relevant entities for acquiring data objects corresponding to the obtained metadata from the source application. Instructions are generated that can be used to configure the database associated with the data warehouse application to acquire a data object based on executing a call to a corresponding programming interface. The generated instructions are provided to the database to configure the database to automatically execute the call to acquire the data object from the source application.