installanywhereExpert created the topic: LaunchAnywhere in InstallAnywhere
LaunchAnywhere is Macrovision’s Java application launcher technology. A native
executable used to launch a Java application, LaunchAnywhere technology creates
double-clickable icons on Windows and Mac OS X. On Unix platforms, a commandline
application is created.
A LaunchAnywhere Java application launcher automatically locates an appropriate
Java Virtual Machine (JVM), either bundled with the application or already installed
on the system, and sets the Java options and settings (such as heap size) depending on

the developer’s specifications. LaunchAnywhere sets the classpath, redirects standard
out and standard error, passes in system properties, environment variables, and
command-line parameters, and launches the Java application. LaunchAnywhere
hides the console window by default for GUI applications, or can be set to display the
console for text-based applications. All LaunchAnywhere settings are configured
within InstallAnywhere, and are automatically set when the installer installs the
application.

Tagged : InstallAnywhere

installanywhereExpert created the topic: Magic Folders in InstallAnywhere
InstallAnywhere uses Magic Folders to define installation locations. These Magic
Folders are a way of keeping track of installation locations. InstallAnywhere can
install to any Magic Folder or sub-folder of a Magic Folder. Magic Folders represent a
specific location, such as the user selected installation folder, the desktop, or the
location for library files. At install time, the installer determines which operating
system it is running on, and sets the Magic Folders to the correct absolute paths. Many
Magic Folders are platform specific and many are predefined by InstallAnywhere. You
can install to nearly standard location on any supported platform. InstallAnywhere
also provides user controlled Magic Folders which can be set as the developer needs
them.

Tagged : InstallAnywhere

installanywhereExpert created the topic: Action Groups in InstallAnywhere
Action Groups make InstallAnywhere projects more manageable and easier to
understand. They allow the developer ability to logically group a set of actions or
panels in Pre-Install, Post-Install, Pre-Uninstall and Post-Uninstall. Rules applied to
the Action Group affect all the actions or panels contained inside it. They can
extremely helpful with large complex installations that contain numerous actions and
panels.

Tagged : InstallAnywhere

installanywhereExpert created the topic: Project File in InstallAnywhere
InstallAnywhere stores every project in its own XML file. These XML-based project
files can be checked in and out of source control systems, and can be modified with
text and XML editors. For added flexibility, project files may also be modified using
XSL transformations, providing the ability to modify referenced file paths, or other
attributes. Several XML and XSL tools to work on the XML project file can be found in
the InstallAnywhere application folder, inside resource/extras/XML Project File
Tools.

Tagged : InstallAnywhere

msiexpert created the topic: Installer UI in InstallAnywhere
Installer UI
The Installer UI task includes the following subtasks:
?? Look & Feel
?? Billboards

Look & Feel
The Look and Feel subtask contains three tabs which enable developers to
configure the look and feel of the installer. These tabs allow developers to customize
many graphic elements and progress panels within the installer. Within these three
tabs are different Preview buttons which display the look and feel of the installer with
the current settings.

General UI Settings
Use the General UI Settings tab to set general look and feel settings for the
installer. Select one or more supported UI modes and the preferred GUI mode (AWT
or Swing). Swing offers the ability to have a background image, such as a company
logo, to be displayed in the installer. This specific background image can also be
defined using this tab. You can also choose the startup splash screen image.
To have progress panels show the progress of the installer, select Additions to GUI
Installer Panels. If Additions to GUI Installer Panels is not selected, the
Installer Panel Additions and Install Progress Panel tabs are disabled.
The Installer Frame UI Settings section allows you to customize the colors, style,
and size of the installer panels. Click Default to restore the default size for panels
(600 pixels width and 400 pixels height). If you enter a custom size, click Preview to
view a sample panel.

Installer Panel Additions
Use the Installer Panel Additions tab to choose installer panels in the left hand
install progress rectangle. If you choose Images as the type of addition, the other fields
on the Installer Panel Additions tab are disabled. Select the Images radio button then
click the Install Progress Panel tab.
Selecting List of Installer Steps as the type of addition enables fields that allow you
to customize labels. The buttons to the right enable developers to add or remove
labels, or change the order of the labels. Developers can edit the text string that is
displayed. The Auto Populate button adds an installer panel for every panel action
added to the Pre-Install and Post-Install tasks. Choose Icon enables developers to
alter the small square graphics that are to the left of the text labels. The default icons
are double arrows for the current step or steps to be completed and a check mark for
installation steps that have been completed.
The Installer Steps Background Image option enables developers to select a
specific image to display in the rectangle on the left hand side where installation step
labels are displayed.

