| CPC G06F 9/4881 (2013.01) [G06F 9/45504 (2013.01)] | 20 Claims |
|
1. A CRON-based routing process to schedule and execute Java code excerpts across backend fault-tolerant load-balanced distributed servers running Java Virtual Machine (JVM) namespaces comprising the steps of:
(a) loading, by a first client into routing table on a CRON server, a first job request containing first fields for a first CRON execution time, a first namespace, a first route name, and first code location indicia identifying a first disk location, a first Jar file containing first partial Java code, a first Java class, and a first Java method;
(b) loading, by a second client into the routing table on the CRON server, a second job request containing second fields for a second CRON execution time, a second namespace, a second route name, and second code location indicia identifying a second disk location, a second Jar file containing second partial Java code, a second Java class, and a second Java method;
(c) loading, by a third client into the routing table on the CRON server, a third job request containing third fields for a third CRON execution time, a third namespace, a third route name, and third code location indicia identifying a third disk location, a third Jar file containing third partial Java code, a third Java class, and a third Java method;
(d) loading, by a fourth client into the routing table on the CRON server, a fourth job request containing fourth fields for a fourth CRON execution time, a fourth namespace, a fourth route name, and fourth code location indicia identifying a fourth disk location, a fourth Jar file containing fourth partial Java code, a fourth Java class, and a fourth Java method;
(e) electing, by the CRON server, a first server as a primary server;
(f) assigning, by the CRON server as secondary servers, a second server, a third server, and a fourth server;
(g) storing, by the CRON server in a server and IP address table, a server identifier, a primary/secondary designation, and an IP address for each of said first server, said second server, said third server, and said fourth server;
(h) allocating, by the primary server to itself and by the primary server to the secondary servers, a first JVM namespace on the primary server, a second JVM namespace on the second server, a third JVM namespace on the third server, and a fourth JVM namespace on the fourth server;
(i) executing, in the first JVM namespace at said first CRON execution time, said first partial Java code from the first Jar file to extract first data from one or more backend machines;
(j) executing, in the second JVM namespace at said second CRON execution time, said second partial Java code from the second Jar file to extract second data from said one or more backend machines;
(k) executing, in the third JVM namespace at said third CRON execution time, said third partial Java code from the third Jar file to extract third data from said one or more backend machines;
(l) executing, in the fourth JVM namespace at said fourth CRON execution time, said fourth partial Java code from the fourth Jar file to extract fourth data from said one or more backend machines;
(m) transforming, by the first JVM namespace, the first data into first frontend data;
(n) transforming, by the second JVM namespace, the second data into second frontend data;
(o) transforming, by the third JVM namespace, the third data into third frontend data;
(p) transforming, by the fourth JVM namespace, the fourth data into fourth frontend data;
(q) loading, by the first server, the first frontend data into frontend-accessible data storage;
(r) loading, by the second server, the second frontend data into said frontend-accessible data storage;
(s) loading, by the third server, the third frontend data into said frontend-accessible data storage;
(t) loading, by the fourth server, the fourth frontend data into said frontend-accessible data storage;
(u) retrieving, by a frontend computer from said frontend-accessible data storage in response to a request from a user, said first frontend data, said second frontend data, said third frontend data, or said fourth frontend data; and
(v) displaying, by the frontend computer, said frontend-accessible data to the user.
|