Flexera Software Logo

InstallAnywhere 2015

Release Notes

originally released August 2015; updated to include SP1, released December 2015


InstallAnywhere is the leading multiplatform installation development solution for application producers who need to deliver a professional and consistent installation experience for physical, virtual, and cloud environments.

For the latest information about this release of InstallAnywhere, including any possible updates to these release notes, see the online version of the InstallAnywhere 2015 release notes.

InstallAnywhere 2015 Service Pack 1 (SP1) offers expanded platform support and resolves a number of issues.


Changes in SP1 (December, 2015)

InstallAnywhere 2015 SP1 offers expanded platform support. It also resolves a number of issues. This service pack is available as a patch installer; that is, you can install it on a machine that has the original release version of InstallAnywhere 2015. The InstallAnywhere 2015 SP1 installer is available via a FlexNet Connect update.

Expanded Platform Support

InstallAnywhere now supports the following platform for the installer run-time environment, as well as for the InstallAnywhere authoring environment:


OS X installers now correctly detect the specified locale for all languages and the locale selection panel of the installer correctly displays the associated locale. For example, if the system locale is set to Japanese, the locale selection panel on the installer will properly display Japanese as a selectable option.


After installing to a mounted Network File System (NFS) directory, the uninstaller will no longer remove any files that were not explicitly installed by the installer. Any new files added after the install are no longer removed by the uninstaller.


Log entries in the "Install File" string that are created by the Install SpeedFolder action are now correctly localized based on the installation's supported language.


When using a Copy File Action or Copy Folder Action to create duplicate files in the installation directory, the Required Disk Space value shown in the Pre-Install Summary Panel is now calculated correctly. The size of the files or folders that are copied are now added to the total required disk space.


String text for words Fatal Error and Non-Fatal Error are now translated to Brazilian Portuguese (Erros Fatais and Errors não fatais, respectively) in the standard installation log.


On Windows and Linux, with Java 7 and Java 8, the Installation directory text on the Custom Code Consoles Panel is no longer wrapping as had been the case in InstallAnywhere 2014 SP1 with Hotfix A and now displays correctly.


When an installer is launched and installed with a locale of Chinese (Simplified), the install log now displays the correct translation.


When you create a console installer with Polish locale enabled, if you include a Show Message Console 'Dialog' Console Action with at least two options enabled, only one colon is displayed after the prompt that asks for your selection.


When setting the Default File Overwrite Behavior to Always prompt user (in the File Settings area of the General Settings view) and the user clicks the No button for the prompt to overwrite uninstaller.app and clicks the No button for the prompt to overwrite LaunchAnywhere.icns, the uninstaller now launches and completes successfully without errors.


When you create a console installer with Chinese (Simplified) locale enabled, word wrapping will not occur when space is adequate.


Merge module advertised variable names in the parent project Install tab of the Organization page's Modules view now display correctly.


According to OVF standards, when a virtual appliance is built for VSphere 5 + hypervisor, the virtual machine version is 8.0. Accordingly, when creating a VMware vSphere 5 virtual appliance in InstallAnywhere, the OVF now displays "vmx-08" as the value for the tag 'VirtualSystemType' under System details.


When you create a virtual appliance in InstallAnywhere, values shown in the virtual appliance's first boot screen have been updated to inform that the virtual appliance was created with InstallAnywhere. Also, the Appliance URL field shown on the boot screen now displays the #hostname# to a properly resolved IP address.


CentOS 7 x64 virtual appliances created using InstallAnywhere can now be deployed on VMware vSphere 5.


InstallAnywhere supports virtual appliance deployment on VMware vCenter Server 5.5 if the virtual appliance was built with VSphere 5.0.


Environment variables containing spaces are enclosed within quotes.


Installers created with or without a Java virtual machine bundled with them now launch correctly (including but not limited to those with target applications using Java 8 Update 60 Release).


InstallAnywhere's Hotfix for Windows Launchers no longer causes the built installer to generate a Windows error on Windows XP and Windows Server 2003. The built installer launches successfully.


ADD commands in Dockerfile now copy files to the correct destination inside the Docker container.


