Abstract: A computer system is provided that stores files in a structured file format and stores configuration files that indicate programmatic definitions for handlers. A processing system generates in-memory models of the structured files and creates a list of observer objects and observable objects. A handler is generated for each observer and observable object. The handlers handle how changes are to be updated and/or propagated to other files. When a data value of one of the files is to be updated and the data value is associated with an observable element of that file, the handler for the corresponding observable object is triggered. A handler for an observer object will also be triggered that shares the topic of the attribute being observed. Once the in-memory representation of the models are updated, the models are persisted back to non-volatile storage (as files) where the changes are reflected.

Abstract: A computer system is provided that stores files in a structured file format and stores configuration files that indicate programmatic definitions for handlers. A processing system generates in-memory models of the structured files and creates a list of observer objects and observable objects. A handler is generated for each observer and observable object. The handlers handle how changes are to be updated and/or propagated to other files. When a data value of one of the files is to be updated and the data value is associated with an observable element of that file, the handler for the corresponding observable object is triggered. A handler for an observer object will also be triggered that shares the topic of the attribute being observed. Once the in-memory representation of the models are updated, the models are persisted back to non-volatile storage (as files) where the changes are reflected.

Abstract: Certain example embodiments provide a generic integration framework for connecting on-premises applications with software as a service (SaaS) applications, and/or for integrating the same. The framework of certain example embodiments involves a layered approach (including a Connector Development Kit, connection factory, metadata handlers, and connector services) that helps to, among other things, allow customization of applications in multi-tenant architectures. Design-time wizards help create runtime artifacts and, during runtime, the connector service helps serve as an intermediary between the on-premises application and the cloud service, thereby hiding the complexity of the specific cloud providers. Certain example embodiments advantageously provide a generic and well-integrated solution for connecting an on-premises application to a cloud service in connection with existing containers.

Abstract: Certain example embodiments provide a generic integration framework for connecting on-premises applications with software as a service (SaaS) applications, and/or for integrating the same. The framework of certain example embodiments involves a layered approach (including a Connector Development Kit, connection factory, metadata handlers, and connector services) that helps to, among other things, allow customization of applications in multi-tenant architectures. Design-time wizards help create runtime artifacts and, during runtime, the connector service helps serve as an intermediary between the on-premises application and the cloud service, thereby hiding the complexity of the specific cloud providers. Certain example embodiments advantageously provide a generic and well-integrated solution for connecting an on-premises application to a cloud service in connection with existing containers.