wise package studio, version 5 - danysoft · wise package studio, version 5.0 ... and a tutorial....

Wise Package Studio, Version 5.0

Copyright© 2001-2003 Wise Solutions, Inc. All Rights Reserved.

This documentation and the accompanying software are copyrighted materials. Making unauthorized copies is prohibited by law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system or translated into any human or computer language without prior written permission of Wise Solutions, Inc. Wise Solutions, Inc. asserts its �Moral Right� to be identified as the author of this work, in all jurisdictions which recognize the �Moral Right.�

NoticeUNLESS OTHERWISE PROVIDED BY WRITTEN AGREEMENT WITH WISE SOLUTIONS, INC., THIS PUBLICATION, AND THE SOFTWARE SOLD WITH THIS PUBLICATION, ARE PROVIDED �AS IS� WITHOUT WARRANTY OF ANY KIND EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK ARISING OUT OF THE USE OR PERFORMANCE OF THIS PUBLICATION AND SOFTWARE REMAINS WITH YOU. IN NO EVENT WILL WISE SOLUTIONS, INC., OR ANY OF ITS SUPPLIERS, BE LIABLE FOR ANY LOST PROFITS, LOST SAVINGS, DIRECT, INCIDENTAL OR INDIRECT DAMAGES OR OTHER ECONOMIC OR CONSEQUENTIAL DAMAGES, EVEN IF WISE SOLUTIONS, INC., OR ITS SUPPLIERS, HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. WISE SOLUTIONS, INC. RESERVES THE RIGHT TO MODIFY THIS DOCUMENT AT ANY TIME WITHOUT OBLIGATION TO NOTIFY ANYONE. IN NO EVENT SHALL WISE SOLUTIONS, INC.�S OR ITS SUPPLIERS� LIABILITY UNDER THIS AGREEMENT EXCEED THE SUM OF ANY AMOUNTS PAID HEREUNDER BY THE CUSTOMER TO WISE OR THE SUPPLIER.

TrademarksWise Solutions, Inc. owns a number of registered and unregistered Trademarks and Service Marks (the �Marks�). These Marks are extremely valuable to Wise Solutions, Inc. and shall not be used by you, or any other person, without Wise Solutions, Inc.�s express written permission. The Marks include, but are not necessarily limited to the following: Application Isolation Wizard�; ApplicationWatch�; ConflictManager®; ExpressBuild�; Installation Development Life Cycle�; InstallBuilder®; InstallMaker®; InstallManager®; InstallTailor�; MSI Debugger�; MSI Script�; PackageManager�; Preflight Deployment�; SetupCapture®; SmartMonitor�; SmartPatch®; Software Distribution Made Easy�; Software Installations Made Easy®; Visual MSIDiff�; Virtual Capture�; WebDeploy�; Wise Installation System®; Wise Package Studio®; Wise Software Repository�; Wise Solutions®; WiseScript�; WiseScript Express�; WiseUpdate®; WiseUser®; and the Wise Solutions logo.

In addition to Wise Solutions, Inc.�s Marks, some Wise Products may include Trademarks or Service Marks owned by other corporations. These other Marks include, but are not necessarily limited to Microsoft® Windows® and Microsoft® Visual Studio® .NET, which are registered Trademarks of Microsoft Corporation.

You shall not use any of the Trademarks or Service Marks of Wise Solutions, Inc., Microsoft Corporation, or any other entity, without the express written permission of such Trademark or Service Mark owner.

Wise Solutions, Inc.47911 Halyard DrivePlymouth, Michigan 48170 USAPhone: 734-456-2100 � Fax: 734-456-2456E-mail: [email protected] � Web: www.wise.com

2

http://www.wise.com

Contents

1 Welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Documentation Roadmap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Getting Help and Product Support . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Getting Updates Over the Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2 Installing Wise Package Studio . . . . . . . . . . . . . . . . 11System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Wise Package Studio Requirements . . . . . . . . . . . . . . . . . . . . . . .12Web Applications Requirements . . . . . . . . . . . . . . . . . . . . . . . . .14.NET Framework System Requirements . . . . . . . . . . . . . . . . . . . .15

Before You Install Wise Package Studio . . . . . . . . . . . . . . . . . . . . . .16Gather Information You Might Need. . . . . . . . . . . . . . . . . . . . . . .16

What Do You Want to Install? . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18Database Configuration for Web Applications . . . . . . . . . . . . . . . .21Choosing the Location for the Share Point Directory . . . . . . . . . . .22Setting Up Database Connections and Authentication . . . . . . . . . .23

Installing Wise Package Studio in a Client-Server Configuration. . . . . .28About the Client-Server Configuration of Wise Package Studio . . . .28Installing Wise Package Studio Client. . . . . . . . . . . . . . . . . . . . . .29Installing Wise Package Studio Client Silently . . . . . . . . . . . . . . . .30

Application Gateway Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Integrating Application Gateway and Wise Package Studio . . . . . . .32Bypassing the Proxy Server for Application Gateway . . . . . . . . . . .34Configuring IIS for Application Gateway . . . . . . . . . . . . . . . . . . . .35

Starting Wise Package Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36If Your Logon Fails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36Wise Package Studio Logon Options . . . . . . . . . . . . . . . . . . . . . .37

Registering Your Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

3 Tutorial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

4 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

3

Contents

4

Chapter 1Welcome

Wise Package Studio® is designed to help system administrators and desktop integration labs streamline the process of packaging software applications for delivery to end users. It encompasses all phases of an application�s lifecycle, starting with the user�s request, continuing with repackaging, and ending with testing and distribution.

Wise Package Studio improves on traditional packaging practices by combining best practice methodologies with industry-leading software installation technology. In addition, software packages created with Wise Package Studio can be distributed through many of the leading software distribution products currently on the market.

Topics include:

! Documentation Roadmap.

! Getting Help and Product Support.

! How to Check Online Help.

! Getting Updates Over the Web.

5

1: Welcome

Documentation RoadmapThe Wise Package Studio 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 Wise Package Studio.

Online Help

The online help contains detailed technical information and step-by-step instructions for performing common tasks. For details on using help, see Check Online Help on page 7.

Reference Manuals

All the material in the online help is also available in .PDF-format reference manuals. Reference manual .PDFs are provided for Wise Package Studio, Software Manager, ConflictManager, WiseScript Editor, and Windows Installer Editor. To access the .PDF reference manuals, select Help menu > Reference Manual from within each Wise Package Studio module.

Getting Started

The printed Getting Started Guide contains system requirements, installation instructions, and a tutorial. To access a .PDF version of the Getting Started Guide, in Wise Package Studio, select Help menu > Getting Started.

Release Notes

A release notes document, in .HTM format, covers new features, enhancements, bug fixes, and known issues for the current version of this product. It also contains links to release notes for other versions. Access the release notes in the following ways:

! Browse the product CD.

! In Wise Package Studio, select Help menu > Release Notes.

! If you are a registered user, visit http://support.wise.com to enter the Support Center, and then click the Downloads link.

Windows Installer SDK Help (Windows Installer Editor only)

You can get technical details about Windows Installer from its own help system, which is written by Microsoft for a developer audience. Select Help menu > Windows Installer SDK Help in Windows Installer Editor.

6

http://support.wise.com

Getting Help and Product Support

Getting Help and Product SupportWise Solutions offers many resources to help you use our products. You can search the product help or reference manual .PDF for answers, or you can use one of the many support resources available to you as a registered Wise Solutions customer.

Check Online Help

You can access help in the following ways:

! To display context-sensitive help for the active page or dialog, press F1.

! To select a help topic from a table of contents, index, or search, select Help menu > Help Topics.

Select other commands from the Help menu to view the .PDF-format reference manual or getting started guide, to view Wise Solutions resources on the Web, or to upgrade to the latest point release. Windows Installer Editor has an additional option in the Help menu for displaying the Windows Installer SDK Help.

If you need help and cannot find the answer in the documentation, read about our technical support options below.

Use the Wise Solutions Technical Support Center

Registered Wise Solutions customers can use the Technical Support Center, located at http://support.wise.com, to submit online support requests, register products, manage customer information, download updates, or search the Knowledgebase. The Knowledgebase contains how-to procedures, answers to common support questions, and workarounds.

Visit Our Newsgroups

Visit Wise Solutions Newsgroups at www.wise.com/newsgroups.asp. Newsgroup postings by your peers contain answers, tips, analysis, and other comments. Contribute your own expertise to help others.

Subscribe to TechInfo

TechInfo is a free e-mail newsletter that contains technical tips, product updates, and other important technical information. To subscribe or to read back issues, visit www.wise.com/techinfo.asp.

Ask Our Support Team

If you can�t find an answer in our online resources, you can obtain support by phone or online at http://support.wise.com. Wise Solutions offers flexible payment options to meet your support needs. For additional details

7


http://www.wise.com/newsgroups.asp

http://www.wise.com/techinfo.asp


1: Welcome

about our support services, see www.wise.com/supportoptions.asp or call 1-734-456-2600.

Before you contact technical support, obtain the following:

! Serial number and product version, which you can find by selecting Help menu > About.

! Operating system version and service pack version if applicable.

! A description of what you do before the problem occurs.

! The text of any error messages that appear.

! Your name, company name, and how to contact you.

! Contract number or payment information, if applicable.

Take Advantage of our Consulting and Training Services

When you have a challenging repackaging or installation problem, turn to Wise Solutions. Our consultants can help with script writing, repackaging, installation development, and other solutions that are fully customizable to fit your project and budget. Visit www.wise.com/consulting.asp for details.

To upgrade your installation and packaging skills, consider Wise Solutions training. Our certified instructors draw from practical experience to provide relevant course content. Visit www.wise.com/training.asp for course descriptions and schedules.

Contact Wise Solutions Sales

Contact Wise Solutions� Sales department to purchase additional products,

upgrades, support services, or consulting and training services.

U.S.: 1-800-554-8565

Europe/Netherlands: +31 70 392 72 20

Other International: 734-456-2100 (in U.S.)

Web Site: http://www.wise.com/ordercentermain.asp

8

http://www.wise.com/supportoptions.asp

http://www.wise.com/consulting.asp

http://www.wise.com/ordercentermain.asp

