Event consumption for high-level programing language platform
Embodiments may facilitate event processing for an ABAP platform. A business object data store may include a RAP model, including a behavior definition, for a business object. A framework may automatically transform the behavior definition of the RAP model into a producer event vian event binding and a cloud event standardized format. Information about the producer event may then be passed to an ABAP application associated with a pre-configured destination at an enterprise business technology platform. In some embodiments, a standalone API enterprise hub data store may contain an event specification. An ABAP development tenant of a business technology platform may automatically parse the event specification and translate the parsed information into high-level programming language structures that reflect an event type at runtime. An event consumption model may then be generated based on the event type.
1. A system to facilitate event processing for a high-level programing language platform, comprising:
an Application Programming Interface (“API”) enterprise hub data store containing electronic records that include an event specification; and
a high-level programming language development tenant of a business technology platform, coupled to the API enterprise hub data store, including:
a computer processor, and
a memory storage device, coupled to the computer processor, including instructions that, when executed by the computer processor, enable the high-level programming language development tenant to:
(i) access, from the API enterprise hub data store, the event specification,
(ii) automatically parse the event specification,
(iii) translate the parsed information into high-level programming language structures that reflect an event type at runtime, and
(iv) generate an event consumption model based on the event type.
2. The system of claim 1 , wherein the high-level programming language comprises an Advanced Enterprise application Programming (“ABAP”) language.
3. The system of claim 2 , wherein the event specification comprises an AsyncAPI specification.
4. The system of claim 3 , wherein the AsyncAPI specification describes a header structure and payload event types emitted and consumed by ABAP applications.
5. The system of claim 3 , wherein the development tenant is associated with an event consumption model wizard.
6. The system of claim 3 , wherein the event type has a behavior definition that defines a hierarchical connection of a named root abstract entity and associated abstract entities.
7. The system of claim 3 , wherein the development tenant, responsive to a detection of an event definition change, adjusts event handler classes and regenerates a data container for the event type.
8. The system of claim 3 , wherein an OData model representation associated with the event type is automatically converted into a corresponding AsyncAPI specification.
9. The system of claim 8 , wherein the conversion is associated with metadata extraction and a simple transformation.
10. The system of claim 3 , wherein the AsyncAPI specification comprises a JavaScript Object Notation (“JSON”) file and a simple transformation is performed on the JSON file to create an ABAP readable representation associated with elements of an abstract entity.
11. The system of claim 10 , wherein the elements comprise at least one of: (i) primitive elements, (ii) primitive element collections, (iii) complex elements, and (iv) complex element collections.
12. A computer-implemented method to facilitate event processing for a high-level programing language platform, comprising:
accessing, by a high-level programming language development tenant of a business technology platform from an Application Programming Interface (“API”) enterprise hub data store, an event specification, wherein the API enterprise hub data store contains electronic records that include the event specification;
automatically parsing the event specification;
translating the parsed information into high-level programming language structures that reflect an event type at runtime; and
generating an event consumption model based on the event type.
13. The method of claim 12 , wherein the high-level programming language comprises an Advanced Enterprise application Programming (“ABAP”) language.
14. The method of claim 13 , wherein the event specification comprises an AsyncAPI specification.
15. The method of claim 14 , wherein the AsyncAPI specification describes a header structure and payload event types emitted and consumed by ABAP applications.
16. The method of claim 14 , wherein the development tenant is associated with an event consumption model wizard.
17. The method of claim 14 , wherein the event type has a behavior definition that defines a hierarchical connection of a named root abstract entity and associated abstract entities.
18. The method of claim 14 , wherein the development tenant, responsive to a detection of an event definition change, adjusts event handler classes and regenerates a data container for the event type.
19. A non-transitory, computer readable medium having executable instructions stored therein to perform a method to facilitate event processing for a high-level programing language platform, the method comprising:
accessing, by a high-level programming language development tenant of a business technology platform from an Application Programming Interface (“API”) enterprise hub data store, an event specification, wherein the API enterprise hub data store contains electronic records that include the event specification;
automatically parsing the event specification;
translating the parsed information into high-level programming language structures that reflect an event type at runtime; and
generating an event consumption model based on the event type.
20. The medium of claim 19 , wherein the high-level programming language comprises an Advanced Enterprise application Programming (“ABAP”) language and the event specification comprises an AsyncAPI specification.
21. The medium of claim 20 , wherein an OData model representation associated with the event type is automatically converted into a corresponding AsyncAPI specification.
22. The medium of claim 21 , wherein the conversion is associated with metadata extraction and a simple transformation.
23. The medium of claim 20 , wherein the AsyncAPI specification comprises a JavaScript Object Notation (“JSON”) file and a simple transformation is performed on the JSON file to create an ABAP readable representation associated with elements of an abstract entity.
24. The medium of claim 23 , wherein the elements comprise at least one of: (i) primitive elements, (ii) primitive element collections, (iii) complex elements, and (iv) complex element collections.