Install Progress Panel
Use the Install Progress

Tagged : InstallAnywhere

msiexpert created the topic: Billboards in InstallAnywhere
Billboards

Billboards are images that appear in the large right hand pane of the installer while
files are being installed. Use the Billiards subtask to add billboards to the installer
panels. 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.

Tagged : InstallAnywhere

msiexpert created the topic: Organization in Installanywhere
Organization

The Organization task enables developers to arrange Install Sets, Product Features,
Components, and Merge Modules. Install Sets and Features allow for levels of
installation options for the end-user of the installer. Components are the smallest
widget that can be selected by a Feature set. Install Sets are groupings of Features, and
are an organizational tool for the developer of the installer. Components may be much
more than files, they can be sophisticated actions that are required to install and run
applications or features properly.
There is an interaction between the Install Sets, Features, and Components
subtasks, as well as the Install task. If an install set is added in the Install Sets
subtask, features can be assigned to that install set in the Features subtask. If a
feature is added in the Features subtask, components can be assigned to that feature
in the Components subtask. If a component is added in the Components subtask,
files and/or actions can be assigned to that component after the files and/or actions
are added in the Install task.

Install Sets
Install Sets are a set of product features. The Install Sets subtask allows developers
to add, name, remove, or order Install sets in the installer. In the Install Set List,
developers define which install set (or sets) to use as the default option to provide to
the end-user. Features are assigned to install sets in the Features subtask.
When the installer requests install set information, each install set is represented by a
graphic element. The Choose Image button enables developers to select the graphic
element.
Rules may be associated with an install set, and that association is created by selecting
Rules in the customizer and adding rules. The rules for install sets are evaluated
before the install set is installed. If the rules on the Install Set evaluate to false, the
Install Set will not be displayed.

Features
Features are meant to identify distinct parts of the product so the end-user may
choose whether or not to install them. InstallAnywhere Product Features are
groupings of components. It is up to the developer to define the logical grouping of
components into features by assigning components to the features in the
Components subtask.

The Features subtask enables developers to add, name, remove, or order features.
Rules may be associated with a feature set, and that association is created by selecting
Rules in the customizer and adding rules. The rules for feature sets are evaluated
before the feature set is installed. If the rules on the Feature evaluate to false, the
Feature will not be displayed.

Components
Components are the smallest unit of organization when creating an installer. Unlike
Features and Install Sets, Components may be versioned. Components are uniquely
identified so developers may update a specific component or use the Find Component
in Registry action to locate a particular component.
The Key File is a file that must be present in all subsequent versions of the component.
The Key File is used to define the components location when the Find Component in
Registry action is used.
The Components subtask enables developers to add, name, remove, order, identify,
and version components.
Rules may be associated with component sets, and that association is created by
selecting Rules in the customizer and adding rules. The rules for component sets are
evaluated before the component set is installed.

Modules
The Modules subtask imports Merge Modules into an InstallAnywhere project.
Merge Modules are created as a build output option in the Build task.
DIM References
The DIM References subtask supports referencing Developer Installation Manifests
(DIMs) in installation projects. DIMs are XML files that describe specific product
subsystems and their requirements. Application developers create DIMs using
InstallShield Collaboration, a plug-in module for Eclipse and Microsoft Visual Studio
.NET. See Referencing Developer Installation Manifests (DIMs) for more information
on referencing DIMs in your installation project.

Tagged : InstallAnywhere

deployexpert created the topic: What’s New in InstallAnywhere 2010
Register now for the upcoming webinar “What’s New in InstallAnywhere 2010″

Wednesday, March 3, 2010, 2pm ET / 1pm CT/ 11am PT

mktg.flexerasoftware.com/mk/get/whatsnew-IA2010

Tagged : InstallAnywhere

msiexpert created the topic: Advanced Designer in InstallAnywhere
Advanced Designer
While the Project Wizard leads developers through a few simple steps to create an
installer, the Advanced Designer gives greater precision, enabling developers to access
all the powerful features of InstallAnywhere. With the Advanced Designer developers
can assign files and actions to feature sets, allowing the user to define which files are
installed; rules can be added which selectively install different files or different
installation locations dependent on the target platform. With the Advanced Designer
developers have precise control over all the design options of an installation project.
The Advanced Designer contains several tasks and subtasks which are displayed on
the left hand side of the Advanced Designer development environment. The tasks are
broken down into discrete subsets of the installer creation process.

