Abstract: A data architecture provides mobile clients with the ability to gain access to business enterprise data sources through configurable Views that interface with the data sources through Data Objects that are defined by Commands, which in turn communicate with the data sources through Connectors (also referred to as Adapters). Each type of View will interface to the data sources with a different functionality so that communications links and other system resources can be used more efficiently. The View types can include Direct Views, Derived Views, Delegated Views, and Definition Views.

Abstract: A data architecture provides View objects that define an enterprise data source interface to an application through connectors, and also by Data Objects defined by Commands. Thus, a Data Object comprises a configurable request for data that is issued through Commands to the Adapters of the enterprise data sources. The architecture provides an application developer with the ability to create custom enterprise connectivity to disparate backend enterprise data sources.

Abstract: A data architecture provides View objects that define an enterprise data source interface to an application through connectors, and also by Data Objects defined by Commands. Thus, a Data Object comprises a configurable request for data that is issued through Commands to the Adapters of the enterprise data sources. The architecture provides an application developer with the ability to create custom enterprise connectivity to disparate backend enterprise data sources.

Abstract: A data architecture provides View objects that define an enterprise data source interface to an application through connectors, and also by Data Objects defined by Commands. Thus, a Data Object comprises a configurable request for data that is issued through Commands to the Adapters of the enterprise data sources. The architecture provides an application developer with the ability to create custom enterprise connectivity to disparate backend enterprise data sources.

Abstract: A data architecture provides View objects that define an enterprise data source interface to an application through connectors, and also by Data Objects defined by Commands. Thus, a Data Object comprises a configurable request for data that is issued through Commands to the Adapters of the enterprise data sources. The architecture provides an application developer with the ability to create custom enterprise connectivity to disparate backend enterprise data sources.

Abstract: A data architecture provides mobile clients with the ability to gain access to business enterprise data sources through configurable Views that interface with the data sources through Data Objects that are defined by Commands, which in turn communicate with the data sources through Connectors (also referred to as Adapters). Each type of View will interface to the data sources with a different functionality so that communications links and other system resources can be used more efficiently. The View types can include Direct Views, Derived Views, Delegated Views, and Definition Views.

Abstract: Operating sequences of a mobile data integration system include operational modules, also called transportable applications (“TransApps”), that are self contained and capable of being linked together with other operating sequences and TransApps. Each operational module can accept input data and can generate output data. The input data can be received from other modules, or from the application user, or from enterprise data sources. The output data can be provided to other modules, or to the application server (for enterprise data sources), or can be provided for display on the mobile computing device itself. Modules can be defined for the purpose of particular problem solutions, and such problem solution modules can be reused during other application design efforts. This supports reuse of earlier solutions to problems.

Abstract: A data architecture provides mobile clients with the ability to gain access to business enterprise data sources through configurable Views that interface with the data sources through Data Objects that are defined by Commands, which in turn communicate with the data sources through Connectors (also referred to as Adapters). Each type of View will interface to the data sources with a different functionality so that communications links and other system resources can be used more efficiently. The View types can include Direct Views, Derived Views, Delegated Views, and Definition Views.

Abstract: A data architecture provides View objects that define an enterprise data source interface to an application through connectors, and also by Data Objects defined by Commands. Thus, a Data Object comprises a configurable request for data that is issued through Commands to the Adapters of the enterprise data sources. The architecture provides an application developer with the ability to create custom enterprise connectivity to disparate backend enterprise data sources.

Abstract: Data is shared between multiple enterprise data sources and mobile clients in a distributed system such that requests from a mobile client for enterprise data are received, the appropriate enterprise data sources that contain the requested data are determined, and the enterprise data is retrieved from the determined enterprise data sources. When the enterprise data is retrieved, it is converted into a relational format that can relate the retrieved data, even if the data comes from multiple enterprise data sources. The converted enterprise data is stored in a relational data store in the mobile client. In this way, mobile applications can be fully integrated with data from multiple enterprise data sources and data updates and configuration changes can be distributed to and from the mobile clients in real-time, without using interim data storage, and thereby avoiding complicated synchronization and data conflict issues between the enterprise data sources and the mobile clients.

Abstract: Data is shared between multiple enterprise data sources and mobile clients in a distributed system such that requests from a mobile client for enterprise data are received, the appropriate enterprise data sources that contain the requested data are determined, and the enterprise data is retrieved from the determined enterprise data sources. Data maintained at a mobile client is shared with multiple enterprise data sources. The mobile clients send requests to an application server for synchronization of data records maintained at the mobile client with corresponding data records at the enterprise data sources. The client request includes metadata that identifies enterprise data sources for the requested data records and that specifies a relational correspondence between the requested data. The mobile client data records and the corresponding data records of the enterprise data sources are compared to identify any data conflicts between the two sets of data records. Any identified data conflicts are resolved.