http://www.wise.com/training.asp

Getting Updates Over the Web

Getting Updates Over the WebYou can get the latest version of Wise Package Studio using your active Internet connection. Minor point releases (x.01, x.02, and so on) are generally free, while major number releases generally incur an upgrade fee. Point releases generally contain maintenance updates such as bug fixes and minor feature additions.

To check for updates:

1. Connect to the Internet.

2. In Wise Package Studio, select Help menu > Check for Updates.

A confirmation prompt appears, then you are connected to the Wise Solutions Web site.

� If you have not registered this product, follow the screen prompts to create a user account with Wise and register. You will need a valid product serial number. After you complete the registration, enter the Wise Technical Support Center and click the Downloads link.

� If you have registered this product, you are connected to the Downloads page.

3. Follow the instructions on the Web page to download the appropriate update.

NoteWise Package Studio can remind you to check for updates. On the Workbench Preferences dialog > General tab, select an option in Check for Updates. This sets the frequency at which you will be reminded to check for updates.

9

1: Welcome

10

Chapter 2Installing Wise Package Studio

Wise Package Studio is comprised of several software components. Refer to the information in this section to before installing Wise Package Studio. Learn about system requirements, product configurations, and specific options to achieve your installation goals.

11

2: Installing Wise Package Studio

System RequirementsYou can install different modules of Wise Package Studio. There are separate requirements for Web applications, and small differences for some modules.

Wise Package Studio Requirements

NoteWise Package Studio cannot be installed on any computer that contains the Enterprise Editions of Wise for Visual Studio .NET 5.x or Wise for Windows Installer 5.x.

The requirements below apply to the following, except as noted:

! Wise Package Studio Standard Edition

! Wise Package Studio Professional Edition

� Client: Full or Minimal

� Complete

! Wise Package Studio Quality Assurance module

12

System Requirements

Installations you create using Wise Package Studio can be run under the following operating systems:

! Windows® 95 or later

! Windows NT 4.0 or later.

For operating systems before Windows Me or Windows 2000, Windows Installer is not included by default, so make sure it is installed before running .MSI-based installations. Use the option for pre-installing Windows Installer located on the Build Options page in Windows Installer Editor.

Wise Package Studio Requirement

Value

Computer/Processor Pentium II, 450 MHz

Operating system Windows® 98 or later*Windows NT 4.0 SP6** or later

* Windows Me or later required for Enterprise Management Server module.** Windows Installer 2.0 requires Service Pack 6 on Windows NT 4. Service pack 6a is recommended.

Microsoft Internet Explorer

5.01 SP 2

RAM 128 MB minimum, 256 MB recommended

Free space on boot drive 150 MB

Free space on installation drive

150 MB*

* Negligible space required for Client installation.

Database (does not apply to Standard Edition)

Microsoft Access drivers, orSQL Server 7.0 (2000 recommended), orMSDE*

* To initially create databases, SQL or MSDE client tools required.

13


Web Applications Requirements Following are system requirements for Wise Package Studio Web applications. You have these Web applications only if you purchased the following:

! Management Reports Web application: included with Enterprise Management Server module.

! Application Gateway Web application: included with Application Gateway module.

! Preflight Web applications (Preflight Data Collector and Preflight Analysis): included with Quality Assurance module.

Also see Database Configuration for Web Applications on page 21.

Web Application Requirement

Value

Computer/Processor Pentium III, 800 MHz

Operating system As required by Microsoft InternetInformation Server

Microsoft Internet Information Server (IIS)

4.0 or later required/5.0 recommended

Microsoft Internet Explorer

5.01 SP 2*

* Required for client computers that connect to Web applications.

RAM 128 MB minimum, 256 MB recommended

Free space on boot drive 150 MB

Free space on installation drive

10 MB

Database (Does not apply to Standard Edition)

Microsoft Access drivers, orSQL Server 7.0 (2000 recommended), orMSDE*

* SQL or MSDE is required for Preflight, and is highly recommended for Application Gateway and Management Reports.

14

System Requirements

.NET Framework System RequirementsThe .NET Framework is required for advanced .NET support in Windows Installer Editor. If the .NET Framework is not installed on your computer, download it from Microsoft�s Web site and install it. The .NET Framework requires Microsoft® Internet Explorer 5.01 or later and one of the following operating systems:

! Microsoft® Windows® 98 or later

! Windows NT® 4 (Service Pack 6a) or later

15


Before You Install Wise Package Studio! You can install different configurations of Wise Package Studio. See

What Do You Want to Install? on page 18 for a summary of all the options.

! You must determine where to locate your share point directory, which is dependent on your team configuration; see Choosing the Location for the Share Point Directory on page 22.

! Based on the installation type, you need to gather information from a team leader, system administrator, database administrator, or other team members. See Gather Information You Might Need.

! If you are installing the Professional Edition and you plan to create databases on a SQL Server or MSDE database server, then either your currently logged in user profile must have database administrator privileges on the database server, or you must have the SQL user name and password of a database administrator available.

Gather Information You Might Need! Have serial numbers available during installation. If this is an upgrade,

you also need the serial number of the previous version. You can find this by opening the previous version of Wise Package Studio and selecting Help menu > About.

! If you are installing the Professional Edition, obtain the following information about the databases you are using:

� What share point directory your team is using. All users, during installation, should designate the same share point for storing project and application data. This allows all users to have access to the same data. See Choosing the Location for the Share Point Directory on page 22.

If you have been using an older version of Wise Package Studio, you can use your existing share point, but data will be updated to a new format.

� Learn what kind of database your organization is using for Wise Package Studio databases: Microsoft Access, MSDE, or Microsoft SQL Server.

� You need the database name, the server name that contains the database, and the authentication method (NT or SQL Server) the database uses.

� Find out whether the database has been created or whether you need to create it during installation. If it does not exist or needs to

16

Before You Install Wise Package Studio

be upgraded, you need database administrator privileges to create or upgrade it.

� If you plan to use a SQL Server or MSDE database server that uses SQL Server authentication, then you might need to assign users to the database you are creating during installation. These users will have access to the database you create. You need to know what user IDs to create.

17


What Do You Want to Install?

Wise Package Studio Standard Edition

Wise Package Studio Standard Edition consists of the Workbench interface along with tools for package creation. Standard Edition can only be installed in one basic configuration.

Wise Package Studio Professional Edition

Wise Package Studio Professional Edition consists of the Workbench interface along with tools for package creation and conflict resolution. You can install Wise Package Studio Professional Edition in several different configurations and can purchase additional modules that extend its functionality:

Wise Package Studio Professional Edition has three main options: Complete, which installs Wise Package Studio locally on this computer, or on a packaging server where it can be used by Wise Package Studio Client installations; Client, which installs shortcuts and system files and runs the actual application files from a server; and Web, which installs Web applications only. Web only appears if IIS is installed and if you�ve entered at least one serial number the includes a Web application.

! Complete.

� Install locally using MS Access without sharing data. You must have Microsoft Access drivers installed. Choose Complete for installation type and choose Access for database type.

� Install locally without sharing data but create a SQL or MSDE database. A computer on your network must have SQL or MSDE Server installed, and you must have DBA privileges to create new databases on it. Choose Complete for installation type and choose SQL/MSDE for database type.

� Install Locally and create a shared SQL database. Do this if you are installing the first copy of Wise Package Studio in your workgroup and if you plan to use a SQL or MSDE database server to store data. Before installing, create a shared directory. During installation, choose Complete for installation type, choose the shared directory for the Wise Share Point, and choose SQL/MSDE for database type. You must have DBA privileges to create new databases on the database server.

� Install on a server where others can run it. Do this if you plan to install Wise Package Studio client later, which installs shortcuts that point to Wise Package Studio application files on a server. Before installation, create two shared directories: one to serve as the share

18


point directory and one to serve as the Wise application files directory. During installation, choose Complete and specify the two shared directories in UNC or mapped drive notation.

! Client. See About the Client-Server Configuration of Wise Package Studio on page 28.

� Full Client. Do this if you already installed the Complete configuration of Wise Package Studio on a server. This installs shortcuts, which point to Wise Package Studio application files on a server, and necessary system files. During installation, choose Client, then choose Full Client. Choose the same directories for Wise Share Point and for Wise Package Studio Directory that were chosen during the server installation.

� Minimal Client. Do this if you already installed the Complete configuration of Wise Package Studio on a server. Use this option if you only need to capture installations. This keeps the repackaging computer clean. This installs a shortcut to SetupCapture only, which point to SetupCapture on a server. During installation, choose Client, then choose Minimal Client. Choose the same directory for Wise Share Point and for Wise Package Studio Directory that was chosen during the server installation.

Quality Assurance - Core Files

Installs Workbench and quality assurance tools. This includes Test Expert, Package Validation with the ability to create ICE files, and Package Instrumentation.

During installation, choose Complete, then make sure this feature is enabled on the Select Features dialog. You must have entered a valid serial number for the Quality Assurance module.

Quality Assurance - Web Applications

Installs Web applications that are needed for Preflight Deployment, a Quality Assurance tool for evaluating installations.

Before installation, make sure Microsoft Internet Information Services 4.0 (5.0 recommended) or later is installed. During installation, either choose Complete and make sure this feature is enabled on the Select Features dialog, or choose Web. When prompted to create the Preflight Database, you must specify a Microsoft SQL Server or MSDE database server. You must have entered a valid serial number for the Quality Assurance module.

When a Wise Package Studio user accesses Preflight Analysis, the Preflight Analysis Web application uses the same account that provides Web browser access to the IIS server. Therefore, the browser account must have access to change the Preflight database. If you know that the browser

19


accesses this IIS server via the IIS guest account, then during database setup for the Preflight database, you should mark the Grant database access to IIS Guest Account... checkbox. Also see Database Configuration for Web Applications on page 21.

Enterprise Management Server

Installs components needed for project management, viewing reports, accessing multiple databases, and automatically importing package information. Includes user and group-based security, which can be integrated with NT authentication. It includes Management Reports and also lets you set up Application Gateway security. This module can only be installed with Wise Package Studio Professional Edition.

