Can i launch an installer from the project

[anitha]

Suppose i have a requirement say:

1.Install A
2. Install B
3. Install both

for 3rd option can i launch an installer from the project
Do IA have an option to call IA installers in the project

[pv7721]

There isn't any special option (unless you use Merge Modules). If not, you can bundle installer B in installer A and install the B setup and use the Execute Target command in order to launch it.

[anitha]

Thanks a lot
i think calling an IA installer in other can be achieved using Merge Modules

Thanks again.

[anitha]

can anyone tell me how does a merge module work

[pv7721]

Quoting from the manual:

Merge Modules

InstallAnywhere 2008 Value Pack 1

Merge Modules are essentially installer sub-projects that can be created independently of one another and later merged together. Like an installer a Merge Module is a reusable collection of installation functionality, complete with features, components, panels, actions, and files. However, a Merge Module cannot be installed on its own; instead, developers use Merge Modules when they want to include the functionality of one installer within another installer.

Merge Modules provide many benefits and provide solutions to complex installation requirements. For instance:
Combine several Merge Modules from different products to create a "Suite Installer."
Independent development teams in different locations can create Merge Modules for different software components. A release engineer can combine those Merge Modules into a single product installer.
Create self-contained units of installer functionality for reuse in future installer projects. For instance, if the same software component needs to be in several different installers, build it into a Merge Module and make it available for all of the installer developers.
Save common installer functionality, such as License Agreement panels and Custom User Input panels, into Merge Modules to simplify future installer project creation.
Combine Merge Modules from 3rd party software packages to build complex software "Solutions," without having to figure out how to install each individual package.

Macrovision provides many 3rd party Merge Modules on its Web site.
Use a Merge Module as the starting point for a new installer project. These Merge Modules are referred to as Templates, and are covered in another section.
Any installer project can be built into a Merge Module. And any Merge Module can be used within any other installer project.
Merge Modules are created as an option through the installer build process. Since a Merge Module contains all of the resources for a project, it is just like building an installer. They can be built automatically when the installer is built, or they can be explicitly built from the Advanced Designer (check the Build Merge Module option on the Build task, under the Distribution tab) or from the command line (use the +merge option).

Merge Modules can be merged into an existing installer in one of three ways:
In the Organization > Modules task, click Import Dynamic Merge Module to merge a merge module into the current installer. All of the merge module's files, actions, and panels (optionally) will be combined into current project. The actions will appear as in an action group in Pre-Install and Post-install. Dynamic Merge Modules are recommended if you have merge modules whose contents constantly change. A parent project will automatically refresh dynamic merge modules when the parent project is loaded and built.
In the Organization > Modules task, click Import Static Merge Module to merge a merge module into the current installer. All of the merge module's features, components, files, actions, and panels (optionally) will be combined into the current project, allowing developers to further customize any settings. Static Merge Modules are recommended if you have merge modules if you want import features and components and if you want more freedom in the place actions. Changes made to a static merge module will not be noted in the parent project.
Merge Modules can also be installed as self-contained sub-installer units, without merging them into the current project. This is useful if developers do not know what will be in a Merge Module, or they will not be modifying any settings. Merge Modules added in this manner are run as silent sub-installers.

Merge modules can be integrated with a project in one of two ways:
Use the Install Merge Module action and select Bundle Merge Module at Build Time, if the merge module is available when ready to build the installer. These Merge Modules will be included in the actual generated installer.
Use the Install Merge Module action and select Locate Merge Module at Install Time to have the installer install a Merge Module that is available at install time, but external to the installer. The Merge Module can be either on the end user's system or stored on a CD. If the location is a folder that contains several Merge Modules, they will all be installed.
Advertised Variables

These are InstallAnywhere variables that the merge module needs from the parent installer or will be passed back from the merge module to a parent installer. On the Build task, under the Distribution tab, click Edit Advertised Variables to add variables, set default values, and add comments. They are used by Dynamic Merge Modules and the Install Merge Module action.

Advertised Variables are defined by task. Variables set as advertised as Pre-Install will only affect the Dynamic Merge Module in Pre-Install. The Install Merge Module action only pays attention to Advertised Variables set in the Install task. Use Advertised Variables to inform master installers of settings required for a Merge Modules configuration, and to return information like status back to the parent installer.

Other important things to know about Merge Modules:
Read Only option: Merge Modules can be locked, preventing them from being opened, used as templates, or being merged into an installer. Read Only Merge Modules can only be installed as a self-contained installer unit.
Optimize Merge Module Size by Platform option: Separate merge modules will be created for each platform. Each will only contain the resources needed for that specific platform. Do not use this option if merge modules will be imported into another installer. Importing a merge module requires a non-optimized merge module.
You can set the stderr and stdout of a merge module to InstallAnywhere variables. This is useful if you want to debug a merge module.

[anitha]

oops sorry for the trouble

Thanks a lot again..