Java Enterprise Resource Management System and Method

A Java enterprise resource management (JERM) method comprising:

• at a server-side end of a communications socket, receiving a serial byte stream communicated over a communications socket from a client-side end of the communications socket to the server-side end of the communications socket, the serial byte stream including at least a first metric monitored and gathered by a production server located on a client side of a network during performance of one or more transactions by the production server;
• in one or more processing devices located on the server side of the network, deserializing the serial byte stream received at the server-side end of the communications socket;
• in said one or more processing devices, analyzing the deserialized byte stream to decide whether at least a first rule is to be applied to said at least a first metric;
• in said one or more processing devices, if a decision is made that at least a first rule is to be applied to said at least a first metric, deciding whether said at least a first metric is in compliance with said at least a first rule and producing a decision regarding compliance;
• and
• in said one or more processing devices, analyzing the decision regarding compliance and making a decision as to whether at least one physical instance, at least one virtual instance, or a combination of one or more physical and virtual instances needs to be scaled out or scaled in on the client side.

A computer-readable medium (CRM) having instructions stored thereon for performing a Java enterprise resource management (JERM) method on a server side of a network, the instructions that are stored on the CRM comprising:

• at least a first deserializer computer code portion, wherein when the first deserializer computer code portion runs on a JERM management server located on the server side of the network, the first deserializer computer code portion receives a serial byte stream corresponding to at least a first metric communicated over a communications socket from a production server located on a client side of the network and deserializes the received byte stream to produce a deserialized byte stream containing information relating to said at least a first metric, said at least a first metric corresponding to one or more metrics monitored and gathered by the production server while a transaction is performed by the production server;
• at least a first rules management computer code portion, wherein when the first rules management computer code portion runs on the JERM management server, the first rules management computer code portion decides whether a rule exists that is associated with said at least a first metric, wherein if the first rules management computer code portion decides that an associated rule exists, the first rules management computer code portion applies the associated rule to the deserialized byte stream and produces a decision as to whether said at least a first metric is in compliance with the associated rule;
• and
• at least a first actions manager computer code portion, wherein when the first actions manager computer code portion runs on the JERM management server, the first actions manager computer code portion determines, based on the decision as to whether said at least a first metric is in compliance with an associated rule, whether at least one action needs to be taken, wherein if the first actions manager computer code portion determines that at least one action needs to be taken, the first actions manager computer code portion causes one or more commands to be sent to the client side of the network to cause one or more production servers located on the client side of the network to perform one or more tasks consistent with said one or more commands.