During installation, choose Complete, then make sure Enterprise Management Server and Wise Package Studio Professional Edition are enabled on the Select Features dialog. You must have entered a valid serial number for both products.

Management Reports

Consists of two pieces: a Web application that communicates with the Workbench database and a Web interface that accesses the Web application. Managers can use the Web interface to view management reports stored in the Software Manager database without having installed any Wise Package Studio software on their computers.

Before installation, make sure Microsoft Internet Information Services 4.0 (5.0 recommended) or later is installed. During installation, choose Complete then make sure Wise Package Studio Professional Edition and Enterprise Management Server are enabled on the Select Features dialog, or choose Web. Also see Database Configuration for Web Applications on page 21.

Application Gateway

Installs a Web application that provides users with a method for requesting applications. Requests appear in Wise Package Studio as requests for repackaging. At least one license for Enterprise Management Server is needed to manage users and permissions for Application Gateway.

Before installation, make sure Microsoft Internet Information Services 4.0 (5.0 recommended) or later is installed. During installation, if prompted, choose Complete, then make sure Application Gateway is enabled on the Select Features dialog, or choose Web. If you entered only an Application Gateway serial number, the installation skips to the Wise Share Point Directory dialog. Choose the same share point as other team members.

20


Database Configuration for Web ApplicationsThere is a very specific configuration issue that may affect the successful execution of the Management Reports or Preflight Web applications. If you are installing either the Management Reports or Preflight Web applications, then you see a Database Logon Information dialog that contains a Grant database access to IIS Guest Account... checkbox.

If the following are also true:

! You are using Windows NT authentication for the Preflight or Workbench databases, and

! The IIS server and the SQL database server are located on different physical computers,

Then you need to do the following additional configuration for the Management Reports or Preflight Web applications to function:

! Clear the Grant database access to IIS Guest Account... checkbox, and

! Either create an identical local user account on both computers (the IIS server and the SQL database server), or identify a domain user that can be specified on each computer (domain account recommended). "Identical" means both the user name and password are the same.

! On the IIS computer, make sure that this user is granted anonymous access in the IIS configuration for the Preflight or Management Reports virtual directories. This user must also have access to the physical directories for these virtual directories.

! On the SQL Server computer, make sure this user is added in SQL Server Enterprise Manager as a user of the Preflight and Workbench databases.

We highly recommend using SQL Server or MSDE, rather than Microsoft Access, to host the Workbench database if using the Management Reports or Application Gateway Web applications, which use ASP code. Microsoft recommends using SQL or MSDE-powered databases to support ASP Web applications. However, Microsoft Access is suitable for product evaluation.

21


Choosing the Location for the Share Point DirectoryWhere should the share point directory be located? That depends on your repackaging environment and the parts of Wise Package Studio you have purchased; see the following table for recommendations. If the share point already exists for your workgroup, you should specify it during installation.

Environment Edition Share Point Location

Single repackager Standard Local PC or network directory.

Repackaging team sharing project files

Professional, Quality Assurance

Shared network directory accessible to team members. In a large enterprise with multiple repackaging teams, each team might have a different share point directory.

Corporate repackaging team maintaining a global process database

Professional, Enterprise Management Server

Shared network directory accessible to all other teams.

22


When the share point directory is located on a shared network drive, each person in a workgroup who installs Wise Package Studio must specify the same share point directory during installation. This allows all users to have access to the same packages and data. Use the following chart to determine if a share point already exists or whether you need to create it.

Setting Up Database Connections and Authentication" Not available in Standard Edition.

During installation, you are asked to configure two or more databases, which store Wise Package Studio data. If you are the first person installing Wise Package Studio for your workgroup, you will set up the initial databases, and you have the option to set up SQL users for those databases. To do this, you need to be familiar with the type of authentication being used on the database server, and you need DBA permissions to create databases and optionally, to create users.

If Then do this:

! Multiple team members plan to share Wise Package Studio data, and

! You are installing the first copy of Wise Package Studio in your workgroup.

! BEFORE installation, create and share a directory on an accessible network location.

! DURING installation, when prompted for the Wise Share Point, specify that shared directory in UNC notation (preferred) or mapped drive notation. (Example of UNC: \\SERVER\WISE SHARE POINT)

! Multiple team members plan to share Wise Package Studio data, and

! Another team member already created and shared a share point directory

! BEFORE installation, obtain the location of the existing share point directory.

! DURING installation, when prompted for the Wise Share Point, specify the existing share point in UNC notation (preferred) or mapped drive notation.

! You do not plan to share data with others

! During installation, when prompted for the Wise Share Point, specify any directory, existing or not, shared or not, as the Wise Share Point. It can be specified with a local path (Example: C:\Wise Share Point)

23


The databases are:

Workbench database

Stores information that Wise Package Studio creates and uses, such as project, process, and security information.

Software Manager database

Contains all software packages as well as other resources that are used by an organization. Other resources include: merge modules, device drivers, group Policy Objects, and standard operating system environment images.

Preflight database

Stores all the results generated from running preflight packages, which are made with the Package Instrumentation tool. You see the contents of the Preflight database with the Preflight Analysis tool. (Quality Assurance module only)

Database Setup Dialogs

" Not available in Standard Edition.

Representative dialogs that appear during database setup are shown below. There is a separate numbered set of dialogs for each database to be set up. Slightly different dialogs appear based on what databases and Wise Package Studio features are being installed. These dialogs might appear during execution of Workbench if any database connection information has become invalid or if the share point directory cannot be found or if it becomes invalid. In that case, you are asked to re-specify database connection and authentication information and the share point directory.

Type of Database Dialog

In Type of Database, you choose the database name to create or connect to, the type of database, and database server for the database whose name is specified at the top of this dialog. If you do not have appropriate software installed, such as SQL Client Tools, the corresponding option is disabled.

24


Database Logon Information Dialog

In the Database Logon Information dialogs, shown below, you specify logon information, which is based on how the SQL or MSDE server security is configured.

You see different versions of these dialogs depending on what features you are installing. These dialogs might appear during execution of Workbench if a database cannot be found or cannot be connected to.

You specify:

! The logon information for a DBA for the selected database server.

! The logon information for users to connect to the database. For instance, Workbench users would use the authentication method you choose to connect to the Workbench database. If you choose SQL Server authentication, you will have an opportunity to create SQL users for the database.

25


! The logon information for a SQL user to be used by a Web application for accessing the database (below). For instance, for the Preflight database, you must specify the account used by the browser to access the database. This depends on your IIS setup.

The Preflight Analysis and Management Reports Web applications use the same account that provides Web browser access to the IIS server. Therefore, the browser account must have access to change the Preflight database. If you know that the browser accesses the IIS server via the IIS guest account, you should mark the Grant database access to IIS Guest Account... checkbox. Also see Database Configuration for Web Applications on page 21.

Create New Users Dialog

If you chose SQL Server authentication, or marked a checkbox to Create logon ID as part of database creation, then you see the following dialog during installation. The DBA logon information you entered earlier will be used to create database users that you specify in this dialog for all databases that are being created (Workbench database, Software Manager database, Prefight database). These users will have modification privileges in all databases.

26


Wise Share Point Directory Dialog

The Wise Share Point Directory may come up at any time during execution of Workbench if the share point directory cannot be found or if it has become invalid. If it appears, choose a valid share point directory or contact your team leader.

Creation Options Dialog

! Import sample applications into the Wise Software Repository. Imports a set of sample application installation data into the Wise Software Repository. This option lengthens installation time.

! Overwrite existing share point and repository. This option appears only if the share point or databases you specified already exist. Mark this option to overwrite it with a blank share point or database.

27


Installing Wise Package Studio in a Client-Server Configuration


You can install Wise Package Studio in a client-server configuration. In a client-server configuration, you install the Complete Wise Package Studio installation on one computer designated the packaging server, and you install the Wise Package Studio Client installation on multiple other client computers. The client installation does not install application files; it installs only the supporting files and shortcuts needed to run the main Wise Package Studio application from the packaging server.

There are several reasons why you might want to work with this configuration:

! It keeps client computers clean for repackaging.

! It simplifies and quickens installation on client computers.

! It causes the configuration and connection to shared databases to be performed automatically on client computers. You can run the client installation silently.

You can use both the client installation and the full installation among members of the same team: the only requirement is that all users designate the same share point directory.

About the Client-Server Configuration of Wise Package Studio


The client installation does not install the actual Wise Package Studio application. It installs the registry settings, .INI files, ODBC data source connections, and shortcuts necessary to run the Wise Package Studio applications from the packaging server. It also installs MDAC, DAO runtime, MFC support files, Crystal Report runtimes, Test Expert support files, and the Windows Installer runtime. If you want a very clean machine for repackaging, install the Minimal Client, which installs SetupCapture only.

Wise Package Studio Client can be run silently from the command line; see Installing Wise Package Studio Client Silently on page 30.

28


NoteTo minimize client installation steps further, you can create a drive image of the client after a successful client installation. Use that image each time you subsequently reimage the computer, then skip all of the client installation steps.

For other Wise Package Studio configuration concepts, see Sharing the Wise Software Repository in the Wise Package Studio Help.

Installing Wise Package Studio Client" Not available in Standard Edition.

If you are using Wise Package Studio in a client-server configuration, you can perform the Wise Package Studio Client installation on the client computers. This is a quick and small installation designed for repackagers who need to re-image their computers frequently. See About the Client-Server Configuration of Wise Package Studio on page 28.

Packaging Server - Wise Package Studio (Complete Installation)

Repackaging Workstation Client Installation




Workbench and Wise Software Repository databases

Requirements for setting up a Wise Package Studio packaging server:- Create and share two directories: an application directory and a share point directory.- Install a Complete installation of Professional. For Wise Package Studio Directory and Share Point Directory, specify the shared directories in UNC notation.

Steps for setting up a Wise Package Studio Client:- Choose the Client option during installation.- During installation, choose the same Wise Package Studio directory and share point directory as created during the Complete installation (use either a mapped drive letter or a UNC path to specify both shared directories)

Client-Server Configuration of Wise Package Studio

29


To install Wise Package Studio Client:

1. Create two directories and make sure they are shared; a Wise Package Studio application directory (where the application will be installed) and a share point directory (where shared data will be stored).