After applying InstallAnywhere 2015 Public Patch and InstallAnywhere 2015 Boreas SP1 Patch installers on InstallAnywhere 2015 RTM, redundant folders are no longer created in the IA_HOME/Launchanywheres directory and the latest launchanywheres for all platforms are present inside the IA_HOME/Launchanywheres folder.


Any heap sizes that are set through the launcher properties are now being properly updated and picked up by the launchers instead of being taken from the IDE settings.


New Features in InstallAnywhere 2015 Original Release Version
(August 2015)

Ability to Build Docker Images from InstallAnywhere Projects

InstallAnywhere Premier Edition with Virtualization and Cloud enables you use your existing InstallAnywhere projects to configure and build Docker images along with your traditional multiplatform installers. You can use the Docker support to prepare your on-premises Web applications for deployment to the cloud and to data centers.

Docker is a platform that enables developers and system administrators to build, distribute, and run applications on physical machines, data center virtual machines, or the cloud; it enables you to separate your applications from your infrastructure. A Docker image is a read-only template that InstallAnywhere can build from your project. A Docker container is launched from a Docker image. A Docker container consists of a complete file system that includes everything that is needed to run—code, system tools, system libraries, and more; it is the run component of the Docker platform.

To enable, configure, and build Docker images, use the new Build Containers view on the Build page in the InstallAnywhere Advanced Designer.

The Build Containers view also enables you to search public and private Docker registries for base images—such as those for Ubuntu, CentOS, Java, and MySQL—and pull them into your Docker images. You can also specify installers that you want to be run on your Docker images.

To customize or further fine-tune the creation of Docker images, advanced users have the ability to edit the Dockerfile—the set of commands that tells the Docker engine how to generate a Docker image—that InstallAnywhere creates as you configure Docker settings in your project; this capability is in the Build Containers view.

Support for Deploying Web Applications to Local or Remote IBM WebSphere Servers

InstallAnywhere Premier Edition offers improvements for deploying Web applications (.ear or .war) to IBM WebSphere servers.

Enabling End Users to Specify Connection Information for WebSphere Servers

Now you can add to your projects run-time panels or consoles that enable end users to specify settings for WebSphere servers before deploying Web applications to these servers. For example, you can let end users specify information such as the local or remote WebSphere server host where they want to deploy the Web application.

To add the new run-time panels to a project, add the WebSphere Runtime Deployment panel or console actions. These actions are available for the Pre-Install view on the Sequence page in the InstallAnywhere Advanced Designer.

By default, these new run-time panels and consoles use variables such as $WEBSPHERE_DEPLOYMENT_OPTION$ and $WEBSPHERE_HOSTNAME$ for storing the values that end users enter.

IBM WebSphere 7, 8, and 8.5 Support

InstallAnywhere now has support for deploying Web applications to WebSphere 7, 8, and 8.5 servers.

Expanded Support for Connecting to IBM DB2, Microsoft SQL Server, and PostgreSQL Databases and Running SQL Scripts

InstallAnywhere Premier Edition offers several improvements for connecting to IBM DB2, Microsoft SQL Server, and PostgreSQL databases and running SQL scripts.

Enabling End Users to Specify Connection Information for Local and Remote Servers

Now you can add to your projects run-time panels or consoles that enable end users to specify connection information such as the name of the local or remote server, as well as the credentials that should be used to connect to the server through server authentication. In addition, you can optionally enable end users to test the connection information that they entered.

To add the new run-time panels and consoles to a project, add the Choose Database Connection panel or console actions. These actions are available for the Pre-Install view on the Sequence page in the InstallAnywhere Advanced Designer.

By default, these new run-time panels and consoles use variables such as $DB_NAME_VARIABLE$ and $DB_SERVERHOST_VARIABLE$ for storing the values that end users enter.

Support for Creating Databases on Target Systems

The Run SQL Script action now optionally supports the creation of Microsoft SQL Server and PostgreSQL databases on target systems. The Properties Customizer that is displayed when you select this action in the Install view on the Sequence page has a Create Database check box that you can use to indicate whether to create the database at run time.

IBM DB2 10.1 and 10.5 Support

