Symantec SOFTWARE MANAGER 7.0 SP2 - REFERENCE FOR WISE INSTALLATION STUDIO V1.0, SOFTWARE MANAGER Installation Manual

Software Manager Reference

Software Manager

The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement.

Documentation version 7.0 SP2

Legal Notice

other countries. Other names may be trademarks of t heir respective owners. The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse

engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any.

THE DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE E XTENT THAT SUCH DISCLAIMERS ARE HELD T O BE LEGALLY INV ALID . SYMANTE C CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 “Commercial Computer Software - Restricted Rights” and DFARS 227.7202, “Rights in Commercial Computer Software or Commercial Computer Software Documentation”, as applicable, and any successor regulations. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation 350 Ellis Street Mountain View, CA 94043

http://www.symantec.com

Software Manager Reference 2

Technical Support

Symantec Technical Support maintains support centers globally. Technical Support’s primary role is to respond to specific queries about product features and functionality. The Technical Support group also creates content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates.

Symantec’s maintenance offerings include the following:

z A range of support options that give you the flexibility to select the right amount of

service for any size organization

z Telephone and/or web-based support that provides rapid response and up-to-the-

minute information

z Upgrade assurance that delivers software upgrades z Global support purchased on a regional business hours or 24 hours a day, 7 days a

week basis

z Premium service offerings that include Account Management Services

For information about Symantec’s support offerings, you can visit our web site at the following URL:

www.symantec.com/business/support/

All support services will be delivered in accordance with your support agreement and the then-current enterprise technical support policy.

Contacting Technical Support

Customers with a current maintenance agreement may access Technical Support information at the following URL:

www.symantec.com/business/support/

Before contacting Technical Support, make sure you have satisfied the system requirements that are listed in your product documentation. Also, you should be at the computer on which the problem occurred, in case it is necessary to replicate the problem.

When you contact Technical Support, please have the following information available:

z Product release level z Hardware information z Available memory, disk space, and NIC information z Operating system z Version and patch level z Network topology z Router, gateway, and IP address information z Problem description:

 Error messages and log files

Software Manager Reference 3

 Troubleshooting that was performed before contacting Symantec  Recent software configuration changes and network changes

Licensing and registration

If your Symantec product requires registration or a license key, access our technical support Web page at the following URL:

www.symantec.com/business/support/

Customer service

Customer service information is available at the following URL:

www.symantec.com/business/support/

Customer Service is available to assist with non-technical questions, such as the following types of issues:

z Questions regarding product licensing or serialization z Product registration updates, such as address or name changes z General product information (features, language availability, local dealers) z Latest information about product updates and upgrades z Information about upgrade assurance and maintenance contracts z Information about the Symantec Buying Programs z Advice about Symantec’s technical support options z Nontechnical presales questions z Issues that are related to CD-ROMs or manuals

Support agreement resources

If you want to contact Symantec regarding an existing support agreement, please contact the support agreement administration team for your region as follows:

Asia-Pacific and Japan customercare_apac@symantec.com Europe, Middle-East, and Africa semea@symantec.com North America and Latin America supportsolutions@symantec.com

Additional enterprise services

Symantec offers a comprehensive set of services that allow you to maximize your investment in Symantec products and to develop your knowledge, expertise, and global insight, which enable you to manage your business risks proactively.

Enterprise services that are available include the following:

Software Manager Reference 4

Managed Services Managed services remove the burden of managing and

monitoring security devices and events, ensuring rapid response to real threats.

Consulting Services

Educational Services

To access more information about Enterprise services, please visit our Web site at the following URL:

www.symantec.com/business/services/

Select your country or language from the site index.

Symantec Consulting Services provide on-site technical expertise from Symantec and its trusted partners. Symantec Consulting Services offer a variety of prepackaged and customizable options that include assessment, design, implementation, monitoring, and management capabilities. Each is focused on establishing and maintaining the integrity and availability of your IT resources.

Educational Services provide a full array of technical training, security education, security certification, and awareness communication programs.

Software Manager Reference 5

Contents

Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 1: Introduction to Software Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

About Software Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Packages in Software Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Package Management with Software Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Starting Software Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

About the Software Manager Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Customizing the Software Manager Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Refreshing the Software Manager Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Icons in Software Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Resource Icons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Relationship Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

About the Wise Software Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

About the Software Manager Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

How Source Files Are Indexed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Sharing the Software Manager Database With Wise Package Studio . . . . . . . . . . . . . . . . . . . . 16

About Applications and Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

About Package Meta Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Defining Custom Meta Data Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Defining a Custom Meta Data Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Product Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 2: Importing Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

About Importing Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

How to Get Packages Into the Software Manager Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

About Formatted Text Strings in Registry Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Package Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Import Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

About Patch and Transform Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Importing From the Share Point Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

About .QUE Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Importing a Windows Installer File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Importing a Merge Module File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Importing a Transform File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Importing a Windows Installer Patch File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Importing Multiple Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Chapter 3: Managing Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

About Managing Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Package Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Creating Package Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Selecting Superseding Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Adding Applications and Packages to Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Editing Package Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Viewing and Editing Package Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Viewing Resource Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Software Manager Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Software Manager Reference 6

Generating a Software Manager Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Using the Report Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Moving a Package to Another Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Deleting a Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Changing the Package Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Chapter 4: Software Manager Database Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . 51

About Software Manager Database Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Changing the Server Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Deleting a Server Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Restructuring the Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Rebuilding the Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Software Manager Reference 7

Chapter 1

Introduction to Software Manager

This chapter includes the following topics:

z About Software Manager on page 8 z Starting Software Manager on page 9 z About the Software Manager Window on page 10 z Icons in Software Manager on page 12 z About the Wise Software Repository on page 14 z About the Software Manager Database on page 15 z About Applications and Packages on page 17 z About Package Meta Data on page 18 z Product Documentation on page 21

About Software Manager

Software Manager provides the interface for working with packages in the Software Manager database, which contains information about all the software packages used by your organization. Storing all your package information in a central location lets you better manage packages during their lifecycle stages—from integration, testing, and deployment through retirement.

Use Software Manager to import and organize packages and their resource information in the Software Manager database, to obtain information about packages and their resources, to set the status of packages, and to prepare a package or group of packages for deployment. Corporate developers can use Software Manager as a centralized point for managing all resources used by applications that they develop.

Software Manager is a tool in the Professional Edition of Wise Package Studio. If you have an installation of Wise Installation Studio that is connected to a Wise

Software Repository, Software Manager is also available as a tool in Windows Installer Editor.

See About the Wise Software Repository on page 14.

Note

Features that are specific to Wise Package Studio are not available when you access Software Manager from Windows Installer Editor.

Packages in Software Manager

In Software Manager, a package consists of any combination of the following:

z Meta data. This is the is minimum amount of information that constitutes a package. z The resources associated with each package’s installation.

Software Manager Reference 8

Adding Packages to the Software Manager Database

For packages to be managed, they must be in the Software Manager database. To get packages into the database, you can do any of the following:

z Add the package’s meta data in Windows Installer Editor. z Import the package and its resources in Software Manager.

See How to Get Packages Into the Software Manager Database on page 23 and Package

Import on page 25.

Package Management with Software Manager

Once packages are in the Software Manager database, you can do the following:

Create and Manage Package Groups

A package group consists of a subset of the packages in the Software Manager database. You can use groups to:

z Organize your packages.

See Package Groups on page 41.

Introduction to Software Manager

Edit Package Information

Use Software Manager to maintain the packages in the Software Manager database.

z Change the package status so you can determine whether a package can be

deployed to end users.

z Edit package information. Example: You can rename the application or package, or

change the reference to the source file paths.

z Enter or edit user-defined package meta data. z Delete a package from the Software Manager database.

See Viewing and Editing Package Attributes on page 45 and Changing the Package

Status on page 49.

View Package Resources

z Use the panes in Software Manager to drill down to the resources (examples: files,

registry keys, merge modules, shortcuts, and so on) that are us ed by each package. See About the Software Manager Window on page 10 and Viewing Resource

Properties on page 46.

If an .MSI contains a merge module, the resources that appear under the Merge Modules folder also appear in the corresponding folders elsewhere in the package. (Example, if an .MSI contains a merge module that has .DLL files in the system32 folder, these files will appear in the system32 folder under the package’s Merge Modules folder and Files/Directories folder.) If a .WSI contains a merge module, the Merge Module s folder and some of its subfolders appear, but none of the merge module’s resources appear.

Starting Software Manager

In the Wise editor, select Tools menu > Software Manager. (In Visual Studio: Project menu > Software Manager.)

Software Manager Reference 9

Software Manager opens.

Which Database is Opened?

The first time you start Software Manager, it opens the database that you connected to during installation. Thereafter, Software Manager opens the database most recently used.

See also:

About the Software Manager Window on page 10

About the Software Manager Window

When you start Software Manager, the main Software Manager window appears. Some of the panes might be empty if no packages are in the Software Manager database.

Software Manager Window

Toolbar

Introduction to Software Manager

Groups pane

Applications/ Packages pane

Package Details pane

Toolbar

Contains buttons for quick access to many Software Manager commands.

Database Pane

Displays summary information about the Software Manager database.

Database pane

Application/ Package Summary pane

The Database pane initially appears immediately below the too lbar, but yo u can mov e or hide it.

Software Manager Reference 10

Introduction to Software Manager

Groups Pane

Displays the package groups defined for each database. A package group consists of a subset of the applications in the database. When a group is selected, the Applications/ Packages pane lists only the packages assigned to that group. This lets you reduce the number of packages you view at one time.

See Creating Package Groups on page 42. The Groups pane initially appears on the left side of the window below the Database

pane, but you can move or hide it.

Application/Package Summary

Displays different information depending on what is selected in the Applications/ Packages pane:

z When you select an application, this pane is named Application and it lists the

packages contained in that application.

z When you select a package, this pane is named Package and it displays a summary