2. Install a Complete Wise Package Studio on a computer designated as your workgroup packaging server. During installation, specify the two directories above as the Wise Package Studio Destination Directory and the Wise Share Point Directory. Use UNC paths (recommended) or mapped drives letters to specify the directories.

3. On a client computer, run the Wise Package Studio installation and choose Client when prompted. Choose the same share point directory and Wise Package Studio directory as were created during the Complete installation. After you choose Client you are prompted to choose between Full Client and Minimal Client. Choosing Minimal Client installs SetupCapture only.

NoteIt is recommended that you specify the shared Wise Package Studio and share point directories using UNC paths. However, if you choose not to use UNC paths, then map separate drive letters to both these directories before client installation.

Installing Wise Package Studio Client Silently" Not available in Standard Edition.

Following are some examples of command lines that run a Wise Package Studio Client installation silently. See About the Client-Server Configuration of Wise Package Studio on page 28.

The /qn and /i options are Windows Installer command line options, described in the Windows Installer SDK Help, which is included in Windows Installer Editor. The /qn option causes installation to be silent, and the /i option causes installation.

Installing the Full Client with the .EXE installer:

<PathToWPS.exe> MODE="Client" CLIENT="Full" SHAREPOINT="\\SERVER1\Wise Share Point" WPSDIR="\\Server1\Wise Package Studio" SERIALS="ABCD-ABCD-ABCD-ABCD|LMNO-LMNO-LMNO-LMNO|WXYZ-WXYZ-WXYZ-WXYZ" /qn /i

Installing the Full Client with the .MSI installer:

<PathToMsiexec.exe> /i "<PathToWPS.exe>" /qn MODE="Client" CLIENT="Full" SHAREPOINT="\\SERVER1\Wise Share Point"

30


WPSDIR="\\Server1\Wise Package Studio" SERIALS="ABCD-ABCD-ABCD-ABCD|WXYZ-WXYZ-WXYZ-WXYZ"

Installing the Minimal Client with the .EXE installer:

<PathToWPSInstaller.exe> MODE="Client" CLIENT="Minimal" SHAREPOINT="\\SERVER1\Wise Share Point" WPSDIR="\\Server1\Wise Package Studio" SERIALS="ABCD-ABCD-ABCD-ABCD" /qn /i

Installing the Minimal Client with the .MSI installer:

<PathToMsiexec.exe> /i "<PathToWPS.exe>" /qn MODE="Client" CLIENT="Minimal" SHAREPOINT="\\SERVER1\Wise Share Point" WPSDIR="\\Server1\Wise Package Studio" SERIALS="ABCD-ABCD-ABCD-ABCD"

31


Application Gateway Server

" Application Gateway module only.

The Application Gateway server is a Web application that lets end users request the deployment of applications to their desktops. It is integrated with Wise Package Studio, so that requests appear as repackaging or deployment requests. The Application Gateway server can only be installed on a computer that is running Microsoft Internet Information Server (IIS) version 4.0 (preferably 5.0) or later.

During the installation of the Application Gateway server, the integration of Application Gateway with Wise Package Studio is set up.

Also see:

Integrating Application Gateway and Wise Package Studio on page 32Bypassing the Proxy Server for Application Gateway on page 34Configuring IIS for Application Gateway on page 35

Integrating Application Gateway and Wise Package Studio

" Application Gateway module only.

The following are essential to successful integration of the Application Gateway server with Wise Package Studio:

! If you choose Windows NT authentication for the Workbench database during installation, then Application Gateway server must be installed on the same computer on which the Workbench and Wise Software Repository databases reside. If you choose SQL authentication for the Workbench database, then the Application Gateway server can be located on a different computer from Workbench and the Wise Software Repository databases. The Application Gateway must use the same Workbench and Wise Software Repository databases as Wise Package Studio. This configuration conforms to Microsoft�s IIS design.

! Repackagers running Wise Package Studio must have an ODBC connection to the Workbench and Wise Software Repository databases.

! All end users accessing the Application Gateway server must have Microsoft Internet Explorer 5.01 or later. They must be provided with the Application Gateway server URL; the default URL is http://server/Wise_Application_Gateway, where server is the computer name of the server.

32


! At least one license of Enterprise Management Server is required to manage users and permissions in Application Gateway.

It is possible to use the Application Gateway server without using the Wise Software Repository. However, it is not advisable. The Repository greatly simplifies the deployment process for applications that have been packaged and made available for deployment.

The following diagram represents a typical setup of the Application Gateway server integrated with Wise Package Studio.

Integration of Wise Package Studio and Application Gateway

You might need to set proxy server settings and IIS configuration settings as follows:

! If you use a proxy server for Internet connectivity, you must set an exception to bypass the proxy server on all client computers that will access Application Gateway; see Bypassing the Proxy Server for Application Gateway.

! If you are running IIS version 5.0 or later, you can configure IIS to avoid certain problems when running Application Gateway; see Configuring IIS for Application Gateway on page 35.

End Users� Workstations that are accessing Application Gateway using Microsoft Internet Explorer 5.01 or later and the default URL, http://server/Wise_Application_Gateway.

Database Server that houses the Workbench database and Wise Software Repository database.

Application Gateway IIS Server with ODBC connection to the Workbench database and Wise Software Repository database.

http://server/gateway ODBC Connection

Repackager�s Workstations that are running Wise Package Studio, accessing the Workbench and Wise Software Repository databases through an ODBC connection, and accessing Application Gateway using the default URL, http://server/Wise_Application_Gateway.

33


Bypassing the Proxy Server for Application Gateway" Application Gateway module only.

Application Gateway cannot work through a proxy server, therefore, if you use a proxy server for your Internet connectivity you must bypass it to access Application Gateway. If you do not bypass the proxy server, then a �page cannot be found� error will appear when a user tries to access Application Gateway.

When you install Application Gateway on the server, if the installation detects that the server uses a proxy server, it automatically sets an exception in Internet Explorer to allow Application Gateway to bypass the proxy server. This exception is set on the server computer only; it is not automatically set on any client (user) computers that access Application Gateway.

In order for Application Gateway to work on client computers, you must bypass the proxy server on every computer that will be used to access Application Gateway. To do so, you could change the setting manually on every client computer, but that would be time-consuming and inefficient. The best way to resolve this issue is to write a group policy to set the proxy server exception; contact your network administrator for assistance.

To allow clients to access Application Gateway by bypassing the proxy server:

This procedure describes how to change the proxy server exception setting manually; you can also write a group policy to change it automatically.

1. In Internet Explorer, select Tools > Internet Options.

2. On the Internet Options dialog, click the Connections tab.

3. Click LAN Settings.

4. On the Local Area Network (LAN) Settings dialog, mark the Use a proxy server for your LAN or the Use a proxy server option, which enables the Advanced button.

5. Click Advanced.

6. The Proxy Settings dialog appears, which contains an Exceptions list. The Exceptions list consists of a semicolon-delimited list of Web addresses that access the Internet directly without using the proxy server.

