Sharing The Software Manager Database With Corporate Developers - Symantec SOFTWARE MANAGER 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0 Reference

Sharing the Software Manager Database With Corporate Developers

Software Manager Reference
Multiple users can resolve conflicts in ConflictManager, provided each user
resolves conflicts for a different package.
Typically, each user is assigned to work on a specific package or packages. Your
corporate standards should specify whether a user can update a package that is
assigned to someone else. This could happen when using one of the aggressive
resolution rule sets or when using the Copy Down button in the ConflictManager
Resolve wizard.
You can set up multiple Software Manager databases within your organization. Each
database might contain packages used by a different department, or packages
managed by a different regional repackaging team.
(Enterprise Management Server only.) Users can open multiple Software Manager
databases simultaneously, and can share packages between databases.
See also:
About the Software Manager Database
Multiple Software Manager Databases
Additional Wise Package Studio Configurations in the Getting Started Guide
Developers who create applications for internal, corporate use might want to obtain
information about external applications that have been tested and deployed throughout
their organization.
If the development team in your organization uses Wise Installation Studio, developers
can connect to the deployment team's Software Manager database.
Why share information in the deployment Software Manager database? Because the
Software Manager database used by Wise Package Studio contains approved versions of
applications that have been deployed, developers can use this information to build
installations that adhere to corporate standards.
Example:
By checking the Software Manager database when building an installation, and selecting
source files from the database, developers can be sure to use the correct versions of
critical files (examples: the Visual Basic runtime or MDAC). The result is that developers
produce more reliable installations that will not conflict with applications already
deployed to end-users' computers. This eliminates the need for the repackaging team to
repackage internally developed applications and lets them focus on other activities. It
also assures the deployment team that applications will perform as expected and
reduces calls to the help desk.
Process for Sharing the Software Manager Database
1. During development, the developer imports a new application to the shared
Software Manager database. The developer can view resources used by applications
that are in development and those that have been deployed.
2. When development is finished, the developer notifies a member of the deployment
team.
3. The deployment process begins.
Introduction to Software Manager
on page 19
on page 19
21