of the package’s resources, information about when the package was imported and changed, and package meta data. It also contains a Package Status drop-down list, which you use to change the package’s status.

See Changing the Package Status on page 49.

The Application/Package Summary pane initially appears on the right side of the window below the Database pane, but you can move or hide it.

Applications/Packages Pane

Displays the applications and packages in the Software Manager database. Expand an application to display its packages. Select a package to make it the active package.

For information on the icons that appear in this pane, see Icons in Software Manager on page 12.

Package Details Pane

Displays the resources in the package selected in the Applications/Packages pane. For information on the icons that appear in this pane, see Resource Icons on page 13. Double-click an item in this pane to display the Properties dialog box. See Viewing Resource Proper t ies on page 46.

Customizing the Software Manager Workspace

z Hide or show the toolbar or one of the panes by selecting its name from the View

menu.

z Move, dock, and undock the panes as you would any Windows pane, by dragging

their title area.

The Applications/Packages pane and Package Details panes cannot be hidden or moved.

Refreshing the Software Manager Display

z Select File menu > Refresh.

Software Manager Reference 11

This rereads the package data and redisplays package information. This can be useful if packages have been added to the Software Manager database since you started this Software Manager session.

Icons in Software Manager

The following icons appear in Software Manager to help you quickly identify items in the database. Although you cannot import some of these items when you run Software Manager from Windows Installer Editor, they might appear in the database if someone else imported them through Wise Package Studio.

Icon Represents Appears in this pane

Software Manager database Applications/Packages

Group Groups

Application Applications/Packages,

Introduction to Software Manager

Package Details

Windows Installer package (installation, transform, patch, or Microsoft hotfix)

When you import an InstallShield® Developer .EXE, it appears as a Windows Installer package because an .MSI is extracted from the .EXE.

Virtual software package (.WVP or .VSA) created in Virtual Package Editor.

Wise package definition file (.WPF) created in Workbench and imported.

WiseScript package Applications/Packages,

Merge module package Applications/Packages,

Any installation file imported using the Universal Import option

SOE Snapshot Applications/Packages,

Device driver package Applications/Packages,

Applications/Packages, Package Details

Package Details

Package Details Applications/Packages,

Package Details

See also:

About the Software Manager Window on page 10

Software Manager Reference 12

Group Policy Object package Applications/Packages,

Package Details

Resource Icons

Introduction to Software Manager

The following icons appear in the Package Details pane in Software Manager. They indicate the types of resources that are installed by a package.

Icon Resource Type

File or Windows Installer component.

Registry key or named value.

Modification to Autoexec.bat. Not applicable in Windows Installer packages.

Modification to Config.sys. Not applicable in Windows Installer packages.

ODBC data source or driver.

Windows NT service.

See also:

About the Software Manager Window on page 10

Relationship Icons

In Software Manager, the following icons appear on the Dependencies tab on the Package Relationships dialog box. These icons represent:

z The dependency relationship, which is what should happen to th e dependency

z The association relationship, which is what should happen to the dependent package

Device driver ins talled in Win.ini. Not applicable in Windows Installer packages.

.INI file and entries.

Shortcut.

Change to the PA TH variable. Not applicable in Windows Installer packages.

package if the dependent package is installed.

if the dependency package is installed.

Software Manager Reference 13

Introduction to Software Manager

Icon Dependency relationship Association relationship

Required. The dependency must precede the

dependent package during installation.

Required.

None.

Required.

The dependency must precede the dependent package during installation.

Required. The dependency must precede the

dependent package during installation.

Optional. Installing the dependency package

is optional. If it is installed, it must precede the dependent package.

Optional. Installing the dependency package

is optional. If it is installed, it must precede the dependent package.

Optional. Installing the dependency package

is optional. If it is installed, it must precede the dependent package.

Supersedes. The dependency replaces the

dependent package during installation.

The dependent package must be installed with the dependency.

Optional. Installing the dependent package

with the dependency is optional.

None.

Required. The dependent package must be

installed with the dependency.

Optional. Installing the dependent package

with the dependency is optional.

None.

About the Wise Software Repository

The Wise Software Repository™ is a collection of resources, and information about those resources, for all applications that are developed and used by an organization. This scalable repository provides a centralized point for managing software packages at any stage of development.

You can connect to a Wise Software Repository that has been configured for an installation of Wise Package Studio. This lets you develop c onsistent, accur ate, and high quality installations based on corporate standards by ensuring that you use the correct versions of resources that are shared across multiple applications.

See Connecting to a Wise Software Repository in the Windows Installer Editor Help. The Wise Software Repository consists of:

Software Manager Reference 14

Introduction to Software Manager

z Share Point Directory

Contains shared resources used to create Windows Installer installations. It also contains source files for packages in the Software Manager database. All Wise Software Repository databases are associated with a specific share point directory.

See About the Share Point Directory in the Windows Installer Editor Help.

z Workbench database

Stores information that Wise Package Studio creates and uses. Examples: project, process, tool, and security information. A repository can contain only one Workbench database.

The Workbench database is not used in Wise Installation Studio.

z Software Manager database

Contains all software packages created by an organization. Package resources might be included also (examples: files, merge modules, registry keys).

See About the Software Manager Database.

z Wise Services database

Stores data that is generated and used by various background operations (examples: package import, the upgrade process).

A repository can contain only one Wise Services database.

See also: Setting Repository Options in the Windows Installer Editor Help

About the Software Manager Database

The Software Manager database contains:

z All software packages used or created by an organization. Package resources might

be included also (examples: files, merge modules, registry keys).

z Merge modules used by an organization. z Other resources used by an organization, such as device drivers and Group Policy

Objects. (These cannot be imported when you run Software Manager from Windows Installer

Editor.)

z Snapshots of standard operating environments used by an organization, for use

during conflict resolution. Create these snapshots with SOE Snapshot. (These cannot be imported when you run Software Manager from Windows Installer

Editor.) You manage the data in the Software Manager database through Software Manager. Most organizations that use Software Manager work in a multi-user, team-based

environment. Multiple users can simultaneously access a single Software Manager database that is stored on a shared server. This means that:

z Multiple users can distribute to the share point directory. z When a package is added to the Software Manager database, all Software Manager

users can view and work with it.

Software Manager Reference 15

See also:

About the Wise Software Repository on page 14 Sharing the Software Manager Database With Wise Package Studio on page 16

How Source Files Are Indexed

A sequentially-numbered directory structure is created under the share point directory to store occurrences of installation source files when:

z You distribute a package to the share point directory. z You import a single package or multiple packages to the Software Manager

database, and you distribute source files. An index file named wamdb.idx, located in the share point directory , records the location

of the source files. Because files are indexed, distributing source files to the share point eliminates storage of duplicate files and results in smaller storage requirements than if you distribute to a network directory.

Example: Suppose you have three pac kages, each c ontaining a v ersion of report. dll. Th e first ti me

you distribute a package containing report.dll, the file is placed in the share point’s 000\001 directory. If you distribute another package containing the same version of report.dll, the file is not saved a second time, but a counter is set for that file in wamdb.idx. If you distribute a third package that uses a different version of report.dll, the file is stored in a second directory, 000\002. The result is a set of all the unique source files used by all the packages in the Software Manager database.

Introduction to Software Manager

See also:

About the Share Point Directory in the Windows Installer Editor Help Copying an Installation to the Share Point Directory in the Windows Installer Editor Help

Importing From the Share Point Directory on page 27

Sharing the Software Manager Database With Wise Package Studio

Developers can use the Software Manager database solely to store information about applications they develop. This situation is typical of an independent software vendor

(ISV) environment. Developers who create applications f or internal, corpor ate 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

Software Manager Reference 16

Introduction to Software Manager

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.

Note

Because applications that are still in development will be mixed with those that have been tested and deployed, members of the deployment team must be careful not to deploy applications that are still in development.

See also: Installation Resources and Their Locations in the Windows Installer Editor Help

About Applications and Packages

When you add a package to the Software Manager database, you assign it an application name and a package name. An application is a group of similar packages. Packages represent different versions of a single application installation, or different components of a larger suite. Group packages that are not likely to coexist on the same computer under a single application. This prevents y ou from seeing resources th at are not relev ant to a specific application. Also, because ConflictManager does not look for conflicts between packages of the same application, this speeds the conflict detection process and avoids showing you conflicts that are not relevant.

Example: Your Software Manager database might contain three Microsoft Office packages: Office

97, Office 2000, and Office XP. Because you are not likely to install multiple versions of Microsoft Office on a single computer, you can group them under one application, named Microsoft Office.

Obtaining Application and Package Names for Installations

If the package’s meta data is in the Software Manager database, the application and package names are pre-filled during import.

Otherwise, they are assigned as described below.

When you import the application/package names are obtained

from:

a single installation file (any type)

prompts during import.

Software Manager Reference 17

Introduction to Software Manager

When you import the application/package names are obtained

from:

from the share point directory

multiple Windows Installer installations

z multiple Windows

Installer installations that do not have a product name and version, or

z multiple WiseScript

installations

the application and package names that were specified during Package Distribution. If the application and package names were not specified during distribution, they are assigned as described below.

The product name and version from the Product Details page in Windows Installer Editor. Application name = product name. Package = product name + version. Example: If the product name is Sample and the version is 1.0.0, the application name will be Sample and the package name will be Sample 1.0.0.

the file name. Example: If you import Sample.msi, the application name and package name will both be Sample.

Naming Applications and Packages for Other Items

z Merge module

You might group merge modules by manufacturer or function. Example: Create an

application named MDAC, and then import merge module files to packages named

MDAC 2.5, MDAC 2.6, MDAC 2.7, and so on.

z Patch

Application name: Use the base package’s application name.

Package name: Describe the patch. Example: Sample_5.01_Update.

z Transform

Application name: If the transform is applied to a blank database, you might give it