InstallAnywhere now has support for managing IBM DB2 10.1 and 10.5 databases, as well as IBM DB2 9.0 and 9.7 databases.

Microsoft SQL Server 2008 R2, 2012, and 2014 Support

InstallAnywhere now has support for managing Microsoft SQL Server 2008 R2, 2012, and 2014 databases.

Support for SHA-2 Digital Certificates

InstallAnywhere now enables you to use digital certificates that use the SHA-2 hashing algorithm for signing your Windows-based installers (the installer .exe file, as well as the installer launcher and the uninstaller launcher) at build time.

SHA-256 is favored over SHA-1, which is being deprecated because of the potential for security vulnerabilities. Microsoft announced that Windows will stop trusting items that were signed and timestamped with SHA-1 certificates after January 1, 2016. In addition, certification authorities-the organizations that issue certificates-are phasing out the creation of SHA-1 certificates. Thus, it is recommended that you replace any SHA-1 certificates in your InstallAnywhere projects with SHA-2 certificates. For the latest information and more specific details, check with your certification authority.

If your project is configured to sign with a SHA-2 certificate, InstallAnywhere uses a SHA-2 hash in the signature of the files that it signs at build time. If your project is configured to sign with a SHA-1 certificate, InstallAnywhere generates a build error: either 813 (a SHA-1 certificate is configured in the project) or 814 (a SHA-1 certificate is configured in the project and a timestamp server is not being used for signing).

This feature resolves issue IOJ-1722004.

Support for the Latest Platforms

InstallAnywhere now supports the following platforms for running installer run-time environment, as well as for the InstallAnywhere authoring environment:


Enhancements in InstallAnywhere 2015 Original Release Version
(August 2015)

Support for Transparent Backgrounds on UI Panels

InstallAnywhere now enables you to make the main body area of each panel in the user interface of your installer transparent. Previously, this area behind the main UI text was always white.

To specify that you want the main body area to be transparent, select the new No Color option in the Inner Panel Background Color setting. To access this setting, on the Installer UI page, click the Look & Feel Settings view. Then, in the General UI Settings area, under the Installer Frame setting, the Inner Panel Background Color setting is available with the new option.

Ability to Change the Text Color of the Installer Steps That the Installer UI Shows for Progress

InstallAnywhere now enables you to customize the font color that is used to display the text of the installer steps that is included on the left side of the installer user interface.

To specify the color, use the Look & Feel Settings view on the Installer UI page. In the List of Labels for Installer Steps setting, click the Installer Step Label settings button; the Installer Steps dialog box opens. On this dialog box, click the Icons and Fonts button. The Choose Label Settings dialog box opens. To change the font color of the text for the installer steps, click the Font Color button.

Enhanced Show Message Dialog Action

The Show Message Dialog action has been enhanced. One of the new settings that you can configure for this Pre-Install action is a check box called Cancel and Exit on ESC or X. If you want the installer to cancel and exit the installation if the end user presses the Escape button or clicks the Close button (X) on the message dialog, select this check box.

This check box is cleared by default.

This enhancement resolves issue IOC-000087766.


Important Information

Evaluating InstallAnywhere

Note that if you have not purchased a license for InstallAnywhere, you can install it and use it for a limited number of days without setting up the licensing. When you are using InstallAnywhere in this scenario, it operates in evaluation mode. The licensing wizard that InstallAnywhere displays whenever you launch InstallAnywhere in evaluation mode shows you how many days are left in the evaluation period. If you do not set up the licensing within the evaluation period, InstallAnywhere stops working when the evaluation period ends. You can set up licensing at any time before or after the evaluation period ends.

When you use InstallAnywhere in evaluation mode, there is a time limit for running installers that it creates. If you build an installer in the evaluation version of InstallAnywhere, your installer will stop working after 3 days.

When you use InstallAnywhere in evaluation mode, InstallAnywhere limits you to a maximum of five successful builds of Docker containers.

Obtaining the Installation and License Files for InstallAnywhere

You can obtain the installation and license files for InstallAnywhere through the Flexera Software Product and License Center. For instructions, see the download and licensing instructions for InstallAnywhere. If you purchased concurrent licenses of InstallAnywhere, the license server software is also available for download from that same site.

