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.

Good Articles

Hi,
This is vinay pls call me to this no 9035759227...