How the Software Library is populated
The Software Library is a secure directory that is the centralized repository of the definitive, authorized versions of the software that your organization manages. A package that is sourced from the Software Library is referred to as a managed package. You place packages in the Software Library to ensure that external users cannot change the packages after they have been approved for rollout in your environment.
See About the Software Library.
Each package is associated with a software resource. Therefore, before you can place a package in the Software Library, you must create a software resource and associate the package with it.
The only packages that are not associated with software resources are as follows:
Packages that are added when you create a Package Delivery task in Software Management Solution and source the package from the Software Library.
Packages that are added as a result of a migration from Software Delivery Solution 6.x to Software Management Solution 7.0.
The only correct ways to add package files to the library are through Software Management Framework as follows:
Do not add package files directly to the Software Library directory on the file system. To do so prevents the proper associations from being made and compromises the integrity of the Software Library. You need to secure the Software Library directory so that only the application identity of Notification Server has access. The application identity of Notification Server is the account that is used to access Notification Server. Do not give directory access to any other users.
See About software resources
See About software packages
Thanks for your feedback. Let us know if you have additional comments below. (requires login)