InstallAnywhere Premier Edition with Cloud Pack Renamed

InstallAnywhere Premier Edition with Cloud Pack has been renamed to InstallAnywhere Premier Edition with Virtualization and Cloud.


Project Upgrade Alerts

The following information describes possible upgrade issues that may occur when you upgrade projects that were created with InstallAnywhere 2014 and earlier to InstallAnywhere 2015. It also alerts you to possible changes in behavior that you may notice between new InstallAnywhere 2015 projects and projects that are upgraded from InstallAnywhere 2014 or earlier to InstallAnywhere 2015.

Database Server Support for Microsoft SQL Server and IBM DB2

If you have an InstallAnywhere 2014 or earlier project that contains a Microsoft SQL Server or IBM DB2 or database server host and you open the project in InstallAnywhere 2015, InstallAnywhere displays a warning and informs you that may need to make changes to incorporate the new run-time panel action that lets end users specify connection information. To learn more, see "Enabling End Users to Specify Database Connection Information" in the InstallAnywhere Help Library.

InstallAnywhere no longer has support for the following versions of Microsoft SQL Server:

InstallAnywhere supports Microsoft SQL Server 2008 R2, 2012, and 2014 databases.

Removal of InstallAnywhere Collaboration Support

All support for the InstallAnywhere Collaboration plug-in and DIM references has been removed from InstallAnywhere. That is, the DIM References view and the DIM-related actions (the Create DIM Reference action and the Create Alias, Link, Shortcut to DIM File action) are no longer be available in InstallAnywhere. It will no longer be possible to build installers that reference DIM files. If you upgrade a project that contains DIM references or DIM actions from InstallAnywhere 2014 or earlier to InstallAnywhere 2015, InstallAnywhere 2015 removes them from your project.

It is recommended that before upgrading a project with DIM support to InstallAnywhere 2015, all DIM references and DIM-related actions be removed from InstallAnywhere projects and replaced with standard files and actions where appropriate.


Resolved Issues in InstallAnywhere 2015 Original Release Version
(August 2015)


When using an authenticated installer with OS X code signing, the uninstaller is now digitally signed during the build process resulting in the digitally signed installer to no longer fail during the build process.


FlexNet Publisher only found one host ID on a Macintosh OS X operating system that had multiple NICs. To address this issue, the FlexNet Publisher libraries in InstallAnywhere were updated from version 11.7 to 11.13.


When the target application is launched with graphical LaunchAnywhere launcher on OS X, the current working directory for Java now uses the correct Java system property user.dir location where the LaunchAnywhere launcher was installed.


Check System Architecture Rule no longer fails when installer is run on Solaris SunOS using Java 8.


In addition to the -? option that is used to display help text, the help menu now also includes the -h, -help, and -help options to "show this help text" as well.


When a file is encoded to UTF-8 using the File Encoding field of the Modify Text File action, the resulting file no longer corrupts certain characters.


Installer on longer hangs when looping Custom Code Actions are included. Previously, the Cancel, Previous, Next, and other buttons become unresponsive and not clickable on the Choose Install Folder Panel.


The Java 8 VM Pack download for Solaris Intel on our website is now correctly pointing to the correct download.


Mac OS X Installer created with InstallAnywhere 2014 SP1 that failed to launch on 10.7.5 OS X has been fixed.

IOJ-1725192, IOJ-1724404

The Expand Archive (TAR) Existing Archive action successfully expands an archive that is present on the target system.


Native dialog text entry hook added within custom code for OS X authenticated installers. As background, InstallAnywhere provides controls that call into the necessary native dialog on OS X to allow text entry. These the controls have been updated to cover all of the controls needed by IBM to allow them to call our native input dialog.


Create JRE VM Pack utility has been fixed to successfully create a valid Solaris VM Pack on Windows and Linux.


Installer fixed to correctly create response file in the directory where install.exe is present when the Output Debug Information action is present in the post-install sequence.


Support added for digitally signing installers for Windows with SHA-2 digital certificates.


