US7743373B2 - Method and apparatus for managing software catalog and providing configuration for installation - Google Patents
Method and apparatus for managing software catalog and providing configuration for installation Download PDFInfo
- Publication number
- US7743373B2 US7743373B2 US11/123,304 US12330405A US7743373B2 US 7743373 B2 US7743373 B2 US 7743373B2 US 12330405 A US12330405 A US 12330405A US 7743373 B2 US7743373 B2 US 7743373B2
- Authority
- US
- United States
- Prior art keywords
- software
- installation
- installable
- responsive
- patches
- 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.)
- Active, expires
Links
- 238000000034 method Methods 0.000 title claims abstract description 38
- 238000009434 installation Methods 0.000 title claims description 80
- 230000007246 mechanism Effects 0.000 claims abstract description 64
- 230000002708 enhancing effect Effects 0.000 claims abstract description 6
- 238000012545 processing Methods 0.000 claims description 37
- 230000008859 change Effects 0.000 claims description 7
- 230000006870 function Effects 0.000 claims description 7
- 238000004590 computer program Methods 0.000 claims 2
- 230000004044 response Effects 0.000 description 17
- 238000010586 diagram Methods 0.000 description 14
- 230000008569 process Effects 0.000 description 14
- 238000004458 analytical method Methods 0.000 description 9
- 238000004891 communication Methods 0.000 description 7
- 230000002093 peripheral effect Effects 0.000 description 5
- 230000005540 biological transmission Effects 0.000 description 2
- 238000009826 distribution Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000003860 storage Methods 0.000 description 2
- 230000006399 behavior Effects 0.000 description 1
- 238000010367 cloning Methods 0.000 description 1
- 230000001427 coherent effect Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000002040 relaxant effect Effects 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 230000035899 viability Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
Definitions
- the present invention relates to a data processing system.
- the present invention relates to enhancing software catalog manageability for provisioning applications.
- the present invention relates to enhancing manageability of a software catalog, abstracting software configuration, and desired state management.
- a response file comprises responses of an installation much like a wizard used during installation, except that the response file is predefined by an administrator with configuration settings of the software product.
- a response file comprises a list of name-value pairs that are predefined before installation. While the response file is useful in automatic deployment of software, it is limiting in that the response file is textual and it lacks the flexibility for change. In addition, the response file fails to capture everything a software product needs during post installation configuration.
- the response file fails to handle dependencies between configuration settings.
- a J2EE Web module running on a Web server on machine X may depend on a database module running on a database server on machine Y.
- the user has to define the IP address of the database server in which the database module resides at installation time in order to invoke the module.
- Embodiments of the present invention provide a first mechanism for enhancing software catalog manageability.
- the first mechanism includes a software model that separates metadata of software from actual binaries of the software.
- embodiments of the present invention provide a second mechanism for abstracting configuration and settings of the software using a hierarchical software resource template.
- embodiments of the present invention provide a third mechanism for comparing software resources or patches installed on a target system with software resources defined in a server template or patches that should be applied to determine a difference and presenting the difference to a user.
- FIG. 1 depicts a pictorial representation of a network of data processing systems in which embodiments of the present invention may be implemented
- FIG. 2 is a block diagram of a data processing system that may be implemented as a server, in accordance with an embodiment of the present invention
- FIG. 3 is a block diagram of a data processing system in which an illustrative embodiment of the present invention may be implemented
- FIG. 4 is a diagram illustrating an exemplary data center, in accordance with an illustrative embodiment of the present invention.
- FIG. 5 is a diagram illustrating an exemplary software model used to separate metadata from the binaries in accordance with an illustrative embodiment of the present invention
- FIG. 6A is a diagram illustrating an exemplary software resource template in accordance with an illustrative embodiment of the present invention.
- FIG. 6B is a diagram illustrating an exemplary software resource template in continuation of FIG. 6A in accordance with an illustrative embodiment of the present invention
- FIG. 7 is a diagram illustrating an exemplary hierarchical structure of a software resource template parallel to the software resource to be created in accordance with an illustrative embodiment of the present invention
- FIG. 8 is a flowchart of an exemplary process for leveraging server template to manage desired state in accordance with an illustrative embodiment of the present invention.
- FIG. 9 is a flowchart of an exemplary process for using software resources in a data center model to assess patch compliance in accordance with an illustrative embodiment of the present invention.
- FIG. 1 depicts a pictorial representation of a network of data processing systems in which embodiments of the present invention may be implemented.
- Network data processing system 100 is a network of computers in which the present invention may be implemented.
- Network data processing system 100 contains network 102 , which is the medium used to provide communications links between various devices and computers connected together within network data processing system 100 .
- Network 102 may include connections, such as wire, wireless communication links, or fiber optic cables.
- server 104 is connected to network 102 along with storage unit 106 .
- clients 108 , 110 , and 112 are connected to network 102 .
- Clients 108 , 110 , and 112 may be, for example, personal computers or network computers.
- server 104 provides data, such as boot files, operating system images, and applications to clients 108 - 112 .
- Clients 108 , 110 , and 112 are clients to server 104 .
- Network data processing system 100 may include additional servers, clients, and other devices not shown.
- network data processing system 100 is the Internet with network 102 representing a worldwide collection of networks and gateways that use the Transmission Control Protocol/Internet Protocol (TCP/IP) suite of protocols to communicate with one another.
- TCP/IP Transmission Control Protocol/Internet Protocol
- At the heart of the Internet is a backbone of high-speed data communication lines between major nodes or host computers, consisting of thousands of commercial, government, educational, and other computer systems that route data and messages.
- network data processing system 100 also may be implemented as a number of different types of networks, such as for example, an intranet, a local area network (LAN), or a wide area network (WAN).
- FIG. 1 is intended as an example, and not as an architectural limitation for the present invention.
- Data processing system 200 may be a symmetric multiprocessor (SMP) system including a plurality of processors 202 and 204 connected to system bus 206 . Alternatively, a single processor system may be employed. Also connected to system bus 206 is memory controller/cache 208 , which provides an interface to local memory 209 . I/O Bus Bridge 210 is connected to system bus 206 and provides an interface to I/O bus 212 . Memory controller/cache 208 and I/O Bus Bridge 210 may be integrated as depicted.
- SMP symmetric multiprocessor
- Peripheral component interconnect (PCI) bus bridge 214 connected to I/O bus 212 provides an interface to PCI local bus 216 .
- PCI Peripheral component interconnect
- a number of modems may be connected to PCI local bus 216 .
- Typical PCI bus implementations will support four PCI expansion slots or add-in connectors.
- Communications links to clients 108 - 112 in FIG. 1 may be provided through modem 218 and network adapter 220 connected to PCI local bus 216 through add-in connectors.
- Additional PCI bus bridges 222 and 224 provide interfaces for additional PCI local buses 226 and 228 , from which additional modems or network adapters may be supported. In this manner, data processing system 200 allows connections to multiple network computers.
- Memory-mapped graphics adapter 230 and hard disk 232 may also be connected to I/O bus 212 as depicted, either directly or indirectly.
- FIG. 2 may vary.
- other peripheral devices such as optical disk drives and the like, also may be used in addition to or in place of the hardware depicted.
- the depicted example is not meant to imply architectural limitations with respect to the present invention.
- the data processing system depicted in FIG. 2 may be, for example, an IBM eServer pSeries® system, a product of International Business Machines Corporation in Armonk, N.Y., running the Advanced Interactive Executive (AIX) operating system or the LINUX operating system.
- AIX Advanced Interactive Executive
- Data processing system 300 is an example of a client computer.
- Data processing system 300 employs a peripheral component interconnect (PCI) local bus architecture.
- PCI peripheral component interconnect
- AGP Accelerated Graphics Port
- ISA Industry Standard Architecture
- Processor 302 and main memory 304 are connected to PCI local bus 306 through PCI Bridge 308 .
- PCI Bridge 308 also may include an integrated memory controller and cache memory for processor 302 . Additional connections to PCI local bus 306 may be made through direct component interconnection or through add-in boards.
- local area network (LAN) adapter 310 small computer system interface (SCSI) host bus adapter 312 , and expansion bus interface 314 are connected to PCI local bus 306 by direct component connection.
- audio adapter 316 graphics adapter 318 , and audio/video adapter 319 are connected to PCI local bus 306 by add-in boards inserted into expansion slots.
- Expansion bus interface 314 provides a connection for keyboard and mouse adapter 320 , modem 322 , and memory 324 .
- SCSI host bus adapter 312 provides a connection for hard disk drive 326 , tape drive 328 , and CD-ROM drive 330 .
- Typical PCI local bus implementations will support three or four PCI expansion slots or add-in connectors.
- An operating system runs on processor 302 and is used to coordinate and provide control of various components within data processing system 300 in FIG. 3 .
- the operating system may be a commercially available operating system, such as Windows® XP, which is available from Microsoft Corporation.
- An object-oriented programming system such as Java, may run in conjunction with the operating system and provide calls to the operating system from Java programs or applications executing on data processing system 300 . “Java” is a trademark of Sun Microsystems, Inc. Instructions for the operating system, the object-oriented programming system, and applications or programs are located on storage devices, such as hard disk drive 326 and may be loaded into main memory 304 for execution by processor 302 .
- FIG. 3 may vary depending on the implementation.
- Other internal hardware or peripheral devices such as flash read-only memory (ROM), equivalent non-volatile memory, or optical disk drives and the like, may be used in addition to or in place of the hardware depicted in FIG. 3 .
- the processes of embodiments of the present invention may be applied to a multiprocessor data processing system.
- data processing system 300 may be a stand-alone system configured to be bootable without relying on some type of network communication interfaces.
- data processing system 300 may be a personal digital assistant (PDA) device, which is configured with ROM and/or flash ROM in order to provide non-volatile memory for storing operating system files and/or user-generated data.
- PDA personal digital assistant
- data processing system 300 also may be a notebook computer or hand-held computer in addition to taking the form of a PDA.
- data processing system 300 also may be a kiosk or a Web appliance.
- Embodiments of the present invention provide a first mechanism for enhancing software catalog manageability.
- the first mechanism includes a software model that separates metadata of a definition of software from binaries of the software.
- embodiments of the present invention provide a second mechanism for abstracting configuration and settings of the software using a hierarchical software resource template.
- the present invention provides a third mechanism for comparing software resources or patches installed on a target system with software resources defined in a server template or patches that should be applied to determine a difference and presenting the difference to a user.
- data center 400 includes resources, such as, customer 402 , server 404 , Virtual Local Area Network (VLAN) 406 , subnet 408 , router 410 , switch 412 , software products 416 , load balancer 418 , and data container 420 .
- resources such as, customer 402 , server 404 , Virtual Local Area Network (VLAN) 406 , subnet 408 , router 410 , switch 412 , software products 416 , load balancer 418 , and data container 420 .
- VLAN Virtual Local Area Network
- Customer 402 may be, for example, a client or an administrator who uses a data processing system, such as data processing system 300 in FIG. 3 .
- Server 404 may be implemented as a data processing system, such as data processing system 200 in FIG. 2 .
- Server 404 may also be implemented as an application server, which hosts Web services, or other types of servers.
- Router 410 and switch 412 facilitate communications between different devices.
- VLAN 406 is a network of computers that behave as if they are connected to the same wire even though they may actually be physically located on different segments of a local area network.
- Subnet 408 is a portion of a network, which may be a physically independent network segment and shares a network address with other portions of the network.
- Software products 416 are applications that may be deployed to a client or a server. Load balancer 418 spreads traffic among multiple systems such that no single system is overwhelmed. Load balancer 418 is normally implemented as software running on a data processing system.
- Data container 420 may be a database, such as DB2® Universal Database, a product available from International Business Machines Corporation.
- Data center 400 is presented for purposes of illustrating an embodiment of the present invention.
- Other resources such as, for example, a cluster of servers and switch ports, may also be included in data center 400 .
- the mechanism of an embodiment of the present invention enhances manageability of software catalog that comprises software products, such as software products 416 .
- the mechanism of an embodiment of the present invention abstracts configuration settings of these software products.
- the mechanism of an embodiment of the present invention provides management of desired state of machines, including, but limited to servers, such as server 404 , and clusters.
- processor 302 may be performed by processor 302 using computer implemented instructions, which may be located in a memory such as, for example, main memory 304 , memory 324 , or in one or more peripheral devices 326 and 330 .
- the present invention enhances manageability of a software catalog by providing a first mechanism that decouples information about the software from the binaries.
- the information about software is known as metadata.
- the metadata describes what functions the software performs and what attributes are used to install the software.
- the binaries are actual software modules that are installed.
- a specific metadata may be defined for the software while relaxing the installation requirements. This makes the software conform to strict metadata.
- the metadata of the software may be generic while installation level details are more specific to a locale. In this way, separation of concerns may be achieved when populating the software catalog with different software products.
- FIG. 5 a diagram illustrating an exemplary software model used to separate metadata from the binaries is depicted in accordance with an illustrative embodiment of the present invention.
- software catalog 506 comprises a number of software modules 502 that represent definitions of software.
- Software module 502 captures relevant metadata, including prerequisites expressed through requirements, and exposed functionality expressed through capabilities. Software module 502 also is a placeholder for multiple abstract configuration structures that can be used at installation or configuration time. Usually, the metadata of software module 502 is predefined by a designer who created the software. Software module 502 is accessible to consumer 504 via software catalog 506 .
- each installation mechanism 508 finds a best matched binary, known as software installable 512 , for installation on a target machine.
- Software installable 512 defines a specific version of binaries for installation. The process of finding a best matched binary is as follows:
- the user When installing a software product defined in software catalog 506 , the user selects the target machines and configuration structures to be used for installation.
- the data center automation system validates the installation requirements as defined in metadata of software module 502 and determines whether software module 502 can be deployed. For example, a target machine may be able to accommodate only a zip format but not Microsoft Software Installer (MSI) format.
- MSI Microsoft Software Installer
- the data center automation system checks the target machine against the metadata to determine if the target machine can satisfy the requirement, in this case, a software module that is in a zip format.
- the data center automation system identifies best matched software installable 512 or binaries for carrying out the installation.
- the system identifies a best matched software installable by traversing the installation packages based on priority 510 .
- the installation packages may reside in file repository 514 . If the installation prerequisites as defined in metadata of software installable 512 are satisfied by the target machine or if the software is already installed, a match is found. Best matched software installable 512 or binaries is then invoked to carry out the installation. Thus, for the above example, a zipped version of the binaries is used for installation.
- the mechanism of the present invention provides greater flexibility when setting up the software catalog. While the metadata deals with what software can be used, the installation mechanisms and software installables define how the software can be installed. In this way, users may group software elements and installation structures closer to the way software deployment is performed in their environment.
- a generic metadata of software definition is used, the result of the best matched binaries is more or less the same, since software elements inside the binaries are interchangeable.
- a generic software definition is defined for an Apache Jakarta project Tomcat software module.
- the resulting best matched binaries may be one of a zip format, a MSI format, an exe format, and a tar format. While these binaries formats vary, the content of the binaries themselves remains essentially the same.
- patch entries in the software catalog may be reduced to a single entry for the patch, which offers multiple installation mechanisms for it.
- patch entries that are grouped for different OS platforms and languages may include en_US for XP, en_US for Win2K en_US for Windows® 2003, fr_FR for XP, and fr_FR for Win2k.
- a single patch entry may be offered in the software catalog that includes multiple installable mechanisms for each of these combinations, such that when installation time arrives, the appropriate installable mechanism is chosen automatically based on the prerequisites defined at the installable level.
- a software installation may be realized by using a setup.exe installable, a solution install package, or a third party distribution application.
- metadata in software modules includes complex configurations of software that are often represented in response files.
- Response files are not only limiting in its flexibility for change.
- Response files also fail to illustrate dependencies between configurations and fail to capture everything the software requires without post-installation adjustments. Therefore, the present invention provides a second mechanism that abstract complex software configuration to a desired resulting structure of a software installation.
- the second mechanism of the present invention provides a hierarchy of software resources templates, which captures all necessary deployment options and configuration parameters for installation.
- the hierarchy of software resource templates is later consumed by a user-defined installation or configuration workflow during actual deployment.
- the hierarchy of the software resource templates deals with the structure of the resulting software resources, and the installation of the software resources, including instances of the software resources.
- the software resource templates of the present invention capture settings and parameters necessary to create a software resource.
- software resources include a DB2® installation, a DB2® instance, a WebSphere® installation, and a WebSphere instance.
- DB2 and WebSphere are products that are available from International Business Machines Corporation.
- the software resource templates also specify the type and device model of the resource once it is created, such that the appropriate behavior can be tied to the deployed software in the form of workflow implementations for the predefined logical device operations.
- Logical device operations are operations that interact directly with data center devices to perform functions.
- FIG. 6A a diagram illustrating an exemplary software resource template is depicted in accordance with an illustrative embodiment of the present invention.
- FIG. 6A settings and parameters needed to create WebSphere software module 602 are described in software resource template 600 in FIG. 6B .
- FIG. 6B a diagram illustrating an exemplary software resource template in continuation of FIG. 6A is depicted in accordance with an illustrative embodiment of the present invention.
- a number of software resource templates are nested.
- IBM HTTP server 606 , server 608 , assembly and deployment tools 610 and embedded messaging 612 are nested within WAS-Standard 604.
- parameters are defined in the form a name-value pair. For example, for WAS-Standard 604, a parameter with a name of “wasBean.installLocation” 614 and a value of “C: ⁇ WebSphere51 ⁇ AppServer” 616 is defined.
- the parameters within each software resource template may be a simple or derived parameter.
- a simple parameter is a parameter that holds its own value.
- a derived parameter is a parameter that composes of one or more tokens with at least one token derived from another parameter.
- the parameter from which the token is derived may be from the same software resource template or another software resource template.
- derived parameters may be used to specify configuration settings for software elements that compose a distributed application.
- settings of one module may depend on another.
- the data source has to be defined for a war module, which depends on the database name, address and port of the database module deployment.
- software resource template 600 in FIG. 6B may also be used to specify features and options of the software.
- Features are pieces of functionalities selectable by a user that may be opted out or in when the software is installed.
- Options are pieces of functionalities mutually exclusive that are selectable by the user.
- software module WebSphere 602 may have multiple software resource templates. Having multiple software resource templates allows for flexibility when automating deployments, since the same software can be installed or configured in various ways in the data center. For example, a test installation is different from a production installation of the same software. At installation time, the user is presented with the preset alternatives for selection of an installation and the desired underlying structure is offered for refinement.
- a series of derived templates may point back to their source.
- the mechanism of the present invention creates a clone resource template structure that is not affected by the changes rather than modifying the original values.
- the cloning sequence takes care of change versioning.
- other users of the same template may not be affected by changes that are made for a single deployment or configuration, which uses the same set of configuration elements. For example, for a DB2 application, if the resource template of one instance of the application is changed, a new instance of the application is added with the customization and passed to the installer, such that the user can configure the new instance of the application before the install.
- the software resource templates such as software resource templates shown in FIGS. 6A and B, are grouped in a hierarchy parallel to the resulting software. In this way, configuration parameter structures may be handled more easily than response files.
- the software resource templates serve as blueprints that show how the end result of the software looks like, where the parameters are placed, and what are actually installed in the target machine.
- DB2 software module 700 includes a hierarchical DB2 installation software resource template 702 that includes two instances of software resource templates: DB2 instance 704 and DB2 instance 706 .
- DB2 installation software installable 710 corresponding to DB2 installation software resource template 702 is realized in server X 708 .
- DB2 instance Gigi 712 corresponding to DB2 instance 704 is realized in server X 710 and DB2 instance Gigica 714 corresponding to DB2 instance 706 is realized in server X 710 .
- the structure in server X 710 is unfilled until the user is presented with the structure during deployment of the software. At that time, the user may fill in the missing values to complete the installation.
- the limitation of post-installation adjustments required by response files is eliminated and that installation information that cannot be predefined may still be included at installation time.
- derived parameters within each template are also realized as dependencies of software on different machines.
- the structure in server X 708 may be consumed by user define workflow implementations which take the templates and retrieve the best matched binaries to start configuration. Software with corresponding structure may then be created according to the template structure.
- the present invention provides a third mechanism that automatically manages desired state of a machine once the software is deployed.
- the third mechanism is capable of making two comparisons.
- the first comparison compares software resources that are installed and configured on a machine with a software specification that is captured using a server template.
- the second comparison compares the patch installed on a machine with approved or available patches that should have been applied to the machine at a given time.
- the first comparison is made against a predefine set of items, while the second comparison is made against patches that are available and approved at the time of the analysis.
- a server template is a fixed target.
- the server template specifies software modules that are part of a default installation and it is used as reference.
- the third mechanism of the present invention first analyzes software resources that are deployed on a machine and identifies modules from which the software resources are installed. The mechanism then compares the modules that should be installed as specified in the server template with ones that are actually installed to determine a delta. This delta, which represents the difference, is presented to the user for analysis.
- the third mechanism of the present invention determines if a given machine is up to date with the most recent patch updates.
- the second comparison is made by first identifying patches that could be applied on the machine for all installed software and then by checking which patches are not already installed on the machine. This analysis takes into account all approved patches from the list of available patches. The available patches may be obtained from the software catalog. In this way, every time a new patch is defined and marked as approved, the mechanism determines if it needs to be applied to the machine automatically without the need for the administrators to examine individual machines.
- the third mechanism of the present invention performs its analysis using data that is stored in a data center model rather than data extracted from individual machines.
- the data center model comprises information about what software is installed in the data center devices.
- the use of the data center model instead of software on individual machines allows analysis to be performed uniformly for all types of systems without any proprietary technology.
- the third mechanism of the present invention provides a centralized patch compliance assessment and desired state management in a data center that comprises heterogeneous devices.
- the patch application analysis may leverage the software model provided by the first mechanism of the present invention. For example, patches that are applicable to the software may be defined in the metadata of the software definition. If a new patch is defined in the software catalog, the software definition of the target machine may be dynamically recalculated to include the new patch.
- FIG. 8 a flowchart of an exemplary process for leveraging a server template to manage a desired state is depicted in accordance with an illustrative embodiment of the present invention.
- the process begins when the mechanism of an embodiment of the present invention analyzes software resources that are deployed on a machine (step 800 ).
- the mechanism of an embodiment of the present invention identifies modules from which the software resources are installed (step 802 ).
- the mechanism of an embodiment of the present invention then makes a comparison between modules that should have been installed as defined in the server template and modules that are actually installed on the machine (step 804 ).
- the mechanism then calculates a delta representing the difference of the comparison (step 806 ) and presents the delta to the user for analysis (step 808 ).
- the process terminates thereafter.
- FIG. 9 a flowchart of an exemplary process for using software resources in a data center model to assess patch compliance is depicted in accordance with an illustrative embodiment of the present invention.
- the process begins when the mechanism of an embodiment of the present invention identifies patches that are available and approved (step 900 ).
- the patches available are obtained from a software catalog, because whenever a new patch is defined, the new patch is marked in the software catalog for the mechanism to determine whether it needs to be applied to the machines.
- the mechanism of an embodiment of the present invention analyzes the list of available and approved patches and identifies what patches should be applied to each piece of software installed on the target machine (step 902 ).
- the mechanism identifies patches that are already installed on the machine (step 904 ). This step may be performed by using data from the data center model. The mechanism then makes a comparison between patches that are available and should be applied to the target machine from step 902 and patches that are already installed in the machines from step 904 (step 906 ) and calculates a delta representing the difference of the comparison (step 908 ). Finally, the mechanism presents the delta to the user for analysis (step 910 ) with the process terminating thereafter.
- embodiments of the present invention enhance manageability of the software catalog by providing a software model that separates metadata of software from its binaries.
- the embodiments of the present invention also provide a mechanism that abstracts software configuration for automation.
- the embodiments of the present invention provide a mechanism of desired state management and patch compliance assessment.
- different specificity may be defined at different levels of the software, such that functional requirements are validated against the target machine for viability.
- best matched software installable may be identified by different installation mechanisms based on satisfaction of installation requirements.
- response files are no longer needed for specifying deployment options and configuration parameters.
- dependencies between parameters, parameters that could not be previously pre-defined, and a more flexible structure may be provided at installation time.
- differences between installed modules or patches and desired modules or patches may be identified and presented to the user for analysis.
Abstract
Description
Claims (21)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/123,304 US7743373B2 (en) | 2005-05-06 | 2005-05-06 | Method and apparatus for managing software catalog and providing configuration for installation |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/123,304 US7743373B2 (en) | 2005-05-06 | 2005-05-06 | Method and apparatus for managing software catalog and providing configuration for installation |
Publications (2)
Publication Number | Publication Date |
---|---|
US20060253849A1 US20060253849A1 (en) | 2006-11-09 |
US7743373B2 true US7743373B2 (en) | 2010-06-22 |
Family
ID=37395421
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/123,304 Active 2029-04-08 US7743373B2 (en) | 2005-05-06 | 2005-05-06 | Method and apparatus for managing software catalog and providing configuration for installation |
Country Status (1)
Country | Link |
---|---|
US (1) | US7743373B2 (en) |
Cited By (26)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040199572A1 (en) * | 2003-03-06 | 2004-10-07 | Hunt Galen C. | Architecture for distributed computing system and automated design, deployment, and management of distributed applications |
US20050108702A1 (en) * | 2003-11-14 | 2005-05-19 | International Business Machines Corporation | On-demand software module deployment |
US20060235962A1 (en) * | 2005-04-15 | 2006-10-19 | Microsoft Corporation | Model-based system monitoring |
US20080196021A1 (en) * | 2007-02-08 | 2008-08-14 | Microsoft Corporation | Accessible Limited Distribution Release Software Change Catalog |
US20080196020A1 (en) * | 2007-02-08 | 2008-08-14 | Microsoft Corporation | Network Service for a Software Change Catalog |
US20100223609A1 (en) * | 2009-02-27 | 2010-09-02 | Dehaan Michael Paul | Systems and methods for automatic discovery of network software relationships |
US20100287271A1 (en) * | 2000-10-24 | 2010-11-11 | Microsoft Corporation | System and Method for Restricting Data Transfers and Managing Software Components of Distributed Computers |
US20100313031A1 (en) * | 2009-06-04 | 2010-12-09 | Bertrand Jaslet | Watermarking during system deployment |
US20100325181A1 (en) * | 2009-06-19 | 2010-12-23 | Aptare, Inc. | Catalog that stores file system metadata in an optimized manner |
US7886041B2 (en) | 2003-03-06 | 2011-02-08 | Microsoft Corporation | Design time validation of systems |
US7941309B2 (en) | 2005-11-02 | 2011-05-10 | Microsoft Corporation | Modeling IT operations/policies |
US20110145790A1 (en) * | 2009-12-15 | 2011-06-16 | International Business Machines Corporation | Deployment and deployment planning as a service |
US8266616B1 (en) * | 2006-05-11 | 2012-09-11 | Hewlett-Packard Development Company, L.P. | Computer system provisioning using templates |
US20130013614A1 (en) * | 2011-07-07 | 2013-01-10 | 1E Limited | Identifying Software |
US20130036208A1 (en) * | 2011-08-05 | 2013-02-07 | Oracle International Corporation | Systems and methods for automatic hardware provisioning based on application characteristics |
US20130125109A1 (en) * | 2006-06-26 | 2013-05-16 | Research In Motion Limited | Method and system for generating a reverse binary patch |
US8489616B2 (en) * | 2011-07-07 | 2013-07-16 | 1E Limited | Identifying software |
US20130198719A1 (en) * | 2012-01-31 | 2013-08-01 | Red Hat Inc. | Automated deployment of an application in a computing platform |
US20130326481A1 (en) * | 2012-06-05 | 2013-12-05 | Shakthi Kannan | System and method for tracking software package dependencies using a graph model |
US8918780B2 (en) | 2013-03-14 | 2014-12-23 | International Business Machines Corporation | Automatic quality assurance for software installers |
US9203786B2 (en) | 2006-06-16 | 2015-12-01 | Microsoft Technology Licensing, Llc | Data synchronization and sharing relationships |
US9235387B1 (en) * | 2013-03-05 | 2016-01-12 | Ca, Inc. | Methods, systems, and computer program products for evaluating the compatibility of a computer program with target data processing environments based on associations between source code instructions and required data processing facilities |
US9262238B2 (en) | 2012-01-31 | 2016-02-16 | Red Hat, Inc. | Connection management for an application in a computing platform |
US9665356B2 (en) | 2012-01-31 | 2017-05-30 | Red Hat, Inc. | Configuration of an application in a computing platform |
US10540159B2 (en) | 2005-06-29 | 2020-01-21 | Microsoft Technology Licensing, Llc | Model-based virtual system provisioning |
US10936305B2 (en) | 2017-11-13 | 2021-03-02 | Sap Se | Configuration guide editor to generate interactive configuration guides and automation content |
Families Citing this family (26)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7779039B2 (en) | 2004-04-02 | 2010-08-17 | Salesforce.Com, Inc. | Custom entities and fields in a multi-tenant database system |
JP5395434B2 (en) | 2005-09-09 | 2014-01-22 | セールスフォース ドット コム インコーポレイティッド | System and method for exporting, publishing, browsing and installing on-demand applications in a multi-tenant database environment |
US7565471B2 (en) * | 2005-09-16 | 2009-07-21 | Emulex Design & Manufacturing Corporation | Message signaled interrupt extended (MSI-X) auto clear and failsafe lock |
US9489187B2 (en) * | 2005-11-07 | 2016-11-08 | Yahoo, Inc. | Adaptive deployment of applications for mobile devices |
US8539496B1 (en) * | 2005-12-12 | 2013-09-17 | At&T Intellectual Property Ii, L.P. | Method and apparatus for configuring network systems implementing diverse platforms to perform business tasks |
EP1818813A1 (en) * | 2006-02-02 | 2007-08-15 | Research In Motion Limited | System and method and apparatus for using UML tools for defining web service bound component applications |
US7853669B2 (en) | 2007-05-04 | 2010-12-14 | Microsoft Corporation | Mesh-managing data across a distributed set of devices |
US8464239B2 (en) | 2007-06-11 | 2013-06-11 | Red Hat, Inc. | Real-time installation and/or configuration assistant |
US8656384B2 (en) * | 2007-06-22 | 2014-02-18 | Red Hat, Inc. | Standardized software application configuration |
US8370829B2 (en) * | 2007-08-31 | 2013-02-05 | Red Hat, Inc. | Post-install configuration for applications |
KR101484680B1 (en) * | 2007-10-04 | 2015-01-21 | 삼성전자 주식회사 | System and Method for Software Product Management with a Component Model |
US8612966B2 (en) * | 2007-11-29 | 2013-12-17 | Red Hat, Inc. | Method and system for preparing software offerings having software application code and post-install configuration information |
US8191075B2 (en) * | 2008-03-06 | 2012-05-29 | Microsoft Corporation | State management of operating system and applications |
US8484174B2 (en) * | 2008-03-20 | 2013-07-09 | Microsoft Corporation | Computing environment representation |
US9298747B2 (en) | 2008-03-20 | 2016-03-29 | Microsoft Technology Licensing, Llc | Deployable, consistent, and extensible computing environment platform |
US8572033B2 (en) | 2008-03-20 | 2013-10-29 | Microsoft Corporation | Computing environment configuration |
US9753712B2 (en) | 2008-03-20 | 2017-09-05 | Microsoft Technology Licensing, Llc | Application management within deployable object hierarchy |
US20090248737A1 (en) * | 2008-03-27 | 2009-10-01 | Microsoft Corporation | Computing environment representation |
US8443357B2 (en) * | 2008-10-13 | 2013-05-14 | Oracle International Corporation | Patching of multi-level data containers storing portions of pre-installed software |
US8495621B2 (en) * | 2009-06-15 | 2013-07-23 | Microsoft Corporation | Catalog-based software component management |
US20150220308A1 (en) * | 2014-01-31 | 2015-08-06 | Dell Products L.P. | Model-based development |
US10146569B2 (en) * | 2016-03-02 | 2018-12-04 | International Business Machines Corporation | Template based software scans |
US20180088926A1 (en) * | 2016-09-27 | 2018-03-29 | Ca, Inc. | Container image management using layer deltas |
US10558450B2 (en) * | 2017-02-07 | 2020-02-11 | Wyse Technology L.L.C. | Mechanism for customizing multiple computing devices |
US11256664B1 (en) | 2017-05-05 | 2022-02-22 | Fannie Mae | Systems and methods for memory management in source agnostic content staging |
US11687063B2 (en) * | 2018-07-24 | 2023-06-27 | Siemens Aktiengesellschaft | Semantics-based internet of things device data processing-related application installation method and apparatus |
Citations (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6272674B1 (en) * | 1998-12-14 | 2001-08-07 | Nortel Networks Limited | Method and apparatus for loading a Java application program |
US20020112232A1 (en) | 2001-02-15 | 2002-08-15 | Ream James A. | System and process for building host computers |
US6564377B1 (en) * | 1999-07-26 | 2003-05-13 | Microsoft Corporation | Self-describing components within a software catalog |
US6678888B1 (en) * | 1999-08-26 | 2004-01-13 | Hitachi, Ltd. | Method and system for software distribution |
US6681323B1 (en) * | 1999-11-29 | 2004-01-20 | Toshiba America Information Systems, Inc. | Method and system for automatically installing an initial software configuration including an operating system module from a library containing at least two operating system modules based on retrieved computer identification data |
US6862581B1 (en) * | 2002-12-19 | 2005-03-01 | Networks Associates Technology, Inc. | Patch distribution system, method and computer program product |
US20050050315A1 (en) | 2003-08-29 | 2005-03-03 | Microsoft Corporation | Selectively authorizing software functionality after installation of the software |
US6957422B2 (en) * | 1998-10-02 | 2005-10-18 | Microsoft Corporation | Dynamic classification of sections of software |
US6964034B1 (en) * | 2000-04-20 | 2005-11-08 | International Business Machines Corporation | Application development server and a mechanism for providing different views into the same constructs within a strongly encapsulated environment |
US6999956B2 (en) * | 2000-11-16 | 2006-02-14 | Ward Mullins | Dynamic object-driven database manipulation and mapping system |
US7149734B2 (en) * | 2001-07-06 | 2006-12-12 | Logic Library, Inc. | Managing reusable software assets |
US7191429B2 (en) * | 2001-09-28 | 2007-03-13 | Manyeta Informatique Inc. | System and method for managing architectural layers within a software model |
US7318216B2 (en) * | 2003-09-24 | 2008-01-08 | Tablecode Software Corporation | Software application development environment facilitating development of a software application |
US7376945B1 (en) * | 2003-12-02 | 2008-05-20 | Cisco Technology, Inc. | Software change modeling for network devices |
US7418700B2 (en) * | 2001-01-29 | 2008-08-26 | Microsoft Corporation | System and method to facilitate installation and/or removal of components |
US7430610B2 (en) * | 2000-09-01 | 2008-09-30 | Opyo, Inc. | System and method for adjusting the distribution of an asset over a multi-tiered network |
US7496910B2 (en) * | 2004-05-21 | 2009-02-24 | Desktopstandard Corporation | System for policy-based management of software updates |
US7505995B2 (en) * | 2006-06-30 | 2009-03-17 | Microsoft Corporation | Object-relational model based user interfaces |
US7536686B2 (en) * | 2000-09-08 | 2009-05-19 | Oracle International Corporation | Techniques for automatically installing and configuring database applications |
US7546594B2 (en) * | 2003-12-15 | 2009-06-09 | Microsoft Corporation | System and method for updating installation components using an installation component delta patch in a networked environment |
US7568195B2 (en) * | 2003-12-16 | 2009-07-28 | Microsoft Corporation | Determining a maximal set of dependent software updates valid for installation |
US7634770B2 (en) * | 2003-05-19 | 2009-12-15 | Hewlett-Packard Development Company, L.P. | Kernel module interface dependencies |
US7634771B2 (en) * | 2005-04-29 | 2009-12-15 | Sap (Ag) | Object generation in packages |
-
2005
- 2005-05-06 US US11/123,304 patent/US7743373B2/en active Active
Patent Citations (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6957422B2 (en) * | 1998-10-02 | 2005-10-18 | Microsoft Corporation | Dynamic classification of sections of software |
US6272674B1 (en) * | 1998-12-14 | 2001-08-07 | Nortel Networks Limited | Method and apparatus for loading a Java application program |
US6564377B1 (en) * | 1999-07-26 | 2003-05-13 | Microsoft Corporation | Self-describing components within a software catalog |
US6678888B1 (en) * | 1999-08-26 | 2004-01-13 | Hitachi, Ltd. | Method and system for software distribution |
US6681323B1 (en) * | 1999-11-29 | 2004-01-20 | Toshiba America Information Systems, Inc. | Method and system for automatically installing an initial software configuration including an operating system module from a library containing at least two operating system modules based on retrieved computer identification data |
US6964034B1 (en) * | 2000-04-20 | 2005-11-08 | International Business Machines Corporation | Application development server and a mechanism for providing different views into the same constructs within a strongly encapsulated environment |
US7430610B2 (en) * | 2000-09-01 | 2008-09-30 | Opyo, Inc. | System and method for adjusting the distribution of an asset over a multi-tiered network |
US7536686B2 (en) * | 2000-09-08 | 2009-05-19 | Oracle International Corporation | Techniques for automatically installing and configuring database applications |
US6999956B2 (en) * | 2000-11-16 | 2006-02-14 | Ward Mullins | Dynamic object-driven database manipulation and mapping system |
US7418700B2 (en) * | 2001-01-29 | 2008-08-26 | Microsoft Corporation | System and method to facilitate installation and/or removal of components |
US20020112232A1 (en) | 2001-02-15 | 2002-08-15 | Ream James A. | System and process for building host computers |
US7149734B2 (en) * | 2001-07-06 | 2006-12-12 | Logic Library, Inc. | Managing reusable software assets |
US7191429B2 (en) * | 2001-09-28 | 2007-03-13 | Manyeta Informatique Inc. | System and method for managing architectural layers within a software model |
US6862581B1 (en) * | 2002-12-19 | 2005-03-01 | Networks Associates Technology, Inc. | Patch distribution system, method and computer program product |
US7634770B2 (en) * | 2003-05-19 | 2009-12-15 | Hewlett-Packard Development Company, L.P. | Kernel module interface dependencies |
US20050050315A1 (en) | 2003-08-29 | 2005-03-03 | Microsoft Corporation | Selectively authorizing software functionality after installation of the software |
US7318216B2 (en) * | 2003-09-24 | 2008-01-08 | Tablecode Software Corporation | Software application development environment facilitating development of a software application |
US7376945B1 (en) * | 2003-12-02 | 2008-05-20 | Cisco Technology, Inc. | Software change modeling for network devices |
US7546594B2 (en) * | 2003-12-15 | 2009-06-09 | Microsoft Corporation | System and method for updating installation components using an installation component delta patch in a networked environment |
US7568195B2 (en) * | 2003-12-16 | 2009-07-28 | Microsoft Corporation | Determining a maximal set of dependent software updates valid for installation |
US7496910B2 (en) * | 2004-05-21 | 2009-02-24 | Desktopstandard Corporation | System for policy-based management of software updates |
US7634771B2 (en) * | 2005-04-29 | 2009-12-15 | Sap (Ag) | Object generation in packages |
US7505995B2 (en) * | 2006-06-30 | 2009-03-17 | Microsoft Corporation | Object-relational model based user interfaces |
Non-Patent Citations (4)
Title |
---|
Junkai et al, "An approach for sensitive file protoction", IEEE, pp. 716-718, 2009. * |
Wang et al, "Jato: A compact binary file format in Java class", IEEE, pp. 467-474, 2001. * |
Xu et al, "Metadata driven memory optimizations in dynamic binary translator", ACM VEE, pp. 148-157, 2007. * |
Yardimci et al, "Mostly static program partitioning of binary executables", ACM Trans. on Prog. Lang. and System, vol. 31, No. 5, article 17, pp. 1-46, 2009. * |
Cited By (45)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100287271A1 (en) * | 2000-10-24 | 2010-11-11 | Microsoft Corporation | System and Method for Restricting Data Transfers and Managing Software Components of Distributed Computers |
US7886041B2 (en) | 2003-03-06 | 2011-02-08 | Microsoft Corporation | Design time validation of systems |
US20040199572A1 (en) * | 2003-03-06 | 2004-10-07 | Hunt Galen C. | Architecture for distributed computing system and automated design, deployment, and management of distributed applications |
US8122106B2 (en) | 2003-03-06 | 2012-02-21 | Microsoft Corporation | Integrating design, deployment, and management phases for systems |
US7890951B2 (en) * | 2003-03-06 | 2011-02-15 | Microsoft Corporation | Model-based provisioning of test environments |
US7890543B2 (en) | 2003-03-06 | 2011-02-15 | Microsoft Corporation | Architecture for distributed computing system and automated design, deployment, and management of distributed applications |
US20050108702A1 (en) * | 2003-11-14 | 2005-05-19 | International Business Machines Corporation | On-demand software module deployment |
US8225307B2 (en) * | 2003-11-14 | 2012-07-17 | International Business Machines Corporation | On-demand software module deployment |
US20060235962A1 (en) * | 2005-04-15 | 2006-10-19 | Microsoft Corporation | Model-based system monitoring |
US8489728B2 (en) | 2005-04-15 | 2013-07-16 | Microsoft Corporation | Model-based system monitoring |
US10540159B2 (en) | 2005-06-29 | 2020-01-21 | Microsoft Technology Licensing, Llc | Model-based virtual system provisioning |
US7941309B2 (en) | 2005-11-02 | 2011-05-10 | Microsoft Corporation | Modeling IT operations/policies |
US8266616B1 (en) * | 2006-05-11 | 2012-09-11 | Hewlett-Packard Development Company, L.P. | Computer system provisioning using templates |
US9203786B2 (en) | 2006-06-16 | 2015-12-01 | Microsoft Technology Licensing, Llc | Data synchronization and sharing relationships |
US20130125109A1 (en) * | 2006-06-26 | 2013-05-16 | Research In Motion Limited | Method and system for generating a reverse binary patch |
US8943492B2 (en) * | 2006-06-26 | 2015-01-27 | Blackberry Limited | Method and system for generating a reverse binary patch |
US8819668B2 (en) | 2007-02-08 | 2014-08-26 | Microsoft Corporation | Accessible limited distribution release software change catalog |
US8196134B2 (en) * | 2007-02-08 | 2012-06-05 | Microsoft Corporation | Network service for a software change catalog |
US20080196021A1 (en) * | 2007-02-08 | 2008-08-14 | Microsoft Corporation | Accessible Limited Distribution Release Software Change Catalog |
US20080196020A1 (en) * | 2007-02-08 | 2008-08-14 | Microsoft Corporation | Network Service for a Software Change Catalog |
US8990368B2 (en) * | 2009-02-27 | 2015-03-24 | Red Hat, Inc. | Discovery of network software relationships |
US20100223609A1 (en) * | 2009-02-27 | 2010-09-02 | Dehaan Michael Paul | Systems and methods for automatic discovery of network software relationships |
US20100313031A1 (en) * | 2009-06-04 | 2010-12-09 | Bertrand Jaslet | Watermarking during system deployment |
US8402071B2 (en) * | 2009-06-19 | 2013-03-19 | Aptare, Inc. | Catalog that stores file system metadata in an optimized manner |
US20100325181A1 (en) * | 2009-06-19 | 2010-12-23 | Aptare, Inc. | Catalog that stores file system metadata in an optimized manner |
US9317267B2 (en) * | 2009-12-15 | 2016-04-19 | International Business Machines Corporation | Deployment and deployment planning as a service |
US20110145790A1 (en) * | 2009-12-15 | 2011-06-16 | International Business Machines Corporation | Deployment and deployment planning as a service |
US9710363B2 (en) | 2009-12-15 | 2017-07-18 | International Business Machines Corporation | Deployment and deployment planning as a service |
US8463792B2 (en) * | 2011-07-07 | 2013-06-11 | 1E Limited | Identifying software |
US20130013614A1 (en) * | 2011-07-07 | 2013-01-10 | 1E Limited | Identifying Software |
US8489616B2 (en) * | 2011-07-07 | 2013-07-16 | 1E Limited | Identifying software |
CN103703445B (en) * | 2011-08-05 | 2017-04-05 | 甲骨文国际公司 | For the system and method for the automatic hardware supply based on application characteristic |
US20130036208A1 (en) * | 2011-08-05 | 2013-02-07 | Oracle International Corporation | Systems and methods for automatic hardware provisioning based on application characteristics |
CN103703445A (en) * | 2011-08-05 | 2014-04-02 | 甲骨文国际公司 | Systems and methods for automatic hardware provisioning based on application characteristics |
US9639402B2 (en) * | 2011-08-05 | 2017-05-02 | Oracle International Corporation | Systems and methods for automatic hardware provisioning based on application characteristics |
US9262238B2 (en) | 2012-01-31 | 2016-02-16 | Red Hat, Inc. | Connection management for an application in a computing platform |
US9665356B2 (en) | 2012-01-31 | 2017-05-30 | Red Hat, Inc. | Configuration of an application in a computing platform |
US9170797B2 (en) * | 2012-01-31 | 2015-10-27 | Red Hat, Inc. | Automated deployment of an application in a computing platform |
US20130198719A1 (en) * | 2012-01-31 | 2013-08-01 | Red Hat Inc. | Automated deployment of an application in a computing platform |
US20130326481A1 (en) * | 2012-06-05 | 2013-12-05 | Shakthi Kannan | System and method for tracking software package dependencies using a graph model |
US9235410B2 (en) * | 2012-06-05 | 2016-01-12 | Red Hat, Inc. | Tracking software package dependencies using a graph model |
US9235387B1 (en) * | 2013-03-05 | 2016-01-12 | Ca, Inc. | Methods, systems, and computer program products for evaluating the compatibility of a computer program with target data processing environments based on associations between source code instructions and required data processing facilities |
US9256417B2 (en) | 2013-03-14 | 2016-02-09 | International Business Machines Corporation | Automatic quality assurance for software installers |
US8918780B2 (en) | 2013-03-14 | 2014-12-23 | International Business Machines Corporation | Automatic quality assurance for software installers |
US10936305B2 (en) | 2017-11-13 | 2021-03-02 | Sap Se | Configuration guide editor to generate interactive configuration guides and automation content |
Also Published As
Publication number | Publication date |
---|---|
US20060253849A1 (en) | 2006-11-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7743373B2 (en) | Method and apparatus for managing software catalog and providing configuration for installation | |
US10430204B2 (en) | System and method for cloud provisioning and application deployment | |
US9710259B2 (en) | System and method for customizing a deployment plan for a multi-tier application in a cloud infrastructure | |
US8185891B2 (en) | Methods and systems for provisioning software | |
US9645858B2 (en) | Single, logical, multi-tier application blueprint used for deployment and management of multiple physical applications in a cloud infrastructure | |
US11941452B2 (en) | System to generate a deployment plan for a cloud infrastructure according to logical, multi-tier application blueprint | |
US10031783B2 (en) | Execution of a distributed deployment plan for a multi-tier application in a cloud infrastructure | |
US8589916B2 (en) | Deploying and instantiating multiple instances of applications in automated data centers using application deployment template | |
US20150112829A1 (en) | System and method for deploying and maintaining software applications | |
US8892700B2 (en) | Collecting and altering firmware configurations of target machines in a software provisioning environment | |
US9021470B2 (en) | Software provisioning in multiple network configuration environment | |
US8782204B2 (en) | Monitoring hardware resources in a software provisioning environment | |
US20030163807A1 (en) | Weighted selection of target systems for distributed software installation | |
US20130232245A1 (en) | Automation for virtualized it environments | |
US20100058328A1 (en) | Systems and methods for differential software provisioning on virtual machines having different configurations | |
US20030037327A1 (en) | Run-time rule-based topological installation suite | |
TW200820075A (en) | Method and apparatus for on-demand composition and teardown of service infrastructure | |
US20090077090A1 (en) | Method and apparatus for specifying an order for changing an operational state of software application components | |
US20080052675A1 (en) | System and method for information collection for an adaptive software dependency model | |
WO2001009721A2 (en) | A system, method and article of manufacture for providing an interface between a first server and a second server. | |
US7752158B2 (en) | System and method for generating an adaptive software knowledge model incorporating new information with model dependency analysis | |
US20050223101A1 (en) | Computer-implemented method, system and program product for resolving prerequisites for native applications utilizing an open service gateway initiative ( OSGi) framework | |
US20240118915A1 (en) | Automated Management of Machine Images | |
US7761395B2 (en) | System and method for scalable processing of collected knowledge by creating knowledge generation nodes | |
US20210392039A1 (en) | Automated Initialization Of Bare Metal Servers |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION,NEW YO Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:AVRAM, MIRCEA;KISSA, PETER;LI, GEYU;AND OTHERS;SIGNING DATES FROM 20050505 TO 20050603;REEL/FRAME:016306/0010 Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:AVRAM, MIRCEA;KISSA, PETER;LI, GEYU;AND OTHERS;REEL/FRAME:016306/0010;SIGNING DATES FROM 20050505 TO 20050603 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: TWITTER, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTERNATIONAL BUSINESS MACHINES CORPORATION;REEL/FRAME:032075/0404 Effective date: 20131230 |
|
REMI | Maintenance fee reminder mailed | ||
FPAY | Fee payment |
Year of fee payment: 4 |
|
SULP | Surcharge for late payment | ||
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.) |
|
FEPP | Fee payment procedure |
Free format text: 7.5 YR SURCHARGE - LATE PMT W/IN 6 MO, LARGE ENTITY (ORIGINAL EVENT CODE: M1555) |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552) Year of fee payment: 8 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 12 |
|
AS | Assignment |
Owner name: MORGAN STANLEY SENIOR FUNDING, INC., MARYLAND Free format text: SECURITY INTEREST;ASSIGNOR:TWITTER, INC.;REEL/FRAME:062079/0677 Effective date: 20221027 Owner name: MORGAN STANLEY SENIOR FUNDING, INC., MARYLAND Free format text: SECURITY INTEREST;ASSIGNOR:TWITTER, INC.;REEL/FRAME:061804/0086 Effective date: 20221027 Owner name: MORGAN STANLEY SENIOR FUNDING, INC., MARYLAND Free format text: SECURITY INTEREST;ASSIGNOR:TWITTER, INC.;REEL/FRAME:061804/0001 Effective date: 20221027 |