1. Field of the Invention
The present invention relates to a method, system, and program for selecting a resource manager to satisfy a service request.
2. Description of the Related Art
In a content management system, a catalog is maintained indicating resource manager systems capable of providing services to subscribers. A subscriber connects to the content manager and requests a particular service listed in the catalog. The content manager then locates a resource manager in the catalog capable of providing the service and routes the service request to the resource manger. For instance, the service may comprise a file to download and the resource manager may comprise a node or system in the network indicated in the catalog that is capable of serving that requested file/service to the requesting subscriber. Additionally, if objects are being loaded into the content manager system, the file is routed to a resource manager to store.
Provided are a method, system, and article of manufacture for selecting a resource manager to satisfy a service request. A catalog indicating a plurality of resource managers and at least one service offered by the resource managers is provided. Further provided is resource manager information indicating resource availability information for resource managers offering at least one service. A request for a requested service from a subscriber is received. The catalog is processed to identify resource managers publishing the requested service and the resource manager information is processed to determine at least one identified resource manager publishing the requested service that also satisfies at least one rule applicable to the service request.
In the following description, reference is made to the accompanying drawings which form a part hereof and which illustrate several embodiments of the present invention. It is understood that other embodiments may be utilized and structural and operational changes may be made without departing from the scope of the present invention.
The rules may further provide for the provisioning of network resources to offer faster transmissions of data, ensure fault recovery of data transmissions by provisioning the receipt of data from multiple providers, dispatching requests to redundant services to offer fault protection and recovery in the event of a hardware or software failure, and capturing and evaluating the state of hardware resources in realtime (CPU, Memory, I/O, Network) within a system.
The coordinator 6 maintains and uses the catalog 12, resource manager information 14, and rules 18 to determine how to process service requests from subscribers 8a, 8b.
One rule may indicate a technical parameter, such as a technical property that must be supported or available at the resource manager 4a, 4b, 4c. Technical parameters may include a minimum amount of available resources (e.g., storage, computational, etc.) at the resource manager 4a, 4b, 4c, minimum connection bandwidth, supported protocols and required features, etc. A technical parameter specifies a technical feature that is a prerequisite for the resource manager 4a, 4b, 4c to be available to provide the requested service. If (at block 106) there is least one rule 80 applicable to the service request having a technical parameter, then a determination is made (at block 108) whether a least one resource manager publishing the requested service satisfies the technical parameter. The resource manager information 70 for the resource managers 4a, 4b, 4c may be processed to determine whether a certain technical parameter is satisfied. If not, an error message is returned (at block 110) that the service is not available.
A check is also made (at block 112) as to whether one rule applicable to the service request includes a quality of service parameter, which may be part of a Service Level Agreement (SLA). A quality of service parameter specifies a requirement that the resource manager 4a, 4b, 4c must satisfy to provide a certain level of performance to the subscriber, such as a required connection bandwidth, a maximum number of currently connected users, a minimum amount of available computational resources, a specified hardware redundancy, performance requirements of the resource manager hardware, etc. The quality of service parameter may specify both a minimum amount of performance or service as well as a maximum. If (at block 112) there is one applicable rule having a quality of service parameter, then the coordinator 6 determines (at block 114) whether at least one resource manager publishing the requested service satisfies the quality of service parameter. The resource manager information 70 for the resource managers 4a, 4b, 4c may be reviewed to determine whether a certain quality of service parameter is satisfied. If not, control proceeds to block 110 to return the message that the service is not available.
The coordinator 6 may also check (at blocks 116 and 120 in
If all the applicable rules are satisfied by at least one resource manager 4a, 4b, 4c and the subscriber 8a, 8b (should rules apply to the subscriber), then the coordinator 6 selects (at block 124) one determined resource manager 4a, 4b, 4c satisfying all the applicable rules to provide the requested service to the subscriber 8a, 8b. If there are multiple resource managers 4a, 4b, 4c satisfying the applicable rules, then the coordinator 6 may use a selection technique to select one resource provider, such as round robin, load balancing based on resource availability and usage at the resource managers 4a, 4b, 4c, etc.
Upon receiving the service request with respect to an object (e.g., file, record, email, etc.) having an applicable business process rule, the coordinator 6 processes (at block 152) the catalog 12 to identify resource managers 4a, 4b, 4c capable of processing the object according to the requested service. The coordinator 6 further processes (at block 154) object parameters and the business process rule to select at least one resource manager 4a, 4b, 4c to process the object. The business process rule may further specify requirements of the resource manager 4a, 4b, 4c to receive the object for archival or storage. The object is then transmitted (at block 156) to the determined resource manager. In one embodiment, the resource managers 4a, 4b, 4c may comprise computer readable devices, wherein the business process rule specifies retention and archival policies that selects one computer readable media in which to store the object based on the object parameters. For instance, the object parameters of the object may indicate the object size, access frequency (e.g., very high, high, frequent, low, etc.), desired availability (high availability, on-line, near online, etc.), coding (e.g., file format, compression, encryption, etc.), subject matter, etc. The business process rule may then specify different types of computer readable media, e.g., tape, hard disk drive, memory, etc., in which to store the object based on conditions related to the object parameters. For instance, if the object access frequency is relatively high, then the object may be stored in memory; if the size is large or the access frequency is low, then the object may be stored on tape; if the access frequency is high and the object is of a certain type, then the object may be stored in a file system; if the object access frequency is high and the object is required to be highly available, then the object may be stored in a disaster recovery or mirror site. Additionally, if the object parameters indicate that the object is related to a certain subject matter, e.g., litigation or transactional related, then the object may be archived for a period of time as specified by the business policy requirements. In this way, a business process rule specifies conditions and target storage and memory locations to store objects subject to a service request so as to implement archival and retention policies.
In one embodiment, the service may comprise an online file sharing service and the catalog 12 provides information on files, e.g., multi-media files, programs, etc., that subscribers 8a, 8b may download. The rules 18 may then be used to select an appropriate resource manager 4a, 4b, 4c that publishes the requested service, i.e., file, to have that appropriate resource manager transfer the file to the subscriber 8a, 8b.
In yet a further embodiment, the service may comprise a request to upload files to a content management system, where a business process rule based on the object parameters of the file being uploaded routes the file to an appropriate storage location in the content management system based on the object parameters, such as file size, access frequency, and other classifications.
The described operations may be implemented as a method, apparatus or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof. The term “article of manufacture” as used herein refers to code or logic implemented in a tangible medium, where such tangible medium may comprise hardware logic (e.g., an integrated circuit chip, Programmable Gate Array (PGA), Application Specific Integrated Circuit (ASIC), etc.) or a computer readable medium, such as magnetic storage medium (e.g., hard disk drives, floppy disks, tape, etc.), optical storage (CD-ROMs, optical disks, etc.), volatile and non-volatile memory devices (e.g., EEPROMs, ROMs, PROMs, RAMs, DRAMs, SRAMs, firmware, programmable logic, etc.). Code in the computer readable medium is accessed and executed by a processor. The tangible medium in which the code or logic is encoded may also comprise transmission signals propagating through space or a transmission media, such as an optical fiber, copper wire, etc. The transmission signal in which the code or logic is encoded may further comprise a wireless signal, satellite transmission, radio waves, infrared signals, etc. The transmission signal in which the code or logic is encoded is capable of being transmitted by one station and received by another station, where the code or logic encoded in the transmission signal may be decoded and stored in hardware or a computer readable medium. Additionally, the “article of manufacture” may comprise a combination of hardware and software components in which the code is embodied, processed, and executed. Of course, those skilled in the art will recognize that many modifications may be made to this configuration without departing from the scope of the present invention, and that the article of manufacture may comprise any information bearing medium known in the art.
The described embodiment provided specific example of rules that may be used to select a resource manager to provide a requested service. In alternative embodiments, additional types of rules and combinations of rules may be implemented and used to select a resource manager based on properties and qualities of the resource manager and/or subscriber.
The illustrated operations of
The foregoing description of various embodiments of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto. The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many embodiments of the invention can be made without departing from the spirit and scope of the invention, the invention resides in the claims hereinafter appended.
This application is a continuation of U.S. patent application Ser. No. 11/089,094, filed on Mar. 23, 2005, which patent application is incorporated herein by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
5341477 | Pitkin et al. | Aug 1994 | A |
5459837 | Caccavale | Oct 1995 | A |
6216173 | Jones et al. | Apr 2001 | B1 |
6704906 | Yankovich et al. | Mar 2004 | B1 |
20020010679 | Felsher | Jan 2002 | A1 |
20020111824 | Grainger | Aug 2002 | A1 |
20020120741 | Webb et al. | Aug 2002 | A1 |
20020143819 | Han et al. | Oct 2002 | A1 |
20030084140 | Takeuchi et al. | May 2003 | A1 |
20030163513 | Schaeck | Aug 2003 | A1 |
20030172145 | Nguyen | Sep 2003 | A1 |
20040122946 | Hu | Jun 2004 | A1 |
20040128555 | Saitoh et al. | Jul 2004 | A1 |
20040220926 | Lamkin et al. | Nov 2004 | A1 |
20050210041 | Taguchi | Sep 2005 | A1 |
20060059565 | Green | Mar 2006 | A1 |
20060218601 | Michel | Sep 2006 | A1 |
20070083899 | Compton et al. | Apr 2007 | A1 |
Number | Date | Country |
---|---|---|
1126371 | Aug 2001 | EP |
5134959 | Jun 1993 | JP |
11252066 | Sep 1999 | JP |
2003131960 | May 2003 | JP |
2004259092 | Sep 2004 | JP |
Entry |
---|
English Abstract and Machine Translation for JP5134959A, published Jun. 1, 1993, Total 15 pp. |
English Abstract for JP2003131960A, published May 9, 2003, Total 1 p (has English counterpart US2003/0084140). |
English Abstract and Machine Translation for JP2004259092A, published Sep. 16, 2004, Total 42 pp. |
Office Action 1, dated Jun. 28, 2007, for U.S. Appl. No. 11/089,094, filed Mar. 23, 2005 by S.E. Tate et al., Total 15 pp. [57.18 (OA1)]. |
Amendment 1, dated Oct. 29, 2007, for U.S. Appl. No. 11/089,094, filed Mar. 23, 2005 by S.E. Tate et al., Total 17 pp. [57.18 (Amend1)]. |
Notice of Non-Compliant Amendment, dated Jan. 23, 2008, for U.S. Appl. No. 11/089,094, filed Mar. 23, 2005 by S. E. Tate et al., Total 2 pp. [57.18 (NNCA)]. |
Response to Notice of Non-Compliant Amendment, dated Jan. 29, 2008, for U.S. Appl. No. 11/089,094, filed Mar. 23, 2005 by S.E. Tate et al., Total 9 pp. [57.18 (Rsp NNCA)]. |
Final Office Action 1, dated Jun. 6, 2008, for U.S. Appl. No. 11/089,094, filed Mar. 23, 2005 by S.E. Tate et al., Total 11 pp. [57.18 (FOA1)]. |
Amendment 2, dated Sep. 8, 2008, for U.S. Appl. No. 11/089,094, filed Mar. 23, 2005 by S.E. Tate et al., Total 9 pp. [57.18 (Amend2)]. |
Office Action 3, dated Oct. 3, 2008, for U.S. Appl. No. 11/089,094, filed Mar. 23, 2005 by S.E. Tate et al., Total 10 pp. [57.18 (OA3)]. |
Amendment 3, dated Jan. 5, 2009, for U.S. Appl. No. 11/089,094, filed Mar. 23, 2005 by S.E. Tate et al., Total 16 pp. [57.18 (Amend3)]. |
Office Action 4, dated Apr. 30, 2009, for U.S. Appl. No. 11/089,094, filed Mar. 23, 2005 by S.E. Tate et al., Total 10 pp. [57.18 (0A4)]. |
Amendment 4, dated Jul. 30, 2009, for U.S. Appl. No. 11/089, 094, filed Mar. 23, 2005 by S.E. Tate et al., Total 14 pp. [57.18 (Amend4)]. |
Final Office Action 2, dated Oct. 27, 2009, for U.S. Appl. No. 11/089,094, filed Mar. 23, 2005 by S.E. Tate et al., Total 11 pp. [57.18 (FOA2)]. |
Amendment 5, dated Mar. 29, 2010, for U.S. Appl. No. 11/089,094, filed Mar. 23, 2005 by S.E. Tate et al., Total 15 pp. [57.18 (Amend5)]. |
Office Action 6, dated Sep. 30, 2010, for U.S. Appl. No. 11/089,094, filed Mar. 23, 2005 by S.E. Tate et al., Total 11 pp. [57.18 (OA6)]. |
Amendment 6, dated Dec. 17, 2010, for U.S. Appl. No. 11/089,094, filed Mar. 23, 2005 by S.E. Tate et al., Total 16 pp. [57.18 (Amend6)]. |
Final Office Action 3, dated Mar. 25, 2011, for U.S. Appl. No. 11/089,094, filed Mar. 23, 2005 by S.E. Tate et al., Total 12 pp. [57.18 (FOA3)]. |
Proposed Amendment 1, dated Jun. 21, 2011, for U.S. Appl. No. 11/089,094, filed Mar. 23, 2005 by S.E. Tate et al., Total 3 pp. [57.18 (PropAmend)]. |
Amendment 7, dated Jun. 27, 2011, for U.S. Appl. No. 11/089,094, filed Mar. 23, 2005 by S.E. Tate et al., Total 11 pp. [57.18 (Amend7)]. |
Advisory Action, dated Jul. 15, 2011, for U.S. Appl. No. 11/089,094, filed Mar. 23, 2005 by S.E. Tate et al., Total 6 pp. [57.18 (AdvAct)]. |
Notice of Allowance 1, dated Oct. 14, 2011, for U.S. Appl. No. 11/089,094, filed Mar. 23, 2005 by S.E. Tate et al., Total 12 pp. [57.18 (NOA1)]. |
IDS Report, Sep. 2, 2011, from the Aug. 9, 2011 Office Action, Total 3 pp. |
PCT Search Report & Written Opinion, dated Jun. 7, 2006, for International Application No. PCT/EP2006/060688, Total 10 pp. |
Tan, Y.S., V. Vellanki, J. Xing, B. Topol, and G. Dudley, “Service Domains”, IBM Systems Journal, vol. 43, No. 4, pp. 734-755 (Sep. 1, 2004), Total 22 pp. |
English Abstract and Machine Translation for JP11252066A, published on Sep. 17, 1999, Total 24 pp. |
IDS Report, Oct. 5, 2012 from the Oct. 4, 2012 Office Action for JP920040114JP1, Total 2 pp. |
Number | Date | Country | |
---|---|---|---|
20120054309 A1 | Mar 2012 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11089094 | Mar 2005 | US |
Child | 13288913 | US |