Method and system for managing programs for distributed processing systems

• US 20050160135A1
• Filed: 09/16/2004
• Published: 07/21/2005
• Est. Priority Date: 01/15/2004
• Status: Active Grant

• Current Assignee: Hitachi, Ltd.
• Original Assignee: Hitachi, Ltd.
• Inventors: Yokoro, Atsushiro
• Granted Patent: US 8,205,199 B2
• Time in Patent Office: Days
• US Class Current: 709/200
• CPC Class Codes: G06F 2209/501 Performance criteria
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548
• CPC Class Codes: G06F 9/4881 Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
• CPC Class Codes: G06F 9/505 considering the load

Abstract

A queue is configured for accumulating a request to process a program component in an application server even when a naming service is used so as to enable priority control, flow control, or load distribution for component processing. A scheduler is provided between client terminals and a container server. The physical position information of the queue is associated with the logical name of the component, for registration in the naming service. The naming service is referenced for name resolution of the logical name of the component on which the processing request has been made from a client terminal, and stores the processing request on the component in the queue corresponding to the obtained physical position information of the queue. By using the queue, the scheduler can perform priority control, flow control, load distribution control, or the like for processing of the component.

Claims

1. A method of configuring a queue for a request to process a program component in an application server comprising:

a container server including a plurality of program components, for executing processing of the program components;

a scheduler including queues for storing requests to process the program components from client terminals, for controlling the processing requests; and

a naming service storing correspondence between logical names of the program components and information representing physical positions of the queues corresponding to the program components, for effecting name resolution of the program components;

wherein when deploying the program component in the container server, the application server deploys the queue for storing the processing request on the program component in the scheduler, and registers in the naming service physical position information of the queue and a logical name of the deployed program component to correspond to each other; and

the naming service is referred to for name resolution of the logical name of the program component on which a processing request has been made from one of the client terminals, and the processing request on the program component is stored in a queue corresponding to the obtained physical position information of the queue.

2. A method of registering a program component in an application server comprising:

a container server including a plurality of program components, for executing processing of the program components;

a scheduler including queues for storing requests to process the program components from client terminals, for controlling the processing requests; and

a naming service storing correspondence between logical names of the program components and physical position information of the queues corresponding to the program components, for effecting name resolution of the program components;

the method comprising the steps of;

deploying the program component by the container server;

associating a queue for storing a request to process the program component with the deployed program component and deploying the queue, by the scheduler;

registering correspondence between physical position information of the deployed program component and physical position information of the deployed queue in a queue management table, by the scheduler; and

associating the physical position information of the queue with a logical name of the deployed program component for registration, by the naming service.

3. A method of registering a program component in an application server comprising:

a container server including a plurality of program components, for executing processing of the program components;

a scheduler including queues for storing requests to process the program components from client terminals, for controlling the processing requests; and

a naming service storing correspondence between logical names of the program components and physical position information of the queues corresponding to the program components, for effecting name resolution of the program components;

the method comprising the steps of;

deploying the program component by the container server;

associating physical position information of the program component with a logical name of the program component, for registration, by the naming service;

obtaining from the naming service the logical names and physical position information of the program components registered in the naming service, by the scheduler;

selecting a newly registered program component based on the obtained logical names of the program components, by the scheduler;

associating a queue for storing a request to process the newly registered program component with the newly registered program component and deploying the queue, by the scheduler;

registering correspondence between physical position information of the newly registered program component and physical position information of the deployed queue in a queue management table, by the scheduler; and

associating the physical position information of the deployed queue with a logical name of the newly registered program component, for registration, by the naming service.

4. A method of controlling execution of a program component in an application server comprising:

a container server including a plurality of program components, for executing processing of the program components;

a scheduler including queues for storing requests to process the program components from client terminals, for controlling the processing requests; and

a naming service storing correspondence between logical names of the program components and physical position information of the queues corresponding to the program components, for effecting name resolution of the program components;

the method comprising the steps of;

outputting to one of the client terminals the physical position information of one of the queues corresponding to the logical name of the program component input from said one of the client terminals, by the naming service;