a unique application name, or group all such transforms under one application name

(example: General Application Registration Transforms). If the transform is applied

to a base package, use the base package’s application name.

Package name: Describe the transform. Example: If the base installation’s

application name is Sample, and the transform changes the language of the

installation dialog boxes to French, name the transform package Sample_French.

About Package Meta Data

Expand the value of the Software Manager database by using meta data to store package information that is not otherwise recorded when the package is created.

z You can view meta data in the Packag e pane in Software Manager, provided

Package Pane is marked on the Meta Data Fields dialog box.

z You can view meta data on the Package Attributes dialog box. z You can add meta data to custom reports as you would any other data in the

Software Manager database.

Software Manager Reference 18

Introduction to Software Manager

Kinds of Meta Data

You define and enter custom meta data in Software Manager. Predefined meta data is created when you create the package in Windows Installer

Editor. See Adding Meta Data to the Software Manager Database in the Windows Installer Editor

Help.

Editing Meta Data

Edit custom meta data on the Package Attributes dialog box in Software Manager. If no meta data values are enabled, it means that custom meta data fields have not been defined.

The predefined meta data is read-only in Software Manager. To edit predefined meta data, use the Product Details page in Windows Installer Editor.

See:

Viewing and Editing Package Attributes on page 45 Defining Custom Meta Data Fields on page 19

Examples of Package Meta Data

You can use meta data to specify:

z Whether an application is developed internally or purchased from a third party. z The type of license model the software uses. z How many licenses are purchased, in use, and available. z The language of the application. z Links to the purchasing department, such as purchase order number or URL to the

purchasing system.

z Package description. z Packager comments about limitations of the package. z Path to original source files. z Path to the package’s end user license agreement. z Path to support documents such as installation instruction s or con figuration options.

Defining Custom Meta Data Fields

You can define custom meta data fields to store package information that is not otherwise recorded when the package is created. Example: You can specify the type of license model the software uses.

See About Package Meta Data on page 18. You must define meta data fields before you can edit their values. The fields you define

appear on the Product Details page in Windows Installer Editor. They also appear on the Package Attributes dialog box in Software Manager.

To define custom meta data fields

1. Select Setup menu > Meta Data Fields.

Software Manager Reference 19

Introduction to Software Manager

The Meta Data Fields dialog box appears.

2. Click Add.

3. In Field Name, enter text to describe this meta data field and press Tab.

4. From Data Type, select the kind of data this field will accept.

Note

If you change the data type for a field that is in use, the data associated with that

field is deleted from all packages.

 String

This field will accept any text entry.

 External Link

This field will accept entry of a UNC path and file name or a URL, which will become an active hyperlink on the Package pane.

 Integer

This field will only accept entry of a numeric character. The user can precede numeric characters with a hyphen to represent a negative number. Decimal points are not accepted.

 True/False

 Yes/No

Any custom data types that you have defined are also listed. You typically define a

custom data type when a meta data field requires the user to select from a set of

predefined values. To define a custom data type, click Custom Data Types.

See Defining a Custom Meta Data Type on page 21.

5. The text you enter in Description appears in a tooltip for this meta data field on the

Product Details page in Windows Installer Editor.

6. Package Pane is marked by default, which causes this field to appear in the

Package pane in Software Manager. If you clear this check box, this field will be

visible in the Package Attributes dialog box only.

7. The meta data fields are displayed to the user in the order they are listed here . To

rearrange the order, click Move Up or Move Down.

8. When you finish adding meta data fields, click OK.

Changing and Deleting Meta Data Fields

z When you change the data type for a meta data field, data in that field is deleted

from all packages.

z When you delete a meta data field that is in use, that field is deleted from all

packages.

z You cannot delete or make changes to the predefined meta data fields.

See also:

Viewing and Editing Package Attributes on page 45

Software Manager Reference 20

Defining a Custom Meta Data Type

When a meta data field requires the user to select from a set of predefined values, you define a custom data type and specify valid values. Example: If you add a meta data field to specify the type of license model the software uses, you might add a custom data type that cont ains these values: per seat; per server; freeware; and none.

To define a custom meta data type

1. Select Setup menu > Meta Data Fields.

The Meta Data Fields dialog box appears.

2. Click Custom Data Types.

The Custom Data Types dialog box appears. Two custom data types are predefined:

True/False and Yes/No. You can delete them if you don’t need them.

3. Click Add Type.

4. In Data Type Name, enter a descriptive name for the new data type.

5. Click Add Value.

6. In Values, enter a value that is valid for this data type.

7. Continue adding values as needed.

Introduction to Software Manager

8. To rearrange the order, click Move Up or Move Down.

The values will appear in this order in a drop-down list on the Package Attributes

dialog box and on the Product Details page in Windows Installer Editor.

9. When you finish adding custom data types, click OK.

The Data Type drop-down list on the Meta Data Fields dialog box contains the

custom data types you added.

Changing and Deleting Custom Meta Data Types

z When you change a value that is in use, fields using that value are changed to use

the new value.

z When you delete a custom data type that is in use, fields using that data type, and

all data associated with those fields in packages, are deleted.

z When you delete a value that is in use, records containing that value are deleted

from all packages.

See also:

Defining Custom Meta Data Fields on page 19

Product Documentation

This documentation assumes that you are proficient in the use of the Windows operating system. If you need help using the operating system, consult its user documentation.

Use the following sources of information to learn about this product.

Software Manager Reference 21

Introduction to Software Manager

Online Help

The online help contains detailed technical information and step-by-step instructions for performing common tasks.

Access help in the following ways:

z To display context-sensitive help for the active window or dialog box, press F1. z To select a help topic from a table of contents, index, or search, select Help menu >

Help Topics.

Reference Manual

All the material in the online help is also available in a .PDF-format reference manual, which you can access by selecting Help menu > Reference Manual.

Getting Started Guide

The Getting Started Guide contains system requirements and installation instructions. You can access a .PDF version of the Getting Started Guide from the Windows Start menu.

Release Notes

The product release notes cover new features, enhancements, bug fixes, and known issues for the current version of this product. T o access the release not es, select Release

Notes from the Symantec program group on the Windows Start menu.

Software Manager Reference 22

Chapter 2

Importing Packages

This chapter includes the following topics:

z About Importing Packages on page 23 z How to Get Packages Into the Software Manager Database on page 23 z Package Import on page 25

About Importing Packages

Software Manager lets you import packages and their resource information into the Software Manager database.

When you import packages that are different versions of the same application, you normally assign them to the same application.

See About Applications and Packages on page 17.

Note

Features that are specific to Wise Package Studio are not available when you access Software Manager from Windows Installer Editor.

How to Get Packages Into the Software Manager Database

When a package is referred to as being in the Software Manager database, it can mean any of the following:

z The package’s meta data has been added to the Software Manager database. z The package’s resources have been imported to the Software Manager database.

Adding Package Meta Data

(.MSI and .WSI files only.) When you specify an application and package name on the Product Details page in Windows Installer Editor and save the installation:

z A record for the package is created in the Software Manager database. z The package’s meta data is added. z The package status is set to New. z Resources are not added.

This lets you add package information to the Software Manager database early in the development process. It also eliminates the need to enter the meta data manually in Software Manager and ensures that every package in the database h as meta data that meets your corporate standards.

Software Manager Reference 23

Importing Packages

See Adding Meta Data to the Software Manager Database in the Windows Installer Editor Help.

Importing Package Resources

When you use the Import Wizard in Software Manager:

z If the package is not already in the Software Manager database, it is added along

with its meta da ta.

z Information about the package’s resources is added to the database. z Depending on the import options you select, the resources themselves might be

copied to the share point directory and their source paths updated in the

installation. This lets other team members view and share resources from the package. It also lets

you manage the package in Software Manager. See Package Import on page 25.

When to Add Packages to the Software Manager Database

Typically, you add packages to the Software Manager Database when certain milestones in the development process are reached. Develop corporate standards for these milestones.

Recommendations:

z When the installation is first created, add its meta data. z When the installation is ready for release, import its resources.

If you import package resources too early in the development process, they are

likely to become outdated. (Example: .DLLs and .EXEs are updated frequently

during a typical development process.) This makes it possible for others to use

those outdated resources in their installations. Consider this when you develop

corporate standards and procedures for importing and sharing resources.

About Formatted Text Strings in Registry Entries

Registry entries in Windows Installer and WiseScript packages can use formatted text strings that, when evaluated literally, might lead to false positives during conflict

detection. To avoid this problem, Software Manager resolves the formatted text strings during import of the following types of packages: .WSI, .MSI, .MSM, .MSP, .MST, .WSE.

Example: Application 1 creates a registry key under HKLM\Software\InstallDirK ey with a value of [$comp1]. Application 2 creates a registry key under HKLM\Software\InstallDirKey with a value of [$comp4]. During installation, both [$comp1] and [$comp4] evaluate to the same value. If these values were not resolved, ConflictManager would identify this as a conflict. However, because Software Manager resolves the values during import, and stores them in the Software Manager database, a conflict is not detected, which is the correct behavior.

SoftwareManager resolves all properties in a Windows Installer installation. In a WiseScript installation (.WSE), SoftwareManager resolves only the following predefined variables:

Software Manager Reference 24

Importing Packages

WiseScript variable Resolves to

%Common% Program Files\Common %fonts% Windows\Fonts %MainDir% Program Files\default maindir

or, if default maindir is empty:

Program Files %Program_Files% Program Files %Sys% Windows\System %Sys32% Windows\System32 %Win% Windows

When the package resource appears in Software Manager and ConflictManager, the resolved value is displayed instead of the formatted text string.

Package Import

Use the Import Wizard in Software Manager to add a package and information about its resources into the Software Manager database.

The Import Wizard provides several options for importing packages. The pages in the Import Wizard differ depending on the type of package you import and where you import it from.

