|Publication number||US7150014 B2|
|Application number||US 10/264,468|
|Publication date||Dec 12, 2006|
|Filing date||Oct 4, 2002|
|Priority date||Oct 4, 2002|
|Also published as||US20040068723|
|Publication number||10264468, 264468, US 7150014 B2, US 7150014B2, US-B2-7150014, US7150014 B2, US7150014B2|
|Inventors||Sven Graupner, Holger Trinks, Vadim Kotov|
|Original Assignee||Hewlett-Packard Development Company, L.P.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (1), Non-Patent Citations (4), Referenced by (34), Classifications (6), Legal Events (6)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present invention relates generally to software packages in computer systems and, more specifically, to automatically deploying such packages.
Currently, deploying software packages such as needed for management agents in computer systems is typically manual and difficult to automate. The management agents or other software entities are customarily identified by Internet Protocol (IP) addresses or hostnames and port numbers, which usually depend on the network infrastructure of machines that store the management agents or the software entities. Further, a node or an instance representing a management agent usually requires individual configuration information that is difficult to maintain when the number of instances increases.
Remote software installation and configuration systems have been available in which configuration engines provide centralized configuration information and interfaces for operators to perform remote configuration tasks, usually described in form of scripts. However, configuration engines are also manual or operator-driven, i.e., the operators are required to initiate configurations. Configuration engines are not designed to install and establish whole topologies as controlled processes. A configuration engine initiates only one process, which does not initiate other processes for installing other instances, and does not facilitate automatic assignment of identity and roles to individual instances.
As the systems and their instances become larger, e.g., in the order of 5,000 to 10,000 instances, deployment tasks are becoming more complicated with issues of software distribution, installation, configuration, etc.
Based on the foregoing, it is desirable that mechanisms are provided to solve the above deficiencies and related problems.
The present invention, in various embodiments, provides techniques for automatically deploying software packages. In one embodiment, management agents represent these packages, a logical tree represents the deployed structure, and a node of the tree represents an agent. A node that does not have any child node is referred to as a leaf node. A recursive process associated with at least one repository generates the tree. The repositories include information for configuring the nodes and thus control the deployment process. During deployment, a non-leaf node, referred to as an initiator node, uses information received from a corresponding repository to generate its child nodes. A child node, if being an initiator node, recursively generates its child nodes until the recursive process stops, as there is no additional child node to be generated. Further, node identifiers are automatically established and assigned to respective nodes. Those identifiers are used by software instances such as management agents represented by nodes to communicate with other software instances such as repositories or directories for registering information about nodes, looking up information about other nodes, etc.
The present invention is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings in which like reference numerals refer to similar elements and in which:
In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be apparent to those skilled in the art that the invention may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the invention.
A node 110 represents a management agent, such as a management server, a sensor, an actuator, or their equivalences. A management agent is comprised of software components, and may be referred to as a software package or a set of computer programs. Generally, management agents are installed into a computer of a data center providing the infrastructure for managing and controlling both hardware and software running on the data center's computers, and perform tasks such as monitoring, processing and disseminating management and control data, making decisions, actuating them, etc. These management agents, being software packages, can use the deployment techniques disclosed in this document. Once all software components are deployed for a particular management agent, a server, a sensor, or an actuator performs its corresponding assigned tasks.
A management server may include and thus manage a plurality of sensors and/or actuators, which provide data streams, report data to the management server, etc. A sensor collects information such as CPU utilization, machine temperature, the amount of data processed in a time period, etc. An actuator performs tasks such as controlling the computer, initiating reboot and shutdown, executing database commands, etc. Typically, an actuator waits for an external command for the actuator to initiate an action while a sensor is self-initiating, usually in a time interval or on the occurrence of events such as when sensor thresholds are passed.
Deploying nodes 110 is automatic through a recursive process, including distributing, installing, and configuring software for each of the software packages represented by a management agent, into a computer. This computer, after the deployment process, may host more than one management agent. A node 110 may be an initiator node 110I or a leaf node 110L. Similarly, due to the nature of the recursive process, a child node of a node 110 may also be an initiator node 110I or a leaf node 110L. An initiator node 110I, having at least one child node, controls the deployment and configuration of its child nodes. A leaf node 110L, having no child node, stops the recursive process, while an initiator node 110I, having at least one child node, continues to deploy its child nodes, and thus continues the recursive deployment process. When all child nodes are leaf nodes, the recursive process stops. An initiator node 110I obtains information from a corresponding repository 120 that provides information related to the child nodes, e.g., whether a child node is an initiator node 110I or a leaf node 110L. A child node, when being an initiator node 110I, performs tasks of initiator nodes, i.e., continues to deploy its child nodes independently and in parallel to other initiator child nodes until the recursive deployment process stops. Typically, a system administrator determines the shape of tree 100, e.g., the number of nodes 110, the number of levels in tree 100, the types of management agents in a level, etc., by providing appropriate information in repositories 120 controlling the recursive deployment processes.
Once initiator nodes 110I have performed their functions of deploying their child nodes as management agents, initiator nodes 110I may be removed from the system. In one embodiment, they remain in the system and are used to remove nodes 110 from tree 100. In this situation, nodes 110 are also recursively removed. Instructions to remove nodes propagate from the top node 110T to leaf nodes 110L each of which is inactivated and/or removed from the system. Once all child nodes of a node 110I are removed from the system, the node 110I is removed from the system. The process propagates up to top node 110T.
Nodes 110 are connected via one or a plurality of communication links, which are mechanisms for nodes 110 to communicate with one another. A communication link may be a single network or a combination of networks that utilizes one or a combination of communication protocols such as the Transmission Control Protocol/Internet Protocol (TCP/IP), the Public Switched Telephone Network (PSTN), the Digital Subscriber Lines (DSL), the cable network, the satellite-compliant, the wireless-compliant, the Internet, etc. Examples of a communication link include network media, interconnection fabrics, rings, crossbars, etc. A node 110 may use a communication link different from that of another node 110.
Repositories 120 contain information about nodes 110, such as relationships among the nodes, references, identifiers or addresses of locations of installation programs or boot code, configuration information, etc. Repositories 120 also contain information that controls the deployment process of nodes 110, information to define tasks for each node 110, i.e., whether a particular node 110 is a server, a sensor, an actuator, etc. Normally, a system administrator determines the number of repositories 120, and provides configuration information to repositories 120 from which automated processes may start.
The number of repositories 120 used in
In one embodiment, information maintained by a repository 120 includes references to bootable installation programs for the management agents, references to configuration data for the installation programs, and references to configuration data for the management agents to be deployed. Installation programs are the code booted for management agents. An installation program performs typical actions, such as creating directories, updating application configuration files, downloading more program files or libraries, etc., for the software packages represented by the management agents. Installation programs are shared for management agents having similar roles. For examples, servers share the same installation program for servers, sensors share the same installation program for sensors, actuators share the same installation program for actuators, etc. Installation programs may contain all the software components for the corresponding management agents. For example, an installation program for an initiator contains software components to form a program providing functions of an initiator; an installation program for a sensor contains software components to form a program providing functions of a sensor, an installation program for an actuator contains software components to form a program providing functions of an actuator, etc.
Configuration data for the installation programs are parameters and actions needed in installing a management agent. Configuration data together with installation programs provide platform or role-specific differences of management agents. Configuration data may be used in setting or testing specific environment variables, creating directories, etc., for the software components comprising a software package represented by a node 110.
Configuration data for management agents are parameters specific for a particular management instance. The data include, for example, environment settings, paths, and command line arguments for the software packages represented by a server, an initiator, a sensor, an actuator, etc., references to managed objects, references to other management agents such as parent, children, etc., in tree 100, interval tines for status reports, etc. In one embodiment, configuration data for a management agent are passed to the management agent when it is launched.
Actual components of installation programs and configuration data may be stored in repositories 120, but may also be stored in other forms or locations. For example, installation programs may be stored at a web site of a company providing management software while configuration data may be stored in another company's web site providing management services for customer environments. Alternatively, installation programs and configuration data may be stored in the same repository having the address of the repository as references. Each installation program may also obtain additional files and configuration data from other locations such as installation servers. Installation programs may refer to scripts written in appropriate languages such as Shell, Perl, Python, Java, etc.
In one embodiment, references to program code and configuration data needed for deploying management agents are stored as three separate lists, each of which corresponds to the installation programs, the configuration information for the installation programs, and the configuration information for the management agents. Upon receiving a request with the management agent's identifier, a repository 120 matches against patterns of all entries in each list. A repository 120 also returns references to installation programs or configuration data of entries with matching patterns. The boot stubs (explained in the following section), based on the references, obtain actual installation programs and configuration data.
A boot stub is a protocol handler that runs on a computer, which is able to host a management agent. The boot stub is responsible for handling the deployment protocols of one or more management agents or other software packages to be deployed on that computer. The boot stub receives control commands and messages from an initiator node 110I, e.g., when initiator node 110I requests the deployment of a node 110. Exemplary control commands include deploying, configuring, starting, activating, inactivating, etc., a management agent.
The boot stub receives information related to installation programs for management agents from a repository 120, installation configuration data, and configuration data for the management agents. In one embodiment, the information is in the form of references from which the boot stub obtains the actual data.
The boot stub also includes information on how to configure, start, and shutdown a program represented by a management agent. In one embodiment, the boot stub, in determining how to start a management agent, recognizes the file format, e.g., binary executable, Perl scripts, Java programs, etc. Further, the boot stub receives a string that represents the command line to start executing a program represented by a management agent.
In one embodiment, boots stub are in the form of a Java servlet. A boot stub uses HTTP to communicate with an initiator node 110I, and the communication message format is XML-based. When an installation program is launched, the boot stub provides the code with the appropriate environment and command-line parameters. However, boot stubs may be implemented in different ways, including, for example, daemon processes launched by inetd on Unix, etc. Normally, boot stubs are implemented in a way that they can launch installation code of different formats, e.g., Java classes, scripts or executable binaries according to the programs. A boot stub can also be part of the boot image of the computer hosting the boot stub and the management agent.
In one embodiment, on request of the initiator that deploys a management agent, a boot stub can reconfigure the management agent even after it has been deployed. Further, the boot stub modifies configuration parameters of the management agents and triggers the management agent to restart with the new configurations. In an alternative embodiment, the boot stub terminates the management agent, obtains a new configuration and/or new installation code and reruns the management agent installation code with new configurations.
Directories 130 are network services that provide boot-stub topology models and management-agent topology models. A directory 130 could be part of network information services (e.g., NIS), or part of a repository 120. A management-agent topology model provides information about the deployed management agents in a domain while a boot-stub topology model provides information about the location of boot stubs hosted on computers, the locations of the computers that are going to host management agents, and the type of management agents to be installed, i.e., whether a management agent is a server, an initiator, a sensor, etc. An initiator node 110I can use a boot-stub topology model to identify and locate computers that should host a management agent 110.
Topology models can be obtained in several ways. A program represented by a management agent initializes a directory 130 with computers that host a boot stub. When a computer boots and the boot stub on that computer is initialized, the boot stub sends a registration message to a pre-configured directory service responsible for registering the management agent. Alternatively, when a boot stub is initialized, it sends a broadcast message to find the directory service, and, once identifying the service, the boot stub registers with the service. Alternatively yet, a directory service periodically sends broadcast messages to find existing boot stubs, which reply to this broadcast with a registration message to the directory.
A management agent's identity or identifier is the information that uniquely identifies the agent when it communicates with other agents and/or entities. For example, management agents represented by nodes 110 use the identity to communicate with repositories 120 and/or directories 130 for registering information about nodes, looking up information about other nodes, etc. In one embodiment, identities of management agents are generated while tree 100 is being generated, based on defined rules. The identity of a child node is represented by a string concatenating the identity of the initiator node, and a unique identifier for the node. Examples of identifiers for nodes may include a number or a character or a sequence of characters. For illustration purposes, unique identifiers for nodes in level 1 may be named “region1,” “region2,” “region3,” etc.; nodes in level 2 are named “zone1,” “zone2,” “zone3,” etc.; nodes in level 3 are named “dc1,” “dc2,” “dc3,” etc. For further illustration purposes, the identity of the top node or node 110T is “top,” then the child nodes of node 110T, or the nodes in level 1, are named “top/region1,” “top/region2,” “top/region3,” etc. The child nodes of node “region1” are named “region1/zone1,” “region1/zone2,” “region1/zone3,” etc. The child nodes of node “region1/zone3” are named “region1/zone3/dc1,” “region1/zone3/dc2,” “region/zone3/dc3,” etc. The identity of a node 110 thus represents a path starting from the top level to the node. In the above example, a character “/” separates a level of tree 100, and is used in one embodiment. However, other characters, including, for example, “\”, “&”, etc., may be used.
In one embodiment, repositories 120 use patterns to match identities of nodes 110 so that repositories 120 can provide information to nodes 110, e.g., when initiator nodes 110I seek information to deploy their child nodes. Repositories 120 provide nodes having similar characteristic with the same configuration file that provides similar configurations. Different patterns may be used to match the identities and thus provide different files for different configurations. Selecting a pattern is based on how tree 100 is desired, including the number of nodes 110, the number of levels, the types of management agents represented by the nodes in each level or in tree 100, etc. For example, nodes in one or several levels may be initiators using the same configuration files for configuring initiators; in a five child node to be deployed, three nodes may be sensors and use the same configuration file for configuring sensors while the other two nodes may be actuators and use the same configuration file for configuring actuators, etc.
Using patterns enables using the same configurations from the same configuration files. As seen in
In step 404, initiator node 110T sends a message to each boot stub B(1), B(2), and B(3), and instructs each boot stub B(1), B(2), and B(3) to initiate the deployment process. That is, boot stub B(1) is to deploy initiator I in computer M(1), boot stub B(2) is to deploy sensor S in computer M(2), and boot stub B(3) is to deploy actuator A in computer M(3).
In step 408, boot stubs B(1), B(2), and B(3) communicate with their corresponding repositories 120 to obtain the installation programs and configuration data for deploying initiator I, sensor S, and actuator A in computers M(1), M(2), and M(3), respectively. For illustration purposes, boot stubs B(1), B(2), and B(3) report to repository 120(1), which also corresponds to all nodes in level one of the tree 100 to be generated. Consequently, repository 120(1) corresponds to child nodes of top node 110T, which are in level 1 of tree 100, and thus include initiator I, sensor S, and actuator A. Even though all boot stubs B(1), B(2), and B(3) report to repository 120(1), each acquires information for deploying an initiator, a sensor, and an actuator, to deploy initiator I, sensor S, and actuator A, respectively.
In step 410, repository 120(1) provides references to installation programs and configuration data. In one embodiment, these references are in the form of a uniform resource locator (URL), and show that installation programs and configuration data for initiators, sensors, and actuators are stored in locations LI, LS, and LA, respectively.
In step 412, each boot stub B(1), B(2), and B(3) obtains the installation programs for each initiator, sensor, and actuator from the referenced locations provided by repository 120(1). Boot stubs B(1), B(2), and B(3) thus obtain the installation programs from locations LI, LS, and LA respectively. The installation programs may contain all the software components for the corresponding initiator I, sensor S, and actuator A. Alternatively, each installation program obtains additional files and configuration data from other locations such as installation servers.
In step 416, boot stubs B(1), B(2), and B(3) obtain configuration data from the locations specified by repository 120(1), which are locations LI, LS, and LA for initiator I, sensor S, and actuator A, respectively. Configuration data include, for example, environment variables and initialization parameters that are passed to and used by the installation programs. In one embodiment, configuration data is in the form of XML documents from different locations.
In step 420, boot stubs B(1), B(2), and B(3), with the received installation data, run the installation programs that install initiator I in computer M(1), sensor S in computer M(2), and actuator A in computer M(3). An installation program performs typical actions, such as creating directories, updating application configuration files, downloading more program files or libraries, etc., for the software packages represented by initiator I, sensor S, and actuator A. After this step 420, necessary software is installed and configured so that initiator I, sensor S, and actuator A can perform their respective functions.
In step 424, to launch initiator I, sensor S, and actuator A, boot stubs B(1), B(2), and B(3) provide these management agents I, S, and A with corresponding configuration data. Initiator I, sensor S, and actuator A thus can start their corresponding functions.
In step 428, each boot stub B(1), B(2), and B(3), reports to initiator 110T that each boot stub has successfully deployed initiator I, sensor S, and actuator A, respectively.
In step 432, initiator 110T updates the management-agent topology model in directory 130 to reflect the new management agents in tree 100 that now includes initiator I, sensor S, and actuator A.
If, in step 436, it is determined that none of the newly installed management agent is an initiator, then the method ends. Otherwise, an initiator continues the deployment process, i.e., deploying its child nodes, using the above steps starting from step 402. In this
In the above example, each computer M(1), M(2), and M(3) is installed with initiator I, sensor S, and actuator A, respectively. However, a computer may be installed with more than one management agent of the same or different types. Normally, each management agent of the same type is responsible for a different function. For example, computer M(1) may be installed with initiator I and a first instance of a sensor S1; computer M(2) may be installed with a second instance of sensor S1, a sensor S2, a sensor S3, and computer M(3) may be installed with a few actuators, one or more sensors, etc. All instances of sensor S1 may be measuring CPU utilization, sensor S2 may be monitoring input/output traffic, actuator A1 may be calculating statistical distribution of CPU utilization over a time period, etc.
CPU 504 controls logic, processes information, and coordinates activities within computer system 500. In one embodiment, CPU 504 executes instructions stored in RAMs 508 and ROMs 512, by, for example, coordinating the movement of data from input device 528 to display device 532. CPU 504 may include one or a plurality of processors.
RAMs 508, usually being referred to as main memory, temporarily store information and instructions to be executed by CPU 504. Information in RAMs 508 may be obtained from input device 528 or generated by CPU 504 as part of the algorithmic processes required by the instructions that are executed by CPU 504.
ROMs 512 store information and instructions that, once written in a ROM chip, are read-only and are not modified or removed. In one embodiment, ROMs 512 store commands for configurations and initial operations of computer system 500.
Storage device 516, such as floppy disks, disk drives, or tape drives, durably stores information for use by computer system 500.
Communication interface 520 enables computer system 500 to interface with other computers or devices. Communication interface 520 may be, for example, a modem, an integrated services digital network (ISDN) card, a local area network (LAN) port, etc. Those skilled in the art will recognize that modems or ISDN cards provide data communications via telephone lines while a LAN port provides data communications via a LAN. Communication interface 520 may also allow wireless communications.
Bus 524 can be any communication mechanism for communicating information for use by computer system 500. In the example of
Computer system 500 is typically coupled to an input device 528, a display device 532, and a cursor control 536. Input device 528, such as a keyboard including alphanumeric and other keys, communicates information and commands to CPU 504. Display device 532, such as a cathode ray tube (CRT), displays information to users of computer system 500. Cursor control 536, such as a mouse, a trackball, or cursor direction keys, communicates direction information and commands to CPU 504 and controls cursor movement on display device 532.
Computer system 500 may communicate with other computers or devices through one or more networks. For example, computer system 500, using communication interface 520, communicates through a network 540 to another computer 544 connected to a printer 548, or through the world wide web 552 to a server 556. The world wide web 552 is commonly referred to as the “Internet.” Alternatively, computer system 500 may access the Internet 552 via network 540.
Computer system 500 may be used to implement the techniques described above. In various embodiments, CPU 504 performs the steps of the techniques by executing instructions brought to RAMs 508. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions to implement the described techniques. Consequently, embodiments of the invention are not limited to any one or a combination of software, firmware, hardware, or circuitry.
Instructions executed by CPU 504 may be stored in and/or carried through one or more computer-readable media, which refer to any medium from which a computer reads information. Computer-readable media may be, for example, a floppy disk, a hard disk, a zip-drive cartridge, a magnetic tape, or any other magnetic medium, a CD-ROM, a CD-RAM, a DVD-ROM, a DVD-RAM, or any other optical medium, paper-tape, punch-cards, or any other physical medium having patterns of holes, a RAM, a ROM, an EPROM, or any other memory chip or cartridge. Computer-readable media may also be coaxial cables, copper wire, fiber optics, acoustic or electromagnetic waves, capacitive or inductive coupling, etc. As an example, the instructions to be executed by CPU 504 are in the form of one or more software programs and are initially stored in a CD-ROM being interfaced with computer system 500 via bus 524. Computer system 500 loads these instructions in RAMs 508, executes some instructions, and sends some instructions via communication interface 520, a modem, and a telephone line to a network, e.g. network 540, the Internet 552, etc. A remote computer, receiving data through a network cable, executes the received instructions and sends the data to computer system 500 to be stored in storage device 516.
In the foregoing specification, the invention has been described with reference to specific embodiments. However, it will be evident that various modifications and changes may be made without departing from the broader spirit and scope of the invention. Accordingly, the specification and drawings are to be regarded as illustrative rather than as restrictive.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US6381742 *||Jun 19, 1998||Apr 30, 2002||Microsoft Corporation||Software package management|
|1||*||"Agent-based configuration management of distributed applications", Berghoff, J.; Drobnik, O.; Lingnau, A.; Monch, C.; Configurable Distributed System, 1996, Proceedings., Third International Conference on May 6-8, 1996, pp. 52-59.|
|2||*||"Essential SNMP", By Douglas Mauro, Kevin Schmidt, O'Reilly Pub Date: Jul. 2001 ,ISBN: 0-596-00020-0, excerpts.|
|3||*||"Linux in a Nutshell, 3rd Edition"By Stephen Figgins, Jessica P. Hekman, Ellen Siever, Stephen Spainhour, O'Reilly Pub Date: Aug. 2000, ISBN: 0-596-0002, excerpts.|
|4||*||"Web Hacking: Attacks and Defense", By Stuart McClure, Saumil Shah, Shreeraj Shah, Publisher: Addison Wesley Professional Pub Date: Aug. 8, 2002, ISBN: 0-201-76176-9, excerpts.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7418710 *||Oct 5, 2007||Aug 26, 2008||Kaspersky Lab, Zao||Processing data objects based on object-oriented component infrastructure|
|US7526550||Mar 26, 2004||Apr 28, 2009||Sap Ag||Unified logging service with a log viewer|
|US7577731||Dec 30, 2003||Aug 18, 2009||Sap Ag||System and method for monitoring program code|
|US7702763 *||Jul 31, 2002||Apr 20, 2010||Hewlett-Packard Development Company, L.P.||Remote monitoring of computer devices|
|US7721266||Mar 26, 2004||May 18, 2010||Sap Ag||Unified logging service with a logging formatter|
|US7725572||Dec 30, 2003||May 25, 2010||Sap Ag||Notification architecture and method employed within a clustered node configuration|
|US7756968||Dec 30, 2003||Jul 13, 2010||Sap Ag||Method and system for employing a hierarchical monitor tree for monitoring system resources in a data processing environment|
|US7788226||Dec 30, 2004||Aug 31, 2010||Sap Ag||Monitoring availability of applications|
|US7802247 *||Dec 30, 2005||Sep 21, 2010||United Services Automobile Association (Usaa)||Method and system for restoring software|
|US7822826||Dec 30, 2003||Oct 26, 2010||Sap Ag||Deployment of a web service|
|US7827549 *||Sep 15, 2006||Nov 2, 2010||Symantec Corporation||Method and system for creating and executing generic software packages|
|US7831968||Dec 30, 2005||Nov 9, 2010||United Services Automobile Association (Usaa)||Method and system for restoring software|
|US7840955||Dec 30, 2005||Nov 23, 2010||United Services Automobile Association (Usaa)||Method and system for restoring software|
|US7840961 *||Dec 30, 2005||Nov 23, 2010||United Services Automobile Association (Usaa)||Method and system for installing software on multiple computing systems|
|US7908605 *||Jan 28, 2005||Mar 15, 2011||Hewlett-Packard Development Company, L.P.||Hierarchal control system for controlling the allocation of computer resources|
|US7941521||Dec 30, 2003||May 10, 2011||Sap Ag||Multi-service management architecture employed within a clustered node configuration|
|US8185889 *||Jun 19, 2007||May 22, 2012||Red Hat, Inc.||Methods and systems for porting software packages from one format to another|
|US8225307 *||Nov 15, 2004||Jul 17, 2012||International Business Machines Corporation||On-demand software module deployment|
|US8234656||Aug 5, 2008||Jul 31, 2012||Kaspersky Lab, Zao||Processing data objects based on object-oriented component infrastructure|
|US8402457 *||Oct 13, 2010||Mar 19, 2013||Kabushiki Kaisha Toshiba||Content distribution method and content distribution package|
|US8566820||Dec 30, 2005||Oct 22, 2013||United Services Automobile Association (Usaa)||Method and system for installing software|
|US8726271||Dec 30, 2005||May 13, 2014||United Services Automobile Association (Usaa)||Method and system for installing software|
|US8843919||Nov 22, 2010||Sep 23, 2014||United Services Automobile Association (Usaa)||Method and system for restoring software|
|US20030028829 *||Jul 31, 2002||Feb 6, 2003||Hewlett Packard Company||Remote monitoring of computer devices|
|US20050108702 *||Nov 15, 2004||May 19, 2005||International Business Machines Corporation||On-demand software module deployment|
|US20050216585 *||Mar 26, 2004||Sep 29, 2005||Tsvetelina Todorova||Monitor viewer for an enterprise network monitoring system|
|US20050257206 *||May 14, 2004||Nov 17, 2005||Semerdzhiev Krasimir P||Pair-update mechanism for update module|
|US20060149729 *||Dec 30, 2004||Jul 6, 2006||Pfeiffer Stephen W||Monitoring availability of applications|
|US20080127171 *||Sep 15, 2006||May 29, 2008||Altiris, Inc.||Method and System for Creating and Executing Generic Software Packages|
|US20080320465 *||Jun 19, 2007||Dec 25, 2008||Kinder Nathan G||Methods and systems for porting software packages from one format to another|
|US20100191724 *||Jan 23, 2009||Jul 29, 2010||Mehmet Kivanc Ozonat||Method and system to identify providers in web documents|
|US20100191725 *||Jan 23, 2009||Jul 29, 2010||Mehmet Kivanc Ozonat||A system and method for discovering providers|
|US20100313031 *||Jun 4, 2009||Dec 9, 2010||Bertrand Jaslet||Watermarking during system deployment|
|US20110035579 *||Oct 13, 2010||Feb 10, 2011||Akira Miura||Content distribution method and content distribution package|
|U.S. Classification||717/174, 717/168|
|International Classification||G06F9/445, G06F9/44|
|Feb 12, 2003||AS||Assignment|
Owner name: HEWLETT-PACKARD COMPANY, COLORADO
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:GRAUPNER, SVEN;TRINKS, HOLGER;KOTOV, VADIM;REEL/FRAME:013749/0703;SIGNING DATES FROM 20020927 TO 20020928
|Jun 18, 2003||AS||Assignment|
Owner name: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.,COLORADO
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HEWLETT-PACKARD COMPANY;REEL/FRAME:013776/0928
Effective date: 20030131
|Apr 28, 2009||CC||Certificate of correction|
|Jun 14, 2010||FPAY||Fee payment|
Year of fee payment: 4
|May 26, 2014||FPAY||Fee payment|
Year of fee payment: 8
|Nov 9, 2015||AS||Assignment|
Owner name: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP, TEXAS
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.;REEL/FRAME:037079/0001
Effective date: 20151027