Project
The Project task displays InstallAnywhere project information, configures, provides
options to bundle or define acceptable VMs, and defines product, file installation, and
localization options. The Project task includes the following subtasks:
?? Info
?? Description
?? File Settings
?? Platforms
?? Locales
?? Rules
?? Config
?? Java

Info
Use the Info subtask to define basic information about the installer, including the
installer title and name, build location, and installation log.

Description
Use the Description subtask to enter vendor and product information to uniquely
identify your product in the product registry. For the target operating systems, the
product registry is essentially a product configuration database which keeps track of
features and components of products and accomplishes tasks such as associating file
name extensions with applications. You must set the Product ID and Version correctly
for the Find Component in Registry action to work. InstallAnywhere finds the
locations of components in the Registry by checking the Product ID.

File Settings
Use the File Settings subtask to define timestamps of installed files and the
overwrite behavior for installed files that already exist in the targets install locations.
Timestamps are considered when an installation file already exists on the target
system.

Platforms
Use the Platforms subtask to define default settings unique to each target operating
system. While InstallAnywhere runs on any Java enabled platform, there are features
that should be defined separately for each target operating system.
The default settings for Windows include default locations for install and shortcut
folders.
The default settings for Mac OS X include default locations for install and alias folders,
default Java VM used for LaunchAnywhere, whether authentication is required for
installation, and permissions for files and folders created on the target system.
The default settings for Linux include default locations for install and link folders,
default user interface mode, permissions for files and folders created on the target
system, and RPM (RedHat Package Management) settings for Linux installations.

Locales
Use the Locales subtask to define the languages for the installer. A locale is enabled
when it is checked.
All enabled locales generate a locale file that is placed in a folder that is in the same
directory as the InstallAnywhere project file. To customize a locale, customize this file.
See Localization for more information about locales and localization.

Rules
Use the Rules subtask to add tasks to the installer before any installation tasks, even
Pre-Install tasks. Use this option to check if this is a proper platform for this
installation, or if the user is logged into the root, or has the necessary permissions to
perform the installation.
Config
Use the Config subtask to define a valid list of Java VMs the installer can use and set
the heap size for the VMs. Use this subtask to enable debug output and select if it
should be sent to a file or to a live console, and also set additional commands to the
Java VM other than those which the installer already sets.

Java
Use the Java subtask to fine tune the classpath settings and decide whether to install
the bundled Java VM. You may choose not to install a VM, Install the VM only while
performing the installation, or to leave the VM on the target system. If you choose to
install the VM, the VM Install folder pull down list provides a variety of locations.

msiexpert replied the topic: Re: Advanced Designer in InstallAnywhere
Good Articles

remold replied the topic: Re: Advanced Designer in InstallAnywhere
Hi,
This is vinay pls call me to this no 9035759227…

Tagged : InstallAnywhere

installanywhereExpert created the topic: Localization in InstallAnywhere
Localization in InstallAnywhere

InstallAnywhere’s Enterprise edition allows developers to build installers for up to 29
different languages. The Standard edition enables developers to build for up to 9
languages. To generate multi-language installers, click the Project | Locales task in the
Advanced Designer, and use the check boxes to select the appropriate languages.
When an installer project is first built, a folder called locales is created
in the same directory as the project file. For each locale selected in the Advanced
Designer there will be a file in this locales folder. The locale files are
generated as custom_, so for English which has a locale code of en, the
name of the locale file will be custom_en. These files contain keys and values for all of
the dynamic strings in the project. The keys are generated by the name of the action,
with a unique value to represent the unique instance of the action, and an additional
parameter to signify which dynamic value of the action is being referenced. For
example:
InstallSet.9733839b90f6.installSetName=Typical
InstallSet.9733839b90f6.description= The most common application features will
be installed.
This option is recommended for most users. The ProjectLocalizationInfo.txt file
contains the mapping between the actions in the project and their keys in the locale
files. Review the ProjectLocalizationInfo.txt file for any questions as to which action
the key refers to.

Tagged : InstallAnywhere