See Import Methods on page 25.

Import Methods

Note

In general, do not import a package from a CD. If you do, you will not be able to export the package after resolving its conflicts, because you will not have access to its source files and you cannot write to a CD.

Import from the share point directory

To place a package into the share point directory and queue it for import, use Package Distribution to distribute a package to the share point.

See Copying an Installation to the Share Point Directory in the Wind ows Installer Editor Help.

Then, open Software Manager and import the package. See Importing From the Share Point Directory on page 27.

Import a single package from any network or local drive

You can import a single package from any accessible drive. Use this method when packages have been distributed to a network drive, or when an installation has been saved to a local or network drive.

Software Manager Reference 25

The following topics describe the types of packages you can import and provide instructions for importing each type of package:

Importing a Windows Installer File on page 29 Importing a Merge Module File on page 31 Importing a Transform File on page 33 Importing a Windows Installer Patch File on page 36

Import multiple packages from any network or local drive

You can import a group of packages from any accessible drive. Use this method when packages have been distributed to a network drive, or when an installation has been saved to a local or network drive.

See Importing Multiple Files on page 38.

See also:

How to Get Packages Into the Software Manager Database on page 23

About Patch and Transform Import

You have two options for importing Windows Installer patches and transforms into the Software Manager database:

Importing Packages

z Apply the patch or transform when you import the base package

The resources installed by the patch or transform are combined with the resources installed by the base package and displayed together as a single package in Software Manager.

This lets you resolve conflicts in files that are installed by the patch or transform. The package is changed so that when you distribute it, the changes made by the patch or transform are included.

z Import the patch or transform separately from the base package

A relationship is created between the patch or transform package and the base package. The resources installed by the patch or transform a re di splay ed se par ately in Software Manager. This lets you:

 Maintain dependencies and sequencing of patches and transforms.  Store meta data for a patch or transform.  Group patches and transforms to determine the collective impact of those

patches or transforms during testing and deployment.

 Easily deploy patches and transforms with distribution systems.

If you have Symantec Management Platform 7.0 SP2 or later, you can use Wise Connector to import the patch or transform from the Software Manager database into Software Management Framework. Wise Connector imports the patch or transform when it imports the base MSI package. You can then use Software Managem ent Solution to deploy the patch or transform.

Defining the State of the Base Package

When you import a patch or transform, you can specify additional transforms to be applied to the base package before the patch or transform you are importing. This changes the state of the base package, which determines the resources that are

Software Manager Reference 26

Importing Packages

included in the imported patch or transform package and changes how it behaves when it is installed.

Example: Suppose that two different transforms can be applied to a base package.

z The Base Package installs File A, File B, and File C. z Transform 1 deletes File C. z Transform 2 installs Registry Key X and modifies File C.

When you apply the transforms like this:

Base Package

Transform 2 does this during installation:

installs Registry Key X Transform 2 Base Package Transform 1 Transform 2

See:

Importing a Windows Installer Patch File on page 36 Importing a Transform File on page 33 Package Groups on page 41

Importing From the Share Point Directory

When the Database pane displays a number of packages that are queued for import, use the Import from share point directory option in the Import Wizard to import the packages into the Software Manager database.

When a package is distributed to the share point directory, the package and its source files are copied to several subdirectories of the share point directory, and a .QUE file is created to represent the package that is waiting to be imported into the Software Manager database.

When you successfully import a package from the share point directory, its .QUE file is deleted and the package information is added to the Software Manager database. Paths to the new source file locations are also updated in the package installation file, except for Wise package definition files.

modifies File C

installs Registry Key X

File C is not present, because the state of

the Base Package has been changed by

applying Transform 1.

See About .QUE Files on page 29 and How Source Files Are Indexed on page 16.

Note

When you use either Windows Installer Editor or WiseScript Editor to add files to a package that has already been distributed to the share point directory and imported, a prompt appears asking if you want to add the new files to the share point directory. If you do so, the .QUE file for that package is reset and you must re-import the package in Software Manager. If you have already detected conflicts for that package, you must also redo the conflict detection process.

To import a package from the share point directory

1. If multiple databases are open, select a database in the Applications/Packages pane.

Software Manager Reference 27

Importing Packages

2. Select Packages menu > Import. The Import Type page appe ars.

3. Mark Import from share point directory. Distribute source files to the share point directory is marked automatically

and unavailable. It is unavailable because the source files were copied when the package was

distributed to the share point. The following items become enabled:

 Overwrite existing application and package

Mark this to overwrite any package that is already in the database with the same application and package names.

If you clear this check box and the application and package names are already in the database:

 If the existing package has resources, the new package is not imported.  If the existing package does not have resources, the new package’s

resources are added to the existing package. An ex istin g pac kage mi ght not have resources if it consists only of meta data.

 Do not modify the original package

Normally, when you import a Windows Installer installation (.MSI or .WSI), the original installation file is updated with Wise-specific version information that speeds future subscriptions and imports of the installation. Mark this to prevent the original file from being changed.

4. To assign all packages that are imported during this session to one or more groups: a. Click Groups on the Import Type page. The Select Groups dialog box appears. b. Mark the check boxes of the groups to assign the package to. c. Click OK.

5. Click Next on the Import Type page. The Packages to Import page appears, listing all packages that are in the share

point and have not been imported.

6. All check boxes in the Packages to Import page are marked. Clear the check boxes for any packages you do not want to import.

Packages you do not select now will reappear on this page the next time you import from the share point directory.

7. Click Finish. The packages you selected are imported into the active Software Manager database.

When the import process is finished, the Import Complete page appears, displaying a log of the import process.

8. T o sav e the import log as a text file, click Sa ve and then choose a name and location for the log file. The default file name is Import Log.log.

9. To close the Import Complete page, click Close.

For information on how the application and package names are assigned, see About

Applications and Packages on page 17.

Software Manager Reference 28

See also:

Package Import on page 25

About .QUE Files

When you use Package Distribution to distribu te to the share point directory, temporary files are created in the Scripts subdirectory. These files, which have the same name as the installation file but with the extension .QUE, represent packages that have been distributed but not imported into the Software Manager database.

In Software Manager, the Database pane displays the number of packages that are Queued for Import. This represents the number of .QUE files in the Scripts directory.

When you import from the share point directory, the share point is searched for .QUE files. When one is found, the package it represents is imported into the Software Manager database. The .QUE file is removed after the package is imported.

Importing a Windows Installer File

You can import a single Windows Installer installation (.MSI or .WSI) into the Software Manager database from a network or local drive.

Importing Packages

When you import an .MSI, you can specify one or more transforms or p atches to be applied to the package. The additional resources in the transform or patch are added to the installation package’s resources in Software Manager so that they can be included in queries or reports of shared resources. To add the additional resources to a separate package in the Software Manager database instead, import the transform or patch separately.

See Importing a Transform File on page 33 or Importing a Windows Installer Patch File on page 36.

When you add a Windows Installer package’s meta data to the Software Manager database from Windows Installer Editor, its resources are not imported. To get the resources into the database, you must import them.

See How to Get Packages Into the Software Manager Database on page 23.

Note

If you have Symantec Management Platform 7.0 SP2 or later, you can use Wise Connector to import the Windows Installer file from the Software Manager database into Software Management Framework. You can then use Software Management Solution to distribute the package.

To import a Windows Installer file

1. If multiple databases are open, select a database in the Applications/Packages pane.

2. Select Packages menu > Import. The Import Type page appe ars.

3. Mark Import a single file into the Software Manager database.

4. In File, specify an .MSI or .WSI to import. Be sure to select the appropriate file type from the Files of type drop-down list on the Open dialog box.

5. The following items become enabled:

Software Manager Reference 29

Importing Packages

 Distribute source files to the share point directory

Mark this to copy all source files to a single, centralized location. Clear this check box to import the package description into the Software

Manager database without copying its source files to the share point directory.

Warning

Distributing source files for a package that represents a Visual Studio integrated project breaks the integration with the Visual Studio solution.

 Overwrite existing application and package

Mark this to overwrite any package that is already in the database with the same application and package names.

If you clear this check box and the application and package names are already in the database:

 If the existing package has resources, the new package is not imported.  If the existing package does not have resources, the new package’s

resources are added to the existing package. An ex istin g pac kage mi ght not have resources if it consists only of meta data.

 Do not modify the original package

6. To assign the imported package to one or more groups: a. Click Groups on the Import Type page. The Select Groups dialog box appears. b. Mark the check boxes of the groups to assign the package to. c. Click OK.

7. Click Next on the Import Type page. The Package Details dialog box appears.

8. Complete the dialog box:

 .MSI/.WSI File

The file you specified is displayed.

 Application Name

To create a new application, enter a unique name. To add this package to an existing application, select an application from the drop-down list.

Note

If the package’s meta data is in the Software Manager database or the package was created in Wise Package Studio, Application Name and Package Name are pre-filled. In that case, don’t change these names. Otherwise, you will have two packages in the database for the same installation: a package with just meta data and the package you import.

For information on application and package names, see About Applications and

Packages on page 17.

Software Manager Reference 30

Importing Packages

 Package Name

Enter a unique name to identify this package. Typically, you use the application name plus specific version information. Example: If the application name is Adobe Acrobat Reader, the package name might be Acrobat Reader 5.05.

To replace an existing package, select a package from the drop-down list.

 Use Transactions for Import

Mark this check box to import installation resources as database transactions instead of importing them individually. This speeds the import, but can lock Software Manager database records temporarily during the update. Use this option if you are the only person importing packages. If multiple people are importing packages at one time, do not mark this check box.

9. If you specified a .WSI, click Finish and skip the remaining steps.

10. If you specified an .MSI, click Next. If the Software Manager database contains one or more patches (.MSP) that apply

to this .MSI, the Existing Patches page appears and lists them. Otherwise, the Transforms and Patches page appears.

