Abstract: A system, method, computer program product are shown for automatically performing deployment activities that can handle deployments for any-sized organization, even for deployments at the enterprise level. According to some approaches, modeling is performed to generate a model of the components in the computing environment. Dependency graphs can be generated for the deployment, and used to then automatically perform the deployment.

Abstract: According to an aspect of the present invention, the dependency information of software components implementing an enterprise application, is used to minimize the down time of the components when applying patches. In an embodiment, all the software components are shut down before applying patches. The patches are then applied and the components are started in a dependency order starting from an independent component. The down time is reduced as a result. According to another aspect, the shutdown also is performed in the reverse of the dependency order. The shutdown and starting are performed using recursive logic.

Abstract: Systems, methods, and machine-readable media are disclosed for patching software based on seeded product information. In one embodiment, patching software can comprise receiving a patch deliverable that can include a software patch and information identifying a target software package. The information identifying the target software package can be read and a determination can be made as to whether the information indicates a known software package. In response to determining the information indicates a known software package, the patch can be installed. In response to determining the information does not indicate a known software package options identifying software packages for which the patch may be used can be presented to a user and a selection of one of the packages can be received. The selected software package can be seeded with the information identifying the target software package and the patch can be installed for the selected software product.

Abstract: A computing system provided according to an aspect of the present invention includes a developer system which sends a set of patches along with metadata in a package. The metadata may include hierarchical paths, with each path indicating a corresponding target (file or archive) which is to be replaced to apply the corresponding patch. A patch tool receives the package and applies the patches using the metadata. According to another aspect of the present invention, a patch tool forms a tree structure based on the hierarchical paths in the metadata. In an embodiment, the tree structure is traversed each time to perform a corresponding patching operation (e.g., backup, and replace). According to yet another aspect of the present invention, only the required archives are unarchived while applying the patches. In an embodiment, the patch tool determines the required archives based on the information in the received metadata.

Abstract: A patch tool receives multiple patches, with each patch designed to fix a corresponding subset of a set of errors in a system. Some of the patches may require that the files from older patches be removed from the system. In an embodiment of the present invention, a developer of a patch is provided the flexibility to specify that a desired file from an older patch fixing a specific error, not be removed during deployment of a new patch designed to fix the same specific error. Rolling back later to the older version of the patch may be simplified by not removing the desired file.

Abstract: In an embodiment of the present invention, a patch tool receives multiple patches, with each patch designed to fix a corresponding subset of a set of errors in a system. The patch tool determines a subset of patches, which together fix all of the set of errors, and deploys only the subset of patches in the system. The patches may be received over a period of time and the subset of patches are determined and deployed in a batch mode.

Abstract: According to an aspect of the present invention, the dependency information of software components implementing an enterprise application, is used to minimize the down time of the components when applying patches. In an embodiment, all the software components are shut down before applying patches. The patches are then applied and the components are started in a dependency order starting from an independent component. The down time is reduced as a result. According to another aspect, the shutdown also is performed in the reverse of the dependency order. The shutdown and starting are performed using recursive logic.

Abstract: A computing system provided according to an aspect of the present invention includes a developer system which sends a set of patches along with metadata in a package. The metadata may include hierarchical paths, with each path indicating a corresponding target (file or archive) which is to be replaced to apply the corresponding patch. A patch tool receives the package and applies the patches using the metadata. According to another aspect of the present invention, a patch tool forms a tree structure based on the hierarchical paths in the metadata. In an embodiment, the tree structure is traversed each time to perform a corresponding patching operation (e.g., backup, and replace). According to yet another aspect of the present invention, only the required archives are unarchived while applying the patches. In an embodiment, the patch tool determines the required archives based on the information in the received metadata.

Abstract: Systems, methods, and machine-readable media are disclosed for patching software based on seeded product information. In one embodiment, patching software can comprise receiving a patch deliverable that can include a software patch and information identifying a target software package. The information identifying the target software package can be read and a determination can be made as to whether the information indicates a known software package. In response to determining the information indicates a known software package, the patch can be installed. In response to determining the information does not indicate a known software package options identifying software packages for which the patch may be used can be presented to a user and a selection of one of the packages can be received. The selected software package can be seeded with the information identifying the target software package and the patch can be installed for the selected software product.

Abstract: In an embodiment of the present invention, a patch tool receives multiple patches, with each patch designed to fix a corresponding subset of a set of errors in a system. The patch tool determines a subset of patches, which together fix all of the set of errors, and deploys only the subset of patches in the system. The patches may be received over a period of time and the subset of patches are determined and deployed in a batch mode.

Abstract: A patch tool receives multiple patches, with each patch designed to fix a corresponding subset of a set of errors in a system. Some of the patches may require that the files from older patches be removed from the system. In an embodiment of the present invention, a developer of a patch is provided the flexibility to specify that a desired file from an older patch fixing a specific error, not be removed during deployment of a new patch designed to fix the same specific error. Rolling back later to the older version of the patch may be simplified by not removing the desired file.

Abstract: An aspect of the present invention enables a developer to include a set of instructions along with a file in a patch, with the instructions specifying the manner in which the file is to be processed during deployment of the patch. The instruction may be designed to cause a custom action to be performed.