Issuu on Google+

InstallAnywhere 2011 Evaluation Guide


Legal Information Book Name:

InstallAnywhere 2011 Evaluation Guide

Part Number:

IA-1200-EG00

Product Release Date:

17 May 2011

Copyright Notice Copyright © 2006-2011 Flexera Software, Inc. and/or InstallShield Co. Inc. All Rights Reserved. This product contains proprietary and confidential technology, information and creative works owned by Flexera Software, Inc. and/or InstallShield Co. Inc. and their respective licensors, if any. Any use, copying, publication, distribution, display, modification, or transmission of such technology in whole or in part in any form or by any means without the prior express written permission of Flexera Software, Inc. and/or InstallShield Co. Inc. is strictly prohibited. Except where expressly provided by Flexera Software, Inc. and/or InstallShield Co. Inc. in writing, possession of this technology shall not be construed to confer any license or rights under any Flexera Software, Inc. and/or InstallShield Co. Inc. intellectual property rights, whether by estoppel, implication, or otherwise. All copies of the technology and related information, if allowed by Flexera Software, Inc. and/or InstallShield Co. Inc., must display this notice of copyright and ownership in full.

Trademarks Flexera Software, Inc., FLEXnet, FLEXnet Connect, FLEXnet Publisher, InstallAnywhere, InstallShield, LaunchAnywhere, SpeedFolder, and Zero G Software are registered trademarks or trademarks of Flexera Software, Inc. and/or InstallShield Co. Inc. in the United States of America and/or other countries. All other brand and product names mentioned herein are the trademarks and registered trademarks of their respective owners.

Restricted Rights Legend The software and documentation are “commercial items,” as that term is defined at 48 C.F.R. §2.101, consisting of “commercial computer software” and “commercial computer software documentation,” as such terms are used in 48 C.F.R. §12.212 or 48 C.F.R. §227.2702, as applicable. Consistent with 48 C.F.R. §12.212 or 48 C.F.R. §227.2702-1 through 227.7202-4, as applicable, the commercial computer software and commercial computer software documentation are being licensed to U.S. government end users (A) only as commercial items and (B) with only those rights as are granted to all other end users pursuant to the terms and conditions set forth in the Flexera Software, Inc. standard commercial agreement for this software. Unpublished rights reserved under the copyright laws of the United States of America.


Contents

