1460931791-97f67e22-6b48-4572-a956-0997de7aeb13

1. An information handling system comprising:
a connection via a network interface for receiving a plurality of executable system integration software application performance data types from an integrated business process event that conducts a transformation of documents between a first document format and a second document format to enable electronic data exchange between data formats using automatically-generated, customized executable system integration software application code having a plurality of integration code elements;
a storage device for storing and aggregating the plurality of executable system integration software application performance data types for one or more integrated business process events being monitored;
a display connected to the information handling system for receiving data to be rendered as a hierarchical dashboard graphical user interface; and
a processor adapted to update the aggregated plurality of executable system integration software application performance data types;
the processor querying and receiving executable system integration software application performance data types; and
the processor preparing the plurality of executable system integration software application performance data types received in response to the query to be rendered as lists or plotted graphs in the hierarchical dashboard graphical user interface in real time,
wherein the plurality of executable system integration software application performance data types further comprises:
a count of inbound documents for transformation into the second format by the integrated business process event
a count of integration code elements used;
an identification of types of integration code elements used for transformation of documents between a first document format and a second document format;
a number of integrated business process event errors recorded during transformation of documents between a first document format and a second document format; and
a status of the integrated business process event conducting the transformation.
2. (canceled)
3. The system of claim 1, wherein the plurality of executable system integration software application performance data types further comprises a count of outbound documents transformed by the integrated business process event.
4. The system of claim 1, wherein the information handling system storage device and display are located in a network separate from a location where the integrated business process event occurred.
5. The system of claim 1, wherein the information handling system storage device and display are located in a same network as a location where the integrated business process event occurred.
6. The system of claim 1, wherein the one or more processors receive data representing elections made via the hierarchical dashboard graphical user interface to determine the scope of one of the plurality of executable system integration software application performance data types to be viewed.
7. (canceled)
8. A method of monitoring operation of executable system integration software application performance for use with an information handling system, the method comprising:
receiving at a database storage device a plurality of executable system integration software application performance data types from an integrated business process event that conducts the transformation of documents between a first document format and a second document format to enable electronic data exchange between data formats using automatically-generated, customized executable system integration software application code having a plurality of integration code elements;
at a processor, periodically checking for the recently received executable system integration software application performance data;
associating one or more integrated business process events with a user account deploying the executable system integration software application;
updating executable system integration software application performance data affiliated with a user account;
receiving data representing elections made via a hierarchical dashboard graphical user interface to determine a scope of at least one executable system integration software application performance data types to be viewed;
according to the elections made, generating the scope of the executable system integration software application performance data of the type elected; and
rendering for display as lists or plotted graphs the plurality of executable system integration software application performance data types in the hierarchical dashboard graphical user interface,
and wherein the plurality of executable system integration software application performance data types further comprises:
a count of integrated business process event errors recorded during the transformation of documents from the first document format to the second document format;
a count of outbound documents transformed by the integrated business process event;
an identification of types of integration code elements used for transformation of documents between a first document format and a second document format; and
a status of the integrated business process event conducting the transformation.
9. (canceled)
10. The method of claim 8, wherein the plurality of executable system integration software application performance data types further comprises throughput levels of data passing through the integrated business process event for the transformation of documents.
11. The method of claim 8, further comprising receiving the plurality of executable system integration software application performance data types for the integrated business process event that occurred in a location that is separate from a network containing the database storage device.
12. The method of claim 8, further comprising receiving the plurality of executable system integration software application performance data types for the integrated business process event that occurred in a location that is the same as a network containing the database storage device.
13. The method of claim 8, further comprising displaying via the hierarchical dashboard graphical user interface a list of integrated business process event errors on a per user account basis and a number of integrated business process event errors for that user account.
14. The method of claim 10, further comprising displaying via the hierarchical dashboard graphical user interface a histogram display of data representing data throughput levels for the integrated business process events for the user account.
15. A non-transitory computer readable medium comprising instructions to:
periodically check a directory of a plurality of executable system integration software application performance data types in a database for a recently received executable system integration software application performance data for an integrated business process event that conducts the transformation of documents between a first document format and a second document format to enable electronic data exchange between data formats using executable system integration software application code;
update executable system integration software application performance data for an integrated business process affiliated with a user account deploying the executable system integration software application code, the update comprising adding recently received executable system integration software application performance data to aggregate executable system integration software application performance data in the database for an integrated business process;
receive data representing elections made via a hierarchical dashboard graphical user interface to determine a scope of the at least one executable system integration software application performance data type to be viewed;
query the updated executable system integration software application performance data; and
according to the elections made, generate the scope of executable system integration software application performance data for the type selected and render for display as lists or plotted graphs the plurality of executable system integration software application performance data types in the hierarchical dashboard graphical user interface,
wherein the plurality of executable system integration software application performance data types further comprises:
throughput levels of data passing through the integrated business process event for the transformation of documents;
an identification of types of integration code elements used for transformation of documents between a first document format and a second document format; and
a number of integrated business process event errors recorded during the transformation of documents from the first document format to the second document format.
16. The computer readable medium of claim 15, wherein the instructions further comprise instructions to generate the plurality of executable system integration software application performance data types further comprising a count of inbound documents for transformation into the second format by the integrated business process event.
17. The computer readable medium of claim 15, wherein the instructions further comprise instructions to generate the plurality of executable system integration software application performance data types further comprising a count of outbound documents transformed by the integrated business process event.
18. The computer readable medium of claim 15, wherein the instructions further comprise instructions to receive the plurality of executable system integration software application performance data types for the integrated business process event that occurred in a location that is separate from a network containing the database.
19. The computer readable medium of claim 15, wherein the instructions further comprise instructions to receive plurality of executable system integration software application performance data types for the integrated business process event that occurred in a location that is the same network containing the database.
20. The computer readable medium of claim 15, wherein the instructions further comprise instructions to display via the hierarchical dashboard graphical user interface a list of integrated business process event errors on a per user account basis and a number of integrated business process event errors for that user account.
21. (canceled)
22. (canceled)
23. The system of claim 1, wherein the plurality of executable system integration software application performance data further comprises a number of integrated business process event errors for each of the plurality of integration code elements.
24. The computer readable medium of claim 15, wherein the instructions further comprise instructions to display via the hierarchical dashboard graphical user interface a list of integrated business process event errors on a per user account basis and a number of integrated business process event errors for that user account.
25. The computer readable medium of claim 15, wherein the instructions further comprise instructions to display via the hierarchical dashboard graphical user interface a list of integrated business process event errors on a per user account basis and a number of integrated business process event errors for that user account.

