public Software package management process

Contents [ show ]

Process steps

The standard package management process is handled by the Software manager and includes the following steps:

  1. the developer uploads the software packages on a global repository
  2. the system automatically synchronizes its software collection once each 24 hours
  3. the user browses the software manager
  4. the user marks packages for install, update or uninstall ("no action" is the default selected action of all the packages in the repository)
  5. the system calculates and resolves all dependencies and generates the list of packages that need to be installed, uninstalled or updated, for the scheduled actions to be possible. Produces an error message, if a dependency could not be satisfied.
  6. the system checks the signature of all packages that are scheduled and warns the user for failed or signatures not being present
  7. the system automatically downloads all the packages from the repositories
  8. the system applies the software packages changes on all frontend cluster members, shutdowns and restarts the web applications in the process. This action requires the wordframe-agent windows service to be present and running on each frontend web server.

How to update the available software packages list

The software manager initially presents only the packages with their latest available versions, found across all subscribed repositories.

Automatic system synchronization
Automatically in any given  24 hour period, the system will synchronize its available software packages list with all the software repositories.
Manually upload packages
If a package is not present in the package list, you can upload a software package manually. Review the local software repositories section for further information.
Last edited by Boz Zashev on 28 Sep 2010 | Rev. 7 | This page is public | Views: 1
Comments: 0 | Filed under: Software management | Tags: