RPM Installer Project Type

InstallShield 11 Universal

The RPM Installer project type installs one product, and can reference and/or install an unlimited number of referenced assemblies. It enables you to leverage RPM as the deployment mechanism for your product while gaining all of the benefits and functionality of Universal assemblies.

This project type can only be built on a development machine with RPM installed.

RPM provides a rich set of delivery functionality, prerequisites management, and stability through package integrity verification. However, it lacks the rich end-user experience and ease of use of the Universal installer and uninstaller engines. Therefore, we have combined these two technologies in this project type. The RPM Installer leverages the InstallShield Wizard user interface and tooling, but its application payload is deployed through RPM. This gives you increased value and a refined end user experience when targeting any machine that has RPM installed.

To include a non-RPM assembly in an RPM Installer project, the non-RPM assembly's Platform Support/Linux/RPM Integration Enabled property (in the Releases view) must have been set to "True" in order for the assembly to be registered by RPM.

The Installation Designer tab views are different from other projects, and they are described below. The default dialogs and actions that are included in the Sequences view are also listed below.

• The end user must be logged in as "root" in order to install a product built with this project type.
• RPM Installer projects cannot be included in a Static Suite.

Installation Designer Tab Views

The Project Assistant is not available for this project type.

The views in this project type are a subset of the views in other project types because some of the concepts of Universal projects do not apply to RPM technology. The differences are listed below:

• Installation Information/General Information—This view is same as in other projects plus the RPM Properties section that enables you to set all of the basic properties that are part of an RPM package.
• Organization
  
  • Installation Design, Features, Components—These views are not included in this project type. The structure for the installation is configured in the Files and Folders view.
  • Assemblies—This view is the same as in other projects except that the assemblies can only be added to the root product. Also, for dependencies on non-RPM assemblies to be checked and maintained, the RPM Integration Enabled property of the non-RPM assembly's Releases/Platform Support/Linux Platform Support must have been set to "True."
  • Installation Types—This view is not included in this project type because Installation Types to not apply to RPM.
• Application Data
  
  • Files and Folders—This view's Files window is similar to the Files view's Files window in Universal Installer and Condenser Installer projects. In this project type, however, it includes an Explorer window that represents the application payload from the perspective of the target machine. This is where you specify which platforms the project should be able to target and set up the directory structure and payload for each platform.
  • Launchers—This view is only for configuring JVM resolution for the Product Uninstaller Launcher, if one was configured in the General Information view. (Java Application Launchers do not apply to RPM.)
• System Configuration—This group of views is not included in this project type.
• Additional Tools—This group of views is the same as in other Universal projects except that it includes an additional view titled RPM Direct Editor. This additional view works the same as the Direct Editor view except that it enables you to define files, dynamic links, directories, and platforms that you would otherwise set in the Files and Folders view. It also enables you to directly edit the properties specific to RPM that would otherwise be edited in the General Information view.

Sequences View

This project type automatically includes the following dialogs and actions in the Sequences view, which are all you need for a successful RPM product installation.

• Product Sequences—Only used when creating this project to be built to install a product
  • Installation Sequence
    • PreInstall
      • Installed Product Check dialog
      • Welcome dialog
      • Destination dialog
      • Update Checks dialog
      • Assembly Category Reference action ("Assembly Pre-Selection")
      • Filter Missing Requirements action
      • Assembly Category Reference action ("Assembly Post-Selection")
      • Install Check dialog
      • RPM Install Test dialog
      • PreInstall Summary dialog
    • PostInstall
      • Install action
      • Assembly Category Reference action ("Assembly Post-Transfer")
      • Post-Install Summary dialog
      • Logout dialog
      • Reboot dialog
  • Uninstallation Sequence
    • PreUninstall
    • Uninstall Welcome dialog
    • RPM Install Test dialog
    • Uninstall Preview dialog
  • PostUninstall
    • Uninstall Summary dialog
    • Logout dialog
    • Reboot dialog
• Assembly Sequences—Only used when creating this project to be built as an RPM assembly
  • Assembly Pre-Selection—Dialogs and actions to be visited after update checks have been completed
  • Assembly Post-Selection—Dialogs and actions to be visited after the filtering of missing requirements has been completed
    • RPM Install Test dialog
  • Assembly Post-Transfer—Dialogs and actions to be visited immediately after the installation of the package

See Also

RPM Support
Creating an RPM Installer Project
Creating a Project to be Built as an Assembly
Adding Dialogs
Adding Actions