US20080005317A1 - Method and apparatus for cross-tier management in multi-tier computing system architecture - Google Patents
Method and apparatus for cross-tier management in multi-tier computing system architecture Download PDFInfo
- Publication number
- US20080005317A1 US20080005317A1 US11/479,511 US47951106A US2008005317A1 US 20080005317 A1 US20080005317 A1 US 20080005317A1 US 47951106 A US47951106 A US 47951106A US 2008005317 A1 US2008005317 A1 US 2008005317A1
- Authority
- US
- United States
- Prior art keywords
- tier
- management
- computing system
- commands
- manageability
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3409—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
Definitions
- the present invention relates to computing systems, and, more particularly, to techniques for management of such computing systems.
- Most Internet service sites such as electronic commerce (e-commerce) web sites have a multi-tier computing system architecture that partitions the processing of web requests into tiers or stages.
- a multi-tier architecture may, for example, include an edge server stage, an Hypertext Transport Protocol (HTTP) server stage, an application server stage, and a database server stage.
- HTTP Hypertext Transport Protocol
- Management systems are typically used to monitor the performance of the computing system and to cause actions to be taken to address performance problems.
- existing management solutions employ only a one-tier management approach.
- an existing management system provides for dynamic capacity provisioning of the application server tier.
- such an approach does not take into account more than one tier of a multi-tier architecture, nor does it take into account interaction between tiers such as between the application server tier and some other tier.
- a resource bottleneck can exist in a backend tier such as the database tier.
- the existing management system employs the one-tier management approach, interaction between the application server tier and the database server tier is not considered. Further, as a result, there is no ability provided by existing management techniques to manage one tier from another tier.
- Principles of the invention provide a management approach that is able to take into account multiple tiers of a computing system architecture, and interactions there between, by managing one or more tiers of the computing system from one or more other tiers of the computing system (i.e., provide cross-tier management).
- a method for managing a computing system includes the steps of monitoring performance of the second tier from the first tier, and sending one or more management commands from the first tier to the second tier based on the monitored performance.
- the first tier may be an application server tier of the computing system
- the second tier may be a database server tier of the computing system.
- the second tier may include a node agent for receiving the one or more management commands such that management control in the first tier extends to the second tier.
- the second tier may include an interface for abstracting the one or more management commands with respect to one or more provider-specific database management plug-in modules.
- the first tier and the second tier may implement a management model including a manageability extension layer, a manageability abstraction layer and a managed resource layer.
- a method for managing a computing system includes the steps of sending performance data from the second tier to the first tier, and receiving one or more management commands from the first tier at the second tier based on the monitored performance.
- apparatus for managing a computing system wherein the computing system includes a first tier and at least a second tier, wherein the first tier and the second tier are configured to respond to a request received by the computing system, comprises: a node agent at the second tier configured to: (i) send performance data from the second tier to the first tier; and (ii) receive one or more management commands from the first tier at the second tier based on the monitored performance; and an interface at the second tier configured to abstract the one or more management commands with respect to one or more provider-specific database management plug-in modules.
- a method for managing one or more goals in a system that includes two or more tiers, whereby work progressively flows from tier-to-tier of the system, includes the steps of communicating one or more directives from a higher-level tier to a lower-level tier, and converting the one or more directives at the lower-level tier into instructions executable by a management component specific to the lower-level tier so as to effect the one or more system goals.
- the communicating step and the converting step may further include communicating one or more directives from the first tier to the second tier, converting the one or more directives at the second tier into instructions executable by a management component specific to the second tier, communicating one or more directives from the second tier to the third tier, and converting the one or more directives at the third tier into instructions executable by a management component specific to the third tier.
- a system for providing cross-tier management of resources in a computer system includes the following layers.
- a manageability extension layer includes node agent code on a managed resource tier for receiving one or more control and configuration commands for the managed resource from an application server tier.
- a manageability abstraction layer includes code for interacting with a management interface and thereby defining a service provider interface for abstracting the one or more control and configuration commands.
- a managed resource layer includes resource-specific code for controlling a managed resource within the managed resource layer.
- management principles of the invention may consider interaction between different tiers of the computing system architecture. Furthermore, principles of the invention may also provide the ability to change resource configurations across multiple tiers.
- FIG. 1 illustrates a multi-tier computing system architecture in which cross-tier management techniques may be implemented, according to an embodiment of the invention.
- FIG. 2A illustrates a cross-tier management model, according to an embodiment of the invention.
- FIG. 2B illustrates a cross-tier management methodology for managing a database tier from an application server tier, according to an embodiment of the invention.
- FIG. 3 illustrates a computer system wherein cross-tier management techniques may be implemented, according to an embodiment of the invention.
- the present invention is not limited to any particular multi-tier computing system architecture. Rather, the invention is more generally applicable to any multi-tier computing system architecture in which it would be desirable to provide a management approach that is able to manage one or more tiers of the computing system from one or more other tiers of the computing system.
- FIG. 1 depicts such a multi-tier computing system architecture.
- Each tier comprises one or more nodes (e.g., hardware entities) that are dedicated to a specific kind of processing.
- the first tier or edge server tier 102 provides load balancing and request routing.
- the second tier or HTTP server tier 104 performs HTTP parsing and response generation.
- the third tier 106 contains application servers typically providing a Java 2 Platform Enterprise Edition (J2EE) for business logic (e.g., the software used to execute the particular e-commerce application).
- the fourth tier 108 contains database server nodes that manage persistent data.
- the architecture may include a fifth tier (not shown) as well, if a separate storage system is used (e.g., a storage area network).
- client requests enter the first tier and are routed to an HTTP server. Some fractions of the HTTP requests also require processing by application servers. A fraction of the requests processed by application servers also require services from a database server. Because inter-tier interaction is synchronous, threads/processes in upstream tiers are blocked while waiting for the completion of processing in downstream tiers. Thus, requests may simultaneously consume resources in the HTTP, application, and database server nodes. After processing by some or all of the tiers of the multi-tier computing system, a response to the request is sent to the client.
- Principles of the invention provide techniques for enabling cross-tier management of resources in a multi-tier computing system. It is to be understood that principles of the invention identify a managed tier (e.g., database tier 108 in FIG. 1 ) and a managing tier (e.g., application server tier 106 in FIG. 1 ).
- a managed tier e.g., database tier 108 in FIG. 1
- a managing tier e.g., application server tier 106 in FIG. 1 .
- Management techniques of the invention employ a multi-layer management model.
- such model 200 includes a manageability extension layer 202 , a manageability abstraction layer 204 , and a managed resource layer 206 .
- the manageability extension layer includes node agent software code that resides on a managed resource tier for receiving control and configuration commands for a managed resource from an application server tier (managing tier).
- the manageability abstraction layer includes software code for interacting with a management interface and thereby defining a service provider interface (SPI).
- SPI service provider interface
- the managed resource layer includes resource-specific software code for controlling a managed resource within the managed resource layer.
- the node agent code on the managed resource tier includes performance reporting code for sending performance information regarding the managed resource back to the application server tier. While the invention is not limited to any particular management environment, it is particularly well suited for use in a WebSphereTM Deployment Management environment (IBM Corporation of Armonk, N.Y.).
- FIG. 2B illustrates a cross-tier management methodology according to an embodiment of the invention.
- model 200 can be applied to controlling a database server tier from an application server tier.
- the controlling entity is WebSphereTM Application Server (WAS) tier and the backend controlled tier is a database tier.
- WAS WebSphereTM Application Server
- an extended WebSphereTM cell 210 includes an on demand router 212 , an application server cluster 214 including WAS nodes 1 , 2 and 3 with respective node agents 215 - 1 , 215 - 2 , and 215 - 3 , administrator console 216 , client 218 , and deployment manager 220 .
- Cell 210 also includes managed database (DB) node 222 including database 1 , database 2 , DB controller 224 , plug-in SPI 226 , node agent 228 , operating system 230 , and plug-ins 232 .
- DB managed database
- a request enters the cell at router 212 and is routed to a particular WAS node in the server cluster 214 .
- the WAS node that handles the request may be selected based on the priority of the request (e.g., high priority requests going to WAS nodes 1 or, and low priority requests going to WAS node 3 ).
- the WAS node may require assistance of a database server node (e.g., Database 1 or Database 2 ) in order to respond to the request.
- the database server node may be selected based on the priority associated with the request.
- WebSphereTM node agents i.e., 215 - 1 through 215 - 3
- management (configuration and control) servers between WAS nodes and the WebSphereTM deployment manager 220 in a WebSphere extended deployment or network deployment setup.
- block 216 is a user interface where a system administrator sets management goals and parameters.
- Block 218 represents software code that executes management functions.
- the WebSphereTM node agent is extended for other non-application tiers (e.g., the managed DB tier, the storage systems, etc.). Such extension is realized in cell 210 of FIG. 2B by node agent 228 , located in managed DB node 222 . This is considered the manageability extension layer ( 202 of FIG. 2A ) of the cross-tier management model of the invention.
- FIG. 2B illustrates the application server (WAS) tier managing the database (DB) tier
- WAS application server
- DB database
- FIG. 2B illustrates the application server (WAS) tier managing the database (DB) tier
- WAS application server
- DB database
- the management infrastructure is as follows.
- WAS is the managing server with respect to DB, the managed resource, and thus WAS puts agent code in the DB tier.
- DB is the managing server with respect to storage, the managed resource, and thus DB puts agent code in the storage tier.
- node agent 228 on the database node 222 allows the database to be managed from the application server tier.
- This node agent 228 can receive any control and configuration commands for different databases thereon from the application tier via deployment manager 220 .
- Node agent 228 can also send back any performance related information of the databases back to the application tier.
- the management extensions to the node agent provide an abstract interface, to a controlling entity such as the WebSphereTM Deployment manager 220 , independent of the underlying virtualization technologies such as OS WLM (e.g., Linux CKRM, AIX WLM, HP-UX WLM, Solaris Resource Manager) and partitioning technologies such as dynamic LPAR, Linux Xen, Meiosys Metacluster, etc.
- OS WLM e.g., Linux CKRM, AIX WLM, HP-UX WLM, Solaris Resource Manager
- partitioning technologies such as dynamic LPAR, Linux Xen, Meiosys Metacluster, etc.
- CKRM refers to class-based kernel resource management (http://ckrm.sourceforge.net/)
- AIX WLM refers to a workload management system (http://www.redbooks.ibm.com/abstracts/sg245977.html)
- dynamic LPAR refers to dynamic logical partitions (http://www-03.ibm.com/servers/eserver/iseries/lpar/)
- Linux Xen is described at http://kerneltrap.org/node/4168.
- This interface may be based on open standards such as Java Management Extensions or Web Services Distributed Management (WS-DM).
- open standards such as Java Management Extensions or Web Services Distributed Management (WS-DM).
- DB controller 224 provides abstraction from platform specific workload management capability. This is considered the manageability abstraction layer ( 204 of FIG. 2A ) of the cross-tier management model of the invention. DB controller 224 defines a Service Provider Interface (SPI) 226 that is implemented by the managed resource layer ( 206 of FIG. 2A ).
- SPI Service Provider Interface
- the manageability abstraction layer contains the logic to interact with any management infrastructure such as JMX or WS-DM.
- JMX Java Management Extensions are described at http://java.sun.com/products/JavaManagement/
- WS-DM Web Services Distributed Management is described at (www.oasis-open.org/committees/wsdm/).
- the preferred management protocol is JMX.
- This layer also has the processing capability to determine which plug-in of the managed resource layer has to be invoked to achieve control.
- the abstraction layer is the layer that serves to hide the implementation details of the resource so that an entity (e.g., system administrator or processing node) that requests some action need only request the action without needing to know how the action is accomplished. For example, if an entity wants to increase the CPU share 10% for an application, it only needs to issue a generic command such as “increase CPU 10%.”
- the abstraction layer translates this command into an executable command according to the respective grammar understood by the different resources, i.e., since the actual command for plug-in Linux CKRM would be different than the actual command for plug-in AIX WLM.
- the managed resource layer contains the implementation of technology specific “glue code” to provide the actual control logic (the glue code refers to the actual command understood by the plug-in). That is, the managed layer contains the resource specific logic to implement the actual control.
- plug-ins 232 define this layer.
- the control of the DB tier resources ( 230 ) can be achieved using various options such as Linux CKRM, AIX WLM, dynamic LPAR, or DB2 WLM.
- An example of configuration and control could be creating classes for the various database instances in the OS WLM and then creating rules for classifying the processes belonging to these instances into the proper class and applying the proper amount of resource (CPU, IO, memory) shares to the classes based on a request from the controlling entity.
- resource CPU, IO, memory
- FIG. 2B illustrates management of a second tier (database server tier) from a first tier (application server tier)
- the management model of FIG. 2A may be applied to three or more tiers of a computing system. That is, principles of the invention may be used to manage end-to-end goals in a system that includes three or more tiers whereby work progressively flows from a first tier to a second tier and subsequently from the second tier to the third tier, and so on to other subsequent tiers.
- the first tier manages the second tier and the second tier manages the third tier and so on.
- Such tier-to-tier management is achieved by employing management translation layers that allow the higher-level tier to communicate directives (commands) to the lower-level tier.
- the lower level tier converts/accepts these directives into its own/native management capability.
- FIG. 3 is a block diagram illustrating an illustrative hardware implementation of a computer system in accordance with which one or more components/steps of a management system (e.g., components/steps described in the context of FIGS. 1 , 2 A, and 2 B) may be implemented, according to an embodiment of the present invention.
- the illustrative architecture of FIG. 3 may be used in implementing any and all of the components (i.e., nodes, node agents, database servers, deployment manager, DB controller, plug-ins, etc.) of any of the tiers shown in FIGS. 1 , 2 A, and 2 B.
- the individual components/steps may be implemented on one such computer system, or more preferably, on more than one such computer system.
- the individual computer systems and/or devices may be connected via a suitable network, e.g., the Internet or World Wide Web.
- a suitable network e.g., the Internet or World Wide Web.
- the system may be realized via private or local networks. The invention is not limited to any particular network.
- the computer system 300 may be implemented in accordance with a processor 302 , a memory 304 , I/O devices 306 , and a network interface 308 , coupled via a computer bus 310 or alternate connection arrangement.
- processor as used herein is intended to include any processing device, such as, for example, one that includes a CPU (central processing unit) and/or other processing circuitry. It is also to be understood that the term “processor” may refer to more than one processing device and that various elements associated with a processing device may be shared by other processing devices.
- memory as used herein is intended to include memory associated with a processor or CPU, such as, for example, RAM, ROM, a fixed memory device (e.g., hard drive), a removable memory device (e.g., diskette), flash memory, etc.
- input/output devices or “I/O devices” as used herein is intended to include, for example, one or more input devices (e.g., keyboard, mouse, etc.) for entering data to the processing unit, and/or one or more output devices (e.g., speaker, display, etc.) for presenting results associated with the processing unit.
- input devices e.g., keyboard, mouse, etc.
- output devices e.g., speaker, display, etc.
- network interface as used herein is intended to include, for example, one or more transceivers to permit the computer system to communicate with another computer system via an appropriate communications protocol.
- software components including instructions or code for performing the methodologies described herein may be stored in one or more of the associated memory devices (e.g., ROM, fixed or removable memory) and, when ready to be utilized, loaded in part or in whole (e.g., into RAM) and executed by a CPU.
- ROM read-only memory
- RAM random access memory
- the present invention also comprises techniques for providing cross-tier management services.
- a service provider agrees (e.g., via a service level agreement or some informal agreement or arrangement) with a service customer to provide cross-tier management services. That is, by way of one example only, the service provider may host the customer's web site and associated applications (e.g., e-commerce applications). Then, in accordance with terms of the contract between the service provider and the service customer, the service provider provides cross-tier management services which may comprise one or more of the methodologies of the invention described herein.
Abstract
Techniques are disclosed for providing cross-tier management in a multi-tier computing system architecture. For example, a method for managing a computing system, wherein the computing system includes a first tier and at least a second tier, wherein the first tier and the second tier are configured to respond to a request received by the computing system, includes the steps of monitoring performance of the second tier from the first tier, and sending one or more management commands from the first tier to the second tier based on the monitored performance. In one embodiment, the first tier may be an application server tier of the computing system, and the second tier may be a database server tier of the computing system.
Description
- The present invention relates to computing systems, and, more particularly, to techniques for management of such computing systems.
- Most Internet service sites such as electronic commerce (e-commerce) web sites have a multi-tier computing system architecture that partitions the processing of web requests into tiers or stages. Such a multi-tier architecture may, for example, include an edge server stage, an Hypertext Transport Protocol (HTTP) server stage, an application server stage, and a database server stage.
- Management systems are typically used to monitor the performance of the computing system and to cause actions to be taken to address performance problems. However, existing management solutions employ only a one-tier management approach. For example, an existing management system provides for dynamic capacity provisioning of the application server tier. However, such an approach does not take into account more than one tier of a multi-tier architecture, nor does it take into account interaction between tiers such as between the application server tier and some other tier.
- By way of example, a resource bottleneck can exist in a backend tier such as the database tier. However, since the existing management system employs the one-tier management approach, interaction between the application server tier and the database server tier is not considered. Further, as a result, there is no ability provided by existing management techniques to manage one tier from another tier.
- Accordingly, it would be desirable to provide a management approach that is able to take into account multiple tiers of a computing system architecture, and interactions there between, by managing one or more tiers of the computing system from one or more other tiers of the computing system.
- Principles of the invention provide a management approach that is able to take into account multiple tiers of a computing system architecture, and interactions there between, by managing one or more tiers of the computing system from one or more other tiers of the computing system (i.e., provide cross-tier management).
- For example, in one aspect of the invention, a method for managing a computing system, wherein the computing system includes a first tier and at least a second tier, wherein the first tier and the second tier are configured to respond to a request received by the computing system, includes the steps of monitoring performance of the second tier from the first tier, and sending one or more management commands from the first tier to the second tier based on the monitored performance.
- The first tier may be an application server tier of the computing system, and the second tier may be a database server tier of the computing system.
- The second tier may include a node agent for receiving the one or more management commands such that management control in the first tier extends to the second tier. The second tier may include an interface for abstracting the one or more management commands with respect to one or more provider-specific database management plug-in modules. The first tier and the second tier may implement a management model including a manageability extension layer, a manageability abstraction layer and a managed resource layer.
- In a second aspect of the invention, a method for managing a computing system, wherein the computing system includes a first tier and at least a second tier, wherein the first tier and the second tier are configured to respond to a request received by the computing system, includes the steps of sending performance data from the second tier to the first tier, and receiving one or more management commands from the first tier at the second tier based on the monitored performance.
- In a third aspect of the invention, apparatus for managing a computing system, wherein the computing system includes a first tier and at least a second tier, wherein the first tier and the second tier are configured to respond to a request received by the computing system, comprises: a node agent at the second tier configured to: (i) send performance data from the second tier to the first tier; and (ii) receive one or more management commands from the first tier at the second tier based on the monitored performance; and an interface at the second tier configured to abstract the one or more management commands with respect to one or more provider-specific database management plug-in modules.
- In a fourth aspect of the invention, a method for managing one or more goals in a system that includes two or more tiers, whereby work progressively flows from tier-to-tier of the system, includes the steps of communicating one or more directives from a higher-level tier to a lower-level tier, and converting the one or more directives at the lower-level tier into instructions executable by a management component specific to the lower-level tier so as to effect the one or more system goals.
- For example, work may progressively flow from a first tier to a second tier and subsequently from the second tier to at least a third tier. Accordingly, the communicating step and the converting step may further include communicating one or more directives from the first tier to the second tier, converting the one or more directives at the second tier into instructions executable by a management component specific to the second tier, communicating one or more directives from the second tier to the third tier, and converting the one or more directives at the third tier into instructions executable by a management component specific to the third tier.
- In a fifth aspect of the invention, a system for providing cross-tier management of resources in a computer system includes the following layers. A manageability extension layer includes node agent code on a managed resource tier for receiving one or more control and configuration commands for the managed resource from an application server tier. A manageability abstraction layer includes code for interacting with a management interface and thereby defining a service provider interface for abstracting the one or more control and configuration commands. A managed resource layer includes resource-specific code for controlling a managed resource within the managed resource layer.
- Advantageously, management principles of the invention may consider interaction between different tiers of the computing system architecture. Furthermore, principles of the invention may also provide the ability to change resource configurations across multiple tiers.
- These and other objects, features and advantages of the present invention will become apparent from the following detailed description of illustrative embodiments thereof, which is to be read in connection with the accompanying drawings.
-
FIG. 1 illustrates a multi-tier computing system architecture in which cross-tier management techniques may be implemented, according to an embodiment of the invention. -
FIG. 2A illustrates a cross-tier management model, according to an embodiment of the invention. -
FIG. 2B illustrates a cross-tier management methodology for managing a database tier from an application server tier, according to an embodiment of the invention. -
FIG. 3 illustrates a computer system wherein cross-tier management techniques may be implemented, according to an embodiment of the invention. - It is to be understood that the present invention is not limited to any particular multi-tier computing system architecture. Rather, the invention is more generally applicable to any multi-tier computing system architecture in which it would be desirable to provide a management approach that is able to manage one or more tiers of the computing system from one or more other tiers of the computing system.
- Before describing management techniques of the invention, we provide a general description of an illustrative multi-tier computing system architecture.
-
FIG. 1 depicts such a multi-tier computing system architecture. Each tier comprises one or more nodes (e.g., hardware entities) that are dedicated to a specific kind of processing. Inarchitecture 100 depicted inFIG. 1 , the first tier oredge server tier 102 provides load balancing and request routing. The second tier orHTTP server tier 104 performs HTTP parsing and response generation. Thethird tier 106 contains application servers typically providing a Java 2 Platform Enterprise Edition (J2EE) for business logic (e.g., the software used to execute the particular e-commerce application). Thefourth tier 108 contains database server nodes that manage persistent data. The architecture may include a fifth tier (not shown) as well, if a separate storage system is used (e.g., a storage area network). - In general, client requests enter the first tier and are routed to an HTTP server. Some fractions of the HTTP requests also require processing by application servers. A fraction of the requests processed by application servers also require services from a database server. Because inter-tier interaction is synchronous, threads/processes in upstream tiers are blocked while waiting for the completion of processing in downstream tiers. Thus, requests may simultaneously consume resources in the HTTP, application, and database server nodes. After processing by some or all of the tiers of the multi-tier computing system, a response to the request is sent to the client.
- Principles of the invention provide techniques for enabling cross-tier management of resources in a multi-tier computing system. It is to be understood that principles of the invention identify a managed tier (e.g.,
database tier 108 inFIG. 1 ) and a managing tier (e.g.,application server tier 106 inFIG. 1 ). - Management techniques of the invention employ a multi-layer management model. In one embodiment, as illustrated in
FIG. 2A ,such model 200 includes amanageability extension layer 202, amanageability abstraction layer 204, and a managedresource layer 206. - As will be illustrated below in the context of
FIG. 2B , the manageability extension layer includes node agent software code that resides on a managed resource tier for receiving control and configuration commands for a managed resource from an application server tier (managing tier). The manageability abstraction layer includes software code for interacting with a management interface and thereby defining a service provider interface (SPI). The managed resource layer includes resource-specific software code for controlling a managed resource within the managed resource layer. - In one embodiment, the node agent code on the managed resource tier includes performance reporting code for sending performance information regarding the managed resource back to the application server tier. While the invention is not limited to any particular management environment, it is particularly well suited for use in a WebSphere™ Deployment Management environment (IBM Corporation of Armonk, N.Y.).
- In accordance with a WebSphere™ environment, principles of the invention provide a cross-tier workload management methodology that is Java application server centric. For ease of explaining the concepts, we use a WebSphere™ application server (WAS) as the application tier and DB2™ (IBM Corporation of Armonk, N.Y.) as the backend tier. However, the concepts introduced herein can be easily applied to other application servers and other backend tiers.
-
FIG. 2B illustrates a cross-tier management methodology according to an embodiment of the invention. In the context ofFIG. 2B , we illustrate howmodel 200 can be applied to controlling a database server tier from an application server tier. The controlling entity is WebSphere™ Application Server (WAS) tier and the backend controlled tier is a database tier. - As shown, an extended
WebSphere™ cell 210 includes an ondemand router 212, anapplication server cluster 214 including WASnodes administrator console 216,client 218, anddeployment manager 220.Cell 210 also includes managed database (DB)node 222 includingdatabase 1,database 2,DB controller 224, plug-inSPI 226,node agent 228,operating system 230, and plug-ins 232. - In general, a request enters the cell at
router 212 and is routed to a particular WAS node in theserver cluster 214. The WAS node that handles the request may be selected based on the priority of the request (e.g., high priority requests going to WASnodes 1 or, and low priority requests going to WAS node 3). Depending on the nature of the request, the WAS node may require assistance of a database server node (e.g.,Database 1 or Database 2) in order to respond to the request. Again, the database server node may be selected based on the priority associated with the request. - Typically, WebSphere™ node agents (i.e., 215-1 through 215-3) are used as management (configuration and control) servers between WAS nodes and the WebSphere
™ deployment manager 220 in a WebSphere extended deployment or network deployment setup. Note thatblock 216 is a user interface where a system administrator sets management goals and parameters.Block 218 represents software code that executes management functions. - In accordance with illustrative principles of the invention, the WebSphere™ node agent is extended for other non-application tiers (e.g., the managed DB tier, the storage systems, etc.). Such extension is realized in
cell 210 ofFIG. 2B bynode agent 228, located in managedDB node 222. This is considered the manageability extension layer (202 ofFIG. 2A ) of the cross-tier management model of the invention. - It is to be understood that while
FIG. 2B illustrates the application server (WAS) tier managing the database (DB) tier, we can place node agents in other tiers with non-identical functions to facilitate distributed administration and workload management beyond WAS instances. For example, besides the WAS tier and the DB tier, suppose we have a third tier, e.g., a storage tier, as well. Hence, the management infrastructure is as follows. WAS is the managing server with respect to DB, the managed resource, and thus WAS puts agent code in the DB tier. Similarly, DB is the managing server with respect to storage, the managed resource, and thus DB puts agent code in the storage tier. - Returning to the embodiment of
FIG. 2B , the placement ofnode agent 228 on thedatabase node 222 allows the database to be managed from the application server tier. Thisnode agent 228 can receive any control and configuration commands for different databases thereon from the application tier viadeployment manager 220.Node agent 228 can also send back any performance related information of the databases back to the application tier. - The management extensions to the node agent provide an abstract interface, to a controlling entity such as the WebSphere
™ Deployment manager 220, independent of the underlying virtualization technologies such as OS WLM (e.g., Linux CKRM, AIX WLM, HP-UX WLM, Solaris Resource Manager) and partitioning technologies such as dynamic LPAR, Linux Xen, Meiosys Metacluster, etc. CKRM refers to class-based kernel resource management (http://ckrm.sourceforge.net/), AIX WLM refers to a workload management system (http://www.redbooks.ibm.com/abstracts/sg245977.html), dynamic LPAR refers to dynamic logical partitions (http://www-03.ibm.com/servers/eserver/iseries/lpar/) and Linux Xen is described at http://kerneltrap.org/node/4168. These are only examples of plug-ins that may be used in the WebSphere™ cell. - The implementation of this interface may be based on open standards such as Java Management Extensions or Web Services Distributed Management (WS-DM).
- As shown in
FIG. 2B ,DB controller 224 provides abstraction from platform specific workload management capability. This is considered the manageability abstraction layer (204 ofFIG. 2A ) of the cross-tier management model of the invention.DB controller 224 defines a Service Provider Interface (SPI) 226 that is implemented by the managed resource layer (206 ofFIG. 2A ). The manageability abstraction layer contains the logic to interact with any management infrastructure such as JMX or WS-DM. JMX: Java Management Extensions are described at http://java.sun.com/products/JavaManagement/, and WS-DM: Web Services Distributed Management is described at (www.oasis-open.org/committees/wsdm/). - In the case of WebSphere, the preferred management protocol is JMX. This layer also has the processing capability to determine which plug-in of the managed resource layer has to be invoked to achieve control.
- Furthermore, the abstraction layer is the layer that serves to hide the implementation details of the resource so that an entity (e.g., system administrator or processing node) that requests some action need only request the action without needing to know how the action is accomplished. For example, if an entity wants to increase the CPU share 10% for an application, it only needs to issue a generic command such as “increase CPU 10%.” The abstraction layer translates this command into an executable command according to the respective grammar understood by the different resources, i.e., since the actual command for plug-in Linux CKRM would be different than the actual command for plug-in AIX WLM.
- The managed resource layer contains the implementation of technology specific “glue code” to provide the actual control logic (the glue code refers to the actual command understood by the plug-in). That is, the managed layer contains the resource specific logic to implement the actual control. In
FIG. 2B , plug-ins 232 define this layer. The control of the DB tier resources (230) can be achieved using various options such as Linux CKRM, AIX WLM, dynamic LPAR, or DB2 WLM. - An example of configuration and control could be creating classes for the various database instances in the OS WLM and then creating rules for classifying the processes belonging to these instances into the proper class and applying the proper amount of resource (CPU, IO, memory) shares to the classes based on a request from the controlling entity.
- Again, it is to be understood that while
FIG. 2B illustrates management of a second tier (database server tier) from a first tier (application server tier), the management model ofFIG. 2A may be applied to three or more tiers of a computing system. That is, principles of the invention may be used to manage end-to-end goals in a system that includes three or more tiers whereby work progressively flows from a first tier to a second tier and subsequently from the second tier to the third tier, and so on to other subsequent tiers. For example, the first tier manages the second tier and the second tier manages the third tier and so on. Such tier-to-tier management is achieved by employing management translation layers that allow the higher-level tier to communicate directives (commands) to the lower-level tier. The lower level tier converts/accepts these directives into its own/native management capability. -
FIG. 3 is a block diagram illustrating an illustrative hardware implementation of a computer system in accordance with which one or more components/steps of a management system (e.g., components/steps described in the context ofFIGS. 1 , 2A, and 2B) may be implemented, according to an embodiment of the present invention. For example, the illustrative architecture ofFIG. 3 may be used in implementing any and all of the components (i.e., nodes, node agents, database servers, deployment manager, DB controller, plug-ins, etc.) of any of the tiers shown inFIGS. 1 , 2A, and 2B. - Further, it is to be understood that the individual components/steps may be implemented on one such computer system, or more preferably, on more than one such computer system. In the case of an implementation on a distributed system, the individual computer systems and/or devices may be connected via a suitable network, e.g., the Internet or World Wide Web. However, the system may be realized via private or local networks. The invention is not limited to any particular network.
- As shown, the
computer system 300 may be implemented in accordance with aprocessor 302, amemory 304, I/O devices 306, and anetwork interface 308, coupled via acomputer bus 310 or alternate connection arrangement. - It is to be appreciated that the term “processor” as used herein is intended to include any processing device, such as, for example, one that includes a CPU (central processing unit) and/or other processing circuitry. It is also to be understood that the term “processor” may refer to more than one processing device and that various elements associated with a processing device may be shared by other processing devices.
- The term “memory” as used herein is intended to include memory associated with a processor or CPU, such as, for example, RAM, ROM, a fixed memory device (e.g., hard drive), a removable memory device (e.g., diskette), flash memory, etc.
- In addition, the phrase “input/output devices” or “I/O devices” as used herein is intended to include, for example, one or more input devices (e.g., keyboard, mouse, etc.) for entering data to the processing unit, and/or one or more output devices (e.g., speaker, display, etc.) for presenting results associated with the processing unit.
- Still further, the phrase “network interface” as used herein is intended to include, for example, one or more transceivers to permit the computer system to communicate with another computer system via an appropriate communications protocol.
- Accordingly, software components including instructions or code for performing the methodologies described herein may be stored in one or more of the associated memory devices (e.g., ROM, fixed or removable memory) and, when ready to be utilized, loaded in part or in whole (e.g., into RAM) and executed by a CPU.
- It is to be further appreciated that the present invention also comprises techniques for providing cross-tier management services.
- By way of example, a service provider agrees (e.g., via a service level agreement or some informal agreement or arrangement) with a service customer to provide cross-tier management services. That is, by way of one example only, the service provider may host the customer's web site and associated applications (e.g., e-commerce applications). Then, in accordance with terms of the contract between the service provider and the service customer, the service provider provides cross-tier management services which may comprise one or more of the methodologies of the invention described herein.
- Although illustrative embodiments of the present invention have been described herein with reference to the accompanying drawings, it is to be understood that the invention is not limited to those precise embodiments, and that various other changes and modifications may be made by one skilled in the art without departing from the scope or spirit of the invention.
Claims (20)
1. A method for managing a computing system, wherein the computing system comprises a first tier and at least a second tier, wherein the first tier and the second tier are configured to respond to a request received by the computing system, the method comprising the steps of:
monitoring performance of the second tier from the first tier; and
sending one or more management commands from the first tier to the second tier based on the monitored performance.
2. The method of claim 1 , wherein the first tier comprises an application server tier of the computing system.
3. The method of claim 1 , wherein the second tier comprises a database server tier of the computing system.
4. The method of claim 1 , wherein the second tier comprises a node agent for receiving the one or more management commands such that management control in the first tier extends to the second tier.
5. The method of claim 1 , wherein the second tier comprises an interface for abstracting the one or more management commands with respect to one or more provider-specific database management plug-in modules.
6. The method of claim 1 , wherein the first tier and the second tier implement a management model comprising a manageability extension layer, a manageability abstraction layer and a managed resource layer.
7. A method for managing a computing system, wherein the computing system comprises a first tier and at least a second tier, wherein the first tier and the second tier are configured to respond to a request received by the computing system, the method comprising the steps of:
sending performance data from the second tier to the first tier; and
receiving one or more management commands from the first tier at the second tier based on the monitored performance.
8. The method of claim 7 , wherein the first tier comprises an application server tier of the computing system.
9. The method of claim 7 , wherein the second tier comprises a database server tier of the computing system.
10. The method of claim 7 , wherein the second tier comprises a node agent for receiving the one or more management commands such that management control in the first tier extends to the second tier.
11. The method of claim 7 , wherein the second tier comprises an interface for abstracting the one or more management commands with respect to one or more provider-specific database management plug-in modules.
12. The method of claim 7 , wherein the first tier and the second tier implement a management model comprising a manageability extension layer, a manageability abstraction layer and a managed resource layer.
13. Apparatus for managing a computing system, wherein the computing system comprises a first tier and at least a second tier, wherein the first tier and the second tier are configured to respond to a request received by the computing system; the apparatus comprising:
a node agent at the second tier configured to: (i) send performance data from the second tier to the first tier; and (ii) receive one or more management commands from the first tier at the second tier based on the monitored performance; and
an interface at the second tier configured to abstract the one or more management commands with respect to one or more provider-specific database management plug-in modules.
14. The apparatus of claim 13 , wherein the first tier comprises an application server tier of the computing system.
15. The apparatus of claim 13 , wherein the second tier comprises a database server tier of the computing system.
16. A method for managing one or more goals in a system that comprises two or more tiers, whereby work progressively flows from tier-to-tier of the system, the method comprising the steps of:
communicating one or more directives from a higher-level tier to a lower-level tier; and
converting the one or more directives at the lower-level tier into instructions executable by a management component specific to the lower-level tier so as to effect the one or more system goals.
17. The method of claim 16 , wherein work progressively flows from a first tier to a second tier and subsequently from the second tier to at least a third tier.
18. The method of claim 17 , wherein the communicating step and the converting step further comprise:
communicating one or more directives from the first tier to the second tier; and
converting the one or more directives at the second tier into instructions executable by a management component specific to the second tier.
19. The method of claim 18 , wherein the communicating step and the converting step further comprise:
communicating one or more directives from the second tier to the third tier; and
converting the one or more directives at the third tier into instructions executable by a management component specific to the third tier.
20. A system for providing cross-tier management of resources in a computer system, comprising:
a manageability extension layer comprising node agent code on a managed resource tier for receiving one or more control and configuration commands for the managed resource from an application server tier;
a manageability abstraction layer comprising code for interacting with a management interface and thereby defining a service provider interface for abstracting the one or more control and configuration commands; and
a managed resource layer comprising resource-specific code for controlling a managed resource within the managed resource layer.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/479,511 US20080005317A1 (en) | 2006-06-30 | 2006-06-30 | Method and apparatus for cross-tier management in multi-tier computing system architecture |
US12/119,828 US8473603B2 (en) | 2006-06-30 | 2008-05-13 | Cross-tier management in multi-tier computing system architecture |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/479,511 US20080005317A1 (en) | 2006-06-30 | 2006-06-30 | Method and apparatus for cross-tier management in multi-tier computing system architecture |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/119,828 Continuation US8473603B2 (en) | 2006-06-30 | 2008-05-13 | Cross-tier management in multi-tier computing system architecture |
Publications (1)
Publication Number | Publication Date |
---|---|
US20080005317A1 true US20080005317A1 (en) | 2008-01-03 |
Family
ID=38878117
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/479,511 Abandoned US20080005317A1 (en) | 2006-06-30 | 2006-06-30 | Method and apparatus for cross-tier management in multi-tier computing system architecture |
US12/119,828 Expired - Fee Related US8473603B2 (en) | 2006-06-30 | 2008-05-13 | Cross-tier management in multi-tier computing system architecture |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/119,828 Expired - Fee Related US8473603B2 (en) | 2006-06-30 | 2008-05-13 | Cross-tier management in multi-tier computing system architecture |
Country Status (1)
Country | Link |
---|---|
US (2) | US20080005317A1 (en) |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090006445A1 (en) * | 2007-06-28 | 2009-01-01 | Esther Shemenzon | Binding between net technologies and SQL server statements |
US8438276B1 (en) | 2004-08-31 | 2013-05-07 | Precise Software Solutions, Inc. | Method of monitoring network and application performance by analyzing web clients and web servers |
US8788527B1 (en) | 2003-12-31 | 2014-07-22 | Precise Software Solutions, Inc. | Object-level database performance management |
US20140244980A1 (en) * | 2011-10-17 | 2014-08-28 | Yahoo! Inc. | Method and system for dynamic control of a multi-tier processing system |
US10176212B1 (en) | 2014-10-15 | 2019-01-08 | Seagate Technology Llc | Top level tier management |
CN109344201A (en) * | 2018-10-17 | 2019-02-15 | 国网江苏省电力有限公司信息通信分公司 | A kind of database performance load evaluation system and method based on machine learning |
US10908969B2 (en) | 2018-09-05 | 2021-02-02 | International Business Machines Corporation | Model driven dynamic management of enterprise workloads through adaptive tiering |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080005317A1 (en) * | 2006-06-30 | 2008-01-03 | International Business Machines Corporation | Method and apparatus for cross-tier management in multi-tier computing system architecture |
US8775498B2 (en) | 2009-10-23 | 2014-07-08 | International Business Machines Corporation | Universal architecture for client management extensions on monitoring, control, and configuration |
CN104660522A (en) * | 2013-11-22 | 2015-05-27 | 英业达科技有限公司 | Automatic node configuration method and server system |
Citations (24)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20010037374A1 (en) * | 2000-04-28 | 2001-11-01 | Shrum Kenneth W. | Internet server system test and measurement |
US6377993B1 (en) * | 1997-09-26 | 2002-04-23 | Mci Worldcom, Inc. | Integrated proxy interface for web based data management reports |
US20020052941A1 (en) * | 2000-02-11 | 2002-05-02 | Martin Patterson | Graphical editor for defining and creating a computer system |
US20020083170A1 (en) * | 2000-10-26 | 2002-06-27 | Metilinx | System-wide optimization integration model |
US20030023505A1 (en) * | 2001-02-28 | 2003-01-30 | Eglen Jan Alan | Digital online exchange |
US20030078960A1 (en) * | 2001-04-30 | 2003-04-24 | Murren Brian T. | Architecture and process for creating software applications for multiple domains |
US20030172362A1 (en) * | 2002-02-01 | 2003-09-11 | Mack-Crane T. Benjamin | Method and system for multi-layer network routing |
US20030208638A1 (en) * | 2002-04-02 | 2003-11-06 | Abrams Thomas Algie | Digital production services architecture |
US20040030739A1 (en) * | 2002-08-06 | 2004-02-12 | Homayoun Yousefi'zadeh | Database remote replication for multi-tier computer systems by homayoun yousefi'zadeh |
US6845397B1 (en) * | 2000-12-29 | 2005-01-18 | Nortel Networks Limited | Interface method and system for accessing inner layers of a network protocol |
US20050049901A1 (en) * | 2003-08-26 | 2005-03-03 | International Business Machines Corporation | Methods and systems for model-based management using abstract models |
US20050086645A1 (en) * | 2003-10-17 | 2005-04-21 | International Business Machines Corporation | Methods and systems for control discovery in computing systems |
US20050172161A1 (en) * | 2004-01-20 | 2005-08-04 | International Business Machines Corporation | Managing failover of J2EE compliant middleware in a high availability system |
US20050182843A1 (en) * | 2004-01-20 | 2005-08-18 | Microsoft Corporation | Computer system instrumentation information |
US6950848B1 (en) * | 2000-05-05 | 2005-09-27 | Yousefi Zadeh Homayoun | Database load balancing for multi-tier computer systems |
US20050268063A1 (en) * | 2004-05-25 | 2005-12-01 | International Business Machines Corporation | Systems and methods for providing constrained optimization using adaptive regulatory control |
US20050273643A1 (en) * | 2004-06-08 | 2005-12-08 | International Business Machines Corporation | Method, system and program for oscillation control of an internal process of a computer program |
US6976054B1 (en) * | 2000-12-29 | 2005-12-13 | Nortel Networks Limited | Method and system for accessing low-level resources in a network device |
US20050278381A1 (en) * | 2004-05-26 | 2005-12-15 | Yixin Diao | Method and apparatus for online sample interval determination |
US20050283539A1 (en) * | 2004-05-21 | 2005-12-22 | Christopher Betts | Balancing load requests and failovers using a UDDI proxy |
US20060210051A1 (en) * | 2005-03-18 | 2006-09-21 | Hiroyuki Tomisawa | Method and system for managing computer resource in system |
US20060277606A1 (en) * | 2005-06-01 | 2006-12-07 | Mamoon Yunus | Technique for determining web services vulnerabilities and compliance |
US20070282988A1 (en) * | 2006-05-31 | 2007-12-06 | Christof Bornhoevd | Device registration in a hierarchical monitor service |
US20080215729A1 (en) * | 2006-06-30 | 2008-09-04 | International Business Machines Corporation | Method and Apparatus for Cross-Tier Management in Multi-Tier Computing System Architecture |
Family Cites Families (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5396635A (en) * | 1990-06-01 | 1995-03-07 | Vadem Corporation | Power conservation apparatus having multiple power reduction levels dependent upon the activity of the computer system |
US6253228B1 (en) * | 1997-03-31 | 2001-06-26 | Apple Computer, Inc. | Method and apparatus for updating and synchronizing information between a client and a server |
US7143153B1 (en) * | 2000-11-09 | 2006-11-28 | Ciena Corporation | Internal network device dynamic health monitoring |
US7058826B2 (en) * | 2000-09-27 | 2006-06-06 | Amphus, Inc. | System, architecture, and method for logical server and other network devices in a dynamically configurable multi-server network environment |
US20070245165A1 (en) * | 2000-09-27 | 2007-10-18 | Amphus, Inc. | System and method for activity or event based dynamic energy conserving server reconfiguration |
US7822967B2 (en) * | 2000-09-27 | 2010-10-26 | Huron Ip Llc | Apparatus, architecture, and method for integrated modular server system providing dynamically power-managed and work-load managed network devices |
USRE40866E1 (en) * | 2000-09-27 | 2009-08-04 | Huron Ip Llc | System, method, and architecture for dynamic server power management and dynamic workload management for multiserver environment |
US7032119B2 (en) * | 2000-09-27 | 2006-04-18 | Amphus, Inc. | Dynamic power and workload management for multi-server system |
US6845392B2 (en) * | 2000-12-07 | 2005-01-18 | International Business Machines Corporation | Remote systems management via DBMS stored procedures and one communication line |
US8140659B2 (en) * | 2001-05-08 | 2012-03-20 | Hewlett-Packard Development Company, L.P. | Calculating an estimated time to complete a request |
US20060248360A1 (en) * | 2001-05-18 | 2006-11-02 | Fung Henry T | Multi-server and multi-CPU power management system and method |
US20040015600A1 (en) * | 2002-02-21 | 2004-01-22 | Ashutosh Tiwary | Workload post-processing and parameterization for a system for performance testing of N-tiered computer systems using recording and playback of workloads |
US6950825B2 (en) * | 2002-05-30 | 2005-09-27 | International Business Machines Corporation | Fine grained role-based access to system resources |
US7702739B1 (en) * | 2002-10-01 | 2010-04-20 | Bao Tran | Efficient transactional messaging between loosely coupled client and server over multiple intermittent networks with policy based routing |
WO2004070584A2 (en) * | 2003-02-04 | 2004-08-19 | Canonline Global Media, Inc. | Method and apparatus for converting objects between weakly and strongly typed programming frameworks |
CA2520933A1 (en) * | 2003-03-31 | 2004-10-21 | System Management Arts, Inc. | Method and apparatus for multi-realm system modeling |
US7194664B1 (en) * | 2003-09-08 | 2007-03-20 | Poon Fung | Method for tracing application execution path in a distributed data processing system |
US7805509B2 (en) * | 2004-06-04 | 2010-09-28 | Optier Ltd. | System and method for performance management in a multi-tier computing environment |
US7558858B1 (en) * | 2005-08-31 | 2009-07-07 | At&T Intellectual Property Ii, L.P. | High availability infrastructure with active-active designs |
US7890458B2 (en) * | 2006-10-20 | 2011-02-15 | Oracle International Corporation | Capturing database workload while preserving original transactional and concurrency characteristics for replay |
US8332824B2 (en) * | 2007-06-28 | 2012-12-11 | Precise Software Solutions, Ltd. | Binding between net technologies and SQL server statements |
-
2006
- 2006-06-30 US US11/479,511 patent/US20080005317A1/en not_active Abandoned
-
2008
- 2008-05-13 US US12/119,828 patent/US8473603B2/en not_active Expired - Fee Related
Patent Citations (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6377993B1 (en) * | 1997-09-26 | 2002-04-23 | Mci Worldcom, Inc. | Integrated proxy interface for web based data management reports |
US20020052941A1 (en) * | 2000-02-11 | 2002-05-02 | Martin Patterson | Graphical editor for defining and creating a computer system |
US20010037374A1 (en) * | 2000-04-28 | 2001-11-01 | Shrum Kenneth W. | Internet server system test and measurement |
US6950848B1 (en) * | 2000-05-05 | 2005-09-27 | Yousefi Zadeh Homayoun | Database load balancing for multi-tier computer systems |
US20020083170A1 (en) * | 2000-10-26 | 2002-06-27 | Metilinx | System-wide optimization integration model |
US6845397B1 (en) * | 2000-12-29 | 2005-01-18 | Nortel Networks Limited | Interface method and system for accessing inner layers of a network protocol |
US6976054B1 (en) * | 2000-12-29 | 2005-12-13 | Nortel Networks Limited | Method and system for accessing low-level resources in a network device |
US20030023505A1 (en) * | 2001-02-28 | 2003-01-30 | Eglen Jan Alan | Digital online exchange |
US20030078960A1 (en) * | 2001-04-30 | 2003-04-24 | Murren Brian T. | Architecture and process for creating software applications for multiple domains |
US20030172362A1 (en) * | 2002-02-01 | 2003-09-11 | Mack-Crane T. Benjamin | Method and system for multi-layer network routing |
US20030208638A1 (en) * | 2002-04-02 | 2003-11-06 | Abrams Thomas Algie | Digital production services architecture |
US7212574B2 (en) * | 2002-04-02 | 2007-05-01 | Microsoft Corporation | Digital production services architecture |
US20040030739A1 (en) * | 2002-08-06 | 2004-02-12 | Homayoun Yousefi'zadeh | Database remote replication for multi-tier computer systems by homayoun yousefi'zadeh |
US20050049901A1 (en) * | 2003-08-26 | 2005-03-03 | International Business Machines Corporation | Methods and systems for model-based management using abstract models |
US20050086645A1 (en) * | 2003-10-17 | 2005-04-21 | International Business Machines Corporation | Methods and systems for control discovery in computing systems |
US20050172161A1 (en) * | 2004-01-20 | 2005-08-04 | International Business Machines Corporation | Managing failover of J2EE compliant middleware in a high availability system |
US20050182843A1 (en) * | 2004-01-20 | 2005-08-18 | Microsoft Corporation | Computer system instrumentation information |
US20050283539A1 (en) * | 2004-05-21 | 2005-12-22 | Christopher Betts | Balancing load requests and failovers using a UDDI proxy |
US20050268063A1 (en) * | 2004-05-25 | 2005-12-01 | International Business Machines Corporation | Systems and methods for providing constrained optimization using adaptive regulatory control |
US20050278381A1 (en) * | 2004-05-26 | 2005-12-15 | Yixin Diao | Method and apparatus for online sample interval determination |
US20050273643A1 (en) * | 2004-06-08 | 2005-12-08 | International Business Machines Corporation | Method, system and program for oscillation control of an internal process of a computer program |
US20060210051A1 (en) * | 2005-03-18 | 2006-09-21 | Hiroyuki Tomisawa | Method and system for managing computer resource in system |
US20060277606A1 (en) * | 2005-06-01 | 2006-12-07 | Mamoon Yunus | Technique for determining web services vulnerabilities and compliance |
US20070282988A1 (en) * | 2006-05-31 | 2007-12-06 | Christof Bornhoevd | Device registration in a hierarchical monitor service |
US20080215729A1 (en) * | 2006-06-30 | 2008-09-04 | International Business Machines Corporation | Method and Apparatus for Cross-Tier Management in Multi-Tier Computing System Architecture |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8788527B1 (en) | 2003-12-31 | 2014-07-22 | Precise Software Solutions, Inc. | Object-level database performance management |
US8438276B1 (en) | 2004-08-31 | 2013-05-07 | Precise Software Solutions, Inc. | Method of monitoring network and application performance by analyzing web clients and web servers |
US20090006445A1 (en) * | 2007-06-28 | 2009-01-01 | Esther Shemenzon | Binding between net technologies and SQL server statements |
US8332824B2 (en) * | 2007-06-28 | 2012-12-11 | Precise Software Solutions, Ltd. | Binding between net technologies and SQL server statements |
US20140244980A1 (en) * | 2011-10-17 | 2014-08-28 | Yahoo! Inc. | Method and system for dynamic control of a multi-tier processing system |
US9378058B2 (en) * | 2011-10-17 | 2016-06-28 | Excalibur Ip, Llc | Method and system for dynamic control of a multi-tier processing system |
US10176212B1 (en) | 2014-10-15 | 2019-01-08 | Seagate Technology Llc | Top level tier management |
US10908969B2 (en) | 2018-09-05 | 2021-02-02 | International Business Machines Corporation | Model driven dynamic management of enterprise workloads through adaptive tiering |
CN109344201A (en) * | 2018-10-17 | 2019-02-15 | 国网江苏省电力有限公司信息通信分公司 | A kind of database performance load evaluation system and method based on machine learning |
Also Published As
Publication number | Publication date |
---|---|
US20080215729A1 (en) | 2008-09-04 |
US8473603B2 (en) | 2013-06-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8473603B2 (en) | Cross-tier management in multi-tier computing system architecture | |
US11481244B2 (en) | Methods and systems that verify endpoints and external tasks in release-pipeline prior to execution | |
US9841962B2 (en) | Hybrid-cloud infrastructures | |
US10511482B2 (en) | Dynamic activation of web applications | |
EP3454214A1 (en) | Infrastructure instantiation, collaboration, and validation architecture for serverless execution frameworks | |
US20190377570A1 (en) | Methods and systems that share resources among multiple, interdependent release pipelines | |
US8028048B2 (en) | Method and apparatus for policy-based provisioning in a virtualized service delivery environment | |
US8140817B2 (en) | Dynamic logical partition management for NUMA machines and clusters | |
US20110078679A1 (en) | Provisioning virtual machine placement | |
US8370802B2 (en) | Specifying an order for changing an operational state of software application components | |
US9348709B2 (en) | Managing nodes in a distributed computing environment | |
US20050289540A1 (en) | Providing on-demand capabilities using virtual machines and clustering processes | |
US20070061811A1 (en) | Modular Event-Driven Processing | |
US11363117B2 (en) | Software-specific auto scaling | |
US11102278B2 (en) | Method for managing a software-defined data center implementing redundant cloud management stacks with duplicate API calls processed in parallel | |
CN109117252B (en) | Method and system for task processing based on container and container cluster management system | |
US20190227793A1 (en) | Code-change and developer rating in an automated-application-release-management subsystem | |
CN103365713A (en) | Resource dispatch and management method and device | |
KR20070057838A (en) | Modular event-driven processing | |
US9184982B2 (en) | Balancing the allocation of virtual machines in cloud systems | |
US20080288622A1 (en) | Managing Server Farms | |
US9516137B2 (en) | Combining disparate applications into a single workload group | |
US20170161101A1 (en) | Modularized automated-application-release-management subsystem | |
US20190012150A1 (en) | Methods and systems that generate proxy objects that provide an interface to third-party executables | |
US20080282242A1 (en) | Simulation management within a grid infrastructure |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:DIAO, YIXIN;SHAIKH, HIDAYATULLAH HABEEBULLAH;SURENDRA, MAHESWARAN;REEL/FRAME:018135/0152 Effective date: 20060802 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |