Patch Handling module
This page details the design for adding support of my project.
1.0 Project Overview
- Overview of the project and it's goals.
The purpose is to define and implement an interface to the openInstaller project through which consumers will detail their requirements in terms of patches. The openInstaller will act upon these requirements by installing or removing the patches during installation or uninstallation phases.
openInstaller 1.0
This functionality is needed by our next customer. (excerpt from http://wikihome.sfbay.sun.com/portalserver/Wiki.jsp?page=OpenInstallerIssuesPS72OpenInstaller) Portal has a dependency on AM7.1u1. AM7.1u1 is available as AM7.1 packages + patches for u1. Can openInstaller install the patches along with the packages as part of AM installation ? Maybe a P1 requirement if AM does not provide freshbitted packages for portal
Gustave Loial
2.0 Project Use case(s)
Case # |
Description |
6514787 |
Framework needs integrated process to update target system to the appropriate patch level |
3.0 High Level Design
- Include graphics if possible
4.0 Detail Design
- Include schema additions, changes, deletions
- Architecture
- Can be filled in in time
- Internal interfaces
- Exposed interfaces
- Can be pointers to other wiki pages as size requires.
5.0 Test Plan
- Unit tests
- Test Product
- Functional tests
- Can be pointers to other wiki pages as size requires.
|