Database job description and scheduling

Patent metadata

Field	Value
Publication number	US-10146824-B2
Application number	US-201414310698-A
Country	US
Kind code	B2
Filing date	Jun 20, 2014
Priority date	Nov 25, 2013
Publication date	Dec 4, 2018
Grant date	Dec 4, 2018

Abstract

A system includes acquisition of executable code of a database job, generation of a definition of the database job in a database repository, the definition of the database job comprising metadata specifying the executable code of the database job and a schedule for executing the executable code, association of a user with the database job, and activation of the database job.

First claim

What is claimed is:

1. A system comprising:
a memory storing:
a database; and
a database repository; and

a processor to execute the processor-executable process steps to cause the system to:
acquire executable code of a database job, wherein the database job is a task different from client request/response processing, and wherein the executable code of the database job comprises a JavaScript function or a SQL-Script procedure identified by a file extension distinguishable from client-side JavaScript function executable code or client-side SQL-Script procedure executable code, and wherein a JavaScript handler reads a runtime object with JavaScript byte code, and invokes the JavaScript runtime for executing the JavaScript function executable code when the executable code of the database job comprises the JavaScript function executable code;
generate a definition of the database job as a repository object in the database repository, the definition of the database job comprising: (1) metadata specifying the executable code of the database job; and (2) a schedule for executing the executable code relative to, and in advance of, a specific time period, wherein the schedule was predetermined during a design time of an application;
associate a user with the database job; and
activate the database job.

2. A system according to claim 1 , wherein the metadata specifies the schedule based on a temporal relation to a last day of a month.

3. A system according to claim 2 , wherein the processor is further to execute the processor-executable process steps to cause the system to:
associate a start timestamp and an end timestamp with the database job.

4. A system according to claim 2 , wherein activation of the database job comprises compilation of executable code associated with the database job into byte code and storing the byte code in the database repository as a runtime object.

5. A system according to claim 2 , wherein the metadata specifies a second schedule for executing the executable code.

6. A system according to claim 1 , further comprising:
associating a start timestamp and an end timestamp with the database job.

7. A system according to claim 1 , wherein activation of the database job comprises compilation of executable code associated with the database job into byte code and storing the byte code in the database repository as a runtime object.

8. A computer-implemented method comprising:
acquiring executable code of a database job, wherein the database job is a task different from client request/response processing, and wherein the executable code of the database job comprises a JavaScript function or a SQL-Script procedure identified by a file extension distinguishable from client-side JavaScript function executable code or client-side SQL-Script procedure executable code, and wherein a JavaScript handler reads a runtime object with JavaScript byte code, and invokes the JavaScript runtime for executing the JavaScript function executable code when the executable code of the database job comprises the JavaScript function executable code;
generating a definition of the database job as a repository object in a database repository, the definition of the database job comprising: (1) metadata specifying the executable code of the database job; and (2) a schedule for executing the executable code relative to, and in advance of, a specific time period, wherein the schedule is predetermined during a design time of an application;
associating a user with the database job; and
activating the database job.

9. A computer-implemented method according to claim 8 , wherein the metadata specifies the schedule based on a temporal relation to a last day of a month.

10. A computer-implemented method according to claim 9 , further comprising:
associating a start timestamp and an end timestamp with the database job.

11. A computer-implemented method according to claim 9 , wherein activating the database job comprises compiling executable code associated with the database job into byte code and storing the byte code in the database repository as a runtime object.

12. A computer-implemented method according to claim 8 , wherein the metadata specifies a second schedule for executing the executable code.

13. A computer-implemented method according to claim 8 , further comprising: associating a start timestamp and an end timestamp with the database job.

14. A computer-implemented method according to claim 8 , wherein activating the database job comprises compiling executable code associated with the database job into byte code and storing the byte code in the database repository as a runtime object.

15. A non-transitory computer-readable medium storing program code, the program code executable by a computer system to cause to the computer system to:
acquire executable code of a database job, wherein the database job is a task different from client request/response processing, and wherein the executable code of the database job comprises a JavaScript function or a SQL-Script procedure identified by a file extension distinguishable from client-side JavaScript function executable code or client-side SQL-Script procedure executable code, and wherein a JavaScript handler reads a runtime object with JavaScript bye code, and invokes the JavaScript runtime for executing the JavaScript function executable code when the executable code of the database job comprises the JavaScript function executable code;
generate a definition of the database job as a repository object in a database repository, the definition of the database job comprising: (1) metadata specifying the executable code of the database job; and (2) a schedule for executing the executable code relative to, and in advance of, a specific time period, wherein the schedule is predetermined during a design time of an application;
associate a user with the database job; and
activate the database job.

16. A non-transitory computer-readable medium according to claim 15 , wherein the metadata specifies the schedule based on a temporal relation to a last day of a month.

17. A non-transitory computer-readable medium according to claim 16 , the program code executable by the computer system to cause to the computer system to:
associate a start timestamp and an end timestamp with the database job.

18. A non-transitory computer-readable medium according to claim 16 , wherein activation of the database job comprises compilation of executable code associated with the database job into byte code and storing the byte code in the database repository as a runtime object.

19. A non-transitory computer-readable medium according to claim 15 , wherein the metadata specifies a second schedule for executing the executable code.

20. A non-transitory computer-readable medium according to claim 15 , wherein activation of the database job comprises compilation of executable code associated with the database job into byte code and storing the byte code in the database repository as a runtime object.

Assignees

• Friedmann Bjoern
• Foebel Florian
• Gruschko Boris
• Mohr Christian
• Strenge Martin
• Zorn Sascha
• Sap Se

Inventors

• Friedmann Bjoern
• Foebel Florian
• Gruschko Boris
• Mohr Christian
• Strenge Martin
• Zorn Sascha

Classifications

• H04L63/08

  for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32) · CPC title

• G06F11/3668

  Testing of software · CPC title

• G06F16/2365 Primary

  Ensuring data consistency and integrity · CPC title

• H04L63/083

  using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226) · CPC title

• G06F16/21

  Design, administration or maintenance of databases · CPC title