Process scheduling and execution in distributed computing environments

Patent metadata

Field	Value
Publication number	US-9804887-B2
Application number	US-201715439798-A
Country	US
Kind code	B2
Filing date	Feb 22, 2017
Priority date	Jul 10, 2014
Publication date	Oct 31, 2017
Grant date	Oct 31, 2017

Abstract

Embodiments of the invention provide systems and methods for scheduling and executing user-restricted processes within distributed computing systems. More specifically, certain embodiments of the present invention describe systems and methods by which runtime requests to execute user-restricted processes may be received, processed, and scheduled via a user application of an enterprise system or other distributed computing system. Requests may be received via transaction pages of user applications to schedule and execute user-restricted processes. The user application, a process scheduler, and/or other components within the distributed computing system may determine user contexts associated with the requests, and may determine whether or not the requested processes may be scheduled and executed. Such processes may include, for example, report generation processes, processes to initiate system functions, and/or processes to perform system maintenance within the distributed computing environment.

First claim

What is claimed is:

1. A method for scheduling execution of a user-restricted process within a distributed computing system, the method comprising:
receiving a runtime request to execute a user-restricted process within a distributed computing system, the runtime request received via a transaction page of a user application during a current runtime session of a user within the distributed computing system;
determining one or more characteristics of the current runtime session of the user within the distributed computing system, the characteristics including a number of user-restricted processes previously initiated by the user during the current runtime session; and
determining whether or not to permit execution of the user-restricted process based on (i) the user-restricted process, (ii) the user, and (iii) the number of user-restricted processes previously initiated by the user during the current runtime session, wherein determining whether or not to permit execution of the user-restricted process comprises:
retrieving a previously stored threshold number of user-restricted processes permitted to be executed by the user per runtime session;
comparing the previously stored threshold number to the number of user-restricted processes previously initiated by the user during the current runtime session; and
in response to determining that the number of user-restricted processes previously initiated by the user during the current runtime session does not exceed the previously stored threshold number, determining that the execution of the user-restricted process is permitted and scheduling execution of the user-restricted process; and

wherein scheduling execution of the user-restricted process comprises:
retrieving data from the transaction page; and
initiating execution of the user-restricted process on the distributed computing system, using the data retrieved from the transaction page.

2. The method of claim 1 , wherein the one or more characteristics of the current runtime session further include a current level of network usage within the distributed computing system, and wherein the determination of whether or not to permit execution of the user-restricted process is further based on the current level of network usage within the distributed computing system.

3. The method of claim 1 , wherein the one or more characteristics of the current runtime session further include a current processing load within the distributed computing system, and wherein the determination of whether or not to permit execution of the user-restricted process is further based on the current processing load within the distributed computing system.

4. The method of claim 1 , wherein the one or more characteristics of the current runtime session further include an amount of time since the user has initiated the user-restricted processes within the distributed computing system, and wherein the determination of whether or not to permit execution of the user-restricted process is further based on the amount of time since the user has initiated the user-restricted processes within the distributed computing system.

5. The method of claim 1 , wherein the one or more characteristics of the current runtime session further include one or more transaction pages visited by the user during the current runtime session, and wherein the determination of whether or not to permit execution of the user-restricted process is further based on the transaction pages visited by the user during the current runtime session.

6. The method of claim 1 , wherein scheduling execution of the user-restricted process further comprises:
initiating the execution of the user-restricted process on the distributed computing system, using a predetermined set of process parameters that are not selectable by the user.

7. The method of claim 1 , wherein scheduling execution of the user-restricted process further comprises:
determining that one or more user-modifiable runtime variables are available for executing the user-restricted process; and
modifying the transaction page with an interface to retrieve the one or more user-modifiable runtime variables.

8. A computing system comprising:
a processing unit comprising one or more processors; and
memory coupled with and readable by the processing unit and storing therein a set of instructions which, when executed by the processing unit, causes the processing unit to schedule execution of a user-restricted process within the computing system by:
receiving a runtime request to execute a user-restricted process within the computing system, the runtime request received via a transaction page of a user application during a current runtime session of a user within the computing system;
determining one or more characteristics of the current runtime session of the user within the computing system, the characteristics including a number of user-restricted processes previously initiated by the user during the current runtime session; and
determining whether or not to permit execution of the user-restricted process based on (i) the user-restricted process, (ii) the user, and (iii) the number of user-restricted processes previously initiated by the user during the current runtime session wherein determining whether or not to permit execution of the user-restricted process comprises:
retrieving a previously stored threshold number of user-restricted processes permitted to be executed by the user per runtime session;
comparing the previously stored threshold number to the number of user-restricted processes previously initiated by the user during the current runtime session; and
in response to determining that the number of user-restricted processes previously initiated by the user during the current runtime session does not exceed the previously stored threshold number, determining that the execution of the user-restricted process is permitted and scheduling execution of the user-restricted process; and

wherein scheduling execution of the user-restricted process comprises:
retrieving data from the transaction page; and

initiating execution of the user-restricted process on the computing system, using the data retrieved from the transaction page.

9. The computing system of claim 8 , wherein the one or more characteristics of the current runtime session further include a current level of network usage within the computing system, and wherein the determination of whether or not to permit execution of the user-restricted process is further based on the current level of network usage within the computing system.

10. The computing system of claim 8 , wherein the one or more characteristics of the current runtime session further include a current processing load within the computing system, and wherein the determination of whether or not to permit execution of the user-restricted process is further based on the current processing load within the computing system.

11. The computing system of claim 8 , wherein the one or more characteristics of the current runtime session further include an amount of time since the user has initiated the user-restricted processes within the computing system, and wherein the determination of whether or not to permit execution of the user-restricted process is further based on the amount of time since the user has initiated the user-restricted processes within the computing system.

12. The computing system of claim 8 , wherein the one or more characteristics of the current runtime session further include one or more transaction pages visited by the user during the current runtime session, and wherein the determination of whether or not to permit execution of the user-

Assignees

• Oracle Int Corp

Inventors

• Rangaraju Ramasimha
• Gupta Virad
• Narayanan Deepankar
• Edalur Raghu
• Sahoo Mohini
• Verma Vivek

Classifications

• G06F21/121

  Restricting unauthorised execution of programs · CPC title

• H04L63/08

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

• G06Q30/0635

  replenishment orders; recurring orders · CPC title

• G06Q10/06

  Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling · CPC title

• G06F9/4843 Primary

  by program, e.g. task dispatcher, supervisor, operating system · CPC title