Ability to assign a custom ICO icon added even if it is not directly present inside IA_PROJECT_DIR directory.


Installations bundled with Java 8 32-bit fixed to uninstall correctly on Windows 8/8.1 machines.


When a valid copy of system unzip command is not found in PATH the installer now displays "Invalid unzip command found" error message.


In cases where the Preserve Timestamp project setting is used, the file timestamp for files is no longer incorrectly updated to the current timestamp after running repair operation. The timestamp for the installed files after installation and before repair are the same as after the repair.


Advanced Designer Interface can now be resized.


The uninstaller directory and uninstaller.properties file are now removed by the uninstaller.


You can now to copy/paste the Find File/Folder panel.


In case of updated installation, the local registry no longer writes duplicate entries of an installed file and instead only keeps one entry for a specific file.


When running installer with version 1.6 JVM, the installation now correctly installs the uninstaller.jar file and completes without errors.


LaunchAnywhere launcher for java application is now able to find a file present in a relative path when using Graphical Launcher.


When using the Choose Install Sets: Features Only panel with a feature with a rule applied, there is no longer a loss of scope of selected features. The feature will now install and uninstall without issue.


When calling Abort Installation in cases where the installer is configured to generate a log file, the installer now successfully exits.


When using Java 7, the installed LaunchAnywhere launcher for the installed application on Mac OS X now successfully finds and loads the native libraries.


The message displayed in the Get User Input panel is now aligned from right-to-left when the installation is done in Arabic and Hebrew locale. The Title of the panel is also aligned right-to-left.


Fix implemented so that if there is an empty action group within either the pre- and post-install phase, it will always be possible to remove or add Installer Step Labels.

IOJ-1563455, IOA-000124793

If a standard user runs an installer configured to write log files to a location under the Program Files or Program Files (x86) directory location, the installer now skips writing the log and notifies of the failure to write a log.


When "PREVIOUS jump action" is included in a project file and executed in console mode in the pre-install phase, the "Installing" progress message is now displayed only once when the installation happens with valid inputs and the Jump action is executed and the installation is moved to the previous step.


Java application launched using graphical LaunchAnywhere can now write to relative file paths on Mac OS X. Relative paths will now behave the same regardless of the execution method.


The VM Pack Utility now creates a VM Pack for 64-bit Windows that has the vm.platform.flavor property value set to win64, not win32. The VM Pack is displayed in the dropdown menu of bundled VM Pack options for a Pure 64-bit Windows Build Target.


Java 7 powered installers fixed to launch correctly at "Forking Java" step on Solaris 11 under multiple locales.


When adding "Chinese - Simplified" as a supported locale, the Choose Locale and Choose Locale By Number String Text has been fixed to be localized to "Chinese - Simplified" on Console Panel.


The Install Set Panel no longer shows a grey background in the checkbox labels.


"Window name no longer being displayed with the title "LAX" for the Advanced Designer or generated installers in instances where it should be either "InstallAnywhere," a customer selected icon, or whatever is configured in the project for Product Name.


Maximum heap space has been fixed to be set to the value entered in project on Linux/AIX.


When using multiple Execute Batch actions, if the initial batch file becomes locked on a subsequent action, the newly created batch file will be run after being created.


When using the Execute Command action to call MsiExec, spaces have been removed from after their optional parameters "=" character, resulting in the command being correctly run exactly as entered into the action.


When creating a French locale (fr) installer, systems that are set to a French Canadian locale (fr_ca) properly fallback to French when a French Canadian bundle is not available but a general French bundle is available.


Fix has been applied to ensure that values set in the parent installer's module panel for a dynamic merge module persist even after rebuilding the module. As background, the problem previously revolved around dynamic merge module variable advertisement and setting values from the parent installer. When the same variable was advertised in both the install phase and the post install phase, the default value from the module overwrote the install phase parent value on every module build.


Text wraparound no longer occurring in the Pre-Install Summary panel during install. The text now fits on the same line and fits regardless of what JVM being used.


You can now set the installer icon using the Project Automation API (Installer UI > Look & Feel > Installer Icon).


