InstallShield 11 Universal
An RPM Assembly Build Configuration is added to your project in the Releases view of an RPM Installer project. It builds the project into an RPM assembly, which must be installed by a project that was built as a product—either a Universal Installer or RPM Installer project that was built with a Product or RPM Build Configuration, respectively. You can also deploy an RPM assembly with a Universal Dynamic Suite.
For example, you can build an RPM Installer project into an assembly, and then include it in a Universal Installer project. You would conditionalize the feature that references the assembly for the platform for which the assembly was built. Then, after building the project with a Product Build Configuration, you could deploy the product to platforms that have RPM installed and those that do not (presuming that you also included non-RPM assemblies in the project).
You can deploy the payload of an RPM assembly to platforms that do not have RPM installed by setting the RPM Assembly Build Configuration's Include Support for Non-RPM Platforms property to "True."
An RPM assembly can require/reference both RPM and non-RPM assemblies.
A built RPM assembly is automatically named assembly.dat, and is saved with the following directory structure:
<UUID>/<Version>/assembly.dat
To also build this project as a product, add and configure an RPM Build Configuration, then build the project with that build configuration selected.
See Also
RPM Assembly Build Configuration Properties
Working With Assemblies