SYSTEM AND METHOD FOR CREATING AND EXECUTING PORTABLE SOFTWARE

• US 20110296528A1
• Filed: 05/26/2010
• Published: 12/01/2011
• Est. Priority Date: 05/26/2010
• Status: Active Grant

• Current Assignee: Automation Anywhere, Inc.
• Original Assignee: Tethys Solutions, LLC
• Inventors: Shukla, Mihir
• Granted Patent: US 8,504,803 B2
• Time in Patent Office: Days
• US Class Current: 726/25
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: G06F 2209/549 Remote execution
• CPC Class Codes: G06F 9/4843 by program, e.g. task dispatcher, supervisor, operating system

Abstract

This invention generally relates to a process, system and computer code for creating a portable unit on a first computer to be executed on remote computers including creating an execution file having one or more tasks for deployment, said tasks having command line arguments executable as variables by the remote computer, assembled into a single execution file, validating the tasks and organizing nested tasks, said organizing step including collecting nested task information for each task and accounting for all dependencies to insure that files, tasks, and environments for running on one or more remote computers are present in the portable unit, said step of creating an execution file further including, reading the task file, scanning for event dependencies and embedding files and links needed for remote execution of the execution file, storing the dependencies in a dependency file, scanning for security, verifying the task file for proper formatting.

Claims

1. A computer method for creating a portable unit on a first computer to be executed on one or more remote computers comprising the steps of:

creating an execution file having one or more tasks for deployment, said tasks having command line arguments executable as variables by the remote computer, assembled into a single execution file, validating the tasks and organizing nested tasks, said organizing step including collecting nested task information for each task and accounting for all dependencies to insure that files, tasks, and environments for running on one or more remote computers are present in the portable unit, said step of creating an execution file further including, reading the task file, scanning for event dependencies and embedding files and links needed for remote execution of the execution file, storing the dependencies in a dependency file, scanning for security, verifying the task file for proper formatting.

2. The computer method as in claim 1, wherein the portable unit includes a play engine.

3. The computer method as in claim 1, further including the step off appending the play engine to the execution file.

4. The computer method as in claim 1, wherein the portable unit passes arguments from the first computer to the remote computers for execution of the execution.

5. The computer method as in claim 1, further including a run script action.

6. The computer method as in claim 5, further including a script included in the execution file.

7. The computer method as in claim 5, wherein the script can have a non-existent script path so that the remote computer can run when tasks include external scripts.

8. Computer software embodied on a computer readable medium for creating a portable unit on a first computer to be executed on one or more remote computers comprising code for:

creating an execution file having one or more tasks for deployment, said tasks having command line arguments executable as variables by the remote computer, assembled into a single execution file, validating the tasks and organizing nested tasks, said organizing including collecting nested task information for each task and accounting for all dependencies to insure that files, tasks, and environments for running on one or more remote computers are present in the portable unit, creating an execution file further including, reading the task file, scanning for event dependencies and embedding files and links needed for remote execution of the execution file, storing the dependencies in a dependency file, scanning for security, verifying the task file for proper formatting.

9. Software embodied on a computer readable medium as in claim 8, wherein the portable unit includes code for a play engine.

10. Software embodied on a computer readable medium as in claim 8, further including code for appending the play engine to the execution file.

11. Software embodied on a computer readable medium as in claim 8, wherein the portable unit passes arguments from the first computer to the remote computers for execution of the execution.

12. Software embodied on a computer readable medium as in claim 8, further including code for a running script action.

13. Software embodied on a computer readable medium as in claim 12, further including code for inserting a script included in the execution file.

14. Software embodied on a computer readable medium as in claim 12, wherein the script can have a non-existent script path so that the remote computer can run when tasks include external scripts.

15. Software embodied on a computer readable medium as in claim 8, further including code supporting one of TN3270 or TN5250 IBM Mainframe access in Terminal Emulator functionality.

16. A computer system for creating a portable unit on a first computer to be executed on one or more remote computers comprising:

a one or more processors, a memory, a communications link and one or more databases containing;

an execution file having one or more tasks for deployment, said tasks having command line arguments executable as variables by the remote computer, assembled into a single execution file, said one or more processors configured to;

(a) validate the tasks and organize nested tasks, said organizing including collecting nested task information for each task and accounting for all dependencies to insure that files, tasks, and environments for running on one or more remote computers are present in the portable unit, (b) create an execution file further including, read the task file, scan for event dependencies and embed files and links needed for remote execution of the execution file, store the dependencies in a dependency file, scan for security, verify the task file for proper formatting.

17. A computer system as in claim 16, wherein the portable unit includes a play engine.

18. A computer system as in claim 16, further include a play engine appended to the execution file.

19. A computer system as in claim 16, wherein the portable unit passes arguments from the first computer to the remote computers for execution of the execution.

20. A computer system as in claim 16, wherein the one or more processors support one of TN3270 or TN5250 IBM Mainframe access in Terminal Emulator functionality.