On Mac OS X, when installing an installer which includes a merge module, a Fatal Application Error no longer occurs at the end of the merge module installation. Both parent and merge modules are installed.


The installation development environment is now clearly displaying rules in the Organization > Features view.


Show Message Dialog close button now correctly forces user to exit installer and not allow user to continue and complete installation.


All documented command line switches to the command line builder are included in the output. Previously, the command "'build.exe /?" did not print all available options to the console.


Installer no longer throws "ZeroGcz: No zip file found for entry" exception if moving and building the project from a new folder when assigning an icon file to the shortcut action and there is no missing resource error at build time.


Disk Space Check now gathers correct free space in instances when USER_INSTALL_DIR contains the same path as a mount point with insufficient space but is set to a path that would not install to that mount point.


When DISPLAY environment variable is set to empty string, uninstaller creation is now successful when a Get User Input GUI Panel is added.


Source Paths from environment variable are now detected on Mac OS X. The source path is set automatically under preferences in InstallAnywhere.


The Check File/Folder Attributes rule has been fixed to work as expected if set to check if a file/folder exists and is a folder or if the folder does not exist prior to the installer starting but is created during the installation.


A "null" message is no longer displayed while uninstalling an Installed component through project uninstallation.


An option has been added to change the Java virtual machine heap size at run time.


All the strings of the "Install_Log" are now localized at run-time to the locale which user selects from the Splash Screen.


User documentation now explains how to set the initial and maximum JVM heap size for the InstallAnywhere Advanced Designer and build commands.


Documentation now states that only InstallAnywhere Premier Edition supports the use of build time variables and custom source path variables.


Documentation now states that when running an installer (with a UNIX-based platform build target) on a UNIX-based platform, a valid copy of the system unzip command is required for the installer to launch.


System Requirements

Requirements for Systems That Are Running InstallAnywhere (Authoring Environment)


256 MB; 512 MB preferred

Hard Disk Free Space

500 MB


High color (16-bit color depth)


Minimum 1200 x 800

Operating System

InstallAnywhere runs on the latest versions of these operating systems, fully updated with the most recent patches and service packs.

Operating System Supported Versions
  • Windows 10 (x86 and x64)
  • Windows 8.1 (x86 and x64)
  • Windows Server 2012 R2 (x64)
  • Windows 8 (x86 and x64)
  • Windows Server 2012 (x64)
  • Windows 7 (x86 and x64)
  • Windows Server 2008 R2 (x64)
  • Windows Vista
  • Windows Server 2008 (x86 and x64)
  • OS X El Capitan (10.11) with Oracle Java 7 or 8
  • OS X Yosemite (10.11) with Oracle Java 7 or 8
  • OS X Mavericks (10.9.2) with Oracle Java 7 or 8
  • OS X Mountain Lion (10.8) with Oracle Java 7 or 8
  • OS X Lion (10.7.3) with Oracle Java 7
  • Red Hat Enterprise Linux 7/7.1
  • Red Hat Enterprise Linux 6.x (desktop and server editions; x86 and x64)
  • Red Hat Enterprise Linux 5.x (x86 and x64)
  • OpenSUSE Linux 11.x, 12.x and 13.1 (x86 and x64)
  • SUSE Linux Enterprise 11 (SP2 and SP3; x64) and 12 (x64)
  • Linux PPC 64-bit (build time only) only with Java 6
  • Ubuntu 15.04 (x64)
  • Ubuntu 14.x (x64)
  • Ubuntu 13.x (desktop and server editions; x86 and x64)
  • Ubuntu 10.x, 11.x, and 12.x (x86 and x64)
  • Fedora 18, 19 and 20 (desktop editions; x64)
Note: When you install InstallAnywhere on a Linux system, the installation attempts to create a symbolic link to the default Linux loader (/lib/ld-linux.so.2) if a link with the same name is not already present. The symbolic link is necessary for the host ID to be displayed on the Host ID dialog, and it is also necessary for successful node-locked licensing. The link is present on systems that are Linux Standard Base (LSB) 3 compliant, but it may not be present on systems that are not LSB compliant. For more information, see Knowledge Base article Q209204.
Solaris Solaris 9, 10, and 11 (SPARC)