The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.

I claim:

1. A method of treating insulin-requiring diabetes in a mammal comprising administering to the mammal in a suitable regimen an effective amount of insulin and an effective amount of a peptide comprising a peptide selected from the group consisting of
(a) glucagon-like peptide 1(7-37);
(b) glucagon-like peptide 1(7-36)amide; and
(c) an effective fragment or analogue of (a) or (b)
2. The method of claim 1 wherein the mammal is a human.
3. The method of claim 2 wherein an effective amount of insulin and an effective amount of a peptide comprising a peptide selected from the group consisting of
(a) glucagon-like peptide 1(7-37);
(b) glucagon-like peptide 1(7-36)amide; and
(c) an effective fragment or analogue of (a) or (b) are administered to the human at a selected time prior to ingestion of a meal.
4. The method of any of claims 1 to 3 wherein the insulin-requiring diabetes is Type I diabetes.
5. The method of any of claims 1 to 3 wherein the insulin-requiring diabetes is Type II diabetes.
6. Use of a peptide comprising a peptide selected from the group consisting of
(a) glucagon-like peptide 1(7-37);
(b) glucagon-like peptide 1(7-36)amide; and
(c) an effective fragment or analogue of (a) or (b) for the preparation of a medicament for use in the treatment of insulin-requiring diabetes in a suitable regimen which additionally comprises treatment with insulin.
7. Use of a peptide comprising a peptide selected from the group consisting of
(a) glucagon-like peptide 1(7-37);
(b) glucagon-like peptide 1(7-36)amide; and
(c) an effective fragment or analogue of (a) or (b) for the preparation of a medicament which also includes insulin for treatment of insulin-requiring diabetes.
8. Use of a peptide in accordance with claim 6 or 7 wherein the insulin-requiring diabetes is Type I diabetes.
9. Use of a peptide in accordance with claim 6 or 7 wherein the insulin-requiring diabetes is Type II diabetes.
10. A pharmaceutical composition for the treatment of insulin-requiring diabetes comprising an effective amount of a peptide comprising a peptide selected from the group consisting of
(a) glucagon-like peptide 1(7-37);
(b) glucagon-like peptide 1(7-36)amide; and
(c) an effective fragment or analogue of (a) or (b) and a pharmaceutically acceptable carrier.
11. A pharmaceutical composition in accordance with claim 10 for the treatment of Type I diabetes.
12. The pharmaceutical composition of claim 10 or 11 further comprising an effective amount of insulin.
13. A method of treating Type I diabetes in a mammal comprising administering to the mammal an effective amount of a peptide comprising a peptide selected from the group consisting of
(a) glucagon-like peptide 1(7-37);
(b) glucagon-like peptide 1(7-36)amide; and
(c) an effective fragment or analogue of (a) or (b).
14. Use of a peptide comprising a peptide selected from the group consisting of
(a) glucagon-like peptide 1(7-37);
(b) glucagon-like peptide 1(7-36)amide; and
(c) an effective fragment or analogue of (a) or (b) for the preparation of a medicament for use in the treatment of Type I diabetes.