1

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 For Systems Running InstallAnywhere (Authoring Environment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9 For Target Systems (Installer Environment). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 Supported Java Virtual Machines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 Installing InstallAnywhere 2011 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 Help Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 Help Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 Contacting Us. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

2

What’s New in InstallAnywhere 2011 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Merge Module Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 Common Uninstaller for Merge Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 Unified Progress Bar for Merge Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 External Resource Bundle Support for Merge Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 JVM Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 JVM Search Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 Consolidated JVM Settings on New JVM Settings Subtask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21 VM Pack Creation Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21 New Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 Expand 7-Zip (LZMA) Archive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 Expand TAR Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 Read/Modify XML File Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 Complex Rule Expressions With Multiple Operator Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 Logging Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23 Consolidated Log Settings in New Log Settings Subtask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23 Maintenance Mode and Uninstall Phase Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

3


Contents

Append STDERR and STDOUT to Install/Uninstall Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23 Consolidated Logging for Parent and Merge Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23 Variables Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24 Consolidated Variables Settings in New Variables Subtask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24 Selecting Variables from a List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24 Search and Replace for InstallAnywhere Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 Increased Number of User Magic Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 Avoid Substitution of Unknown Variables for Select Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 Choose Install Set Variables Now Recorded in Response Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26 Installer Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26 Option to Disable Cancellation of Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26 Option to Change Installer and LaunchAnywhere Icons (Windows). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26 Option to Specify .ico Files for Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 Signed JARs Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 Prevent Multiple Launches of Installer/Uninstaller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 Disk-Space Checking and Related Display Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 Change Version at Build Time Using the productVersion Parameter in build.exe Command Line . . . . . . . . . . . . . . . . .28 Billboard Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 Revised Licensing Procedure and Requirements for InstallAnywhere 2011 . . . . . . . . . . . . . . . . . . . . . . . . . . .29

3

Key InstallAnywhere Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 InstallAnywhere Technology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32 The InstallAnywhere Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32 Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34 Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34 Silent and Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34 LaunchAnywhere™. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 InstallAnywhere’s Custom Code API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 Localizing Installers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 InstallAnywhere Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36 SpeedFolder™ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36 Install Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37 Magic Folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

4

Using the Project Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Starting InstallAnywhere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 Creating a New Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 Setting Project Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42 Adding Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

4

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Contents

Choosing a Main Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46 Setting a Classpath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48 Building the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 Trying the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50 Testing the Uninstaller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

5

Using the Advanced Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Opening a Project in the Advanced Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 Choosing Custom Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56 Adding a Billboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56 Setting a Custom Graphic for the Splash Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 Choosing a Specific Panel Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60 Adding Pre-Install Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61 Defining the Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 Adding Files to the Install Task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 Adding a LaunchAnywhere Executable to the Install Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68 Creating and Applying Build Configuration Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72 Adding Post-Install Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74 Customizing the Uninstaller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80 Building the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80 Testing the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84

6

Key InstallAnywhere Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

5


Contents

6

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


1 Introduction

InstallAnywhere is the leading multiplatform development solution for software producers needing to deliver a professional and consistent installation experience for cross-platform desktop and server applications. From a single project file and build environment, InstallAnywhere enables developers to create reliable installations for the broadest range of current platforms including Windows, Linux, MAC OS X, Solaris, AIX, HP-UX and IBM iSeries. From a company who set the standard for installations with InstallShield; InstallAnywhere brings that experience and knowledge for multiplatform developers, which allows developers to create high-quality installations, reducing technical support costs and increasing customer satisfaction. InstallAnywhere 2011 has more capabilities to support distributed install development and deployment. As software teams implement agile development practices, they need more flexible ways to author, build and package installations. InstallAnywhere 2011 contains multiple enhancements to address key issues related to distributed and component-based install development and deployment. The InstallAnywhere 2011 Evaluation Guide introduces evaluators and reviewers to key functionality of InstallAnywhere 2011. This Guide introduces you to the new features in InstallAnywhere 2011, describes some key concepts, provides tutorials for using both the Project Wizard and Advanced Designer interfaces, and then provides links to procedures that explain how to perform the most common InstallAnywhere tasks.

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

7


Chapter 1: Introduction System Requirements

The InstallAnywhere 2011 Evaluation Guide is organized into the following chapters: Table 1-1 • InstallAnywhere 2011 Evaluation Guide Topic

Content

What’s New in InstallAnywhere 2011

Provides a brief description of the new features included in InstallAnywhere 2011.

Key InstallAnywhere Concepts

Describes InstallAnywhere’s conceptual framework.

Using the Project Wizard

Guides you through the process of using the Project Wizard interface in a simple step-by-step manner to create an installer for a sample Java application.

Using the Advanced Designer

Explains how to use the Advanced Designer interface to create a more customized installer.

Key InstallAnywhere Tasks

Provides links to procedures that explain how to perform the most common InstallAnywhere tasks.

The remainder of this chapter provides the following information: •

System Requirements

Installing InstallAnywhere 2011

Help Resources

Contacting Us

System Requirements InstallAnywhere 2011 has the following system requirements:

8

For Systems Running InstallAnywhere (Authoring Environment)

For Target Systems (Installer Environment)

Supported Java Virtual Machines

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 1: Introduction System Requirements

For Systems Running InstallAnywhere (Authoring Environment) InstallAnywhere 2011 has the following system requirements for systems running the InstallAnywhere authoring environment: Item

Description

RAM

128 MB free

Color

Minimum of 8-bit color depth (256 colors)

Resolution

Minimum 1024 x 768 resolution

Operating System

InstallAnywhere runs on the latest versions of these operating systems, fully updated with the most recent patches and service packs: Windows

Windows 7 (32-bit and 64-bit)

Windows Vista

Windows XP

Windows 2000

Macintosh

Mac OS X 10.4, 10.5, and 10.6 with Java 1.6

Linux

Red Hat Enterprise Linux 4 and 5 (x86)

Red Hat Enterprise Linux 6 (32-bit and 64-bit)

SUSE Linux 9, 10 (32-bit x86)

SUSE Linux 11.2, 11.3 (32-bit x86 and 64-bit)

Ubuntu 10.10 (32-bit x86)

Fedora 14

Note • When you install InstallAnywhere on a Linux system, the installation attempts to create a symbolic link to the default Linux loader (/lib/ld-linux.so.2) if a link with the same name is not already present. The symbolic link is necessary for the host ID to be displayed on the Host ID dialog, and it is also necessary for successful node-locked licensing. The link is present on systems that are Linux Standard Base (LSB) 3 compliant, but it may not be present on systems that are not LSB compliant. For more information, see Knowledge Base article Q209204.

Solaris

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

Solaris 9, 10, and 11 (SPARC)

9


Chapter 1: Introduction System Requirements

Item

Description

Operating System

HP-UX

HP-UX 11i (PA-RISC)

AIX

AIX 5.2, 5.3, and 6.1 (Power/PowerPC)

(Continued)

Note • A Japanese-localized version of InstallAnywhere Enterprise Edition is available on the Windows platform only. Installers can be built from any platform for any other platform or language. Localizations for 31 languages are included with Enterprise Edition. Localizations for 9 languages are included with Standard Edition.

For Target Systems (Installer Environment) The following are the system requirements for systems running InstallAnywhere 2011 installers: Item

Description

RAM

64 MB free

Color

Minimum of 8-bit color depth (256 colors)

Resolution

Minimum 640 x 480 screen resolution

Operating System

Installers run on any version of these operating systems, as long as the operating system supports Java 1.4 or newer:

Note • InstallAnywhere installers are not supported on beta or on early access releases unless explicitly mentioned.

Windows

Macintosh

10

Windows 7 (x86 and x64)

Windows Vista (x86 and x64)

Windows XP (x86, x64, Itanium 2, and AMD-64)

Windows Server 2008 (x86 and x64)

Windows Server 2008 R2 (64-bit)

Windows Server 2003 (x86, x64, Itanium 2, and AMD-64)

Windows 2000 and NT (x86)

Mac OS X 10.2, 10.3, 10.4, 10.5 and 10.6 (Snow Leopard)

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 1: Introduction System Requirements

Item

Description

Operating System

Linux

(Continued)

Solaris

Red Hat Enterprise Linux 4 and 5 (x86, Itanium 2, and AMD-64)

Red Hat Enterprise Linux 6 (32-bit and 64-bit)

SUSE Linux 9, 10, 11.2, 11.3 (x86)

Linux on zSeries

Ubuntu 9.10 (x86)

Fedora 13 and 14

Solaris 9, 10, and 11 (SPARC, x86, and AMD-64) Solaris 11 (Intel)

HP-UX

HP-UX 11i (Itanium 2 and PA-RISC)

AIX

AIX 5.2, 5.3, 6.1, and 7.1 (Power/PowerPC)

IBM

i5/OS (OS/400) on System i - V5R3 and V5R4 (Enterprise Edition only)

z/OS

FreeBSD

Other Linux and Unix operating systems (POSIX-compliant shell required)

Other

Supported Java Virtual Machines InstallAnywhere 2011 supports the following Java virtual machines: Manufacturer

Versions

Sun

1.4.x, 1.5.x, 1.6.x

IBM

1.4.x, 1.5.x, 1.6.x

Apple

1.4.x, 1.5.x, 1.6.x

HP

1.4.x, 1.5.x, 1.6.x

The InstallAnywhere installer installs Java 1.6 VM packs. Any Java virtual machine can be bundled with an installer ensuring that the target system meets the minimum requirements for both the installers and your applications. To download additional VM packs, go to http://www.flexerasoftware.com/installanywhere/utilities and open the VM Packs tab.

Note • InstallAnywhere installers are not supported on beta or on early access releases of Java. InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

11


Chapter 1: Introduction Installing InstallAnywhere 2011

Installing InstallAnywhere 2011 To install an evaluation copy of InstallAnywhere 2011, perform the following steps:

Task:

To install an evaluation copy of InstallAnywhere 2010: 1.

Open the Flexera Software Product Trials page: http://www.flexerasoftware.com/resources/trials.htm#installanywhere

2.

Click the link for the InstallAnywhere edition you want to try and follow the instructions to complete the download process.

Note • InstallAnywhere is available in two editions: Enterprise and Standard. For a complete list of the features available in each edition, locate the InstallAnywhere features list on the Flexera Software Web site. 3.

Run the installer and follow its on-screen instructions.

Help Resources There are several resources available to better familiarize yourself with InstallAnywhere. Table 1-2 • InstallAnywhere Help Resources Item

Description

InstallAnywhere 2011 Help Library

The InstallAnywhere Help Library contains detailed information on how to use InstallAnywhere to create multi-platform installers, along with tutorials to familiarize you with the Project Wizard and Advanced Designer interfaces. •

Product Help Library—You can open the Help Library from the Advanced Designer interface by selecting InstallAnywhere Help from the Help menu or by clicking the Help button.

Web-Based Online Help—Web-based online help is available to you 24 hours a day, seven days a week, on our Web site at: http://helpnet.flexerasoftware.com

Documentation Center—InstallAnywhere documentation is also available in PDF format from the Flexera Software Documentation Center: http://support.flexerasoftware.com/doc/List.aspx?m=installation

Knowledge Base

For answers to many commonly asked questions and new information about InstallAnywhere 2011, visit the Knowledge Base at: http://kb.flexerasoftware.com

12

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 1: Introduction Help Resources

Table 1-2 • InstallAnywhere Help Resources Item

Description

InstallAnywhere Online Communities

The free online InstallAnywhere community allows you to learn from other installation developers at: http://community.flexerasoftware.com/forumdisplay.php?f=213

Support

A constantly updated support portal filled with answers, news, tips, and other resources for InstallAnywhere users is available at: http://www.flexerasoftware.com/support.htm

Webinars

Experts walk you through new features and capabilities available in InstallAnywhere 2011. Webinars can be found at: http://www.flexerasoftware.com/resources/webinars.htm#installanywhere

Files & Utilities

Obtain the latest custom code, VM packs, and merge modules from: http://www.flexerasoftware.com/products/installanywhere/files-utilities.htm

Help Conventions In this Evaluation Guide and in the InstallAnywhere Help Library, reader alert and style conventions are used to bring your attention to specific information or help you identify information.

Reader Alert Conventions Reader alerts are used throughout this documentation to notify you of both supplementary and essential information. The following table explains the meaning of each alert. Table 1-3 • Reader Alert Conventions Image

Alert Name

Description

Note

Notes are used to draw attention to pieces of information that should stand out.

Important Note

Important notes are used for information that is essential for users to read.

Caution

Cautions indicate that this information is critical to the success of the desired feature or product functionality.

Tip

Tips are used to indicate helpful information that could assist you in better utilizing the desired function or feature.

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

13


Chapter 1: Introduction Help Resources

Table 1-3 • Reader Alert Conventions (cont.) Image

Alert Name

Description

Best Practices

Best Practices alerts instruct you on the best way to accomplish a task.

Edition-Specific Note

Edition-specific notes indicate that the information applies to a specific edition of a product (such as Professional or Premier edition).

Project-Specific Note

Project-specific notes are used to highlight information that may vary depending on the project type used (such as a Basic MSI or Merge Module project).

Version-Specific Note

Version-specific notes indicate that the information applies to a specific version of a product (such as Version 9.0 or Version 11.0).

Windows Logo Guideline

Windows Logo Guideline alerts accompany Microsoft logo compliance requirements and recommendations.

Security

Security alerts identify security issues.

Task

The Task graphic indicates that procedural instructions follow.

Advanced Note

Advanced notes are used in training manuals to identify information that is for advanced users.

Lab

In training manuals, the Lab graphic indicates that a lab exercise follows.

Tutorial

In training manuals, the Tutorial graphic indicates that a tutorial exercise follows.

Style Conventions The following style conventions are used throughout this documentation. Table 1-4 • Style Conventions

14

Style

Example

Description

User Interface Elements

On the File menu, click Open.

User interface elements appear in bold when referenced in tasks.

Variables

fileName

Variables appear in italics.

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 1: Introduction Help Resources

Table 1-4 • Style Conventions (cont.) Style

Example

Description

Code

#define HWND_BROADCAST 0xffff

Code snippets appear in a monospace typeface.

User-Inputted Text

Type $D(install).

Text that is to be entered as a literal value is displayed in a monospace typeface, in bold, and in blue.

File Names and Directory Paths

My files are located in the C:\MyDocuments\SampleCode directory.

File names and directory paths are presented in a monospace typeface.

.INI File Text

Insert the line LimitedUI=Y into the file to display only the Welcome dialog box when the Windows Installer package is run.

Text in .INI files is presented in a monospace typeface.

Command-Line Statements

To run the installation silently, enter:

Command-line statements and parameters are presented in a monospace typeface.

Environment Variables

Set the value of the windir environment variable.

Environment variables are presented in a monospace typeface.

Examples

Create two groups, one called Admins and the other called General.

Examples are presented in bold.

Functions

FeatureAddItem adds a new feature to a script-created feature set.

Functions are presented in presented in bold.

Properties

In the Name property, enter a name for this custom control that is unique among all of the controls in your project.

Properties are presented in bold.

If you type an incorrect parameter, the message

Screen output (from a log file or from the console) is displayed in a monospace typeface, and in blue.

Screen Output

Setup.exe /s /v/qn

The system cannot find the path specified.

is displayed. Links

Obtain the latest modules, white papers, project samples, and more from:

Links appear in blue.

http://www.yourcompany.com/downloads.htm

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

15


Chapter 1: Introduction Contacting Us

Contacting Us You may contact us from anywhere in the world by visiting our Web site at: http://www.flexerasoftware.com

Customer Feedback We invite you to test both our vision and our execution with this release. If there is anything we can do better, or if you need assistance, please do not hesitate to contact us at: http://www.flexerasoftware.com/promolanding/productfeedback.htm

16

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


2 What’s New in InstallAnywhere 2011

InstallAnywhere continues to deliver the functionality developers need to build successful multi-platform installations. InstallAnywhere 2011 includes new features in the following categories: •

Merge Module Enhancements

JVM Enhancements

New Actions

Complex Rule Expressions With Multiple Operator Support

Logging Enhancements

Variables Enhancements

Installer Enhancements

Revised Licensing Procedure and Requirements for InstallAnywhere 2011

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

17


Chapter 2: What’s New in InstallAnywhere 2011 Merge Module Enhancements

Merge Module Enhancements InstallAnywhere 2011 includes the following merge module enhancements: •

Common Uninstaller for Merge Modules

Unified Progress Bar for Merge Modules

External Resource Bundle Support for Merge Modules

Common Uninstaller for Merge Modules With InstallAnywhere 2011, you can choose to implement a single uninstaller which can uninstall both your main project as well as your merge modules. To specify this option for a dynamic merge module, select the Uninstall Merge Module when parent is uninstalled option on the Install tab of the Dynamic Merge Module customizer on the Organization > Modules subtask for the specific merge module. The point of uninstallation of merge modules can also be configured using the Uninstall Merge Modules uninstaller action in the Uninstall task. You can also specify this option for an individual merge module by selecting the Uninstall Merge Module when parent is uninstalled option on the Install Merge Module action customizer in the Install task.

Unified Progress Bar for Merge Modules In releases prior to InstallAnywhere 2011, when a merge module was being installed, only the message Installing Merge Module was displayed on the Install Progress panel, with no indication of progress. Because large merge modules take a longer time to install, the end user was not informed of which part of the merge module was currently getting installed. Starting with InstallAnywhere 2011, the installation progress of merge modules is merged into the main installer’s progress information. Therefore, the end user can see the installation progress of a merge module reflected in the main installer’s progress bar on the Install Progress panel.

External Resource Bundle Support for Merge Modules Starting with InstallAnywhere 2011, merge modules can access their own external resource bundles and are also able to access the external resource bundles of their parent installer during the installation and uninstallation phases. This is applicable to one-level nested merge modules and to multiple-merge modules which get installed with a single parent.

18

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 2: What’s New in InstallAnywhere 2011 JVM Enhancements

JVM Enhancements InstallAnywhere 2011 includes the following JVM enhancements: •

JVM Search Enhancements

Consolidated JVM Settings on New JVM Settings Subtask

VM Pack Creation Utility

JVM Search Enhancements InstallAnywhere 2011 gives you finer control over the JVM that is selected by the installer launcher. You can either choose to go with the default search algorithm or define JVM specs through which you can control the search directories, Windows registry search, and also control the validation of the found VM. •

Specifying VM Search Instructions on Build Targets Subtab

Using JVM Spec Files

Specifying VM Search Instructions on Build Targets Subtab You can now specify new VM Search Instructions for each build target on the Build Targets subtab of the Build Configurations tab of the Build task. When setting the VM search instructions, you specify whether or not the installer should search for a VM on the target system, and whether to use a bundled VM or to download a JVM in VM pack format from a URL you specify.

Figure 1: VM Search Instructions Area of Windows Build Target on Build Targets Subtab

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

19


Chapter 2: What’s New in InstallAnywhere 2011 JVM Enhancements

If you do not want to include a Java virtual machine with this build target, select the Without VM option. If you select this option, you also need to select one of the following options to specify how the installer will find the VM it will use: •

Search for VM; if not found exit—Select this option to instruct the installer to search the target machine for a VM. If one is not found, the installer will exit.

Search for VM; if not found, download from URL—Select this option to instruct the installer to search the target machine for a VM. If one is not found, the installer will download a VM from the URL specified in the text box.

Don’t search for VM; download from URL—Select this option to instruct the installer to always download a VM from the URL specified in the text box.

If you want to include a Java virtual machine with this build target, select the With VM option. If you select this option, you also need to select one of the following options to specify whether the installer should use the bundled VM if a VM is found on the target machine. •

Search for VM; if not found, use bundled VM—Select this option to instruct the installer to search the target machine for a VM. If one is not found, the installer will use the bundled VM.

Don’t search for VM; use bundled VM—Select this option to instruct the installer to always use the bundled VM, even if a VM exists on the target machine.

VM to Bundle with Installer—If you select the With VM option, select a bundled VM from this list.

Important • While you can obtain VM packs by downloading them from the Flexera Software Web site, these VM packs are provided for your convenience only and should not be referenced by your installation project. Therefore, if you select the Search for VM; if not found, download from URL or Don’t search for VM; download from URL options, do not specify a URL pointing to one of the VM packs on the www.flexerasoftware.com website. If you do, the build will fail. Instead, you should host the VM pack on your own file server or FTP server and specify the URL to that location.

Using JVM Spec Files If you instruct the installer to search for a VM, it will use the JVM search instruction files specified in the JVM Search Settings list on the Build Targets subtab. You can instruct the installer to use more than one JVM spec file at the same time by listing more than one file in the JVM Search Settings list. InstallAnywhere provides a set of JVM spec files which target all the supported platforms that you can use or you can write one of your own.

20

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 2: What’s New in InstallAnywhere 2011 JVM Enhancements

Consolidated JVM Settings on New JVM Settings Subtask In InstallAnywhere 2011, all the JVM-related settings have been consolidated into a single, convenient subtask: Project > JVM Settings. Previously, these JVM-related settings were spread across the Project > Platforms, Project > Config, and Project > Java subtasks. The Project > JVM Settings subtask includes JVM settings organized into three tabs: •

General Settings—Use to modify the settings for the entire project, such as classpath settings for your project’s LaunchAnywhere applications.

Installer Settings—Use to modify the settings for the installer launcher, such as defining a list of valid VMs for installers built from this project, setting the heap size for the VMs, setting optional installer arguments, deciding whether to install the bundled/downloaded Java VM, and defining classpath settings.

Search Panel Settings—Use to specify criteria to use to find valid VMs for the application you are installing.

VM Pack Creation Utility In InstallAnywhere 2011, you can use the Create VM Pack dialog box, which is opened when you select Create VM Pack on the File menu, to create a VM pack for any platform. On the Create VM Pack dialog box, you specify the directory where the VM is installed, the directory where you want to store the new VM pack, the platform of the new VM pack, and a name for the VM pack. You can also use the VM Pack utility as a standalone tool on a machine where InstallAnywhere is not installed.

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

21


Chapter 2: What’s New in InstallAnywhere 2011 New Actions

New Actions InstallAnywhere 2011 includes three new actions: Expand Archive (7-zip), Expand Archive (TAR), and Read/Modify XML File.

Expand 7-Zip (LZMA) Archive In InstallAnywhere 2011, you can use the Expand Archive (7-zip) action to expand a 7-zip or LZMA compressed archive file. You can now make use of LZMA compression to compress your files and use this new action to expand these archives in a fast and reliable way. The Expand Archive (7-zip) action is available in the Install phase.

Expand TAR Archive In InstallAnywhere 2011, you can use the Expand Archive (TAR) action to expand a TAR archive file on the target system. This action has the advantage of preserving the permissions of all files that are part of the TAR archive.

Read/Modify XML File Action You can use the Read/Modify XML File action to modify an existing XML file on the target system or an XML file that the installer deploys on the target system. You can specify whether to read a specific value, replace a specific value, or find an occurrence of a specific value. You can search by XML element, subelement, or attribute, and can specify a variable to store the value. To perform complex modifications of an XML file, you can use multiple Read/ Modify XML File actions.

Complex Rule Expressions With Multiple Operator Support In InstallAnywhere 2011, you can now write complex rule expressions using multiple logical operators and precedence operators. When you add multiple rules to an item, each rule’s unique ID is listed in the Rule Expression field and, by default, the rules are joined by the AND operator. If you want to write complex rule expressions, you can edit the expression in the Rule Expression field to use multiple logical operators—such as AND (&&), OR (||), and NOT (!)—and precedence operators (parentheses) to express the relationship between two or more rules. To validate the rule, click the Validate Rule Expression button.

22

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 2: What’s New in InstallAnywhere 2011 Logging Enhancements

Logging Enhancements InstallAnywhere 2011 includes the following enhancements to its logging functionality: •

Consolidated Log Settings in New Log Settings Subtask

Maintenance Mode and Uninstall Phase Logs

Append STDERR and STDOUT to Install/Uninstall Log

Consolidated Logging for Parent and Merge Modules

Consolidated Log Settings in New Log Settings Subtask In InstallAnywhere 2011, all of the logging-related settings have been consolidated into a single, convenient subtask: Project > Log Settings. On the Log Settings subtask, you can enable logging during installation and also during the Maintenance Mode options (Uninstall, Add Features, Repair Installation, Remove Features), and can choose to append the stderr and stdout output to the install/uninstall logs.

Maintenance Mode and Uninstall Phase Logs In InstallAnywhere 2011, the logging feature has been extended to the Uninstall and Maintenance Mode phases (Install, Add, Repair, Remove, and Uninstall). You can select the phases for which you want to enable logging and specify the path for each log file.

Append STDERR and STDOUT to Install/Uninstall Log In InstallAnywhere 2011, the stderr and stdout entries of any installation can be appended to the install/uninstall logs, which makes it easier to perform installation/uninstallation debugging. You can send installer debug output (stderr and stdout) to a console (or Console.app on Mac OS X) or store it in a file.

Consolidated Logging for Parent and Merge Modules A merge module’s installation log can now be consolidated into the parent's installation log by selecting the Add merge module log to parent log option available in the merge module's customizer. For merge modules that are imported as a dynamic merge module from Organization > Merge Modules subtask, then this setting is available in the Install section of the customizer.

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

23


Chapter 2: What’s New in InstallAnywhere 2011 Variables Enhancements

Variables Enhancements InstallAnywhere 2011 provides several enhancements that make it easier to use and manage variables: •

Consolidated Variables Settings in New Variables Subtask

Selecting Variables from a List

Search and Replace for InstallAnywhere Variables

Increased Number of User Magic Folders

Avoid Substitution of Unknown Variables for Select Actions

Choose Install Set Variables Now Recorded in Response Files

Consolidated Variables Settings in New Variables Subtask To enable you to manage variables more effectively, a new Project > Variables subtask is introduced, which you can use to advertise variables for merge modules, list variables to encrypt in or exclude from the response files, and set security options. The Project > Variables subtask also includes a scrollable list of all variables defined in the installation project. Each listed variable includes a Substitute Recursively option, enabling you to specify that you do not want the variable to be substituted at runtime. In cases where you expect that the variable could contain multiple $ characters—such as in a user-defined password—you would clear the selection of the Substitute Recursively option for a variable.

Selecting Variables from a List In InstallAnywhere 2011, instead of having to manually type in the name of variables in text boxes or text areas in your installation project, you can open the Choose Variable dialog box and select a variable from a list. While you are editing the contents of a text box or a text area, you can open the Choose Variable dialog box by pressing Alt + V. The Choose Variable dialog box lists all of the variables available in your project, grouped by category, with embedded help for the selected variable. Whenever you add a new variable to your installation project, the Choose Variable dialog box is refreshed to include it.

24

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 2: What’s New in InstallAnywhere 2011 Variables Enhancements

Search and Replace for InstallAnywhere Variables In InstallAnywhere 2011, you can search a project to locate all references to a specific variable. You can choose to search for a variable in any of the installation tasks/phases (Pre-Install, Install, Post-Install, Pre-Uninstall, Uninstall, Post-Uninstall) and can choose to search Features and/or Components. You can also perform global replacements of variables. You can search for an exact match of a variable or for a partial text string in a variable. You also have an Ignore Case option. To perform a variable search, select Search on the File menu or press Ctrl + F. Search results are displayed on the Search Results dialog box.

Increased Number of User Magic Folders InstallAnywhere 2011 has increased the number of user Magic Folders from 10 to 25.

Avoid Substitution of Unknown Variables for Select Actions With InstallAnywhere 2011, you can avoid the substitution of unknown variables for the select actions using the Do not substitute unknown variables option in the customizer of the action. The select actions include: •

Execute Command Action

Execute Target File

Execute Script / Batch File

Set InstallAnywhere Variable (Single) Action

Set InstallAnywhere Variable (Multiple) Action

If your installation project includes a nested variable which could possibly contain multiple $ characters (such as a password), this could result in the creation of an unknown variable. Therefore, select the Do not substitute unknown variables option to instruct InstallAnywhere to only resolve InstallAnywhere variables which are listed in the project under Project > Variables (the known variables).

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

25


Chapter 2: What’s New in InstallAnywhere 2011 Installer Enhancements

Choose Install Set Variables Now Recorded in Response Files In InstallAnywhere 2011, the Choose Install Set panel/console variables are now recorded in response files. Here is an example: #Choose Product Features #---------------------CHOSEN_FEATURE_LIST=Application,Help CHOSEN_INSTALL_FEATURE_LIST=Application,Help CHOSEN_INSTALL_SET=Typical

Installer Enhancements InstallAnywhere 2011 provides the following enhancements to installer design and functionality: •

Option to Disable Cancellation of Installation

Option to Change Installer and LaunchAnywhere Icons (Windows)

Option to Specify .ico Files for Icons

Signed JARs Support

Prevent Multiple Launches of Installer/Uninstaller

Disk-Space Checking and Related Display Enhancements

Change Version at Build Time Using the productVersion Parameter in build.exe Command Line

Billboard Timers

Option to Disable Cancellation of Installation In InstallAnywhere 2011, you can select the Disable cancel button when install is in progress option on the Project > Info subtask to prevent end users from being able to cancel an installation using the Cancel button (or the close [X] button). Disabling the Cancel button during installation helps to avoid unfinished installations.

Option to Change Installer and LaunchAnywhere Icons (Windows) In InstallAnywhere 2011, you can specify a custom icon to be displayed for the Installer or the LaunchAnywhere:

26

Installer—The installer icon can be specified on the Installer Icon tab of the Installer UI > Look & Feel subtask.

LaunchAnywhere—The LaunchAnywhere icon can be specified in the customizer of the LaunchAnywhere.

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 2: What’s New in InstallAnywhere 2011 Installer Enhancements

Note • This feature is available for Windows only.

Option to Specify .ico Files for Icons In previous versions of InstallAnywhere, you could only specify a 16x16 or 32x32 .gif file as an icon. These .gif files were converted to .ico files internally, resulting in a significant reduction in quality. In InstallAnywhere 2011, this issue has been addressed. You can now specify an .ico file for an icon. •

Installer—On the Installer Icon tab of the Installer UI > Look & Feel subtask, you can specify a custom Windows icon file (.ico) to be used for the installer.

LaunchAnywhere—On the Choose Icon dialog box, which is opened from a LaunchAnywhere customizer, you can also select an .ico file.

Note • You can specify an icon (.ico) file for the installer on Windows platforms only.

Signed JARs Support InstallAnywhere now supports adding signed JARs as dependencies to Custom Code Actions, Custom Code Panels, Custom Code Consoles, and Custom Rules. Also, a JAR or ZIP file that contains custom code can now be signed. In previous versions of InstallAnywhere, although you could build a project that contained signed JARs, the installer that was generated would not launch. InstallAnywhere would extract all entries of the signed JAR, including the manifests, and would add them to the installer ZIP files (such as execute.zip). But when the installer ZIP files were added to the classpath of the installer, the installer would fail to launch because Java Security Exceptions would be thrown when initializing the JAR. Starting with InstallAnywhere 2011, in the case of a signed JAR, InstallAnywhere will not unpack the JAR and the JAR entry will be left intact inside the execute.zip file during build time. Therefore, during runtime, the signed JARs are extracted to temporary directories and are added to the InstallAnywhere classpath, making them ready to be consumed for the custom codes or any relevant actions requiring the contents of this signed JAR.

Prevent Multiple Launches of Installer/Uninstaller InstallAnywhere 2011 enables you to prevent end users from being permitted to launch multiple simultaneous instances of the same installer or uninstaller (as identified by having the same Product ID). This can be specified using the Prevent multiple launches of an installer at a given time option on the Project > Info subtask.

Note • Invoking multiple simultaneous instances of the installer or uninstaller could corrupt the InstallAnywhere registry. InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

27


Chapter 2: What’s New in InstallAnywhere 2011 Installer Enhancements

Disk-Space Checking and Related Display Enhancements In InstallAnywhere 2011, you can create an installer that performs a disk space check at various points in the installation life cycle, and you can customize how that disk space is displayed. To display disk space on the on the Pre-Installation Summary panel of the installer, select the Disk Space Information in setting on the customizer of the Pre-Install Summary panel, and select the magnitude you wish to use (Bytes, KiloBytes, MegaBytes, or GigaBytes) from the list. If you want to use more than one magnitude to display disk space information (such as to displaying Free Disk Space in GBs while showing Required Disk Space in MBs), you can use the following variables. •

Free Disk Space $FREE_DISK_SPACE_BYTES$ $FREE_DISK_SPACE_KILOBYTES$ $FREE_DISK_SPACE_MEGABYTES$ $FREE_DISK_SPACE_GIGABYTES$

Required Disk Space $REQUIRED_DISK_SPACE_BYTES$ $REQUIRED_DISK_SPACE_KILOBYTES$ $REQUIRED_DISK_SPACE_MEGABYTES$ $REQUIRED_DISK_SPACE_GIGABYTES$

Change Version at Build Time Using the productVersion Parameter in build.exe Command Line In InstallAnywhere 2011, you can use the productVersion parameter in the command line of build.exe to change the version of an InstallAnywhere project at build time. The following example changes the version to 2.1.3.24: build.exe MyProduct.iap_xml productVersion=2.1.3.24

Note • Versions are conventionally represented in the following format: [Major].[Minor].[Revision].[Subrevision], such as: 2.1.3.24.

Billboard Timers In InstallAnywhere 2011, you now have more control over how much time billboards will be shown while the installation is in progress. When multiple billboards are specified, you can control how much time each billboard will be displayed while the installation is in progress by using the Display billboards for every nn seconds option on the Installer UI > Billboards subtask. The default time for a billboard to be displayed is 0.5 seconds. To change this time period, select the Display billboards for every nn seconds option and enter a number in the seconds box.

28

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 2: What’s New in InstallAnywhere 2011 Revised Licensing Procedure and Requirements for InstallAnywhere 2011

Revised Licensing Procedure and Requirements for InstallAnywhere 2011 The procedure for setting up InstallAnywhere licensing has been revised. In earlier versions of InstallAnywhere, users with node-locked licenses registered their product by entering a serial number, while users with concurrent licenses used a Flexera Software-generated license file. In InstallAnywhere 2011, both license models (traditional node-locked licenses and concurrent licenses) require a license file that is generated through a new Web site: the Flexera Software Product and License Center. •

Node-locked licenses—With this license model, the product license is tied to a specific user and machine. This model is the traditional option and the one that is most often purchased. The license file is based on the host ID (the Ethernet/MAC address of the network interface card) for the machine on which InstallAnywhere is installed.

Concurrent licenses—This model enables sharing or floating of InstallAnywhere product licenses among multiple users. With this model, you set up a licensing server in your environment, and install InstallAnywhere on as many machines as needed. The InstallAnywhere license is tied to the specific licensing server, and each machine checks out a license from the server when a user launches InstallAnywhere. The licensing server manages how many instances of InstallAnywhere can be run simultaneously based on the terms of the concurrent license that is purchased. For this model, the license file is based on the host ID of the licensing server.

Use the Flexera Software Product and License Center (https://flexerasoftware.subscribenet.com/) to generate and download the node-locked or concurrent license files that you have purchased and to view the license generation history. To learn how to use this site and set up the licensing for either licensing model, see the licensing instructions at: http://www.flexerasoftware.com/instructions/product-license.htm Note that if you have not purchased a license for InstallAnywhere, you can install it and use it for a limited number of days without setting up the licensing. The new licensing wizard that InstallAnywhere displays whenever you launch InstallAnywhere in evaluation mode shows you how many days are left in the evaluation period. If you do not set up the licensing within the evaluation period, InstallAnywhere stops working when the evaluation period ends. You can set up licensing at any time before or after the evaluation period ends.

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

29


Chapter 2: What’s New in InstallAnywhere 2011 Revised Licensing Procedure and Requirements for InstallAnywhere 2011

30

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


3 Key InstallAnywhere Concepts

For many users, learning how to use InstallAnywhere is aided by an understanding of its conceptual framework. The following InstallAnywhere concepts are described below: •

InstallAnywhere Technology

The InstallAnywhere Environment

Actions

Rules

Silent and Console Mode

LaunchAnywhere™

InstallAnywhere’s Custom Code API

Localizing Installers

InstallAnywhere Variables

SpeedFolder™

Install Sets

Features

Components

Magic Folders

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

31


Chapter 3: Key InstallAnywhere Concepts InstallAnywhere Technology

InstallAnywhere Technology Before building your first installer, it is important to understand the fundamentals behind InstallAnywhere’s multiplatform installer technology. The installer may be packaged in two ways: •

Executable installers with a native wrapper—Executable installers with a native wrapper may be invoked like any other native application, either by typing their name directly onto a command-line interface or by double-clicking their icon in a GUI environment. If you are deploying a Java application, executable installers have the advantage of being able to create LaunchAnywhere executables, which make it possible to run installed Java applications in a similar fashion. InstallAnywhere supports executable installers on Windows, Solaris, Linux, and Mac OS X.

Java-enabled installer—The Java-enabled option may be used to deploy onto other platforms without executable support, such as i5/OS. The Java-enabled installer, rather than being a native executable, is a .jar file. Although it can run on any Java-enabled platform, Pure Java installers must be run using the traditional invocation mechanisms of the target platform. Typically this means that the deployment needs to be executed from the command line.

In general, you can build executable installers for as many platforms as you are targeting. You also have the option of bundling a VM with the installer—thus ensuring its availability for installation and application use. The bundled VM may be used by the installer and the installed product. For more information on downloading VM packs to bundle with your installer, please see Adding Pre-Install Actions. Alternatively, executable installers can search the target machine for a suitable Virtual Machine to use. To likewise identify a VM for use with the LaunchAnywhere launchers your installer deploys, a similar search can be applied, either automatically or on demand. You can allow the user to select from a list of valid VMs found by the search or to independently choose a VM that does not appear in the search results.

The InstallAnywhere Environment InstallAnywhere runs in two modes: the Project Wizard and the Advanced Designer. •

Project Wizard—The Project Wizard creates simple, straightforward installers in minutes. In many situations, you may need to build installers that execute custom code, display license agreements, or deploy to multiple locations on the target system.

Advanced Designer—Use the Advanced Designer for these purposes, as it provides greater control and flexibility in installer design.

You can combine the two modes by building a simple installer in the Project Wizard and switch to the Advanced Designer in order to add custom features. By default, InstallAnywhere starts up in Project Wizard mode, but can be configured to start in the Advanced Designer.

Note • In addition to the Project Wizard and Advanced Designer environments, InstallAnywhere provides a command-line build tool and integrates with Ant (through the use of the InstallAnywhere Ant task—iaant.jar). Expert users can also leverage InstallAnywhere APIs to extend and automate InstallAnywhere functionality.

32

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 3: Key InstallAnywhere Concepts The InstallAnywhere Environment

Setting the InstallAnywhere Startup Interface to the Advanced Designer To set the InstallAnywhere startup interface to the Advanced Designer, perform the following steps:

Task:

To configure InstallAnywhere to start in Advanced Designer mode: 1.

Choose Edit > Preferences. The InstallAnywhere Preferences dialog box opens.

2.

On the General Settings tab, set InstallAnywhere Startup to Advanced Designer.

3.

Click OK.

Functionality Available in the Advanced Designer Use the Advanced Designer if you need any of the following functionality: •

Install multiple Install Sets (Typical Install, Minimum Install, etc.).

Install multiple Java applications.

Create additional shortcuts, links, or aliases—beyond the one that is created by default.

Execute custom code during installation.

Display custom graphics for the installer splash screen.

Use special actions (Execute Command, Find File, Execute Target File, etc.).

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

33


Chapter 3: Key InstallAnywhere Concepts Actions

Actions Actions represent the operations the installer performs. InstallAnywhere supports an extensible action architecture that provides the ability to perform additional operations during installation, such as installing files and folders, creating shortcuts, executing custom code during the installation process, or extracting contents from a compressed file. The most frequently used actions are Install File and Create Folder, but there are many more actions, including Create Alias, Link, Shortcut; Execute Target File; Execute Command; and Expand Archive.

Rules InstallAnywhere uses variable-based Boolean rules to control most aspects of installer behavior. Rules normally direct the execution of platform-specific actions on the target system, but they may check other conditions as well. In InstallAnywhere 2011, you can now write complex rule expressions using multiple logical operators and precedence operators. When you add multiple rules to an item, each rule’s unique ID is listed in the Rule Expression field and, by default, the rules are joined by the AND operator. If you want to write complex rule expressions, you can edit the expression in the Rule Expression field to use multiple logical operators—such as AND (&&), OR (||), and NOT (!)—and precedence operators (parentheses) to express the relationship between two or more rules. To validate the rule, click the Validate Rule Expression button. For example, you could choose to conditionally install files only if they do not currently exist on an end user’s hard drive, edit the Windows 7 Win32 Registry while bypassing the Windows XP registry, or include the addition of a license agreement and product information in Italian for users who designate Italian as their installation language. InstallAnywhere further expands the flexibility and control of your installer with the addition of rules and comparisons based upon regular expressions. Rules are accessible under the Project > Rules subtask, or in the Rules customizer for each action within the PreInstall, Install, and Post-Install tasks.

Silent and Console Mode Silent mode allows an installer to run without any user interaction and supports setting target and shortcut directories and Features/Install Sets via either command-line arguments or a properties file or response file. Console mode, available for Windows, UNIX, Linux and Mac OS X (see note) platforms, duplicates the default GUI steps provided by InstallAnywhere and uses standard input and output.

Note • Console mode, on Mac OS X, requires use of a UNIX installer.

34

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 3: Key InstallAnywhere Concepts LaunchAnywhere™

LaunchAnywhere™ A LaunchAnywhere executable, InstallAnywhere’s Java application launcher technology, is a unique executable that is used to launch a Java application on Windows, UNIX (including Solaris, Linux, HP-UX, AIX, BSD, and others), and Mac OS X platforms. On Windows, LaunchAnywhere technology creates double-clickable icons that invoke a Java application. For Mac OS X, InstallAnywhere generates application bundles. On UNIX platforms end users type a simple command to launch the application. LaunchAnywhere technology sets the classpath, redirects standard out and standard error, passes in system properties and command-line parameters, and performs many other environment configuration functions.

InstallAnywhere’s Custom Code API With InstallAnywhere’s Application Programming Interface (API), software producers can write custom Java code that runs in the same Java VM as InstallAnywhere, creating custom actions and end-user panels that interact with and extend InstallAnywhere functionality. There are four major classes of custom code: •

Custom Actions that run within InstallAnywhere’s action framework, alongside default InstallAnywhere actions. They may be invoked at both install and uninstall time.

Custom Panels that run within InstallAnywhere’s GUI during installation. Developers may use this mechanism to add custom panels to the Installer.

Custom Console Actions that run within InstallAnywhere’s console interface during installation. Developers may use this to add custom console elements to the Installer.

Custom Rules are evaluated when the action they are associated with is about to be executed. Rules return a Boolean value that determines if the action will run.

Note • InstallAnywhere also includes APIs that help you run automated tests and to leverage programmatic access to virtually all the project-editing features available in the Advanced Designer.

Localizing Installers InstallAnywhere builds installers in many different languages. InstallAnywhere Standard Edition supports 9 languages. InstallAnywhere Enterprise Edition supports 31 languages. If you want to generate installers for a subset of the languages included in InstallAnywhere, go to the Advanced Designer, select the Project > Locales subtask, and use the check boxes to select the desired languages. To localize custom strings, you can use InstallAnywhere’s built-in localization files or take advantage of InstallAnywhere support for external resource bundles.

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

35


Chapter 3: Key InstallAnywhere Concepts InstallAnywhere Variables

InstallAnywhere Variables InstallAnywhere keeps track of dynamic values through the use of variables. Almost every dynamic value in InstallAnywhere is represented by an InstallAnywhere variable. Variables may be modified or accessed in order to affect the design or output of an installer; they can also be modified during the progress of the installer in order to change the installer’s behavior. To enable you to manage variables more effectively, a new Project > Variables subtask has been introduced in InstallAnywhere 2011, which you can use to advertise variables for merge modules, list variables to encrypt in or exclude from the response files, and set security options. The Project > Variables subtask also includes a scrollable list of all variables defined in the installation project. Also in InstallAnywhere 2011, instead of having to manually type in the name of variables in text boxes or text areas in your installation project, you can open the Choose Variable dialog box and select a variable from a list of all of the variables available in your project. While you are editing the contents of a text box or a text area, you can open the Choose Variable dialog box by pressing Alt + V. You can also use Search on the File menu to search a project to locate all references to a specific variable.

SpeedFolder™ SpeedFolders treat multiple items as a pointer to a particular directory (as opposed to a traditional folder, where every item inside of it is a separate action). Using a SpeedFolder dramatically increases installation speed and memory efficiency. SpeedFolders always include whatever files are found in the source directory when the installer is built. If files are added or removed between installer builds, the contents of the installer will reflect whatever is inside of the directory specified as a SpeedFolder. (Standard folders require you to add or remove any files that are present or absent since the last installer build, or an error will occur.) SpeedFolders work well in an automated build environment and have filters that allow inclusion or exclusion of files that meet particular naming criteria. You cannot designate individual files or folders inside of a SpeedFolder into different components. Nor is it possible to convert SpeedFolders to traditional folders and back again. (To do this, you must delete the folder of one type and replace it with the folder of another type.) You may not have multiple SpeedFolders with the same name.

Install Sets Install Sets are groupings of features that make up entire installations, organized for a specific type of end user. For example, a Typical Install Set could include all of your files and a Minimal Install Set could exclude any nonessential files, such as the Help files. Install Sets have nothing to do with any true file or folder organization, but serve to organize your installation into categories. Most installers have Typical and Minimal Install Sets. Sometimes installers have different Install Sets for each individual application inside the installer, such as My Word Processor and My Spreadsheet. You can create as many Install Sets as you would like, but you need at least one. A good starting point is to begin with the ones supplied by InstallAnywhere. Install Sets allow end users to choose which collection of features should get installed on their system. To make sure your end users can choose which Install Set gets installed, add the Choose Install Sets panel action via the Pre-Install task in the Advanced Designer.

36

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 3: Key InstallAnywhere Concepts Features

Features Features are logical groupings of components. Feature designation arranges your components by function. Features may be hierarchical. You can create as many features as you wish, but every project needs at least one. Features are visible to the end user. Features are effective if you want to provide end users fine-grained choice in terms of what they install. For example, you might have a main application feature, a shared libraries feature, and a help feature. To allow your end users to choose which feature gets installed, add the Choose Install Sets panel in the Pre-Install task. Be sure to select the Choose Install Sets [followed by] Choose Product Features option on the Choose Install Sets panel customizer. To allow your end users to choose which features get uninstalled, add the Choose Features to Uninstall panel to the Pre-Uninstall task. The Organization > Features subtask shows the features (functional groupings of files) in your installer.

Components Components are groupings of files and actions, and are invisible to the end user. A component may be a group of files, registry changes, or other elements necessary for a feature to work correctly. Components are the smallest units of an installer. Advanced developers use components in complex installers to organize their resources into shared units, and to version their installation components. However, developers working with more simple installers can rely on InstallAnywhere to generate components automatically. All installers must have at least one component, and can have as many as needed. Components may belong to as many features as necessary but must belong to at least one. Although InstallAnywhere creates components automatically, it still provides the option of modifying them manually. The Components task displays the components in your installer. Components allow fine-grained control over which functionality gets installed. You could share common components between multiple installers, multiple versions of a product, or multiple products. For example, two products in a suite could have several shared components. Components may represent individual pieces of an application you want to check for in an installation. Additionally, components are versioned and each has a unique ID, so that you could search for a particular version of a component on a system to see if the latest version has been installed at a particular location. The InstallAnywhere uninstaller is also component-based, and can provide feature-level uninstallation functionality.

Magic Folders A Magic Folder™ is a special location on a target computer, independent of the target operating system. InstallAnywhere can install to any Magic Folder or sub-directory of a Magic Folder. For example, User Install Folder ($USER_INSTALL_DIR$) resolves to the directory the end user selects as their desired installation directory when the installer is running.On the Properties tab of each Install File and Create Folder action customizer are controls with which you can select that item’s destination, such as its Magic Folder.

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

37


Chapter 3: Key InstallAnywhere Concepts Magic Folders

38

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


4 Using the Project Wizard

The Project Wizard guides you through the process of creating an installer in a simple step-by-step manner. To become familiar with using the Project Wizard interface, perform the following tasks: •

Starting InstallAnywhere

Creating a New Project

Setting Project Information

Adding Files

Choosing a Main Class

Setting a Classpath

Building the Installer

Trying the Installer

Testing the Uninstaller

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

39


Chapter 4: Using the Project Wizard Starting InstallAnywhere

Starting InstallAnywhere InstallAnywhere has two main modes or environments: the Project Wizard and the Advanced Designer. In this section, we’ll use the Project Wizard to build a basic installer.

Note • To facilitate your evaluation, we have provided a set of sample files for your use in building an installer. These files are stored in the OfficeSuiteSourceFiles folder inside the InstallAnywhere installation folder. The method you use to launch InstallAnywhere depends upon the operating system you are using.

Task:

To start InstallAnywhere and open the Project Wizard interface: 1.

Perform one of the following steps: Operating System

Steps

Windows

Select InstallAnywhere from the Windows Start menu,

UNIX

Enter cd to change to the directory where InstallAnywhere is installed and then enter sh. /InstallAnywhere to launch InstallAnywhere. Alternatively, you can invoke InstallAnywhere via the symbolic links created during the InstallAnywhere installation process.

Mac OS X

40

Navigate to the InstallAnywhere installation directory and then double-click on the InstallAnywhere icon.

2.

If you are prompted by the InstallAnywhere Licensing Wizard to specify license information, select Continue to evaluate InstallAnywhere and click Next to proceed in Evaluation mode. The New Project panel of the Project Wizard opens.

3.

Proceed with the steps in Creating a New Project.

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 4: Using the Project Wizard Creating a New Project

Creating a New Project On the New Project panel of the Project Wizard, you enter a name for the new project and specify the location where you want to save the project.

Task:

To create a new project: 1.

Perform the steps in Starting InstallAnywhere to Launch InstallAnywhere. The New Project panel of the Project Wizard opens, with the Create New Project option selected by default.

2.

Click Save As. The Save New Project As dialog box opens. By default, the project is named My_Product.iap_xml.

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

41


Chapter 4: Using the Project Wizard Setting Project Information

3.

Next to Path, click Go and select the location where you want to save this new project.

4.

In the File name text box, enter OfficeSuite.iap_xml.

5.

Click Save. The name of the new project is now listed in the Project File Name box.

6.

Click Next. The Project Info panel of the Project Wizard opens.

7.

Continue with the steps in Setting Project Information.

Setting Project Information On the Project Info panel, you define basic information about the installer, such as the product name (as displayed on the installer), the name of the installer to be produced, the name of the destination folder, and the application name.

Task:

To set project information: 1.

Perform the steps in Creating a New Project. The Project Info panel opens.

2.

On the Project Info panel of the Project Wizard, confirm that the following information is entered: Option

Description

Product Name

OfficeSuite

Note • This value is derived from the project name.

42

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 4: Using the Project Wizard Adding Files

Option

Description

Installer Name

install

Install Folder Name

$PRODUCT_NAME$

Note • The InstallAnywhere variable $PRODUCT_NAME$ used in this field is a way

of dynamically linking the name of the installation folder to the name you provide for the product. Application Shortcut name

OfficeSuite

Note • This value is derived from the project name.

3.

Click Next. The Add Files panel of the Project Wizard opens.

4.

Continue with the steps in Adding Files.

Adding Files On the Add Files panel, you add files and folders to your installer.

Task:

To add files to your installer: 1.

Perform the steps in Setting Project Information. The Add Files panel opens.

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

43


Chapter 4: Using the Project Wizard Adding Files

44

2.

Click Add Files. The Add Files To Project dialog box opens.

3.

Browse to find and select the OfficeSuiteSourceFiles folder, which is in the InstallAnywhere installation directory. Two subfolders are listed: ImagesAndDocs and OfficeSuite2000:

4.

Click Add All to add the ImagesAndDocs and OfficeSuite2000 folders to the Files to Add list.

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 4: Using the Project Wizard Adding Files

5.

Click Done. The folders (along with all of the files and subfolders they contain) now appear in the File/Folder Hierarchy list.

Note • You can also drag and drop files directly into the Project Wizard to add files. 6.

Click Next. The Choose Main panel of the Project Wizard opens.

7.

Proceed with the steps in Choosing a Main Class.

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

45


Chapter 4: Using the Project Wizard Choosing a Main Class

Choosing a Main Class On the Choose Main panel, you select the starting class for the application, the Java class that contains the main method to be executed by this launcher. On the Choose Main panel, you may also specify custom icons (in GIF format) for your LaunchAnywhere executable.

Task:

To choose the main class: 1.

46

Perform the steps in Adding Files. The Choose Main panel opens.

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 4: Using the Project Wizard Choosing a Main Class

2.

Click Automatically Find Main Classes. InstallAnywhere locates all main classes and adds them to the Choose Your Main Class list. In this example, com.acme.OfficeSuite is listed.

Note • If you are not installing a Java application, you should skip ahead by clicking Next without specifying a main class. When the Choose a Main Class dialog box appears, click No to move to the next step. 3.

To specify a custom icon for your LaunchAnywhere executable, click Change. The Choose Icon dialog box opens.

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

47


Chapter 4: Using the Project Wizard Setting a Classpath

4.

Under 32x32 Icon, click Choose GIF File. The Choose a GIF image dialog box opens.

5.

Open the ImagesAndDocs folder of the OfficeSuiteSourceFiles folder and select officeIcon.gif.

6.

Click Open to confirm and then click OK to close the Choose Icon dialog box. The new icon is displayed under LaunchAnywhere Icon:

7.

Click Next. The Classpath panel opens.

8.

Proceed with the steps in Setting a Classpath.

Setting a Classpath On the Classpath panel, you can automatically configure a Java application classpath.

Task:

To set a classpath: 1.

Perform the steps in Choosing a Main Class. The Classpath panel opens.

Note • The Classpath is an argument set on the command-line, or through an environment variable, that tells the Java Virtual Machine where to look for user-defined classes and packages in Java programs.

48

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 4: Using the Project Wizard Building the Installer

2.

Click Automatically Set Classpath. InstallAnywhere calculates which files need to be added to the classpath. A small CP icon appears at the bottom of those folders. In this example, a CP icon appears on the OfficeSuite2000 folder.

3.

Click Next. The Build Installer panel opens.

4.

Proceed with the steps in Building the Installer.

Building the Installer The platforms listed on the Build Installer step—Mac OS X, Windows, AIX, HP-UX, Linux, Solaris, and Unix (all)—represent installers that are double-clickable on their respective platforms. The final option, Other Java-Enabled Platforms, is a “pure” Java installer that can be invoked on any Java-enabled platform. To build installers with an embedded Virtual Machine, select the check box in the With VM column.

Task:

To build installers for your project: 1.

Perform the steps in Setting a Classpath. The Build Installer panel opens.

2.

Click the Without VM or With VM check box for the platform that matches your authoring platform plus any additional platforms for which you want to build installers.

Note • Installers built without bundled VMs are smaller and download faster than installers that include a VM.

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

49


Chapter 4: Using the Project Wizard Trying the Installer

3.

Click Build. When the build is complete, the location of the installers is displayed on the Try Installer panel:

By default, InstallAnywhere places the OfficeSuite_Build_Output folder in the same location as your project file. The InstallAnywhere Web Install process allows end users to choose the appropriate installer for their system. 4.

Proceed with the steps in Trying the Installer.

Trying the Installer Now that you’ve built an installer, you can test it by clicking the Try It button on the Try Installer panel.

Task:

To test the installer: 1.

Perform the steps in Building the Installer. The Build Complete message is displayed on the Try Installer panel.

2.

Click Try It. The product installer launches.

Tip • Hold down the Control key [CTRL] while your installer launches to see the debug output (Windows only). 3.

50

Proceed with the steps in the installer to install OfficeSuite.

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 4: Using the Project Wizard Testing the Uninstaller

4.

When installation is complete, launch OfficeSuite using one of the following methods: •

On Windows, go to the OfficeSuite program group and choose OfficeSuite.

On UNIX, cd to the directory where you installed the program and enter ./OfficeSuite.

On Mac OS X, double-click the OfficeSuite icon.

OfficeSuite’s Start Page opens.

5.

Click OK to open OfficeSuite.

6.

Quit OfficeSuite by choosing Exit from its File menu.

Testing the Uninstaller As a final step, ensure that the OfficeSuite uninstaller was properly deployed and works to remove the application from the target system.

Task:

To test the uninstaller: 1.

Navigate to the OfficeSuite installation folder.

2.

Open the _OfficeSuite_installation folder.

3.

Run Change OfficeSuite Installation.

4.

Verify that OfficeSuite has been removed from your system.

For further testing, you may post the installer directory to a Web server and install the software onto other platforms as well.

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

51


Chapter 4: Using the Project Wizard Testing the Uninstaller

52

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


5 Using the Advanced Designer

The Advanced Designer offers a much wider range of configuration over InstallAnywhere’s many options than the Project Wizard.

Figure 5-1: Advanced Designer Interface

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

53


Chapter 5: Using the Advanced Designer

You can use the Advanced Designer to: •

Assign files to different Install Sets.

Install multiple LaunchAnywhere executables.

Add custom panels to the installer.

Customize the installer’s look and feel.

Customize the uninstaller.

Set rules to selectively install files to specific platforms.

Define multiple Build Configurations.

The InstallAnywhere Advanced Designer breaks down the installer creation process into discrete tasks, which are listed on the left side of the screen: Table 5-1 • Advanced Designer Tasks

54

Task

Description

Project

Displays project information, configures project settings, provides options to bundle or define acceptable VMs, and defines product, file installation, and localization options.

Installer UI

Sets user interface options such as the default UI mode, splash screen images, billboard graphics, panel backgrounds, installer help, and more.

Organization

Provides tools to arrange Install Sets, Product Features, Components, Merge Modules, DIM references, and Database Server and Application Server hosts.

Pre-Install

Represents the actions the installer takes prior to the Install task. Generally, this task collects the actions that execute before the installer deploys the payload of files to be installed.

Install

Contains the install actions that take place during the step when InstallAnywhere deploys files to the target system.

Post-Install

Represents the actions the installer takes after the Install task. Generally, this task collects the actions that execute after the installer deploys files to the target system.

Pre-Uninstall

Represents the actions the uninstaller takes prior to the uninstall task. Generally, this task contains the actions that execute before the uninstaller removes installed files.

Uninstall

Represents the actions the uninstaller takes during uninstallation. The Uninstall task gives you additional flexibility and more control over how the uninstallation is performed. You can use the Uninstall task to customize the Uninstaller by adding, removing or changing some of the uninstall actions.

PostUninstall

Represents the actions the uninstaller takes after the uninstall task. Generally, this task collects the actions that execute after the uninstaller removes installed files.

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 5: Using the Advanced Designer Opening a Project in the Advanced Designer

Table 5-1 • Advanced Designer Tasks (cont.) Task

Description

Build

Provides the options for building an installer including creating and selecting Build Configurations, setting build targets, bundling VM packs, and defining distribution options.

Note • The tasks of the Advanced Designer may be accessed in any order. To become familiar with using the Advanced Designer interface, perform the following tasks: •

Opening a Project in the Advanced Designer

Choosing Custom Images

Adding Pre-Install Actions

Defining the Installation Tasks

Adding Post-Install Actions

Customizing the Uninstaller

Building the Installer

Testing the Installer

Opening a Project in the Advanced Designer You can enter the Advanced Designer mode from the Project Wizard process by clicking the Advanced Designer button at any point of the installer creation process.

Tip • Many developers use the Project Wizard to create a basic installer and then switch to the Advanced Designer in order to customize their installer with more advanced functionality.

Task:

To open an existing InstallAnywhere project: 1.

Start InstallAnywhere, as described in Starting InstallAnywhere. The New Project panel of the Project Wizard opens.

2.

Select the Open Existing Project option.

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

55


Chapter 5: Using the Advanced Designer Choosing Custom Images

3.

Locate and select the OfficeSuite project file (OfficeSuite.iap_xml) that you created in the previous tutorial, Using the Project Wizard.

4.

Click Advanced Designer to open the Advanced Designer interface.

5.

Continue with the steps in Choosing Custom Images.

Choosing Custom Images Some common activities in the Advanced Designer focus on customizing the images rendered during installation.

Adding a Billboard Billboards are graphic images displayed during an installation, frequently used to advertise product features or complementary products. Billboards images appear in the large right hand pane of the installer while files are being installed.

56

Several billboard graphics may be added for larger (and longer) installations.

For small installations, like the tutorial OfficeSuite example, only one billboard will show.

Billboards may also be assigned to features, and will only be displayed if the feature they are associated with installs.

When adding multiple billboards, the billboards appear in the order they are shown in the Billboard List.

When multiple billboards are specified, you can control how much time each billboard will be displayed while the installation is in progress by using the Display billboards for every nn seconds option.

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 5: Using the Advanced Designer Choosing Custom Images

Note • The maximum and preferred size for billboards is 380 x 270. If the preferred GUI mode is AWT and you have chosen not to display a side panel during the Install Progress step, the maximum size is 587 x 312. In this exercise, you will select a billboard image to use in the OfficeSuite installer.

Task:

To add a billboard image: 1.

Perform the steps in Opening a Project in the Advanced Designer to open the OfficeSuite project.

2.

Select the Installer UI > Billboards subtask.

3.

Click Add Billboard. The Choose an Image File dialog box opens.

4.

Select billboard1.gif located in the OfficeSuiteSourceFiles/ImagesAndDocs folder and click Open. The path to the graphic is now listed in the Billboard customizer.

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

57


Chapter 5: Using the Advanced Designer Choosing Custom Images

Note • There is no practical limit to the number of billboards you can add to an installation.

58

5.

Click Preview to view the new image.

6.

Proceed with the steps in Setting a Custom Graphic for the Splash Screen.

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 5: Using the Advanced Designer Choosing Custom Images

Setting a Custom Graphic for the Splash Screen The splash screen is displayed while the installer loads, and is also is displayed on the HTML page of the Web installation. In this exercise, you will select a custom image for the OfficeSuite splash screen.

Task:

To set a custom graphic for the splash screen: 1.

Perform the steps in Adding a Billboard.

2.

Select the Installer UI > Look & Feel subtask.

3.

Open the General UI Settings tab.

4.

In the Startup Splash Screen section, click Choose. The Select an Image File dialog box opens.

5.

Choose OfficeSplash.jpg in the OfficeSuiteSourceFiles/ImagesAndDocs folder and click Open.

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

59


Chapter 5: Using the Advanced Designer Choosing Custom Images

6.

Click Preview to confirm that the graphic has changed to the selected image.

7.

Continue with the steps in Choosing a Specific Panel Image.

Choosing a Specific Panel Image You can include customized graphics on each panel of the installer. To do this, you set an option on the Installer Steps tab of the Installer UI > Look & Feel subtask to display images rather than a list of installer steps on the left side of installer panels, and then open the Pre-Install task and specify an image on the Image Settings tab of each Panel action’s customizer.

Task:

60

To choose a specific panel image: 1.

Perform the steps in Setting a Custom Graphic for the Splash Screen.

2.

In the Advanced Designer, open the Installer UI > Look & Feel subtask.

3.

Open the Installer Steps tab.

4.

In the Type of Additions to Installer Panels section, select Images.

5.

Open the Pre-Install task.

6.

Select a panel action in the Pre-Install Action List.

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 5: Using the Advanced Designer Adding Pre-Install Actions

7.

Open the Image Settings tab in the panel’s Properties customizer.

8.

Select Specify an image (170 x 305).

9.

Click Choose Image. The Select an Image File dialog box opens.

10. Select OfficePanel.jpg in the OfficeSuiteSourceFiles/ImagesAndDocs folder and click Open. 11. Click Preview to view the selected image in the panel.

12. Continue with the steps in Adding Pre-Install Actions.

Adding Pre-Install Actions The next step in creating an installer using the Advanced Designer is to review and edit the Pre-Install actions. In this tutorial, you will add a Choose Java VM panel to an installer to provide end users with the option of using a VM you bundled with the installer or searching their computer for a compatible one. When this feature is activated, the end user can select from a list of Java VMs and choose the appropriate one.

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

61


Chapter 5: Using the Advanced Designer Adding Pre-Install Actions

Note • For a discussion of Java virtual machine selection, see Java Virtual Machine Concepts in the InstallAnywhere Help Library.

Tip • To download additional Java VMs, select Download Additional VM Packs from the Advanced Designer Help menu to open the InstallAnywhere Files & Utilities Web site, and then open the VM Packs tab: http://www.flexerasoftware.com/products/installanywhere/files-utilities.htm

Task:

62

To add a pre-install action: 1.

Perform the steps in Choosing Custom Images.

2.

Select the Pre-Install task.

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 5: Using the Advanced Designer Adding Pre-Install Actions

The Pre-Install task sets the panels and actions that occur prior to the installation of files. By default, a new InstallAnywhere project contains the following panels: Panel

Description

Introduction

This panel allows developers to introduce the product or installation process.

Choose Install Folder

This panel allows end users to choose the installation location for the product.

Choose Alias, Link Shortcut Folder

This panel allows end users to specify the location for any Mac OS X Aliases, Windows Shortcuts, and Unix Symlinks (used as shortcuts) that will be installed.

Pre-Install Summary

This panel provides end users with a summary of various installation settings prior to the installation of files.

Note the following regarding the Pre-Install task:

3.

Order of actions—Actions in the Pre-Install task will occur in the order set in the task list. The order of panels and actions can be manipulated using the Arrow buttons in the middle right of the Advanced Designer screen.

Customizers—The behavior and content of panels can be modified by highlighting each panel. The dialog along the bottom half of the Advanced Designer will change to reflect the panel selected. In InstallAnywhere’s vocabulary, this is known as a customizer, and is available for each action and panel in the installer. The following is an example of the customizer for the Choose Alias, Link, Shortcut Folder panel.

In the Pre-Install Action List, select Panel: Choose Alias, Link, Shortcut Folder and then click Add Action. The Choose an Action dialog box opens.

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

63


Chapter 5: Using the Advanced Designer Adding Pre-Install Actions

64

4.

Select the Panels tab.

5.

On the Panels tab, select Panel: Choose Java VM and click Add, and then click Close to close the Choose an Action dialog box. The new action appears in the Pre-Install Action list and the Choose Java VM customizer opens:

6.

To provide the end-user with the most possible options for choosing a Java VM, select all three options: •

Allow the end user to install the bundled VM—Makes the VM you bundle with your project available in the Choose Java VM panel.

Allow the end user to search for locations other than the paths defined under Project > JVM > Search Panel Settings—Adds a Search Another Location button to this panel. This button opens Browse for Folder dialog box in which your users can specify an additional search path.

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 5: Using the Advanced Designer Defining the Installation Tasks

Allow the end user to choose a specific Java executable—Adds a Choose Java Executable button to this panel. This button shows an Open dialog box in which you users can locate the executable for a specific VM and select it as the VM your LaunchAnywhere launchers use.

7.

Now, select the Project > Advanced subtask and locate the Maintenance Mode options.

8.

Select Enable Maintenance Mode support. The four options under it are then enabled.

9.

Select Add Features, Repair Installation, Remove Features, and Uninstall Product.

10. Return to the Pre-Install task. You will notice that additional Action Groups and Actions have automatically been added to the Pre-Install Action List to support the selected Maintenance Mode options: one for Add Features and one for Repair Installation. And the panel actions that were there before the Maintenance Mode options were enabled are now grouped in a new Action Group named Pre-Installation.

11. Proceed with the steps in Defining the Installation Tasks.

Defining the Installation Tasks The Install task contains the install actions that take place during the step when InstallAnywhere deploys files to the target system. The Install task displays files and directories in the way the installer will deploy them on the target system. You can use the controls on the Install task to assign files, directories, and actions to either components or product features. In this tutorial, you will customize the images rendered during installation. •

Adding Files to the Install Task

Adding a LaunchAnywhere Executable to the Install Task

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

65


Chapter 5: Using the Advanced Designer Defining the Installation Tasks

Adding Files to the Install Task To add files to the project using the Advanced Designer, perform the following steps.

Task:

66

To add files to the Install task: 1.

Perform the steps in Adding Pre-Install Actions.

2.

Select the Install task. The Install task defines the files to install, the folder location to install those files, and the order of the tasks that need to happen as the files are being installed. If you have performed the steps in the Adding Files section of the Using the Project Wizard tutorial, this project will already have files and folders displayed in the Install task:

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 5: Using the Advanced Designer Defining the Installation Tasks

3.

If you did not perform the steps in the Adding Files section of the Using the Project Wizard tutorial, perform the following steps to add files to this installer project: a.

Click Add Files. The Add Files To Project dialog box opens.

b.

Browse to the OfficeSuiteSourceFiles directory, which is located inside the InstallAnywhere installation directory. Two directories are listed: ImagesAndDocs and OfficeSuite2000.

c.

Click Add All to add the ImagesAndDocs and OfficeSuite2000 subfolders of the OfficeSuiteSourceFiles folder. These folders are now listed in the Files to Add list.

d.

Click Done. The selected folders are now listed in the Visual Tree in the Install task.

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

67


Chapter 5: Using the Advanced Designer Defining the Installation Tasks

4.

Under User Install Folder ($USER_INSTALL_DIR$) in the Visual Tree, open the _$PRODUCT_NAME$_installation folder. This folder, which is created by default, contains any InstallAnywhere uninstaller/Maintenance Mode actions, and a comment action with instructions pertaining to the uninstaller.

5.

Proceed with the tasks in Adding a LaunchAnywhere Executable to the Install Task.

Adding a LaunchAnywhere Executable to the Install Task A LaunchAnywhere Executable (LAX) is a unique native executable, created by InstallAnywhere, that is used to launch a Java application. While the InstallAnywhere Wizard specifically asks to select a main class and automatically creates a single launcher, the Advanced Designer allows developers to add as many launchers as they would like. There are two ways to add a LaunchAnywhere Launcher to an InstallAnywhere Project file. The Create LaunchAnywhere for Java Application option may be added by:

Task:

68

•

Clicking the Add Action button and selecting it from the Choose an Action dialog box.

•

Clicking the Add Launcher button on the middle control bar in the Advanced Designer.

To add a LaunchAnywhere executable: 1.

Perform the steps in Defining the Installation Tasks. The Install task is opened and the OfficeSuite2000 files and folders are listed in the Visual Tree.

2.

Highlight the User Install Folder in the Visual Tree, and click the Add Launcher button. You are prompted to automatically find classes with main methods.

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 5: Using the Advanced Designer Defining the Installation Tasks

3.

Click OK. The Choose a main class dialog box opens with a class listed.

Note • When adding a launcher, InstallAnywhere automatically inspects the added files (including introspecting into JAR and ZIP files) to find class files with main methods specified. 4.

Choose the com.acme.OfficeSuite as main class for the application and click OK.

Note • Since OfficeSuite is a simple project, com.acme.OfficeSuite is the only class. By clicking the Add Launcher button, you have not only added the launcher to the file structure (OfficeSuite), but also created a Shortcut, Link, or Alias action in the Shortcuts’ Destination Folder Magic Folder. This location is variable and will be specified by the Choose Alias, Link, and Shortcut panel in the Pre-Install task.

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

69


Chapter 5: Using the Advanced Designer Defining the Installation Tasks

5.

To customize the appearance the launcher will have as a shortcut, highlight the OfficeSuite launcher. The customizer along the lower portion of the Advanced Designer screen will change to reflect the options for the Create LaunchAnywhere for Java Application action.

In the lower right of the customizer (below the Arguments field) are a set of buttons that control the icon associated with the launcher.

70

6.

Click Change to alter the icon. The Choose Icon dialog box opens.

7.

On the Windows tab next to the 32x32 Icon, click Choose GIF File.

8.

Select officeIcon.gif, which is located in the OfficeSuiteSourceFiles\Images and Docs folder within the InstallAnywhere installation directory.

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 5: Using the Advanced Designer Defining the Installation Tasks

Note • Interlaced GIF files cannot be used with InstallAnywhere. The conversion process does not support these files and their use can result in blank icons. For Mac OS X, provide an ICNS file (created with iconbuilder—part of the Mac OS X Developer Tools). InstallAnywhere maintains a general classpath that is used to create launchers for the Java Application. 9.

For the 16x16 Icon, select officeIconSmall.gif from the same directory.

10. Click OK to close the Choose Icon dialog box. The new icons are now displayed in the Create LaunchAnywhere for Java Application customizer. 11. Back on the Install task, click the Set Classpath button. You are prompted to specify whether you want to automatically set the classpath.

12. Click OK. A blue CP icon appears on folders and archives that the process has added to the classpath. 13. To view the Classpath as determined by the Set Classpath action, open the Project task and then select the General Settings tab of the JVM Settings subtask.

Note the following regarding the General Settings tab of the Project > JVM Settings subtask: •

Since Office Suite is a simple product, only one main folder is listed: OfficeSuite2000 (which contains loose class files).

If our example project contained JAR or ZIP files containing classes, they would also have been added to this list.

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

71


Chapter 5: Using the Advanced Designer Defining the Installation Tasks

If a file is added mistakenly to the Classpath List, it can be removed on this subtask or by selecting that file in the Visual Tree on the Install task and clearing the selection of the In Classpath check box in the customizer for that file.

14. Proceed with the steps in Creating and Applying Build Configuration Tags.

Creating and Applying Build Configuration Tags You can use Tags to bundle different sets of actions, panels, features, and components with Build Configurations. Using Tags involves three main steps: •

Create Tags—First you define a set of Tags to use with Build Configurations.

Assign Tags to project elements—Next, you assign an appropriate Tag to all of those project elements that you want to include in some Build Configurations but exclude from others.

Associate Tags with Build Configurations—Finally, for each Build Configuration, you specify which Tags you want to include and which Tags you want to exclude.

When a Build Configuration that has been customized using Tags is built, it results in an installer that includes: •

All untagged project elements—The installer will include all untagged project elements: project elements that do not have any Tags listed in the Associated Tags list on the Tags subtab of its customizer:

Project elements associated with a Tag that is also associated with the Build Configuration—The installer will include those project elements that have been associated with one or more Tags, one of which is also associated with the selected Build Configuration. For example, if the selected Build Configuration is associated with a Tag named Professional, a project element that is also associated with the Professional Tag will be included in the installer.

All other project elements will be excluded. If a project element is associated with one or more Tags, none of which is associated with the selected Build Configuration, that project element will be excluded from the installer. 72

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 5: Using the Advanced Designer Defining the Installation Tasks

In this exercise, we will create two Tags and then apply them to files in the Install task.

Task:

To create and apply Build Configuration Tags: 1.

Perform the steps in Adding a LaunchAnywhere Executable to the Install Task.

2.

Locate the license.txt file on your computer in the following directory: <InstallAnywhere Installation Directory>\OfficeSuiteSourceFiles\ImagesAndDocs

3.

Make a copy of the license.txt file and name it license_ja.txt.

4.

Return to InstallAnywhere and open the Install task.

5.

Click Add Files. The Add Files To Project dialog box opens.

6.

Select license_ja.txt file that you just created and click Add. The license_ja.txt file is now listed in the Files To Add list.

7.

Click Done. The license_ja.txt file is now selected in the Visual Tree, and the Install File customizer opens.

8.

In the Install Folder customizer, select the Tags subtab.

9.

Click Create Tag. The Create Tag dialog box opens.

10. In the Tag Name box, enter English. 11. Because you want to associate this Tag with all project elements, keep the Associate with all project elements option selected. 12. Repeat the steps above to create another Tag named Japanese. Now, both of these new Tags appear in the Associated Tags list for the license_ja.txt file.

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

73


Chapter 5: Using the Advanced Designer Adding Post-Install Actions

Note • You can also create Tags (as well as delete and rename Tags) in the Manage Tags area of the Project > Advanced subtask. 13. Because you only want the Japanese Tag associated with the selected file, select English in the Associated Tags list and click >> Remove Tag. Now, only Japanese is listed in the Associated Tags list. 14. Proceed with the steps in Adding Post-Install Actions.

Adding Post-Install Actions The Post-Install task list specifies actions and panels to occur after the installation of files. Like Pre-Install, the Post-Install step is ordered with the top actions occurring first. By default, InstallAnywhere has added two actions to the InstallAnywhere project: Panel: Install Complete and Restart Windows.

Figure 5-2: Post-Install Task, Default Actions These actions are:

74

Panel: Install Complete—This panel appears when the installation has completed successfully. This action is determined by the status of the $INSTALL_SUCCESS$ variable. This panel displays only if $INSTALL_SUCCESS$ contains no error conditions.

Restart Windows—This action restarts a Windows system if the installer determines that it is necessary.

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 5: Using the Advanced Designer Adding Post-Install Actions

About InstallAnywhere Rules InstallAnywhere installations are controlled primarily by InstallAnywhere Rules. By default, the Restart Windows action has two Compare InstallAnywhere Variables rules assigned to it, which are displayed when you select the Restart Windows action and open the Rules tab of the customizer:

Figure 5-3: Restart Windows Action Rules Customizer

Note • Starting in InstallAnywhere 2011, you can write complex rule expressions using multiple logical operators and precedence operators. When you add multiple rules to an item, each rule’s unique ID is listed in the Rule Expression field and, by default, the rules are joined by the AND (&&) operator. If you want to write complex rule expressions, you can edit the expression in the Rule Expression field to use multiple logical operators—such as AND (&&), OR (||), and NOT (!)—and precedence operators (parentheses) to express the relationship between two or more rules. To validate the rule, click the Validate Rule Expression button. The rules set on the Restart Windows action are simple rules set to compare InstallAnywhere variables. InstallAnywhere rules are Boolean and allow the file, panel, or action to be installed, displayed, or run only if the rule resolves to True.

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

75


Chapter 5: Using the Advanced Designer Adding Post-Install Actions

Adding a Post-Install Action To add an action to the Post-Install task, perform the following steps:

Task:

76

To add post-install actions: 1.

Perform the steps in Adding a LaunchAnywhere Executable to the Install Task.

2.

Open the Post-Install task.

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 5: Using the Advanced Designer Adding Post-Install Actions

3.

Click the Add Action button to open the Choose an Action dialog box.

4.

On the General tab, select Execute Target File.

Note â&#x20AC;˘ The Execute Target File action is used to execute files that are included as part of the installation, and consequently it is available only in the Install and Post-Install tasks of the installation. The Execute Target File action is not available in the Pre-Install task because files cannot be executed that are not installed yet.

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

77


Chapter 5: Using the Advanced Designer Adding Post-Install Actions

5.

Click Add. The Execute Target File action is added to the Post-Install Action List and its customizer opens in the bottom of the screen.

The Choose an Action dialog box will remain open so additional actions could be added.

Note â&#x20AC;˘ If the Execute Target File action panel was added at a location other than the bottom of the PostInstall task, move it now. Either utilize the up and down arrows, or drag the action to the bottom of the task list. 6.

78

In the Name field of the Properties tab of the Execute Target File customizer, enter a name for the action. Naming the action will help identify the action when looking at the visual tree.

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 5: Using the Advanced Designer Adding Post-Install Actions

7.

To select the target, click the Choose Target button next to the Target field. The Choose an Action dialog box opens and displays the file installation tree specified in the Install task.

8.

File(s) can be executed in this stage. To execute the just installed Office Suite application, select the OfficeSuite icon under the User Install Folder (not the icon listed under the Shortcuts Destination Folder) and click OK.

Note • You need to choose the actual OfficeSuite launcher, and not the shortcut, because shortcuts— especially on Windows and Mac OS systems—are pointers and are not inherently executable. InstallAnywhere will not execute a shortcut.

Important • By using the Command Line field, modifications can be made to the command line used to execute the file, such as adding a handler, or an argument to the execution. Do not remove or modify the $EXECUTE_FILE_TARGET$ entry, as this represents the file to execute. To specify a handler, prepend an

executable path, to specify an argument, append a file path. These paths must be absolute, however the paths can include InstallAnywhere variables.

Note • The user experience for the Execute Target File action can be tailored by using the Suspend the installation until the process completes option on the Properties tab of the Execute Target File customizer. This option is particularly useful in cases where a later step in the installation is dependant on the execution. You can also select a sub-option, Show indeterminate dialog, to specify an indeterminate progress bar with a message. This option can be used if the execution may take some time (for example, an execute that installs another product, or configures a database or other application). 9.

Continue with the steps in Customizing the Uninstaller.

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

79


Chapter 5: Using the Advanced Designer Customizing the Uninstaller

Customizing the Uninstaller InstallAnywhere automatically creates an uninstaller for the project. The Uninstaller, much like the Installer, is a collection of panels, consoles, and actions. The standard Uninstaller uninstalls the application by executing each actionâ&#x20AC;&#x2122;s uninstallation procedure. However, in some situations, you may want additional flexibility and have more control over how the uninstallation is performed. Therefore, you may want to use the Uninstall task in the Advanced Designer to customize the Uninstaller by adding, removing or changing some of the uninstall actions. For example, you may want to disable the uninstallation of an entire set of resources, rename files, copy and move files, display additional dialog messages, or execute some custom code at uninstall time.

Task:

To customize the Uninstaller: 1.

Perform the steps in Adding Post-Install Actions.

2.

Open the Uninstall task.

3.

Select Uninstall Category: Registry Entries in the Visual Tree.

4.

Click the Up arrow to move this category above Uninstall Category: Shortcuts/Links/Aliases.

5.

Continue with the steps in Building the Installer.

Building the Installer The InstallAnywhere Build task allows the options that will be used to build the installer(s) to be set. Each InstallAnywhere project can have multiple Build Configurations, each representing how the installer will be built for particular set of platforms, files, build distributions, JVMs, locales, and other settings. You can create and modify Build Configurations on the Build Configurations tab of the Build task.

Tip â&#x20AC;˘ For early testing, build only for the development platform. Each additional platform adds to the time required to build, cycling through run-rebuild-run-rebuild stages. A faster build will makes the development process easier.

80

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 5: Using the Advanced Designer Building the Installer

Task:

To build the installer: 1.

Perform the steps in Customizing the Uninstaller.

2.

Open the Build task of the Advanced Designer.

3.

Under Select Build Configuration, click Add. The Add Configuration dialog box opens.

4.

In the New Build Configuration Name box, enter English.

5.

Create another Build Configuration and name it Japanese.

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

81


Chapter 5: Using the Advanced Designer Building the Installer

6.

7.

From the Select Build Configuration list, select English, and then do the following: a.

On the Build Configurations tab, select the Tags subtab.

b.

In the Associated Tags list, select Japanese and click Remove Tag >> to move it to the Available Tags list. Only English remains in the Associated Tags list.

c.

Select the Locales subtab.

d.

From the Locale List, select English.

Now, from the Select Build Configuration list, select Japanese, and do the following: a.

On the Build Configurations tab, select the Tags subtab.

b.

In the Associated Tags list, select English and click Remove Tag >> to move it to the Available Tags list. Only Japanese remains in the Associated Tags list.

c.

Select the Locales subtab.

d.

From the Locale List, select Japanese.

8.

On the Build Targets tab for each Build Configuration, click the plus sign next to the Windows platform name to display the platform customizer.

9.

Select the Without VM checkbox, and under it select Search for VM; if not found exit.

10. Select the With VM checkbox, and under it select Donâ&#x20AC;&#x2122;t search for VM; use bundled VM. This instructs InstallAnywhere to bundle the installer with a VM.

Note â&#x20AC;˘ The Build Configurations tab of the Build task also includes the Distribution subtab. The Distribution tab allows developers to set options for the type of installers to build, and the optimization options for each installer. Because the installer being built in this tutorial does not contain any platform specific files, it will not need to be optimized at this point. However, if the installer did include platform specific files, these files would be optimized based on the application of the Check Platform rules.

82

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 5: Using the Advanced Designer Building the Installer

Note â&#x20AC;˘ The Build Log tab of the Build task displays the XML log of previous builds. 11. On the File menu, select Save to save this project. 12. Click Build All to build both Build Configurations of the OfficeSuite installer. The Building information dialog will appear. 13. Click the blue arrow on the lower left of that dialog to see the Build Details.

When the build is complete, Build successful will appear. (For this tutorial, the build should take a minute or less). 14. Click OK to close the Building dialog box. 15. Proceed with the steps in Testing the Installer.

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

83


Chapter 5: Using the Advanced Designer Testing the Installer

Testing the Installer After the Build process is complete, try the installer by selecting either the Try Web Install or Try Installer button. In this case, use the Try Web Install button to launch our browser and the InstallAnywhere Web Install Page generated by the build process.

Task:

To test the installer: 1.

Perform the steps in Building the Installer.

2.

On the Build task, click Try Web Install. The Web Install Page will load, and should request a security access.

3.

Grant this access to allow the Web Install Applet to run the InstallAnywhere installer.

4.

Click one of the download lines below the image to download the installer. The download will begin.

5.

When the download is complete, run the installer, accepting the default values.

6.

On the Install Complete panel, click Done. The installer will close and OfficeSuite will be launched.

Note â&#x20AC;˘ You can also launch OfficeSuite on Windows by selecting it from the Windows Start menu.

84

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


6 Key InstallAnywhere Tasks

The InstallAnywhere Help Library contains detailed information on how to use InstallAnywhere to create multiplatform installers, along with tutorials to familiarize you with the Project Wizard and Advanced Designer interfaces. You can open the Help Library from the Advanced Designer interface by selecting InstallAnywhere Help from the Help menu or by clicking the Help button. The InstallAnywhere Help Library is also available on Flexera Software’s HelpNet Web site at: http://helpnet.flexerasoftware.com This chapter provides links to help topics on HelpNet that explain how to perform essential InstallAnywhere tasks. Table 6-1 • Key InstallAnywhere Tasks Category

Task

Getting Started

Authoring Environments

Opening a Project

Organizing Features and Components

Working With Variables

Enabling and Configuring Maintenance Mode

Controlling the VM Your Launchers Use

Getting User Input

Deploying Your Product With FlexNet Connect

Setting Installation Rollback Options

Localizing Projects and Installers

Referencing Developer Installation Manifests (DIMs)

Designing the Installer Look and Feel

Configuring a Project

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

85


Chapter 6: Key InstallAnywhere Tasks

Table 6-1 • Key InstallAnywhere Tasks Category

Task

Customizing the Pre-Install Task

Customizing the Pre-Install Panels and Actions

Setting Up the Install Task

Defining the Install Task

Adding Files to a Project

Adding Install Actions

Adding LaunchAnywhere Executables to the Install Task

Creating Launchers for Java Applications

Installing Fonts

Defining Rules

Building Complex Rule Expressions

Assigning a Rule to the Installer

Assigning a Rule to an Action

Customizing Built-in Rules

Rules Reference

Customizing the Post-Install Task

Customizing the Post-Install Task

Customizing the Uninstall Task

Customizing the Uninstaller

About the Uninstaller / Maintenance Mode Launcher

Setting Build Options and Building Installers

Creating and Editing Build Configurations

Using Tags to Customize Build Configurations

Defining Build Targets

Setting Build Distribution Options

Creating Merge Modules

Using the Install Merge Module Action

Building Installers Using Build Configurations

Testing Installers

Working With VM Packs

Controlling the Install of Bundled VMs

Assigning Rules

86

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Chapter 6: Key InstallAnywhere Tasks

Table 6-1 • Key InstallAnywhere Tasks Category

Task

Reference

Actions

Install Actions

Uninstall Actions

General Actions

Panel Actions

Console Actions

System i (i5/OS) Actions

Packaging and Executing Custom Code

Digitally Signing Installers

Variables

Product Registry

Response Files

BuildProperties.xml File Settings in the Advanced Designer

buildproperties.properties File Settings in the Advanced Designer

InstallAnywhere Ant Task Reference

Custom Code APIs

Command Line Reference

InstallAnywhere 2011 Evaluation Guide

IA-1200-EG00

87


Chapter 6: Key InstallAnywhere Tasks

88

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


Index

A

C

actions 34 Advanced Designer 32, 53 adding a billboard 56 adding files 66 adding LaunchAnywhere executable 68 adding Post-Install actions 74, 76 adding Pre-Install actions 61 adding rules 75 Build task 80 building the installer 80 choosing a panel image 60 choosing custom images 56 Install task 65 installation tasks 54 opening a project 55 Post-Install task 74 Set Classpath 71 setting a custom graphic for the splash screen 59 testing the installer 84 Uninstall task 80 API 35

Choose Java VM panel action 64 classpath 48 components 37

Enable Maintenance Mode 65 Execute Target File action 77

F features 37 files adding to project 43, 66

H help Help Library conventions 13 using 12

I

B

install sets 36 Install task 65, 66 InstallAnywhere actions 34 Advanced Designer 32, 53 API 35 choosing a panel image 60 components 37

billboard 56 build configurations tags 72 Build task 80

InstallAnywhere 2011 Evaluation Guide

E

IA-1200-EG00

89


Index

console installer mode 34 creating a new project 41 downloading 12 install sets 36 installer modes 34 installer technology 32 installing 12 links to help topics 85 localization 35 magic folders 37 new features in InstallAnywhere 2011 17 overview 7 Project Wizard 32, 39 rules 34 silent installer mode 34 SpeedFolders 36 starting 40 starting on Windows, UNIX, and Mac 40 system requirements 8 user interface 32 whatâ&#x20AC;&#x2122;s new 17 installer building 49, 80 installers Java-enabled 32 with a native wrapper 32 installing 12

L LaunchAnywhere 35 LaunchAnywhere executable 68 adding 68 localization 35

setting Install Folder Name 43 setting Installer Name 43 setting Product Name 42 setting project information 42 setting shortcut name 43 trying the installer 50 using to create an installer 39

R rules 34, 75

S SpeedFolder 36 splash screen 59 system requirements 8

T tags 72 creating 72 testing 84

U Uninstall task 80 uninstaller customizing 80 testing 51

M magic folders 37 main class 46

P Post-Install task 74, 76 Pre-Install task 61 project creating 41 Project Wizard 32 adding files 43 building the installer 49 choosing a main class 46 setting a classpath 48 90

IA-1200-EG00

InstallAnywhere 2011 Evaluation Guide


word