How the Software Library is populated

HOWTO62937
Last Updated December 17, 2011

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:

Automatically

Package files can be added to the Software Library automatically when you import a package file to create a software resource.

See Importing a package to create a software resource.

If you have a data provider that lets you import software resources and their associated software packages, you can create a schedule for the import. When the import runs, it can import any available software resources and the software packages that are associated with those software resources. The software packages are imported into the Software Library.

See Importing data from a data provider.

Manually

When you manually associate a package with a software resource, you can choose to add the package file to the Software Library.

See Associating a package with a software resource.

If an existing package in a software resource is not sourced from the Software Library, you can change its source to the Software Library. When you change a package's source to the Software Library, the package folder and files are copied to the Software Library folder.

See Adding an existing package to the Software Library.

If you have a data provider that lets you import software resources and their associated software packages, you can manually import specific software packages. You gather a list of software resources that are available for import. You then select from this list the specific software resources that you want to import from this data provider. When you import a software resource, you can also import its associated software package into the Software Library.

See Importing data from a data provider.

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

Imported Document ID: HOWTO62937
Legacy ID: v16897697_v66611926

Thanks for your feedback. Let us know if you have additional comments below. (requires login)

    © 1995-2019 Symantec Corporation