storing one of the processing requests for the program component input from said one of the client terminals in said one of the queues, by the scheduler;

extracting said one of the processing requests for the program component stored in said one of the queues, referring to a queue management table to obtain physical position information of the program component, and requesting processing on the program component indicated by the physical position information of the program component to the container server, by the scheduler;

executing the program component on which said one of the processing requests has been made, by the container server; and

sending data resulting from the execution of the program component to said one of the client terminals through the scheduler, by the container server.

5. A program for registering a program component in an application server comprising:

a container server including a plurality of program components, for executing processing of the program components;

a scheduler including queues for storing requests to process the program components from client terminals, for controlling the processing requests; and

a naming service storing correspondence between logical names of the program components and physical position information of the queues corresponding to the program components;

the program causing a computer in the application server to operate as;

means for deploying the program component in the container server;

means for deploying in the scheduler a queue for storing a request to process the program component corresponding to the deployed program component;

means for registering correspondence between physical position information of the deployed program component and physical position information of the deployed queue in a queue management table; and

naming service means for associating the physical position information of the queue with a logical name of the deployed program component, for registration.

6. A program for registering a program component in an application server comprising:

a container server including a plurality of program components, for executing processing of the program components;

a scheduler including queues for storing requests to process the program components from client terminals, for controlling the processing requests; and

a naming service storing correspondence between logical names of the program components and physical position information of the queues, for effecting name resolution of the program components;

the program causing a computer in the application server to operate as;

means for extracting from the naming service the logical names and physical position information of the program components registered in the naming service;

means for selecting a newly registered program component based on the extracted logical names of the program components;

means for deploying a queue for storing a request to process the newly registered program component corresponding to the newly registered program component;

means for registering correspondence between physical position information of the newly registered program component and physical position information of the deployed queue in a queue management table; and

second naming service means for associating the physical position information of the deployed queue with a logical name of the newly registered program component, for registration.

7. A program for controlling execution of a program component in an application server comprising:

a container server including a plurality of program components, for executing processing of the program components;

a scheduler including queues for storing requests to process the program components from client terminals, for controlling the processing requests; and

a naming service storing correspondence between logical names of the program components and physical position information of the queues corresponding to the program components, for effecting name resolution of the program components;

the program causing a computer in the application server to operate as;

means for outputting to one of the client terminals the physical position information of one of the queues corresponding to the logical name of the program component input from said one of the client terminals;

means for storing one of the processing requests for the program component input from said one of the client terminals in said one of the queues;

means for causing the scheduler to extract said one of the processing requests for the program component stored in said one of the queues, refer to a queue management table to obtain physical position information of the program component, and request processing on the program component indicated by the physical position information of the program component to the container server;

means for causing the container server to execute the program component on which said one of the processing requests has been received; and

means for sending data resulting from the execution of the program component to said one of the client terminals through the scheduler.

8. An application server comprising:

a container server including a plurality of program components, for executing processing of the program components;

a scheduler including queues for storing requests to process the program components from client terminals, for controlling the processing requests; and

a naming service storing correspondence between logical names of the program components and physical position information of the queues corresponding to the program components, for effecting name resolution of the program components;

wherein

when deploying a program component in the container server, the application server deploys a queue for storing a processing request on the program component in the scheduler, and associates physical position information of the queue with a logical name of the deployed program component, for registration in the naming service;

the naming service does the name resolution of the logical name of the program component on which the processing request has been made from one of the client terminals, and the processing request on the program component is stored in the queue corresponding to the obtained physical position information of the queue; and

the processing request for the program component stored in the queue is extracted from the queue to execute the program component.

9. The application server according to claim 8, wherein the scheduler includes a queue management table for associating physical position information of a plurality of the program components with one of the queues.

10. The application server according to claim 8, wherein the container server comprises a plurality of container servers each with a same one of the program components deployed therein.

11. The application server according to claim 8 connected to other application server to each other, wherein

the naming service further associates physical position information of program components deployed in a container server of the other application server with logical names of the program components, for registration;

and

when the scheduler has received a processing request on one of the program components registered in the container server of the other application server, the scheduler sends the processing request to a scheduler of the other application server.