11. If the Existing Patches page appears, you can click Save to save the list of patches to a text file.

12. Click Next on the Existing Patches page. The Transforms and Patches page appears.

13. To apply a transform or patch to this .MSI before importing it into the Software Manager database, click Add on the Transforms and Patches page and specify the transform or patch. Specify additional transforms or patches if needed. The transforms and patches are applied to the package in the order they appear in the list. To rearrange the order, click Move Up or Move Down.

14. Click Finish. The Wise Task Manager dialog box appears and remains open until the operation is

completed. However, you can close or minimize the dialog box and continue your work in Wise Package Studio. From this dialog box, you can view a log file for the import.

The package you selected is imported to the active Software Manager database. During the import process, errors are displayed as they are encountered.

Note

If the import fails and its log file indicates that some files cannot be found, the source file paths might be absolute or the source files might have been deleted. Verify that the source files are in the correct locations. To avoid this problem, store installations and their source files in a shared directory instead of on a local drive.

See also: Wise Task Manager in the Windows Installer Editor Help

Importing a Merge Module File

You can import a Windows Installer merge module (.MSM or .WSM) into the Software Manager database from a network or local drive. This lets you:

Software Manager Reference 31

Importing Packages

z Manage and use the shared resources in merge modules. z Add merge modules from the Software Manager database to installations in

Windows Installer Editor, if you mark Read Merge Modules List from Wise Software Repository in Wise Options.

To import a merge module file

1. If multiple databases are open, select a database in the Applications/Packages pane.

2. Select Packages menu > Import. The Import Type page appe ars.

3. Mark Import a single file into the Software Manager database.

4. In File, specify an .MSM or .WSM to import. Be sure to select the appropriate file type from the Files of type drop-down list on the Open dialog box.

5. The following items become enabled:

 Distribute source files to the share point directory

Mark this to copy all source files to a single, centralized location. Clear this check box to import the package description into the Software Manager database without copying its source files to the share point directory.

If you mark this check box, the source files are available so you can add a merge module from the Software Manager database to an installation.

 Overwrite existing application and package

Mark this to overwrite any package that is already in the database with the same application and package names.

If you clear this check box and the application and package names are already in the database:

 If the existing package has resources, the new package is not imported.  If the existing package does not have resources, the new package’s

resources are added to the existing package.

7. Click Next on the Import Type page. The Package Details dialog box appears.

8. Complete the dialog box:

 .MSM/.WSM File

The file you specified is displayed.

 Package Name

Software Manager Reference 32

For information on application and package names, see About Applications and

Packages on page 17.

Enter a unique name to identify this package. To replace an existing package, select a package from the drop-down list.

 Use Transactions for Import

9. Click Finish. The Wise Task Manager dialog box appears and remains open until the operation is

completed. However, you can close or minimize the dialog box and continue your work in Wise Package Studio. From this dialog box, you can view a log file for the import.

The package you selected is imported to the active Software Manager database. During the import process, errors are displayed as they are encountered.

See also: Wise Task Manager in the Windows Installer Editor Help

Importing a Transform File

Importing Packages

You can import a Windows Installer transform (.MST) into the Software Manager database from a network or local drive. This creates a separate package for the transform and keeps the transform’s resources separate from the resources in the base package.

T o add the transform’ s resources to the base package instead, apply the transform when you import the base installation. When you do this, you cannot distribute the transform as a separate entity.

You can distribute the transform as part of a group for easy deployment by a distribution system.

See Creating Package Groups on page 42.

Note

If you have Symantec Management Platform 7.0 SP2 or later, you can use Wise Connector to import the transform from the Software Manager databa se int o So f t ware Management Framework. Wise Connector imports the transform when it imports the base MSI package. You can then use Software Management Solution to distribute the package.

See Importing a Windows Installer File on page 29.

Options for Applying Imported Transforms

z Apply the transform to a blank Windows Installer database (schema.msi).

The resulting transform package includes additions only and excludes deletions and modifications. The transform package has no dependencies. You might use this option when you have a standard, corporate transform that you apply to all packages. (Example: General Application Registration Transforms.)

When you apply the transform to a blank Windows Installer database, you cannot resolve conflicts in or export the transform package.

Software Manager Reference 33

Importing Packages

If the transform contains file additions that are in components of the base installation, those files are not imported with the stand-alone transform package because they only apply to the specific base installation.

Example: Suppose the base package contains Component A. The transform adds File 1 to Component A, and adds File 2 to a new Component B. When you import the transform and apply it to a blank database, File 2 is imported as a resource but not File 1.

Certain transforms cannot be applied to a blank database. The transform you specify is checked before the import begins and a message appears if it cannot be applied to the blank database.

z Apply the transform to a base package.

The resulting transform package includes all additions, deletions, and modifications to the base package. The transform package is designated as a dependent of the base package.

When you apply the transform to a base package, you can resolve conflicts in and export the transform package.

You can define the state of the base package, which determines the resources that are included in the imported transform package and changes how it behaves when it is deployed.

See About Patch and Transform Import on page 26.

To import a transform file

1. If multiple databases are open, select a database in the Applications/Packages pane.

2. Select Packages menu > Import. The Import Type page appe ars.

3. Mark Import a single file into the Software Manager database.

4. In File, specify an .MST to import. Be sure to select the appropriate file type from the Files of type drop-down list on the Open dialog box.

5. The following items become enabled:

 Distribute source files to the share point directory

Mark this to copy all source files to a single, centralized location. Clear this check box to import the package description into the Software

Manager database without copying its source files to the share point directory.

Warning

If the transform contains a resource that is an output of a Visual Studio integrated project, distributing the source files breaks the integration with the Visual Studio solution.

 Overwrite existing application and package

Mark this to overwrite any package that is already in the database with the same application and package names.

Software Manager Reference 34

If you clear this check box and the application and package names are already in the database:

 If the existing package has resources, the new package is not imported.

Importing Packages

 If the existing package does not have resources, the new package’s

resources are added to the existing package.

7. Click Next on the Import Type page. The Package Details dialog box appears.

8. Complete the dialog box:

 .MST File

The file you specified is displayed.

 Application Name

To create a new application, enter a unique name. To add this package to an existing application, select an application from the drop-down list.

For information on application and package names, see About Applications and

Packages on page 17.

 Package Name

Enter a unique name to identify this package. To replace an existing package, select a package from the drop-down list.

9. Click Next on the Package Details page. The Select Target Package page appears, where you set de pen dencies for this

package.

10. Complete the page. You have two options:

 Mark Apply transform to a blank Windows Installer database to include

only additions in the transform package.

 Select the Application Name and Package Name of the base package to

include all additions, deletions, and modifications in the transform package. The drop-down lists contain only packages that are in the Software Manager

database. If the base package is not in the Software Manager database, cancel this import process and import it. If the base package you specify is a .WSI with multiple releases, select the release that this transform applies to.

11. Do one of the following:

 If you marked the Apply transform to a blank Windows Installer database

check box, click Finish on the Select Target Package page and skip the next steps.

 If you cleared the Apply transform to a blank Windows Installer database

check box, click Next on the Select Target Package page. The Select Additional Transforms page appears, listing other transform

packages in the Software Manager database.

12. To define the state of the base package, you can specify additional transforms to be applied to the base package before the transform you are importing.

 Select a transform and click one of the Move buttons to move it to or from the

Software Manager Reference 35

Transforms Not Included and Included Transforms lists.

Importing Packages

 The transforms are applied to the package in the order they appear in the list.

To rearrange the order, click Move Up or Move Down.

13. Click Finish. The Wise Task Manager dialog box appears and remains open until the operation is

completed. However, you can close or minimize the dialog box and continue your work in Wise Package Studio. From this dialog box, you can view a log file for the import.

The package you selected is imported to the active Software Manager database. During the import process, errors are displayed as they are encountered.

Note

See also: Wise Task Manager in the Windows Installer Editor Help

Importing a Windows Installer Patch File

You can import a single Windows Installer patch (.MSP) into the Software Manager database from a network or local drive. This creates a separate package for the patch and keeps the patch’s resources separate from the resources in the base package. The patch package is designated as a dependent of the base package. Y ou can distri bute the patch as part of a group for easy deployment by a distribution system.

A patch can apply to multiple packages. To apply a patch to another package, re-import the patch and specify a different base package on the Select Target Package page. The contents of this second package might differ from the first one, depending on the contents of the base packages.

You can define the state of the base package, which determines the resources that are included in the imported patch package and changes how it behaves when it is deployed.

See About Patch and Transform Import on page 26. To add the patch’s resources to the base package instead, apply the patch when you

import the base installation. When you do this, you cannot distribute the patch as a separate entity.

See Importing a Windows Installer File on page 29.

Note

If you have Symantec Management Platform 7.0 SP2 or later, you can use Wise Connector to import the patch from the Software Manager database into Software Management Framework. Wise Connector imports the patch when it imports the base MSI package. You can then use Softwa re Management Solution to distribute the package.

Software Manager Reference 36

Importing Packages

To import a Windows Installer patch file

1. Verify that the base package that the patch applies to is in the Software Manag er database.

2. If multiple databases are open, select a database in the Applications/Packages pane.

3. Select Packages menu > Import. The Import Type page appe ars.

4. Mark Import a single file into the Software Manager database.

5. In File, specify an .MSP to import. Be sure to select the appropriate file type from the Files of type drop-down list on the Open dialog box.

6. The following items become enabled:

 Distribute source files to the share point directory

Mark this to copy all source files to a single, centralized location. Clear this check box to import the package description into the Software

Manager database without copying its source files to the share point directory.

Warning

If the patch contains a resource that is an output of a Visual Studio integrated project, distributing the source files breaks the integration with the Visual Studio solution.

 Overwrite existing application and package