7. In the Exceptions list, add the Application Gateway URL. (Example: http://server/gateway)

8. Click OK in the Proxy Settings dialog, and then click OK in the Local Area Network (LAN) Settings and Internet Options dialogs.

34


Configuring IIS for Application Gateway" Application Gateway module only.

Internet Information Server 5.0 or later only:The settings described in this section can be configured on Microsoft Internet Information Server (IIS) version 5.0 or later only. You cannot configure these settings on versions of IIS earlier than 5.0 because the earlier versions do not have the Internet Services Manager that is needed to configure the settings.

If you have Internet Information Server 5.0 or later, you should change certain settings in Internet Services Manager after you install the Application Gateway server. These new settings provide a custom error page for Application Gateway to use instead of the default error page.

Do the configuration on the same computer on which you installed the Application Gateway server; this must be a computer that is running the Microsoft Internet Information Server (IIS) version 5.0 or later.

To add a custom error page for Application Gateway:

1. Access Internet Services Manager for the computer that is running Application Gateway.

2. Under the default Web site tree in Internet Services Manager, navigate to the Application Gateway virtual directory and display its Properties dialog.

3. Click the Custom Errors tab.

4. In the HTTP Error list, click the HTTP Error 500 and click Edit Properties.

The Error Mapping Properties dialog appears.

5. Set the properties as follows:

� From Message Type, select URL.

� In URL, enter:

/Application Gateway/_ScriptLibrary/ErrorReport.asp

� Click OK to save the changes and close the dialog.

6. In the HTTP Errors list, click the HTTP Error 500;100 and click Edit Properties. Set the properties the same as you did in the preceding step.

7. When you are finished setting properties, click Apply in the Gateway Properties dialog and then click OK.

35


Starting Wise Package Studio1. Select Windows Start menu > Programs > Wise Solutions.

2. Click the Wise Package Studio icon.

3. If the Wise Package Studio Logon dialog appears, log on as instructed by your Wise Package Studio administrator. For details, see Wise Package Studio Logon Options on page 37. (Not available in Standard Edition.)

If you cannot log on, you might see one or more dialogs. For details, see If Your Logon Fails on page 36.

4. Click OK.

If Wise Package Studio cannot find the default Workbench database, the Database Setup wizard starts. Do the following:

! If the Applications in Use dialog appears, close the applications listed, close Wise Package Studio, and click Next.

! In the Share Point Directory dialog, specify the share point you are using and click Next. Then set up the database as described in Setting Up Database Connections and Authentication on page 23.

For information on using Wise Package Studio, see the Wise Package Studio Help.

If Your Logon Fails" Not available in Standard Edition.

If you have not been assigned a Wise Package Studio license, you cannot log on.

! If a serial number is available, you might be assigned a serial number automatically. If not, the Assign User Licensing dialog appears. Mark one or more checkboxes for the licenses to assign to this user.

With Enterprise Management Server, you cannot be assigned a serial number automatically. The Wise Package Studio administrator must assign licenses.

! If a serial number is not available, the Add Serial Number dialog appears.

! If you entered a logon from a Windows NT domain, and Security Setup does not contain a group that matches the domain group you belong to, you are prompted to contact your Wise Package Studio administrator. (Enterprise Management Server only.)

36

Starting Wise Package Studio

Wise Package Studio Logon Options" Not available in Standard Edition.

When a user starts Wise Package Studio, the Wise Package Studio Logon dialog appears. Users have several options for logging on to Wise Package Studio.

Workbench Logon

When to use: When the computer is not connected to a Windows NT domain. For example, when using Workbench on a lab computer.

What to enter on the Wise Package Studio Logon dialog:

! User name from User Licensing Setup or, with Enterprise Management Server, from Security Setup.

! Password from Security Setup. (Enterprise Management Server only.)

! Select (Workbench Database) in Use Security From.

! Clear Always Use Current Network Login.

Current Windows NT Logon

(Windows NT environments only.)

When to use: To log on to Wise Package Studio as the currently logged-on Windows NT user.


! Mark Always Use Current Network Login and leave the remaining fields blank.

When the user starts Wise Package Studio in the future, they will be logged on automatically.

Windows NT Domain Account

(Windows NT environments only.)

When to use: To log on to Wise Package Studio with a Windows NT account. This account can be different from the one that is currently logged on to Windows. This lets users log on to Wise Package Studio from someone else�s computer, or from a remote computer. The computer must have Wise Package Studio installed.


! Windows NT user name from the Windows NT domain.

! Password from the Windows NT domain.

! Select the Windows NT domain name in Use Security From.

37


! Clear Always Use Current Network Login.

NoteWith Enterprise Management Server only, when a user logs on with a Windows NT account, or when they use the current network logon, Security Setup must contain a group whose name matches a valid group in the NT domain, and the user must be defined in that domain group. If the user is defined in multiple domain groups, they are logged in under the first valid group encountered.

38

Registering Your Software

Registering Your SoftwareIt is very important that you register your software. By registering, you are automatically qualified to receive technical support via newsgroups and e-mail, plus notifications about future product upgrades. If you did not register your software online during the setup process, you may do so in either of the following ways.

Registering Online

You can register your software online from within Wise Package Studio. Select Help menu > Wise on the Web > On-Line Registration. Follow the onscreen instructions to complete the registration process. You must be connected to the Internet. After you create a profile, you can register on the Product Registration page of the Support section.

Registering By Mail

If you are unable to register online, you can register by filling out the registration card included with your software package and mailing it to Wise Solutions. Complete all of the information on the card and drop it in the mail. If you are not mailing in the United States, affix the proper postage before mailing.

39


40

Chapter 3Tutorial

This section guides you through the process of repackaging an application into Windows Installer format. You use a sample application installation for QuickFacts, which is included with Wise Package Studio to provide you with a realistic practice scenario.

" Professional Edition.This tutorial uses features not available in the Standard Edition of Wise Package Studio.

In this tutorial, you will:

! Create a new Wise Package Studio project.

! Use SetupCapture to recreate the existing installation in Windows Installer format.

! Customize the installation package in Windows Installer Editor.

! Verify that the package complies with standards.

! Test the repackaged installation.

! Detect and resolve conflicts in ConflictManager.

! Deploy the application to end users.

NoteIf you are using the Enterprise Management Server, security settings can limit access to some features. See your manager or system administrator if a feature described in this tutorial is not available.

41

3: Tutorial

Before You StartIn order to follow the procedures in this tutorial, you must meet the following prerequisites:

! This tutorial uses features of the Professional Edition of Wise Package Studio. Make sure you are using this edition.

! Obtain Wise Package Studio logon information.

� If you are using an evaluation version of Wise Package Studio, you can log on as Admin and leave the password blank.

� If you are using a production version, ask your manager or Wise Package Studio administrator for logon information.

! Close other applications before starting this tutorial. During the repackaging process, you capture the actions performed by an installation; it is important to close all applications other than Wise Package Studio to avoid capturing the activities of other applications and processes.

! It is assumed that you are installing the sample program, QuickFacts, on your computer for the first time. If you have installed QuickFacts on your computer, uninstall it and remove any files and registry keys related to it. Files left from previous installations can cause your results to deviate from the information presented in this tutorial.

Import a Sample Package into the Software Manager Database

Before you start the tutorial, you must import a sample package into the Software Manager database. Later in the tutorial, you will detect conflicts between the sample package and the new package you create.

Frequently, you will need to import a package into the Software Manager database without repackaging. You might do this with a package that has already been approved and deployed so that all packages that have been installed throughout your company are in the Software Manager database.

To import a sample package:

1. Select Windows Start menu > Programs > Wise Solutions > Wise Package Studio.

The Wise Package Studio Logon dialog appears.

2. Enter your logon information and click OK.

Wise Package Studio opens.

42

Before You Start

3. Click the Tools tab. At the top of the Tools tab, double-click Software Manager.

Software Manager opens.

4. Select Packages > Import.

The Import Type dialog appears.

5. Mark Import a single file into the Software Manager database and then mark the following checkboxes:

� Distribute source files to the share point directory. Mark this checkbox to copy the package�s source files to the share point directory.

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

6. Click Next in the Import Type dialog.

The Select Package Type dialog appears, containing options for the types of files you can import.

7. Mark the Windows Installer-based Installation (.MSI/.WSI) option and click Next.

The Package Details dialog appears.

8. Complete the Package Details dialog:

� .MSI/.WSI File. Browse to the Tutorial directory within the Wise Package Studio directory and open Sample Conflict.msi.

� Application Name. Enter Sample Conflict. This is the name of the application in the Software Manager database.

� Package Name. Enter Conflict 1.0 to identify this package in the Software Manager database. Typically, you use the application name plus specific version information as the package name.

� Use Transactions for Import. Leave this checkbox blank.

9. Click Next in the Package Details dialog.

The Transforms and Patches dialog appears.

10.Click Finish.

The package you selected is imported into the Software Manager database. It appears in Software Manager�s Applications/Packages pane.

11.Exit Software Manager.

Software Manager closes and the right pane in Workbench reappears.

43

3: Tutorial

You have now imported a package into the Software Manager database using Software Manager. In the next procedure, you will create a new project in Wise Package Studio.

Create a New ProjectIn this procedure, you create a new project called QuickFacts in Wise Package Studio. The project defines the name and location of files, as well as the project name and other information. You also assign a repackaging process called Repackage for Windows Installer to the project. This process contains tasks, which you will complete as you go through this tutorial. The tasks guide you through the basic steps of repackaging. All tasks automatically access the appropriate project files.

NoteFollow the instructions exactly as presented, otherwise your results can deviate from the information presented in this tutorial.

To create a new project:

1. If Wise Package Studio is not open, open it and log on.

2. Select File menu > New Project.

The Project Setup dialog appears. A new project appears in the Project list on the left and is selected by default.

3. Fill out the project fields on the right exactly as described below.

� Project Name: Type: QuickFacts.

� Project Directory: Leave the default.

� Status: Leave the default of Open.

� Product Vendor: Select Wise Solutions

� Application Name: Type: QuickFacts.

� Package Name: Type: QuickFacts version 2.0.

� File Name: If it is not defaulted, type: QuickFacts.

� Vendor Package: Do not type in this field�instead, click the button next to the field. Navigate to the Tutorial directory within the Wise Package Studio directory and open QuickFactsInstall.exe.

� Project Owner: This field appears with Enterprise Management Server only. Leave the default.

� Process: Select Repackage for Windows Installer. The Repackage for Windows Installer process contains the tasks for repackaging an installation into a Windows Installer package.

44

Before You Start

Your Project Setup dialog should look like this:

4. In the Project Setup dialog, click Close.

5. If the Projects tab is not displayed in the left pane of Wise Package Studio, click it.

6. From Active Project, select QuickFacts.

The Projects tab displays the process you�ll follow to repackage the QuickFacts application. This process consists of a set of tasks that appear in the Task list.

NoteIf a task is disabled, it means you do not have a license to use the tool associated with it. With Enterprise Management Server, it might also mean you do not have permission to use the tool associated with the task or have not been assigned as the task�s owner.

45

3: Tutorial

That�s all there is to creating a new project. Next, you�ll complete the Create package task.

Create the QuickFacts PackageThe first task in the Application Integration phase is to repackage the existing QuickFacts installation program. To complete the Create package task, you use the SetupCapture tool. SetupCapture records an installation and recreates it in Windows Installer Editor. SetupCapture also copies the directory structure and source files of the installation to the Projects\QuickFacts directory in your share point. The repackaged installation that results from this SetupCapture will reference the source files in your share point directory rather than those installed in the Program Files directory.

Before following the procedure for this task, you must have created the project as described in Create a New Project on page 44.

NoteNormally, you perform SetupCapture on a clean machine, which represents the base machine for your organization, and you reboot during the capture. However, for this tutorial, the installation you are capturing has been specially designed so it does not require a clean machine or a reboot. For most other applications, a clean machine is required.

The Active Project is the one you are currently working on.

Process, made up of tasks. You�ll follow these tasks to perform the repackaging of the sample application.

46

Before You Start

To create the QuickFacts package:

1. In Wise Package Studio, click the Projects tab. QuickFacts should appear in the Active Project drop-down list.

2. Make sure all other applications besides Wise Package Studio are closed. This includes background applications that might create or change files on the computer.

3. Click the Run link next to the Create package task.

The Welcome dialog appears.

4. Click Settings.

The SetupCapture Configuration dialog appears.

5. Click the File and Folder Exclusions tab.

If a message about file exclusions located under your user profile appears, click Yes.

6. Click Add on the File and Folder Exclusions tab.

The File Exclude dialog appears.

7. Leave the Directory field blank.

8. In File/Wildcard, enter *.tmp and click OK in the File Exclude dialog.

This adds *.tmp to the list of files that SetupCapture will ignore when it captures an installation.

9. Click the Directories to Watch tab and note the drive letter that will be watched.

47

3: Tutorial

When you install QuickFacts later in this tutorial, you need to install it to this watched drive.

10.Click OK in the SetupCapture Configuration dialog.

The Welcome dialog reappears.

11.Click Next in the Welcome dialog. What happens next depends on the version of Windows you are using.

� If you are on Windows NT, 2000, or XP, the Capture Methodology dialog appears.

� If you are on Windows 95, 98, or Me, the Capture Methodology dialog is skipped. The capture methodology is permanently set to use snapshot comparisons because of operating system limitations. You can skip the next step.

12. If the Capture Methodology dialog appears, do the following:

� Mark Snapshot.

� Make sure Use SmartMonitor in conjunction with Snapshot is cleared.

� Click Next.

NoteSnapshot comparisons look at the difference between a �before� snapshot of the system and an �after� snapshot to determine what happened during the installation.

13. If SetupCapture previously scanned the machine, the Initial Scan dialog appears. Mark the Rerun the initial scan option and click Next.

The Begin Installation Capture dialog appears.

14.Click Next in the Begin Installation Capture dialog.

SetupCapture scans your machine; this might take several minutes. When the scan is finished, the Execute Installation dialog appears. The setup program that you specified earlier, while creating the QuickFacts project, appears in the .EXE Name field. This is the installation that you will capture with SetupCapture.

15.Click Execute in the Execute Installation dialog.

The QuickFacts 2.0 Setup program opens in front of SetupCapture:

48

Before You Start

16. In the QuickFacts 2.0 Setup program, proceed through the installation and accept all default settings.

This installs a sample application called QuickFacts on your computer. QuickFacts is a small utility that displays facts and bitmaps. It was created by Wise Solutions to illustrate the repackaging process.

17.After the QuickFacts installation is finished, click Next in the Execute Installation dialog.

The End Installation Capture dialog appears.

18.Click Next in the End Installation Capture dialog.

SetupCapture scans your machine for a second time to determine what changed. This might take several minutes. When the scan is finished, the SetupCapture Inclusions dialog appears, which lists all the files, registry entries, shortcuts, and .INI file changes that will be included in the repackaged installation.

49

3: Tutorial

Typically, you exclude from your installation those files and registry entries that are not applicable to all machines, or are not applicable to Windows Installer technology. Additional files that are not related to QuickFacts might be included in the list. Examples: temporary Internet files, cookies, and files that have to do with software that runs constantly in the background, such as virus protection software.

19.Exclude extraneous files by selecting the file name in the list box and clicking Exclude.

Some files, such as INSTALL.LOG and Unwise.exe, which are related to uninstalling and are therefore unnecessary, were excluded automatically by being included in the exclusions list.

The only files that should remain are QuickFacts files, listed below:

License.txtQckFacts.exeReadMe.txtConsulting and Training.bmpConsulting and Training.qftDeveloper Products.bmpDeveloper Products.qftSystem Administrator Products.bmpSystem Administrator Products.qftQuickFacts.cntQuickFacts.hlpQFGUITAM.dll

50

Before You Start

NoteYou can enlarge the window in the SetupCapture Inclusions dialog by dragging the lower right corner. You can also widen the Directory or File columns.

20. To see registry entries on the SetupCapture Inclusions dialog, select Registry keys from Inclusion Type.

21. If necessary, exclude extraneous registry keys, such as those related to uninstalling, by selecting the key in the list box and clicking Exclude.

Keep registry entries with QuickFacts or QckFacts in their Key name. Registry keys for file associations vary by operating system. The list should include registry keys with the following ValueNames:

CaptionFontNameFactsBkColorBlueFactsBkColorGreenFactsBkColorRedTitleFontSizeTitleText

NoteOnce you become familiar with your particular operating system environment, you will be able to more easily tell what files and registry entries are extraneous to an application. You can also run the SetupCapture Configuration tool and automatically build an exclusion list to further reduce extraneous files and registry entries.

22.Click Next in the SetupCapture Inclusions dialog.

The SetupCapture Exclusions dialog appears, which shows the registry keys that are slated to be excluded from the repackaged installation.

Change Exclusion Type to Files to see the files you excluded. There might be additional files and registry keys other than those you excluded if you have previously run/configured SetupCapture or if they are in the default SetupCapture exclusion list. For example, the files INSTALL.LOG and Unwise.exe appear because they are in the default SetupCapture exclusion list.

23.Click Next in the SetupCapture Exclusions dialog.

The Finish dialog appears.

24. The project fields should appear exactly as described below. If not, edit the fields as necessary.

� Name: QuickFacts

� Version: 2.0

� Manufacturer: Wise Solutions

51

3: Tutorial

� Default Directory: C:\Program Files\QuickFacts; where C: is the drive where QuickFacts is installed

� Destination Feature: Complete

Your Finish dialog should look like this, if the Program Files directory is located on your C: drive:

25.Click Finish.

This saves the captured installation in Windows Installer format and copies the directory structure and source files of the installation to the Projects\QuickFacts directory of your share point. This allows you to create and edit your QuickFacts.msi package using relative paths, independent of the original installation.

You are now finished capturing the QuickFacts installation. On the Projects tab, the checkbox next to the Create package task is marked to indicate that the task is complete. In the next task, you open the package in Windows Installer Editor and customize the installation.

Edit the Package InstallationTo complete the Edit Package task, you use Windows Installer Editor to open the QuickFacts installation package you captured in the previous

52

Before You Start

procedure, and then customize it for your organization. Windows Installer Editor is an installation development environment for Windows Installer.

Windows Installer Editor has three major views: Installation Expert, MSI Script, and Setup Editor. Each view provides a different development environment. The only view that you will use in this tutorial is Installation Expert. You will access various pages in Installation Expert. Each page lets you review and edit a specific aspect of your installation.

Before following the procedure for this task, make sure you have completed the previous step in this tutorial�Create the QuickFacts Package on page 46�as well as all preceding steps.

To edit the package installation in Windows Installer Editor:

1. Make sure you are in Wise Package Studio with the Projects tab selected and QuickFacts selected in the Active Project drop-down list.

2. Click the Run link next to the Edit package task.

The repackaged QuickFacts installation opens in Windows Installer Editor.

3. Make sure you are in Installation Expert by clicking the Installation Expert tab at the bottom left of the window.

NoteAlong the left side of the window, you see page group headings, such as Project Definition, below which appear linked page names. Click a page group name, for example Project Definition, to expand or collapse it. Click the page names below the page group names to go to a particular page.

4. In the Project Definition page group, click Product Details.

The Product Details page appears. This page specifies project information. Some of this information is used to customize the installation, and some is used by Windows Installer to identify the installation. Because you filled out much of the required information before you exited SetupCapture, most of the fields are already filled. The fields should be filled as shown below:

� Name: QuickFacts

� Version: 2.0

� Manufacturer: Wise Solutions

� Default Directory: Program Files\QuickFacts

� Product Code: Leave the default. This is a unique code, called a GUID, that Windows Installer uses to identify the product.

� Application Type. Make sure this is set to Win32 (non .NET).

53

3: Tutorial

� Installation Target. Make sure this is set to Windows-based desktop/server PC.

5. Optionally, in the Project Definition page group, you can go to the General Information page and the Add/Remove Programs page and fill in the fields on those pages.

The information on the General Information page is displayed if an end user right-clicks on the installation .MSI in Windows Explorer and selects Properties. The information on the Add/Remove Programs page appears on Windows 2000 or higher machines in the Add/Remove control panel for QuickFacts.

6. In the Project Definition page group, click Features.

The Features page appears.

7. Expand the Complete feature tree.

NoteYou�ll notice that there are two features, named Complete and Feature. The QckFacts.exe file and its advertised shortcut are isolated in a separate feature to avoid a common performance issue related to Windows Installer repair functionality. The issue can cause repeated attempts to repair the application. Isolating the advertised .EXE and its shortcut fixes the problem. By default the feature named Feature is hidden from the end user.

8. On the Features page, rename the Feature feature to MainApp.

� First, double-click the word Feature in the list of features.

The Feature Details dialog appears.

� In both the Name and Title fields, type: MainApp.

� Leave the defaults in the remaining fields.

� Click OK to close the Feature Details dialog.

9. In the Feature Details page group, click Files.

The Files page appears and the files for the MainApp feature are displayed. To see the files for the Complete feature, select Complete from the Current Feature drop-down list at the top of the page. The Current Feature drop-down list indicates the number of files in each feature. In the lower left list box, navigate to the QuickFacts folder to see the directories for that feature. The files in each directory are displayed in the lower right list box.

54

Before You Start

NoteOptionally, you can review the shortcuts and registry entries by selecting the Shortcuts and Registry pages in the Feature Details page group. Only the shortcuts or registry entries for the current feature appear. Change the current feature by selecting the feature name in the Current Feature drop-down list at the top of the page.

10. In the Target System page group, click System Requirements. You might have to scroll down to see the Target System page group.

The System Requirements page appears.

On this page, do the following to change the system requirements of this installation:

� Double-click the Windows Version requirement.

� In the Minimum System Requirements dialog, select Windows 98 from Windows Version. This allows the program to install on Windows 98 or higher.

� In Message Text, enter:

You must have Windows 98 or higher to run this installation.

� Click OK in the Minimum System Requirements dialog.

� Leave the Windows NT requirement set to All Versions, which includes Windows NT 4.0, Windows 2000, and higher.

11. In the User Interface page group, click Dialogs.

The Dialogs page appears. On this page you specify which dialogs appear, and you specify a ReadMe file to display.

� Turn OFF the User Information dialog by clearing its checkbox.

� Turn ON the Readme dialog by marking its checkbox.

� While the Readme dialog is still selected, click Import Text, which is to the right of the displayed Readme dialog.

� In the Open dialog, navigate to <Wise Share Point>\Projects\QuickFacts\Program Files\QuickFacts, where <Wise Share Point> is the path to your share point directory. This is the location of the source files for this package, which were copied during SetupCapture. Change the Files of type drop-down list to Text files. Select the ReadMe.txt file and click Open.

The ReadMe text file appears in the Readme Information dialog and will appear in this dialog during installation.

12.Save the installation by selecting File menu > Save.

13.Exit Windows Installer Editor.

55

3: Tutorial

You are now finished customizing the QuickFacts installation package in Windows Installer Editor. On the Projects tab, the checkbox next to the Edit package task is marked to indicate that the task is complete. The Application Integration phase of the Repackaging for Windows Installer process is now complete. In the second phase, Package Testing, you validate and test the package you created.

Validate the Installation PackageThe first task in the Package Testing phase is to validate the QuickFacts package. To complete the Validate compliance with standards task, you use the Package Validation tool. The Package Validation tool verifies that the package complies with Microsoft�s Application Specification for Windows 2000.

Before following the procedure for this task, make sure you have completed the previous phase of the Repackage for Windows Installer process�Edit the Package Installation on page 52�as well as all preceding steps.

To validate the package:


2. Click the Run link next to the Validate compliance with standards task.

Dialogs appear briefly and the .WSI is compiled into a .MSI. The Welcome dialog for the Package Validation tool appears, listing the predefined validation tests that can be performed. To see a description of each test, click the test name, and the description appears on the right of the dialog.

3. Mark Windows Installer SDK Internal Consistency. If necessary, clear all other checkboxes.

4. Click Next.

The test begins running. This might take a few minutes. When the test is finished, the View / Correct dialog appears, which contains all the possible problems detected.

For QuickFacts, normally no errors appear, although for more complex installations, errors are more likely to appear. If there were errors and if the Correct button became enabled when the error was selected, you could click Correct to resolve the problem. Otherwise, you would open the installation in Windows Installer Editor (click Run next to the Edit package task), fix the error, and recompile. Errors are documented in the Windows Installer SDK Help. Start with the topic Internal Consistency Evaluators - ICEs.

56

Before You Start

5. Exit the Package Validation tool by clicking Finish.

You are now finished validating the QuickFacts installation package. On the Projects tab, the checkbox next to the Validate compliance with standards task is marked to indicate that the task is complete. In the next task, you will test the installation package. The steps in the next task differ depending on whether you have the Quality Assurance module. If you have the Quality Assurance module, you will use Text Expert to test the package, see Test the Package With Test Expert on page 58. If you don�t have the Quality Assurance module, see Test the Package Without Test Expert.

Test the Package Without Test Expert

NoteUse this section if you don�t have the Quality Assurance module. If you have the Quality Assurance module, skip this section and proceed to Test the Package With Test Expert on page 58.

To complete the Test package task, you test the package on a system that is identical to the target machines on which you expect it to be installed. If this application is to be installed on several different configurations of target systems, you should test the package on each configuration.

If you were really distributing this package, it would require more thorough testing. To test in a corporate environment, you would copy the finished .MSI file to a file server or other media, such as a CD. Then you would install the application on the system or systems that are representative of the target machines and test it to see that it was installed correctly.

This tutorial, however, leads you through testing the installation on your own computer. The finished .MSI file is located in your share point directory (usually named Wise Share Point) at Projects\QuickFacts\QuickFacts.MSI. The Test package task automatically opens this file, so that you can install the repackaged installation. After the package is tested, it can be distributed to the share point directory.

Before following the procedure for this task, make sure you have completed the previous step in this tutorial�Validate the Installation Package on page 56�as well as all preceding steps.

To test the package on your computer:

1. First, uninstall the previous copy of QuickFacts that you installed during the first part of this tutorial. Use the Add/Remove Programs icon in the Control Panel to uninstall.

57

3: Tutorial


3. Click the Run link next to the Test package task. The new repackaged installation that you just created begins.

4. Run through the installation, accepting all the defaults.

5. After installation is finished, open QuickFacts by selecting Windows Start menu > Programs > QuickFacts.

6. Make sure QuickFacts works as you expect. You can check that its shortcuts are created, that its registry entries are created, that all the files are installed, and so on.

After you run the QuickFacts installation from the Projects tab, the checkbox next to the Test package task is not marked, unlike other tasks, because additional testing might be necessary. On the Projects tab, manually mark the checkbox next to the Test Package task after you perform additional testing, such as testing on a clean machine. Then, in the next task, you will distribute the package to the share point directory; see Distribute the Package on page 62. Skip the next section, which is only applicable if you have the Quality Assurance module.

Test the Package With Test Expert

" Quality Assurance module only.Test Expert is available only with the Quality Assurance module. If you don�t have the Quality Assurance module, skip this section and perform the steps in Test the Package Without Test Expert on page 57.

To complete the Test Package task, you use Test Expert to perform integration and acceptance testing of the package. Test Expert automatically generates a master test plan based on the contents of a package and guides users through the execution of various test cases. This makes the testing process more efficient and focused, eliminating the random approach often used in an ad hoc testing environment. Test Expert performs analysis on .MSI-based installations only.

Before following the procedure for this task, make sure you have completed the previous step in this tutorial�Validate the Installation Package on page 56�as well as all preceding steps.

NoteUnder normal testing conditions, Test Expert requires a clean machine to ensure the integrity of the repackaged installation.

58

Before You Start

To test the package using Test Expert:

1. First, uninstall the previous copy of QuickFacts that you installed during the first part of this tutorial. Use the Add/Remove Programs icon in the Control Panel to uninstall.

You uninstall because during this procedure, you are going to install and test the repackaged version of QuickFacts. Removing the original QuickFacts ensures that you only test the repackaged installation.


3. Make sure all other applications besides Wise Package Studio are closed. This includes background applications that might create or change files on the computer.

4. Click the Run link next to the Test Package task.

NoteIf the Test Package task is disabled, it means you do not have a Quality Assurance license.

Dialogs appear briefly and the package is recompiled. The Test Expert window appears, with QuickFacts.msi opened.

When you open a package in Test Expert, you see the Master Test Plan for that package displayed. Each time you open the package, the package is read and test cases are generated automatically based on the contents of the package. In addition to the Master Test Plan, you can add user-defined test cases to fully test the package for the requirements of your organization. However, for this tutorial, you will only perform two of the test cases provided in the Master Test Plan.

5. In the Installation Tests section in the left pane, select the Verify Installation test case.

The Verify Installation page appears in the right pane. This test case ensures that the installation runs without errors by installing the QuickFacts package you created during SetupCapture.

6. Click Install on the toolbar at the top of the window. Then, in the Welcome dialog, click Cancel to skip the Machine Capture.

Machine Capture is only necessary if you plan to perform Uninstall Tests, which are skipped in this tutorial.

The QuickFacts Setup program opens in front of Test Expert.

7. In the QuickFacts Setup program, proceed through the installation and accept all default settings. This installs the QuickFacts package.

59

3: Tutorial

8. If the QuickFacts installation ran without errors, from Status of Test Case, select Passed.

In the next step, you use the installed QuickFacts application to perform the File Coverage test case.

9. In the Application Execution Tests section, select the File Coverage test case.

A list of all files accessed by the QuickFacts application appears in the All Test Items tab in the right pane. The File Coverage test case lets you know which installed files are accessed as the application is run.

10.Click Run on the toolbar.

The Run Application Execution Tests dialog appears.

11. In the File to Run list, select QckFacts.exe and click OK.

The QuickFacts application opens and the Application Monitor window appears.

NoteYou must leave the Application Monitor window open while you exercise the functionality of the application because your system is monitored only when it is open. Move or minimize it if necessary.

12. To test QuickFacts, use each function of the QuickFacts application. The Application Monitor window updates as files are accessed.

For best results, use every QuickFacts function as follows:

� In the Select an item to see facts list, select all three items, one at a time.

� Select Help menu > Help Contents.

� Select Help menu > QuickFacts Readme.

� Click About in the lower right of the QuickFacts dialog.

When you are finished testing, the File Coverage graph in Application Monitor indicates the percentage of the files that were accessed.

NoteSome files are not accessed by an application during normal use. For example, in the QuickFacts application, the License.txt file is not accessed during normal application execution.

13. To return to Test Expert, click Exit in the QuickFacts application and close the QuickFacts ReadMe.

14.Close the Application Monitor window. Monitoring does not cease until it is closed.

60

Before You Start

In the All Test Items tab, all files except License.txt should display the Passed status. Because the License.txt file is not accessed during normal application execution, it has a Pending status. The test items should look like this:

15. To set the status of the License.txt file to the Passed status, double-click the License.txt file on the All Test Items tab.

The Test Item Details dialog appears.

� In Status, select Passed.

� In Test Details, type:

This file is not accessed during normal application execution.

� Click OK.

16.On the File Coverage page, from Status of Test Case, select Passed.

NoteYou might notice that all test case names under Application Execution Tests have become un-bolded, which indicates they have been run. This is because all Application Execution Tests are run simultaneously.

17. Exit Test Expert.

For the purposes of this tutorial, you are now finished testing the package. Normally you would execute all test cases. On the Projects tab, the checkbox next to the Test package task is marked automatically after Test Expert runs. In the next task, you distribute the package to the share point directory.

61

3: Tutorial

Distribute the PackageIn the Distribute to share point directory task, you distribute the QuickFacts package to the share point directory so that it can later be imported into the Software Manager database.

The Package Distribution tool, which runs silently and automatically in the background, places the package into a queue for later import by Software Manager.

Before following the procedure for this task, make sure you have completed the previous step in this tutorial�Test the Package Without Test Expert on page 57 or Test the Package With Test Expert on page 58�as well as all preceding steps.

To distribute the package:


2. Click the Run link next to the Distribute to share point directory task.

A dialog appears briefly and the package is automatically copied to the share point directory, which means that the package is ready to import into the Software Manager database.

You are now finished distributing the package to the share point directory. On the Projects tab, the checkbox next to the Distribute to share point directory task is marked to indicate that the task is complete. In the next task, you import the package into the Software Manager database.

Import into the Software Manager DatabaseIn the Import into Software Manager database task, the QuickFacts package is imported into the Software Manager database. The import is handled by Software Manager, which, in this task, runs silently and automatically in the background. Software Manager administers the information stored in the Software Manager database. Once the package is in the Software Manager database, the package can be checked for conflicts with other packages in the database.

Before following the procedure for this task, make sure you have completed the previous step in this tutorial�Distribute the Package on page 62�as well as all preceding steps.

To import into the Software Manager database:


62

Before You Start

2. Click the Run link next to the Import into Software Manager database task.

A dialog appears briefly and the package is automatically imported to the Software Manager database, which means that the package is ready to be checked for conflicts with other packages in the database.

You are now finished importing the QuickFacts Installation project into the Software Manager database. On the Projects tab, the checkbox next to the Import into Software Manager database task is marked to indicate that the task is complete. In the next task, you detect and resolve software conflicts.

Resolve ConflictsTo complete the Resolve conflicts task, you use ConflictManager to compare the QuickFacts package with the Sample Conflict package. ConflictManager detects and resolves software conflicts before you deploy applications throughout your organization. Once all conflicts are resolved, the application can be made available to end users.

Before following the procedure for this task, make sure you have completed the previous step in this tutorial�Import into the Software Manager Database on page 62�as well as all preceding steps.

To find and resolve conflicts between QuickFacts and the Sample Conflict package:


2. Click the Run link next to the Resolve conflicts task, which launches ConflictManager.

The Detect Conflicts dialog should appear. If it doesn�t, select Conflicts menu > Detect to display it.

3. Mark the Detect conflicts for selected packages option. Select both QuickFacts and Sample Conflict. Click OK.

The conflict detection process begins, and may take a few minutes. While the conflict detection is running, the status is displayed at the right end of the toolbar.

4. When the status of the conflict detection process is Idle, expand the QuickFacts tree in the Applications/Packages pane and select the QuickFacts version 2.0 package.

In the Conflict List pane, a conflict for QFGUITAM.dll appears. The red exclamation point next to it indicates that it is classified as an error. If warnings existed, which are not as serious as errors, they would appear in this list with a yellow question mark icon.

63

3: Tutorial

5. To fix the conflict, select Conflicts menu > Resolve.

The Welcome dialog of the Resolve wizard appears.

6. From Application, select QuickFacts. QuickFacts version 2.0 automatically appears in the Package field.

7. From Isolation method, select Isolated Components (Windows 98 SE/Me/2000/XP).

Isolating a conflict means that each application will use its own version of the conflicting file. The files will be stored in different directories, and will be managed by Windows Installer.

8. Click Next.

The File Conflicts dialog appears, displaying QFGUITAM.dll in the upper list box. The upper list box contains the name and information of the file in your package that has conflicts. The lower list box indicates the package with which the file conflicts, and also contains information about the other application�s conflicting file.

9. Select QFGUITAM.dll in the upper list box and click Move on the right of the File Conflicts dialog.

The exclamation point turns white to indicate the problem has been fixed. Because you selected Isolated Components as the Isolation Method, the Move button isolates the file so that each package that uses QFGUITAM.dll will use its own version. This means that a copy of QFGUITAM.DLL will be installed into the QuickFacts directory, and QuickFacts will reference its own copy of the .DLL file.

10.Click Next in the File Conflicts dialog.

The File Conflicts in Registry dialog appears, which should be empty.

11.Click Finish.

In the Conflict List pane, QFGUITAM.dll appears with a yellow question mark icon next to it. The file conflict has been resolved by isolating the file in different directories but is still listed as a warning. This is because two installation packages install a non-16-bit file with the same file name but different file information (file version number or date/time) to different directories. Also, the File Conflicts bar graph in the Summary pane indicates one warning.

12. To view only errors (red exclamation points) in ConflictManager, not warnings (yellow question marks), do the following:

� Select Conflicts menu > Filter to display the Conflict Filter dialog.

� In the Conflict Types to Display section, clear Warnings.

� Click OK.

The conflict filter is globally set to show only errors in the Conflict List display.

64

Before You Start

Now, you are ready to export and recompile the application.

13.Select Packages menu > Export and Recompile.

The Export Changed Packages and Recompile dialog appears, listing your QuickFacts package.

14.Mark the checkbox for the QuickFacts package. Also, mark Compile the packages after export.

15.Click OK.

Several progress dialogs appear briefly during the export.

16.After progress dialogs stop appearing, exit ConflictManager.

The file change is made in the QuickFacts.WSI file with which you�ve been working, which is in the Projects\QuickFacts subdirectory of the share point. It is also compiled to an .MSI file named QuickFacts.MSI. The conflict that it had with the Sample Conflict package is now resolved because each package will use its own version of the .DLL file instead of one .DLL overwriting the other .DLL. In a corporate scenario, the database would be populated with your own standard set of applications.

On the Projects tab, the checkbox next to the Resolve conflicts task is marked to indicate that the task is complete. If you don�t have the Quality Assurance module, all the tasks in the Package Testing phase of the Repackaging for Windows Installer process are now complete. If you have the Quality Assurance module, there are 3 additional tasks in the Package Testing phase: Prepare package for deployment, Deploy instrumented package, and Analyze Results. This tutorial skips these tasks because they require integration with other computers.

In the final phase, Release Management, you release the application to end users.

Make the Package AvailableIn the Make Package Available task, the status of the package in the Software Manager database is updated to Available and the package is copied to the Available Packages directory in the share point directory. This task is handled by Software Manager, which runs silently and automatically in the background. The Available Packages directory provides a centralized location for storing all of your packages that are complete and available for deployment, keeping them separate from packages that are still in development. After the status of the package is updated and the package is copied, the application can be distributed to end users.

Before following the procedure for this task, make sure you have completed the previous phase of the Repackage for Windows Installer process�Resolve Conflicts on page 63�as well as all preceding steps.

65

3: Tutorial

To make the package available:


2. Click the Run link next to the Make Package Available task.

A dialog appears briefly. The package status is automatically updated to Available, and the package is copied to the Available Packages directory in the share point directory and marked as Read-only.

You are now finished making the package available for distribution to end users. On the Projects tab, the checkbox next to the Make package available task is marked to indicate that the task is complete. In the next task, the package is distributed to end users.

Distribute the Finished PackageTo complete the Distribute package task, you use the Package Distribution tool to distribute the package to a location that can be accessed by end users. Typically, this would be a shared network drive or a distribution system. However, for this tutorial, you will distribute it to your local drive. After the package is distributed to end users, the Repackage for Windows Installer process is complete.

Before following the procedure for this task, make sure you have completed the previous step in this tutorial�Make the Package Available on page 65�as well as all preceding steps.

To distribute the package:


2. Click the Run link next to the Distribute Package task. Dialogs appear briefly and the package is recompiled.

The Distribution Method dialog of the Package Distribution tool appears. Options are available based on the type of package and based on the distribution systems available on the computer.

3. In the Other Distribution Options section, mark the Network and Installation Only options and click Next.

The Network Directory dialog appears.

4. In Network Directory, specify a directory in which to save the installation. Typically, this would be a shared network drive available to users. For this tutorial, select a directory on your local drive.

5. To save the installation with a name other than its current name, enter the new name in Destination File Name.

6. Click Finish.

66

Before You Start

The package is distributed to the directory you specified.

On the Projects tab, the checkbox next to the Distribute Package task is marked to indicate that the task is complete.

You have now completed the application repackaging process from capturing an application to distributing a package to end users. By following this process, you have ensured that your application is ready for deployment, installation, use, and maintenance within the context of the infrastructure of your organization.

Optionally, if you are working in your company�s production database, you should remove the test applications Sample Conflict and QuickFacts from the database. If this is necessary, follow the procedure below.

Removing Tutorial Packages from the Software Manager Database

To ensure that your Software Manager database contains only production packages, remove the QuickFacts and Sample Conflict packages from the Software Manager database.

To delete the sample packages from the Software Manager database:

1. In Wise Package Studio, click the Tools tab. At the top of the Tools tab, double-click Software Manager.

Software Manager opens.

2. Select Packages menu > Delete.

The Delete Package dialog appears.

3. Select both the Sample Conflict and QuickFacts packages.

4. To delete the package�s source files from the share point directory, mark the checkbox at the bottom of the dialog.

5. Click OK.

The Sample Conflict and QuickFacts packages are deleted from the database.

6. Exit Software Manager and Wise Package Studio.

You have now completed this tutorial.

67

3: Tutorial

68

Index

Symbols

.NET Frameworkrequirements 15

A

Access 13

Application Gateway 20about 32bypassing proxy 34custom configuration 35database configuration 21default URL 32IIS version 35illustration 33integration issues 32requirements 14

authenticationdatabases 23

C

checking for updates 9

client installation 19, 28, 29about 28installing 29silently 30why use 28

Complete installation 18

D

databaseconfiguration issues 21connection 23creating new users 26creation options 27logon info 25requirements 13

database setup dialogs 24

documentation, using 6

domain logon 37

E

Enterprise Management Server 20

G

Getting Started Guide 6

grant db access 19, 21

guest account 21

H

helpabout 6using 7Windows Installer SDK 6

I

IISgrant db access 19version for Application

Gateway 20, 35version for Quality Assurance

19

installationclient 19, 28, 29complete 18what you need 16

L

launching Wise Package Studio 36

logoncurrent Windows logon 37if logon fails 36options 37to network 37Windows NT domain 37Workbench 37

M

Management Reports 20database configuration 21system requirements 14

manualaccessing online 6

Microsoft Access 13

Microsoft Data Engine 13

Microsoft Internet Information Service

see IIS

Minimal client 19

MSDE 13

N

network logon 37

new featuresRefer to Release Notes

newsgroups 7

P

Preflightabout 19database 24database configuration 21system requirements 14

prerequisitesinstallation 12tutorial 42

proxy server, bypassing for Application Gateway 34

Q

Quality Assurance module 19

R

readmeSee release notes

69

Index

reference manualSee manual

registrationby mail 39online 39

release notes 6

S

sales contact, Wise Solutions 8

serial number 16

share pointwhere to locate 22

Software Manager database 24

SQL ServerMicrosoft SQL Server 13

starting Wise Package Studio 36

support, Wise 7newsgroups 7online support 7

system requirements

.NET Framework 15Application Gateway 14database 13Management Reports 14Preflight 14Wise Package Studio 12

system requirements, productRefer to Getting Started Guide

T

technical support, Wise 7newsgroups 7online support 7

training 8

tutorial 41prerequisites 42Refer to Getting Started Guide

U

update, checking for 9

W

Windows Installerdeveloper documentation 6help 6

Windows Installer SDK Help 6

Wise Package Studiostarting 36

Wise Package Studio Professional Edition 18

Wise Package Studio Standard Edition 18

Wise Software Repositoryimporting sample package 42

Wise Solutionsconsulting 8getting updates 9sales contact 8technical support 7training 8

Workbench database 24

70

wise package studio, version 5 - danysoft · wise package studio, version 5.0 ... and a tutorial....

Documents