GENERATING NOTIFICATION FROM DATABASE UPDATE
A computer-implemented method for generating a notification from an in-memory database update includes: detecting an in-memory database event that inserts, deletes or modifies a first record in an in-memory database; executing a first database trigger that corresponds to the detected in-memory database event; identifying a first business event definition that is mapped to the executed first database trigger; and generating a first notification that corresponds to the identified first business event definition, the first notification generated for a first subscriber to the identified first business event definition.
1 . A computer-implemented method for generating a notification from an in-memory database update, the method comprising:
detecting an in-memory database event that inserts, deletes or modifies a first record in an in-memory database;
executing a first database trigger that corresponds to the detected in-memory database event;
identifying a first business event definition that is mapped to the executed first database trigger; and
generating a first notification that corresponds to the identified first business event definition, the first notification generated for a first subscriber to the identified first business event definition.
2 . The computer-implemented method of claim 1 , wherein the first database trigger is executed using a trigger engine operating in a server hosting the in-memory database, wherein the first business event definition is identified by an event publisher operating in an application server associated with the server, and wherein the notification is generated by a notification publisher operating in a gateway system hosted by the application server.
3 . The computer-implemented method of claim 1 , wherein:
an application is operated by executing custom code in an application container hosted by an application server;
the first subscriber to the first identified business event includes at least the application;
the application generates an alert to a gateway system hosted by the application server, the alert generated using an API of the gateway system;
a subscription manager in the gateway system identifies a second subscriber to the generated alert; and
a notification publisher hosted by the gateway system generates a second notification that corresponds to the generated alert, the second notification generated for the identified second subscriber.
4 . The computer-implemented method of claim 1 , wherein the executed first database trigger further inserts, deletes or modifies a second record in the in-memory database, and wherein the insertion, deletion or modification of the second record further causes a second database trigger to be executed.
5 . The computer-implemented method of claim 4 , wherein the first subscriber to the identified business event definition is not a subscriber to a second business event definition that is mapped to the executed second database trigger.
6 . The computer-implemented method of claim 1 , further comprising specifying, before the first database trigger is executed, whether the first database trigger is executed (i) once for each affected record in the in-memory database, or (ii) once for each execution of an operation that affects one or more records in the in-memory database.
7 . The computer-implemented method of claim 1 , further comprising presenting a subscription control adjacent a user interface feature regarding at least the first record in the in-memory database, wherein activation of the subscription control establishes subscription to the first business event definition.
8 . A computer program product embodied in a non-transitory computer-readable storage medium and comprising instructions that when executed by a processor perform a method for generating a notification from an in-memory database update, the method comprising:
detecting an in-memory database event that inserts, deletes or modifies a first record in an in-memory database;
executing a first database trigger that corresponds to the detected in-memory database event;
identifying a first business event definition that is mapped to the executed first database trigger; and
generating a first notification that corresponds to the identified first business event definition, the first notification generated for a first subscriber to the identified first business event definition.
9 . The computer program product of claim 8 , wherein the first database trigger is executed using a trigger engine operating in a server hosting the in-memory database, wherein the first business event definition is identified by an event publisher operating in an application server associated with the server, and wherein the notification is generated by a notification publisher operating in a gateway system hosted by the application server.
10 . The computer program product of claim 8 , wherein:
an application is operated by executing custom code in an application container hosted by an application server;
the first subscriber to the first identified business event includes at least the application;
the application generates an alert to a gateway system hosted by the application server, the alert generated using an API of the gateway system;
a subscription manager in the gateway system identifies a second subscriber to the generated alert; and
a notification publisher hosted by the gateway system generates a second notification that corresponds to the generated alert, the second notification generated for the identified second subscriber.
11 . The computer program product of claim 8 , wherein the executed first database trigger further inserts, deletes or modifies a second record in the in-memory database, and wherein the insertion, deletion or modification of the second record further causes a second database trigger to be executed.
12 . The computer program product of claim 11 , wherein the first subscriber to the identified business event definition is not a subscriber to a second business event definition that is mapped to the executed second database trigger.
13 . The computer program product of claim 8 , the method further comprising specifying, before the first database trigger is executed, whether the first database trigger is executed (i) once for each affected record in the in-memory database, or (ii) once for each execution of an operation that affects one or more records in the in-memory database.
14 . The computer program product of claim 8 , the method further comprising presenting a subscription control adjacent a user interface feature regarding at least the first record in the in-memory database, wherein activation of the subscription control establishes subscription to the first business event definition.
15 . A system comprising:
one or more processors; and
a computer program product embodied in a non-transitory computer-readable storage medium and comprising instructions that when executed by a processor perform a method for generating a notification from an in-memory database update, the method comprising:
detecting an in-memory database event that inserts, deletes or modifies a first record in an in-memory database;
executing a first database trigger that corresponds to the detected in-memory database event;
identifying a first business event definition that is mapped to the executed first database trigger; and
generating a first notification that corresponds to the identified first business event definition, the first notification generated for a first subscriber to the identified first business event definition.
16 . The system of claim 15 , wherein the first database trigger is executed using a trigger engine operating in a server hosting the in-memory database, wherein the first business event definition is identified by an event publisher operating in an application server associated with the server, and wherein the notification is generated by a notification publisher operating in a gateway system hosted by the application server.
17 . The system of claim 15 , wherein:
an application is operated by executing custom code in an application container hosted by an application server;
the first subscriber to the first identified business event includes at least the application;
the application generates an alert to a gateway system hosted by the application server, the alert generated using an API of the gateway system;
a subscription manager in the gateway system identifies a second subscriber to the generated alert; and
a notification publisher hosted by the gateway system generates a second notification that corresponds to the generated alert, the second notification generated for the identified second subscriber.
18 . The system of claim 15 , wherein the executed first database trigger further inserts, deletes or modifies a second record in the in-memory database, and wherein the insertion, deletion or modification of the second record further causes a second database trigger to be executed.
19 . The system of claim 18 , wherein the first subscriber to the identified business event definition is not a subscriber to a second business event definition that is mapped to the executed second database trigger.
20 . The system of claim 15 , the method further comprising presenting a subscription control adjacent a user interface feature regarding at least the first record in the in-memory database, wherein activation of the subscription control establishes subscription to the first business event definition.