Providing an error log to a mobile device

1. A computer-implemented method of providing an error log, comprising:

establishing, by a hub computing system, a connection with a back-end computing system, the back-end computing system executing a first computer-implemented programming language;

receiving, at the hub computing system, a request for an error log from an Open Data Protocol (OData) application that resides on a mobile communications device, the mobile communications device executing a second computer-implemented programming language different than the first computer-implemented programming language, and the error log including error log entries associated with a runtime processing of a data model;

registering, on the hub computing system, the error log as an OData service configured to be provided over an OData channel between the hub computing system and the mobile communications device; and

providing, by the hub computing system, the error log to the OData application as the OData service over the OData channel.

2. The computer-implemented method of claim 1 , wherein providing the error log to the OData application comprises providing the error log though a web-based graphical user interface.

3. The computer-implemented method of claim 1 , further comprising authorizing the mobile communications device to receive the error log.

4. The computer-implemented method of claim 1 , wherein providing the error log to the OData application further comprises formatting the error log for display on a graphical user interface of the mobile communications device.

5. The computer-implemented method of claim 1 , wherein registering the error log as an OData service comprises:

generating a model provider class and a data provider class that are each associated with the error log; and

registering the model provider class and the data provider class to provide the error log as the OData service.

6. The computer-implemented method of claim 5 , further comprising:

generating a data object access class; and

based on the generated data object access class, providing access to an application programming interface (API) associated with the error log.

7. A non-transitory computer storage medium encoded with a computer program, the program comprising instructions that when executed by one or more computers cause the one or more computers to perform operations comprising:

establishing, by a hub computing system, a connection with a back-end computing system, the back-end computing system executing a first computer-implemented programming language;

receiving, at the hub computing system, a request for an error log from an Open Data Protocol (OData) application that resides on a mobile communications device, the mobile communications device executing a second computer-implemented programming language different than the first computer-implemented programming language, and the error log including error log entries associated with a runtime processing of a data model;

registering, on the hub computing system, the error log as an OData service configured to be provided over an OData channel between the hub computing system and the mobile communications device; and

providing, by the hub computing system, the error log to the OData application as the OData service over the OData channel.

8. The non-transitory computer storage medium of claim 7 , wherein providing the error log to the OData application comprises providing the error log though a web-based graphical user interface.

9. The non-transitory computer storage medium of claim 7 , the operations further comprising authorizing the mobile communications device to receive the error log.

10. The non-transitory computer storage medium of claim 7 , wherein providing the error log to the OData application further comprises formatting the error log for display on a graphical user interface of the mobile communications device.

11. The non-transitory computer storage medium of claim 7 , wherein registering the error log as an OData service comprises:

generating a model provider class and a data provider class that are each associated with the error log; and

registering the model provider class and the data provider class to provide the error log as the OData service.

12. The non-transitory computer storage medium of claim 11 , the operations further comprising:

generating a data object access class; and

based on the generated data object access class, providing access to an application programming interface (API) associated with the error log.

13. A system of one or more hardware computing devices, the one or more hardware computing devices configured to perform operations comprising:

establishing, by a hub computing system, a connection with a back-end computing system, the back-end computing system executing a first computer-implemented programming language;

receiving, at the hub computing system, a request for an error log from an Open Data Protocol (OData) application that resides on a mobile communications device, the mobile communications device executing a second computer-implemented programming language different than the first computer-implemented programming language, and the error log including error log entries associated with a runtime processing of a data model;

registering, on the hub computing system, the error log as an OData service configured to be provided over an OData channel between the hub computing system and the mobile communications device; and

providing, by the hub computing system, the error log to the OData application as the OData service over the OData channel.

14. The system of claim 13 , wherein providing the error log to the OData application comprises providing the error log though a web-based graphical user interface.

15. The system of claim 13 , the operations further comprising authorizing the mobile communications device to receive the error log.

16. The system of claim 13 , wherein providing the error log to the OData application further comprises formatting the error log for display on a graphical user interface of the mobile communications device.

17. The system of claim 13 , wherein registering the error log as an OData service comprises: generating a model provider class and a data provider class that are each associated with the error log; and

registering the model provider class and the data provider class to provide the error log as the OData service.