Mark this to overwrite any package that is already in the database with the same application and package names.

If you clear this check box and the application and package names are already in the database:

 If the existing package has resources, the new package is not imported.  If the existing package does not have resources, the new package’s

resources are added to the existing package.

7. To assign the imported package to one or more groups: a. Click Groups on the Import Type page. The Select Groups dialog box appears. b. Mark the check boxes of the groups to assign the package to. c. Click OK.

8. Click Next on the Import Type page. The Package Details dialog box appears.

9. Complete the dialog box:

 .MSP File

The file you specified is displayed.

 Application Name

To create a new application, enter a unique name. To add this package to an existing application, select an application from the drop-down list.

Software Manager Reference 37

For information on application and package names, see About Applications and

Packages on page 17.

Importing Packages

 Package Name

Enter a unique name to identify this package. To replace an existing package, select a package from the drop-down list.

10. Click Next on the Package Details page. The Select Target Package page appears, where you set de pen dencies for this

package.

11. Complete the page. The drop-down lists contain only packages in the Software Manager database that

are valid targets of the patch you are importing. If the base package is not in the Software Manager database, cancel this import process and import it.

 Application Name

Select the application that contains the base package that this patch applies to.

 Package Name

Select the base package that this patch applies to. You can apply a patch to another patch.

 Release

If the base package you specify is a .WSI with multiple releases, select the release that this patch applies to.

12. Click Next on the Select Target Package page. The Select Additional Transforms page appears, listing transform packages in the

Software Manager database.

13. To define the state of the base package, you can specify transforms to be applied to the base package before the patch you are importing.

 Select a transform and click one of the Move buttons to move it to or from the

Transforms Not Included and Included Transforms lists.

 The transforms are applied to the package in the order they appear in the list.

To rearrange the order, click Move Up or Move Down.

14. Click Finish. The Wise Task Manager dialog box appears and remains open until the operation is

completed. However, you can close or minimize the dialog box and continue your work in Wise Package Studio. From this dialog box, you can view a log file for the import.

The patch you selected is imported to the active Software Manager database. During the import process, errors are displayed as they are encountered.

See also: Wise Task Manager in the Windows Installer Editor Help

Importing Multiple Files

You can import a bat ch of package s from an y network or local di re ctory you can access. Use this method when you use the Network distribution method in Package Distribution, or when the installations are saved on a network or local directory. When you import multiple packages, all packages you specify must be of the same type. You can import multiple packages of the following types:

Software Manager Reference 38

Importing Packages

z Windows Installer installation (.MSI, .WSI) z Merge Module (.MSM, .WSM)

Note

See How to Get Packages Into the Software Manager Database on page 23.

To import multiple files

1. If multiple databases are open, select a database in the Applications/Packages pane.

2. Select Packages menu > Import. The Import Type page appe ars.

3. Mark Import multiple files into the Software Manager database. The following items become enabled.

 Distribute source files to the share point directory

Mark this to copy all source files to a single, centralized location. Clear this check box to import the package description into the Software

Manager database without copying its source files to the share point directory.

Warning

Distributing source files for a package that represents a Visual Studio integrated project breaks the integration with the Visual Studio solution.

 Overwrite existing application and package

Mark this to overwrite any package that is already in the database with the same application and package names.

If you clear this check box and the application and package names are already in the database:

 If the existing package has resources, the new package is not imported.  If the existing package does not have resources, the new package’s

resources are added to the existing package. An ex istin g pac kage mi ght not have resources if it consists only of meta data.

 Do not modify the original package

Software Manager Reference 39

Importing Packages

c. Click OK.

5. Click Next on the Import Type page. The Select Package Type page appears, containing options for the types of files you

can import.

6. Mark the option for the type of file to import and click Next. The Package Search page appears.

7. In Search Directory, specify a directory to search for files to import. To search for files in subdirectories of the directory you specify, mark Search subdirectories.

Example: If you store all installations in a default project directory under the share point directory, specify the subdirectory in which they are stored, and mark the check box to search all subdirectories of the default project directory.

8. Click Next on the Package Search page. The Packages to Import page appears, listing all packages of the specified type that

are in the directory you entered.

9. All check boxes in the Files to Import page are marked. Clear the check boxes for any packages you do NOT want to import.

The Files to Import page lists all packages of the specified format in the directory you specified, including packages you have already imported. If you don’t want to re-import those packages, either clear their check boxes on this page or back up to the Import Type page and clear Overwrite existing application and package.

10. T o import a package that is not listed on the P ackages to Import page, click Add and specify the file.

The package you specified is added to the list on the Packages to Import page with its check box marked. Repeat this step to add other files to the list.

11. Click Finish on the Packages to Import page. The Wise Task Manager dialog box appears and remains open until the operation is

completed. However, you can close or minimize the dialog box and continue your work in Wise Package Studio. From this dialog box, you can view a log file for the import.

The packages you selected are imported into the active Software Manager database. However, if you selected .VSA packages, they are converted to .WVP packages and only the .WVP packages are imported.

For information on how the application and package names are assigned, see About

Applications and Packages on page 17.

See also: Wise Task Manager in the Windows Installer Editor Help

Software Manager Reference 40

Chapter 3

Managing Packages

This chapter includes the following topics:

z Package Groups on page 41 z Viewing and Editing Package Attributes on page 45 z Viewing Resource Properties on page 46 z Software Manager Reports on page 46 z Moving a Package to Another Application on page 47 z Deleting a Package on page 48 z Changing the Package Status on page 49

About Managing Packages

After a package has been imported into the Software Manager database, you can do the following to manage it:

z Group packages for more efficient management. z View package resources, either on-screen or by running any of the predefined

Software Manager reports.

z Perform operations on .MSI or .WSI packages to add, remove, or replace merge

modules.

Note

Features that are specific to Wise Package Studio are not available when you access Software Manager from Windows Installer Editor.

Package Groups

A package group consists of a subset of the packages in the Software Manager database. It can represent a functional area within your company, any other entity that uses a subset of your packages, or a series of applications that are likely to be installed together. A group can contain a single package, and it can have many levels of subgroups.

You can use groups to:

z Organize your packages, which lets you filt er the displays and some of the reports in

Software Manager. Example: Suppose you develop applications for engineers and graphic designers.

The engineers never use the graphic designer applications, and vice versa, so you create a package group for the engineering applications and a package group for the graphic design applications. Then you can filter your resource reports by group, because it doesn’t matter whether the engineer ing applications share resources with the graphic design applications.

Software Manager Reference 41

Managing Packages

z Deploy multiple related packages at once, enforcing package dependencies and

installation order, and defining command lines that run the package installations. Example: Group a package with its related transforms and patches, specify the order in which the transforms and patches are applied, and define the command lines that are needed to run the transforms. Or, group several packages that are always installed together.

z Install packages that you would not otherwise be able to repackage and deploy.

Example: Create a group containing a single package that consists of a Setup.exe file of unknown format and the command line needed to run the .EXE.

Package Inheritance

A package group can inherit package assignments from its parent or child groups. This affects which packages are displayed when a group i s selected. The Inheritance setting on the Package Groups dialog box determines how groups inherit packages. When you delete, or unassign, a package from the group it was originally assigned to, it is also deleted from any inheriting groups.

Example: Suppose a package group named Corporate contains two child groups: Accounting and Engineering. The Engineering group contains a child group named Testing.

If your package groups are set up to inherit from both parent and child groups, then whenever you assign a package to the Engineering group, that package is inherited by the Corporate group and the Testing group. However, it is not inherited by the Accounting group.

Package inheritance is different from package relationships, which define dependencies between packages.

Creating Package Groups

Use the Groups pane in Software Manager to create and edit package groups. You can set up groups and subgroups, add packages to groups, and delete packages from groups. To show the Groups pane, select View menu > Groups.

The right-click menu provides quick access to most of the tasks that you can accomplish in the Groups pane. You also can drag packages into package groups.

To create a package group

1. If multiple databases are open, select a database in the Applications/Packages pane.

2. Select Setup menu > Groups > Edit Groups. The Edit Groups dialog box appears.

3. Verify the Inheritance setting. This affects the way package assignments are shared between groups.

Software Manager Reference 42

Managing Packages

 No inheritance from parent or child

When you assign a package to a group, the package stays within that group; it is not shared with other groups.

 Inherit from parent groups

When you assign a package to a group, that package is also assigned to that group’s child groups.

 Inherit from child groups

When you assign a package to a group, that package is also assigned to that group’s parent groups.

 Inherit from both parent and child groups

When you assign a package to a group, that package is also assigned to all parent and child groups above and below that group.

Note

The Inheritance setting affects all package groups, not just the specific group you are creating.

4. Click New Group. The New Group dialog box appears.

5. Complete the dialog box: a. In Group Name, enter a name for the new group. b. If this is a subgroup, select its parent group from Parent Name.

6. On the Edit Groups dialog box, in the Packages not in Group list, select all the packages to include in this group and click <<Move.

You can select more than one package simultaneously. To move just one package, double-click it. To remove a package from the Packages in Group list, select it and click Move>>.

7. If you add a package that has a supersedence relationship, the Superseding Packages dialog box appears, where you specify whether the package will be superseded. This dialog box also appears if you click Check Supersedence. Complete the dialog box and click OK.

See Selecting Superseding Packages on page 43.

8. When you finish defining the new package group, click OK.

Selecting Superseding Packages

In a supersedence relationship, one package replaces another package. Example: If you have two versions of the same package, you would make the latest version a dependency that supersedes the earlier version.

When a package has a supersedence relationship, you must specify whether the package will be superseded. You do this in the Superseding Packages dialog box, when add the package to a group.

It is possible to create complex supersedence relationships, in which one package might be superseded by two different packages. In such cases, you must select which superseding package to use.

Software Manager Reference 43

To select a superseding package