Installers can be built from any supported authoring platform for any other supported target platform or language. Localizations for 31 languages are included with Premier Edition. Localizations for 9 languages are included with Professional Edition.

Requirements for Docker Images

Support for building Docker images from InstallAnywhere 2015 when Docker is installed on the platforms below.

Item Description
Docker Version Supported Docker 1.7.1
Platforms Windows
  • Windows 7
  • Ubuntu 14.10
  • Red Hat Enterprise Linux 7.1
  • CentOS 7.1
  • OS X 10.8.x, 10.9.x, and 10.10.3

Requirements for Target Systems (Installer Run-Time Environment)


64 MB


High color (16-bit color depth)


Minimum 640 x 480

Operating System

Installers run on any version of these operating systems, as long as the operating system supports Java 6, 7, or 8 (but Oracle Java 7 or 8 for OS X). InstallAnywhere-generated installers are not supported on beta versions or on early-access releases unless they are explicitly mentioned.

Operating System Supported Versions
  • Windows 10 (x86 and x64)
  • Windows 8.1 (x86 and x64)
  • Windows Server 2012 R2 (x64)
  • Windows 8 (x86 and x64)
  • Windows Server 2012 (x64)
  • Windows 7 (x86 and x64)
  • Windows Server 2008 R2 (x64)
  • Windows Vista (x86 and x64)
  • Windows Server 2008 (x86 and x64)
  • Windows XP (x86, x64, Itanium 2, and AMD-64)
  • Windows Server 2003 (x86, x64, Itanium 2, and AMD-64)
Windows-based target systems must also support the SSE2 instruction set.
  • OS X El Capitan (10.11) with Oracle Java 7 or 8
  • OS X Yosemite (10.10) with Oracle Java 7 or 8
  • OS X Mavericks (10.9.2) with Oracle Java 7 or 8
  • OS X Mountain Lion (10.8) with Oracle Java 7 or 8
  • OS X Lion (10.7.3) with Oracle Java 7
  • Red Hat Enterprise Linux 7/7.1
  • Red Hat Enterprise Linux 6.x (desktop and server editions; x86 and x64)
  • Red Hat Enterprise Linux 5 (x86, x64, Itanium 2, and AMD-64)
  • OpenSUSE Linux 11.x, 12.x and 13.1 (x86 and x64)
  • SUSE Linux Enterprise 11 (SP2 and SP3; x64) and 12 (x64)
  • Red Hat Enterprise Linux 6.x, SUSE 11.x on zSeries
  • Red Hat Enterprise Linux 6.x SUSE 11.x PPC 64-bit (build time only) with Java 6
  • Red Hat Linux 7.1 PPC Little Indian (silent and console mode only)
  • Ubuntu 15.04 (x64)
  • Ubuntu 14.x (x64)
  • Ubuntu 13.x (desktop and server editions; x86 and x64)
  • Ubuntu 9.x, 10.x, 11.x, 12.x (x86 and x64)
  • Fedora 17, 18, 19 and 20 (desktop editions; x64)
  • Solaris 11 (x86 and SPARC)
  • Solaris 9, 10 (x86, SPARC, and AMD-64)
HP-UX HP-UX 11i (Itanium 2 and PA-RISC)
AIX AIX 5.2, 5.3, 6.1, and 7.1 (Power/PowerPC)
  • i5/OS (OS/400) on System i - V5R3 and V5R4 (Enterprise Edition only), IBM i 6.1, and IBM i 7.1
  • z/OS
  • FreeBSD
  • Other Linux and UNIX operating systems (POSIX-compliant shell required)

Supported Java Virtual Machines

InstallAnywhere supports the following Java virtual machines:

Manufacturer Supported JVM Versions
Sun 1.6.x, 1.7.x
IBM 1.6.x, 1.7.x, 1.8.x
HP 1.6.x, 1.7.x
Oracle 1.7.x, 1.8.x

The InstallAnywhere installer installs JRE 1.7.0_60 VM packs. Any Java virtual machine can be bundled with an installer ensuring that the target system meets the minimum requirements for both the installers and your applications. To download additional JRE VM packs, visit http://www.flexerasoftware.com/installanywhere/utilities and click the VM Packs tab.

