Method and apparatus for load balancing in a distributed object architecture

Claim 3

The system of claim 1 , wherein publishing an event includes passing the event to the event publisher for further publication into an event channel, wherein the event channel passes the event to the plurality of event subscriber objects.

Claim 4

The system of claim 1 , wherein the load parameters calculated from the plurality of selected server hosts includes a value representing a number of system threads in queue waiting on a central processing unit on the server host and a power rating which has been pre-assigned to the plurality of server hosts.

Claim 5

The system of claim 1 , wherein the event subscriber instantiates an object of a subscribing server class on the selected server host identified in the event for the subscribing server class in the event that no such object is instantiated on the selected server host when the event subscriber receives the event.

Claim 6

The system of claim 1 , wherein the plurality of load balancers query the plurality of server hosts at randomized time intervals.

Claim 7

The system of claim 1 , wherein the selected server host identity and subscribing server class are coupled in a table within the published event.

Claim 8

In a system for balancing the distribution of event messages in a distributed object computing environment having at least one client publishing an event containing information and a plurality of server classes residing on a plurality of server hosts, at least one server class subscribing to the event published by the client, a plurality of event subscriber objects each being affiliated with a server host, and a plurality of load balancers, each load balancer querying the plurality of server hosts to calculate a load parameter for each server host, a computer program product comprising a computer useable medium having computer readable program code to direct the system to perform at least the following steps: a) registering at least one server class as a subscriber for selected events; b) for each subscribing server class, registering one or more server hosts as capable of running an instance of the subscribing server class; c) publishing the event by the client; d) reception of the event by at least one of the plurality of load balancers; e) selection and identification of a server host for each subscribing server class registered to subscribe to the event by the load balancer receiving the event based on load parameters calculated and the server hosts registered capable of running an instance of the subscribing server class; f) coupling the selected server host identity for each subscribing server class to the event and further publication of the event into the distributed object computing environment by the load balancer receiving the event; g) reception of the event by each event subscriber object, each event subscriber object reviewing the selected server host identity information, if the selected server host affiliated with at least one event subscriber object, the event subscriber object passing the event onto the selected server host for processing; and h) performance of logical operations by at least one instance of each subscribing server class for the published event as designated by the selected server host identity information coupled to the event, and not by instances on other server hosts.

Claim 9

In a system for balancing the distribution of event messages in a distributed object computing environment having at least one client publishing an event containing information and a plurality of server classes residing on a plurality of server hosts, at least one server class subscribing to the event published by the client, a plurality of event subscriber objects each being affiliated with a server host, and a plurality of load balancers, each load balancer querying the plurality of server hosts to calculate a load parameter for each server host, a computer program product comprising a computer useable medium having computer readable program code to direct the system to perform at least the following steps: a) registering at least one server class as a subscriber for selected events; b) for each subscribing server class, registering one or more server hosts as capable of running an instance of the subscribing server class; c) publishing the event by the client; d) reception of the event by at least one of the plurality of load balancers; e) selection and identification of a server host for each subscribing server class registered to subscribe to the event by the load balancer receiving the event based on load parameters calculated and the server hosts registered capable of running an instance of the subscribing server class; f) coupling the selected server host identity for each subscribing server class to the event and further publication of the event into the distributed object computing environment by the load balancer receiving the event; g) reception of the event by each event subscriber object, each event subscriber object reviewing the selected server host identity information, if the selected server host affiliated with at least one event subscriber object, the event subscriber object passing the event onto the selected server host for processing; and h) performance of logical operations by at least one instance of each subscribing server class for the published event as designated by the selected server host identity information coupled to the event, and not by instances on other server hosts.

Claim 10

The computer program product of claim 7 , wherein publishing the event includes passing the event to an event publisher for further publication into an event channel, wherein the event channel passes the event to the plurality of event subscribers.

Claim 11

The computer program product of claim 7 , wherein the event subscriber object instantiates an object of a subscribing server class on the selected server host identified in the event for the subscribing server class in the event that no such object is instantiated on the selected server host when the event subscriber object receives the event.

Claim 14

The method of claim 10 , wherein publishing the event includes passing the event to an event publisher for further publication into an event channel.

Claim 15

The method of claim 11 , wherein the event channel passes the event to a plurality of event subscribers, wherein for each event published, at least one event subscriber passes the event to the subscribing server object on the identified server host.

Claim 16

The method of claim 10 , wherein at least one of the load parameters collected from the plurality of server hosts include a value representing a number of system threads in queue waiting on a central processing unit on the selected server host.

Claim 17

The method of claim 13 , further comprising the step of: g) assigning to the pluralty of server hosts a power rating, wherein the power rating is combined with the other load parameters to determine which of the plurality of server hosts having at least one subscribing object thereon should receive the event.

Claim 18

The method of claim 10 , wherein the distributed object computing environment is a distributed manufacturing execution system environment and the at least one client inputs information to the manufacturing execution system from a manufacturing floor.

Claim 19

The method of claim 10 , wherein the plurality of load balancers query the plurality of server hosts for the load parameter at predetermined overlapping time intervals wherein as the number of load balancers in the distributed object computing environment increases, the queries become randomized.