1. Access the Superseding Packages dialog box. On the Edit Groups dialog box, add a package that has a supersedence relationship

or click the Check Supersedence button. See Creating Package Groups on page 42. On the Superseding Packages dialog box, the packages in the group are at the top

level of the tree. Superseding packages are listed below the top level.

2. For each top-level package, select its superseding package by marking its check box. To prevent the top-level package from being superseded, mark th e top-level check box.

3. Click OK. The group is updated. This does not affect the package relationships in other

groups.

Adding Applications and Packages to Groups

In Software Manager, you can add applications and packages to groups in several ways. When you add an application or package to a group, the application or package might

also be added to parent or child groups, depending on the Inheritance setting on the Edit Groups dialog box.

Managing Packages

z During the Import wizard

On the Import T ype page, click Groups. On the Select Groups page, mark the check boxes of the groups to assign the package to.

See Package Import on page 25.

z On the Edit Groups dialog box

In the Groups pane, right-click a group and select Edit Groups. Use the Move buttons to move packages back and forth between the Packages in Group and Packages not in Group lists.

See Editing Package Groups on page 44.

z In the Groups pane

Drag the entire application or package over a group name in the Groups pane. You can select multiple applications or packages.

Editing Package Groups

In Software Manager, you can edit a package group to add or delete packages or assign the group to a different parent group.

To edit a package group

1. If multiple databases are open, select a database in the Applications/Packages pane.

2. In the Groups pane, right-click a group and select Edit Groups. The Edit Groups dialog box appears, with the selected group displayed.

3. Edit the package group in any of the following ways.

Software Manager Reference 44

 Use the Move buttons to move packages back and forth between the Packages

in Group and Packages not in Group lists.

 Select a different parent group from Parent.  Delete the group by clicking Delete Group.  Change the package inheritance by making a new selection in Inheritance.

This affects all groups, not just the one you are editing.

 When you add a package that has a supersedence relationship or click the

Check Supersedence button, the Superseding Packages dialog box appears. Complete the dialog box and click OK.

See Selecting Superseding Packages on page 43.

4. When you finish editing the package group, click OK.

Viewing and Editing Package Attributes

To view and edit package attributes

1. If multiple databases are open, select a database in the Applications/Packages pane.

Managing Packages

Note

Be sure to click a package; you cannot display attributes for an application.

2. Select Packages menu > Attributes. The Package Attributes dialog box appears.

3. Click the General tab and view or edit the following information.

 Application

Change this to rename the application in the Software Manager database. This changes the application name for the selected package only and not for other packages within the application. If an application with this name already exists in the Software Manager database, this package is moved to that application. If that application already has a package with the same name, a 1 is added to the name of the package you move.

This does not change the application name in the installation file.

 Package

Change this to rename the package in the Software Manager database. This does not change the package name in the Workbench project or the installation file.

 Package Meta Data

The Package Meta Data section contains both predefined and custom meta data fields. To edit custom meta data, click in the Value column and enter or select a value. If the field requires a URL, include http:// or other tag (mailto:, ftp:, file:) so that the field will become an active hyperlink on the Package pane.

Software Manager Reference 45

The predefined meta data is read-only. To edit predefined meta data, use the Product Details page in Windows Installer Editor.

If no meta data values are enabled, it means that custom meta data fields hav e not been defined.

See Defining Custom Meta Data Fields on page 19.

4. Click the Source tab and view or edit the following information.

 Installation File

Edit to change the location of the package installation file. You might need to do this if the server is renamed or reorganized.

Note

Selecting a new file location here does not move the installation file or its source files. You must redistribute the package installation to the new location.

 Transforms and Patches applied

Lists the transforms and patches that were applied to the package in the order in which they were applied (read-only).

5. Click OK.

See also:

About Package Meta Data on page 18

Managing Packages

Viewing Resource Properties

In Software Manager, you can view properties for any package resource item by displaying a read-only Properties dialog box, which shows additional information about the resource.

To view resource properties

1. If multiple databases are open, select a database in the Applications/Packages pane.

2. In the Applications/Packages pane, expand a package to display its resource folders.

3. Expand the resource folder until the resource items are displayed in the Package Details pane.

4. In the Package Details pane, double-click the resource item for which to view properties.

The Properties dialog box appears. The information on the dialog box differs depending on the type of resource you are viewing; typically it includes resource details and conflict information, if any.

Software Manager Reports

Software Manager lets you generate reports that provide information about the packages in the Software Manager database.

Note

When you install Wise Package Studio, triggers are added to the Software Manager database. Because the default SQL Server backup process does not include triggers, you should change your backup configuration to include them.

Software Manager Reference 46

Managing Packages

Report Name Reports Menu

Command

Package Contents Summary

Package Contents by Feature

Package Cont ents > Summary

Package Contents > By Feature

What This Report Does

Lists detailed information for every resource in an installation, including files, registry keys, shortcuts, file associations, and merge modules. Y ou can generate this report for .WSI, .MSI, .WSM, and .MSM files.

Contains the same information as the Package Contents Summary report, but arranges it by feature. You can generate this report for .WSI and .MSI files.

Generating a Software Manager Report

To generate Package Contents reports

If a package’s path to its installation file is missing or broken, you cann ot generate thes e reports.

1. From the Reports menu, select a report. The Select Package dialog box appears. For the Package Contents Summary report,

it lists all .WSI, .MSI, .WSM, and .MSM packages in the selected database that have resources. For the By Feature report, it lists all .WSI and .MSI packages that have resources.

2. Select a package and click OK. The report is generated and opens in a dialog box.

Use a report’s table of contents to quickly access information about a specific type of resource. You can print the report or save it as an HTML or XML file.

Using the Report Viewer

After you generate a report, it is displayed in a report viewer window.

z To save a report, click Save As in the lower right of the report viewer window. You

can save a report in HTML, XML, or CSV format. When you save a report as HTML, an HTML file is created for each page of the report, and each file has the same name with its page number appended.

z To print a report, click Print in the lower right of the report viewer window. z The date and time when the report was generated appears in the lower left corner of

the report.

z To perform a text search, click on the report and press Ctrl+F.

Moving a Package to Another Application

You can mov e a package from one application to another. This is helpful if two packages for the same application are imported with different application names. (Example: If Office 2000 and Office 2003 are imported as separate applications.)

Software Manager Reference 47

To move a package to another application

1. If multiple databases are open, select a database in the Applications/Packages pane.

2. In the Applications/Packages pane, click the package to move.

3. Select Packages menu > Attributes. The Package Attributes dialog box appears.

4. In Application, enter the name of the application where you want to move the package.

5. Click OK. The package is moved to the application you specified. If that application already

has a package with the same name, a 1 is added to the name of the package you move.

This does not change the application name in the installation file.

Deleting a Package

You can delete a package from the Software Manager database. However, the Software Manager database should contain all packages used by your organization, even those that are obsolete.

Managing Packages

Deleting a package from the Software Manager database removes information about that package from the database. It does not delete the original package file from any of the share point directories, such as the Scripts directory or your default project directory.

To delete a package, you must have the package checked out of revision control. If the package is checked into revision control or another user has the package checked out, you will not be able to delete the package.

Warning

Deleting a package cannot be undone.

To delete a package

1. If multiple databases are open, select a database in the Applications/Packages pane.

2. Select Packages menu > Delete. The Delete Packages dialog box appears.

3. Select one or more packages to delete.

4. To delete the package’s source files from the share point directory (the 000, 001, etc. subdirectories), mark Delete source files from the share point directory if they are not referenced by other packages. Source files are deleted only if they are not referenced by any other packages in the current Software Manager database.

Software Manager Reference 48

Warning

If you delete a package’s source files, you will never be able to recompile that package because the source paths in the installation will refer to files that no longer exist. Delete source files only when you are sure you will not need to compile the package again.

5. Click OK. The packages you selected are deleted from the database.

Changing the Package Status

Use Software Manager to maintain the status of packages in the Software Manager database. The package status helps you determine whether a package is ready to be deployed to end users.

In Windows Installer Editor, when you open an Available package from the Wise Software Repository, you are prompted to change the status to Under Development.

To change the package status

1. If multiple databases are open, select a database in the Applications/Packages pane.

Managing Packages

2. In the Applications/Packages pane, click a package. Information about that package appears in the Package pane.

3. If necessary , sh ow the Pa ckage pane by selecting View menu > Application/P ackage Summary

4. The Package pane displays one of these statuses in Package Status:

 New

This status is assigned when the package meta data is added from within Windows Installer Editor, but its resource information has not been imported. It is also assigned when a Wise package definition file is imported from Workbench.

You cannot change to or from this status manually. A New package is changed to Under Development only when you use the Import Wizard to import its resource information.

 Under Development

The installation is still being developed. You might need to check the package for conflicts and perform testing before

deploying it to end users. Packages are assigned this status when they are imported to the Software Manager database.

 Available

The package is ready for deployment or has been deployed. When you change a package’s status to Available, the installation and its associated files are copied to the Available Packages directory, and the installation file is set to read-only.

 Retired

Software Manager Reference 49

The package is no longer used in your organization. Why should you keep an obsolete package in the Software Manager database?

When a legacy application that you no longer deploy is still in use in some

limited cases, you need to ensure that new applications don’t break the legacy application.

5. To change to a different status, select it from Package Status.

Managing Packages

Software Manager Reference 50

Chapter 4

Software Manager Database Maintenance

This chapter includes the following topics:

z About Software Manager Database Maintenance on page 51 z Changing the Server Path on page 51 z Deleting a Server Path on page 53 z Restructuring the Index on page 53 z Rebuilding the Index on page 54

About Software Manager Database Maintenance

Software Manager has a Network Index Properties dialog box that lets you maintain the server path and database index of the Software Manager database.

z The server path is where files associated with an installation are stored. If the drive

with the original server path becomes full, you can create a new server path on a different drive and set it as the new default.