InstallAnywhere-generated installers are not supported on beta versions or on early-access releases of Java.

Requirements for Virtual Appliances

System Requirements for Building and Auto-Deploying Virtual Appliances

The following table lists the system requirements for building and auto-deploying virtual appliances from within InstallAnywhere.

Hypervisor Requirements
VMware vSphere 5/vCenter
  • Credentials to a VMware vSphere 5 Server
  • If your VMware vSphere 5 Server is managed by a VMware vCenter 5 Server, the credentials to the VMware vCenter Server are also required.
  • Host machine credentials (credentials to a physical/virtual machine that closely resembles the virtual appliance operating system)
Amazon EC2
  • Amazon EC2 account information (account number, access key, secret key, X.509 certificate, and private key associated with your Amazon EC2 account)
  • Host machine credentials (credentials to a physical/virtual machine that closely resembles the virtual appliance operating system)

Supported Hypervisors and Platforms for Virtual Appliances

InstallAnywhere supports the creation of virtual appliances that run on VMware vSphere 5 and Amazon EC2 hypervisors. A VMware vSphere 5 virtual appliance is deployable on a licensed VMware vSphere 5 Server (standalone) or a licensed VMware vSphere 5 Server that is managed by a licensed VMware vCenter 5 Server.

The following table identifies the operating systems that are supported on the supported hypervisors.

Supported Hypervisor Supported Operating Systems
VMware vSphere 5/vCenter
  • CentOS 7, 6.2 and 6.3 (x86 and x64)
  • OpenSUSE 12.2 (x86 and x64) and SUSE Linux Enterprise Server 11 SP2—Requires the use of an existing SUSE VM or snapshot (No support for using a SUSE VM virtual appliance template)
  • Red Hat Enterprise Linux 6.4 (x86 and x64)—Requires the use of a Red Hat Network–registered RHEL VM virtual appliance template
  • Red Hat Enterprise Linux 6.3 (x64)—Requires the use of a Red Hat Network–registered RHEL VM virtual appliance template
  • Ubuntu 13.04 (x86 and x64)
  • Ubuntu 12.10 (x86 and x64)
  • Ubuntu 12.04 (x86 and x64)
  • Ubuntu 11.10 (x86 and x64)
Amazon EC2
  • Ubuntu 11.10 (x32)
  • Ubuntu 12.04 (x32)

Creating virtual appliances requires that InstallAnywhere be launched with JRE 1.7 or 1.8.


Known Issues

For a list of known issues, see the InstallAnywhere 2015 Known Issues knowledge base article.


Legal Information

Copyright Notice

Copyright © 2015 Flexera Software LLC. All Rights Reserved.

This publication contains proprietary and confidential information and creative works owned by Flexera Software LLC and its licensors, if any. Any use, copying, publication, distribution, display, modification, or transmission of such publication in whole or in part in any form or by any means without the prior express written permission of Flexera Software LLC is strictly prohibited. Except where expressly provided by Flexera Software LLC in writing, possession of this publication shall not be construed to confer any license or rights under any Flexera Software LLC intellectual property rights, whether by estoppel, implication, or otherwise.

All copies of the technology and related information, if allowed by Flexera Software LLC, must display this notice of copyright and ownership in full.

Intellectual Property

For a list of trademarks and patents that are owned by Flexera Software, see http://www.flexerasoftware.com/intellectual-property. All other brand and product names mentioned in Flexera Software products, product documentation, and marketing materials are the trademarks and registered trademarks of their respective owners.

Restricted Rights Legend

The Software is commercial computer software. If the user or licensee of the Software is an agency, department, or other entity of the United States Government, the use, duplication, reproduction, release, modification, disclosure, or transfer of the Software, or any related documentation of any kind, including technical data and manuals, is restricted by a license agreement or by the terms of this Agreement in accordance with Federal Acquisition Regulation 12.212 for civilian purposes and Defense Federal Acquisition Regulation Supplement 227.7202 for military purposes. The Software was developed fully at private expense. All other use is prohibited.