See Changing the Server Path.

z The database index is wamdb.idx. You can restructure t he index or rebuild the index

if it becomes corrupted. See Restructuring the Index on page 53 and Rebuilding the Index on page 54.

Only a database administrator or someone under the guidance of a database administrator should perform database maintenance.

Warning

Do not change the contents of Index Location on the Network Index Properties dialog box. Changing this field changes the share point value. Only change the share point value in the Wise Repository Manager.

To create and configure Software Manager databases, use the Wise Repository Manager. (The Wise Repository Manager is avai lable on the Wise P ackage Studio s erver only.) See

Managing the Wise Software Repository in the Wise Package Studio Getting Started Guide.

See also:

Deleting a Server Path on page 53

Changing the Server Path

The Software Manager server path contains the subdirectories in which the source files associated with an installation package are stored. Initially, the server path is the same

Software Manager Reference 51

Software Manager Database Maintenance

as the share point directory. However, you can add new server paths. You might do this if you distribute a large number of packages to the share point directory, and the drive containing the share point directory becomes full. When that happens, you can create a new directory on another network drive and set the new location as the active server path. The server path information is stored in the index file, wamdb.idx, which remains in the original share point directory.

Software Manager can support up to 255 different server paths, but only one path can be active at a time. When you distribute to the share point, the package’s source files are placed in the active server path.

After you set a new active server path, when anyone distributes to the share point directory, the source files associated with the package are stored in the new active server path location. The .QUE file and, in some cases, the related package installation file, are stored in the Scripts directory under the original share point. Using an additional server path does not result in duplicate files. The files are still indexed to prevent file duplication across all server paths.

Warning

To change the active server path

1. Select Setup menu > Network Index Properties. The Network Index Properties dialog box appears.

2. Click Add. The Choose Server Path dialog box appears.

3. In Select Path, specify the new server path. Click OK to return to the Network Index Properties dialog box.

4. In the Storage Paths list, select the new server path and click Details. The Server Path Settings dialog box appears.

5. Mark Active Path and click OK to return to the Network Index Properties dialog box.

The “Yes” in the Active column nex t to the new server path name indicates that this is now the active server path.

6. Click OK.

Whenever someone distributes to share point directory, the source files will be stored in the new path location.

See also:

How Source Files Are Indexed on page 16

Software Manager Reference 52

Deleting a Server Path

You can delete a Softwa re Manager ser ver path, bu t only i f you h av e not y et adde d dat a to it. Do this if you add a new server path in the Network Index Properties dialog box, then realize that you mis-typed the name or selected the wrong path. This does not delete the directory path from the computer; it only deletes the path from Software Manager. You cannot delete a server path that is active or that contains files.

Warning

To delete a server path

1. Select Setup menu > Network Index Properties. The Network Index Properties dialog box appears.

2. If the server path you want to delete is currently active, set a different path to be the active one:

Software Manager Database Maintenance

a. In the Storage Paths list, select the server path to make active and click

Details.

b. On the Server Path Settings dialog box, mark Active Path and click OK to

return to the Network Index Properties dialog box.

3. In the Storage Paths list, select the server path to delete and click Delete. The path is removed from the Storage Paths list.

4. Click OK.

See also:

Changing the Server Path on page 51

Restructuring the Index

Note

This procedure is intended for database administrators.

After you have used Software Manager for some time, if distribution to the share point directory runs slower than it did at first, you might want to restructure the index by increasing the index block size, the hash table size, or both. This changes the index file, wamdb.idx.

Warning

Software Manager Reference 53

Software Manager Database Maintenance

To restructure the index

1. Select Setup menu > Network Index Properties. The Network Index Properties dialog box appears.

2. In the Rebuild Index Settings section:

 Location

Leave this field blank.

 Block Size

To increase the block size, select a higher number.

 Hash Table Size

To increase the hash table size, enter a higher number.

3. From Method, select Rebuild using existing index file (not corrupt).

4. Click Build. The index is restructured. This can take a long time, depending on the size of the

database.

5. When the Rebuild is Complete message appears, click OK.

See also:

How Source Files Are Indexed on page 16

Rebuilding the Index

Note

This procedure is intended for database administrators.

If you encounter errors, such as the in ability to c opy files, while distributing to the share point directory, the database index is probably corrupt. To resolve the database corruption and eliminate the distribution errors, you should rebuild the index (wamdb.idx).

Warning

To rebuild a corrupt index

1. Select Setup menu > Network Index Properties. The Network Index Properties dialog box appears.

2. From Method, select the method to use to rebuild the index; do not make any other changes in the dialog box.

 Rebuild using existing index file (not corrupted)

Software Manager Reference 54

Mark this when the index file is not corrupted but you need to rebuild it because you chan ged the Block Size or Hash Table Size.

See Restructuring the Index on page 53.

Software Manager Database Maintenance

 Rebuild using file/directory structure

When you mark this, the rebuild process reads all files and directories in the share point directory and all its server paths in the Storage Pat h s list. This method is recommended because it gathers all possible data from the Software Manager database.

 Rebuild using database data

This method is provided for backward compatibility with earlier versions of Wise Package Studio. Mark this only if all the packages that have distributed to the share point directory have been imported into Software Manager. Because this method only reads the Software Manager database, it does not record packages that have been distributed but not imported. This is the slowest method of rebuilding the index.

3. Click Build. The index file is rebuilt. Expect this process to take a long time, even an hour or

more, depending on the size of the database.

4. When the Rebuild is Complete message appears, click OK.

See also:

How Source Files Are Indexed on page 16

Software Manager Reference 55

Index

Numerics

000 directory 16

application

about 17 adding to group 44 naming 17

renaming 45 Application Summary pane 11 Application/Package Summary

pane 11 Applications/Packages pane

about 11 apply during import

patch 29

transform 29 attributes, package

editing 45 available package status 49

base package

applying patch 29

applying transform 29, 34

defining state 26

customize workspace 11

database index 16

block size 53

corrupted 54

rebuilding 54

restructuring 53 Database pane 10 database, Software Manager

See Software Manager database database, Wise Software Repository

See Software Manager database database, Workbench

See Workbench database delete

package from database 48 documentation, Wise 21

file location, changing 51 formatted text string 24

Getting Started Guide 22 group, package

about 41 adding packages 44 creating 42 editing 44 inheriting package 42, 42

Groups pane 11

hash table size 53 help

about 22 using 22

icons

relationship 13 resource 13 Software Manager 12

import

about 25 from share point 27 merge module 31, 39 MSI 29, 39 MSM 31, 39 MSP 36 MST file 33 multiple files 38 patch 36 transaction 31, 33 transform 33 when to import 24 Windows Installer file 29, 39 WSI 29, 39

WSM 31, 39 Import Wizard 25 index

block size 53

corrupted 54

rebuilding 54

restructuring 53 index, database 16 inheritance, group 42, 42

Also see package inheritance installation file location, changing 46

launch Software Manager 9

main window 10

manual, reference 22 merge module

importing 31 importing multiples 39 resouces 9

meta data

about 18 adding to database 23 custom 19 examples 19 predefined 19, 20 tooltip text 20 when to add to database 24

meta data field

changing 20 defining 19 deleting 20

meta data type

adding custom 21 changing 21

deleting 21 MSI file, importing 29, 39 MSM file, importing 31, 39 MSP file, importing 36 MST file, importing 33 multiple files, importing 38 multi-user environment 15

Network Index Properties

about 51

adding server path 52

deleting server path 53

rebuilding index 54

restructuring index 53 new features

Refer to Release Notes new status 49

package

about 17

adding to group 44

Also see base package

attributes, editing 45

defined 8

deleting from database 48

getting into Software Manager 23

moving 47

naming 17

renaming 45 Package Contents by Feature

report 47

Software Manager Reference 56

Package Contents reports 47 Package Contents Summary report 47 Package Details pane 11 package import

See import package inheritance 42, 42 package resources

Also see resource

viewing 9 Package Summary pane 11 patch

applying to base 29

importing 36

options for import 26 properties

resource 46

QUE file

about 29

readme

See release notes rebuild index 54 reference manual 22 refresh display 11 registry key

formatted text string 24 relationships, package

icons 13 release notes 22 rename

application 45

package 45 report

predefined 47

printing 47

text search, performing 47

viewer 47 repository

See Wise Software Repository repository database

See Software Manager database resource

icons 13

properties 46

viewing 9 restructure index 53 retired package status 49

schema.msi 33 Scripts directory 29 server path

active 52

adding 51

changing 51 deleting 53

share point directory

importing from 27 Scripts subdirectory 29 temporary file 29

Software Manager database 15

about 15 sharing with developers 16

Software Manager window

about 10 customizing 11 refreshing 11

toolbar 10 Software Manager, about 8 source file

indexing 16 source files

changing location 51

deleting 48 SQL Server

backing up triggers 46 start Software Manager 9 status, package

about 49

changing 49 superseding package 43 system requirements, Wise product

Refer to Getting Started Guide

temporary package file 29 toolbar

hiding 11

Software Manager 10 transactions for import 31, 33 transform

applying to base 29, 34

applying to blank database 33

importing 33

options for import 26 triggers

adding to backup process 46

under development package status 49

wamdb.idx

about 16

corrupt 54

rebuilding 54

restructuring 53 Windows Installer file

importing 29

importing multiples 39 Wise Services database

about 15

Wise Software Repository

about 14

Wise Software Repository database

See Software Manager database

Workbench database

defined 15 WSI file, importing 29, 39 WSM file, importing 31, 39

Software Manager Reference 57

Symantec SOFTWARE MANAGER 7.0 SP2 - REFERENCE FOR WISE INSTALLATION STUDIO V1.0, SOFTWARE MANAGER Installation Manual

Specifications and Main Features

Frequently Asked Questions

User Manual