InstallAnywhere 2017
Release Notes
originally released November 2016; updated to include SP1, released May, 2017
Introduction
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.
InstallAnywhere 2017 offers expanded platform support. It also resolves a number of issues.
Changes in SP1
Refer to the following sections for new features and changes in InstallAnywhere 2017 SP1:
• | Integration with FlexNet Code Aware |
• | Enhancement to Existing GUI Automation Fixture |
• | Resolved Issues in SP1 |
Integration with FlexNet Code Aware
Note • For complete information about FlexNet Code Aware, refer to the FlexNet Code Aware user documentation.
InstallAnywhere now includes integration with FlexNet Code Aware, an automated open source risk assessment and package discovery solution that enables you to quickly scan your products for security and intellectual property (IP) compliance risk.
The current release of FlexNet Code Aware supports analysis of the following files:
• | Java Packages |
• | Node Packages |
• | Nuget Packages |
• | RPM Packages |
• | Ruby Packages |
• | EXE & DLL Files |
Security vulnerabilities are looked up against the National Vulnerability Database (NVD).
Running FlexNet Code Aware
FlexNet Code requires a separate license from InstallAnywhere. There is also trial/evaluation version. For more information, refer to the FlexNet Code Aware product page of the Flexera Software website.
To run FlexNet Code Aware from within InstallAnywhere, click Run FlexNet Code Aware Analysis from the InstallAnywhere Tools menu. This menu option is disabled out if you are not currently in an open InstallAnywhere project.
When FlexNet Code Aware completes the scan of your project, a summary displays showing the number of files scanned, and the number of open-source packages and vulnerabilities found. A View report button is provided if you have a fully licensed version of FlexNet Code Aware. For more information about the details provided in this report, refer to Reading the FlexNet Code Aware Report.
Reading the FlexNet Code Aware Report
Note • The FlexNet Code Aware Report is not available in trial/evaluation mode. A fully licensed version of FlexNet Code Aware is required.
To view the FlexNet Code Aware Report, click View report on the summary dialog that appears after FlexNet Code Aware has scanned your project.
The FlexNet Code Aware report consists of several sections:
• | The initial Summary View presents the user with a Scan Summary, Operational Risk assessment, Security Vulnerability Exposure, and License Exposure. |
• | The Scan Summary section provides details regarding the codebase that was scanned, including a breakdown of file types, percent of files analyzed, and number of findings. |
• | The Operational Risk section provides a composite risk rating based on the combination of packages with Intellectual Property (IP) issues and packages with Security Vulnerabilities. |
• | The Security Vulnerability Exposure and License Exposure sections provide a breakdown of the types and categories of identified issues. |
• | The Package Inventory View, available by clicking view full package inventory in the Scan Summary section, provides a complete list of discovered open source and third-party packages with associated licenses, security vulnerabilities, dependencies, and detected copyright statements. |
The Package Inventory View provides filters that you can use to execute targeted queries to refine the list to various package types of interest.
The following figures show the initial Summary View of a sample FlexNet Code Aware Report.
Figure 1-1: FlexNet Code Aware Initial Summary View
The following figures show the Package Inventory View of a sample FlexNet Code Aware Report.
Figure 1-2: FlexNet Code Aware Package Inventory View
Viewing Package Details
Click a vulnerability count listed in the Vulnerabilities column of the Package Inventory report page for each package you want to review:
The Vulnerabilities detail page appears, covering a portion of the Package Inventory report:
Enhancement to Existing GUI Automation Fixture
InstallAnywhere now has improved GUI Automation Fixture by adding new APIs for launching binaries; that is, you can now launch Windows/Linux native installers in addition to the pure Java installer. The new APIs have ability to interact with various UI components and get UI attributes of the components like labels, text fields, checkboxes, radio buttons, combo boxes, list boxes and buttons.
Parameters that the APIs need can be obtained as an optional tool tip by running the installer with a special command line.
install.exe -Diashowtooltip=true
For complete information about each of the APIs, refer to the docs available at IA_HOME/gui-test-auto/javadocs. For a sample GUI Automation class, refer to your InstallAnywhere build directory at IA_HOME/gui-test-auto/example/source/com/installanywhere/ia/automation/gui/samples/basic/BasicProjectAutomation.java.
Supporting platforms: Windows and Linux.
Resolved Issues in SP1
For descriptions of resolved issues in InstallAnywhere 2017 SP1, refer to InstallAnywhere 2017 SP1.
New Features
InstallAnywhere 2017 includes the following new features:
• | New Rules Manager Allows Creation of Complex Rule Expressions at the Project Level |
• | Customizable Advanced Runtime UI Themes |
• | Ability to Install RPMs and DEBs from Install Linux Package Action |
• | Support for the Latest Platforms |
New Rules Manager Allows Creation of Complex Rule Expressions at the Project Level
InstallAnywhere now includes a rule expression manager which allows installer authors to:
• | Create complex rule expressions at the project level |
• | Combine multiple rules and save them to a single rule expression |
• | Reuse a rule or a set of rules across the project |
• | Associate a rule expression to a file extension, including the option to automatically associate the rule expression to a file whenever a file containing that file extension is added to the project |
• | Remove associated rules from custom file extensions |
See the following help topics in the InstallAnywhere Help library for procedures about various functionality that you can do with project level rule expressions:
• | Configuring and Saving a New Rule Expression |
• | Associating a Rule Expression to a File Extension |
• | Loading a Rule Expression |
• | Deleting a Saved Rule Expression |
Customizable Advanced Runtime UI Themes
InstallAnywhere has improved the runtime user experience of the installer by adding customizable advanced runtime UI themes. A theme is a set of runtime UI settings that are used to customize the installer panels and frames. For example, you can specify fonts, font attributes, and even import your own fonts. You can customize the colors of windows and buttons, choose to use frameless windows, display your company’s own logo in the installer steps panels, and many other settings.
For complete information about each of the advanced runtime UI theme settings available and for information about how to customize advanced runtime UI themes, see the “UI Panel Settings Area” topic in the InstallAnywhere Help library.
Ability to Install RPMs and DEBs from Install Linux Package Action
Edition • These features are available in the following editions:
• | InstallAnywhere Premier Edition with Virtualization and Cloud |
• | InstallAnywhere Premier Edition |
In InstallAnywhere 2017, the Install Linux RPM install action has been updated to Install Linux Package and now allows you to install and uninstall Linux RPM Package Manager (.rpm) files, Debian (.deb) packages, or files from a default or a custom repository. The package files can either be bundled with the installer or can be pre-existing on the system.
If you choose to install from a repository, there are two options:
• | Install from Repository—Install from the default distribution repository on the machine you are targeting. |
• | Install from Repository / Custom Repository—Install from a specified location of a custom repository. When you click the Custom Repository check box, the Choose Repository button is enabled, allowing you to search for the custom repository location, choosing either a *.list file for Debian file distributions or *.repo for Linux. |
If the RPM or DEB is relocatable, and the Relocatable check box is selected in the action customizer, the file is installed to its location in the file tree.
Additionally, the RPM or DEB can be set to Ignore Dependencies (similar to the --nodeps option for the command-line RPM tool) and to Force Installation (--force).
You can also choose Do Not Uninstall. For custom repositories, the only check box that is available is to Do Not Uninstall.
The Install Linux Package action allows you to add only one package at a time. If you want to add additional packages, click Add Action again.
For complete information about install actions, refer to the “Install Actions” topic in the InstallAnywhere Help library.
Support for the Latest Platforms
InstallAnywhere now supports the following platforms for running the installer run-time environment, as well as for the InstallAnywhere authoring environment:
• | Windows 10 Anniversary Update (x86 and x64) |
• | Windows 2016 Server (x64) |
• | macOS Sierra (10.12) |
• | Red Hat Enterprise Linux 7.2 (x64) |
• | OpenSUSE Linux 13.2 (x64) |
• | SUSE Linux Enterprise 12 (SP1, x64) |
• | Fedora 24 (desktop editions; x64) |
InstallAnywhere now supports the following platforms for running the installer run-time environment:
• | CentOS 7 (x86, x64) |
• | CentOS 6.8 (x86, x64) |
• | Red Hat Enterprise Linux 7.2 for PowerPC (little endian) |
• | Ubuntu 16.04 LTS (x64) |
Enhancements
This section lists enhancements that were included in InstallAnywhere 2017:
• | New Command-Line Build-Related Argument to Generate Encrypted Variable Value |
• | New Require Root Setting Available Under Project Page in the Platforms View |
• | Modify Text File Action Enhancement |
• | Support for Croatian Local Added |
New Command-Line Build-Related Argument to Generate Encrypted Variable Value
When building using the command line, you can use a new build-related argument to allow you to generate an encrypted hexadecimal value that can be directly copied and pasted into a response file as an encrypted variable value.
build -encrypt <product-code> <text-to-encrypt>
The resulting encrypted hexadecimal value can then be used later. For example, you could update the master response file with an encrypted value generated from a password without needing to first run the entire installation to only generate this value.
This enhancement resolves issue IOJ-1758930.
New Require Root Setting Available Under Project Page in the Platforms View
The following new settings are available in the Unix area of the Project Page under the Platforms view.
Setting |
Description |
Require Root |
Specify whether the installer requires root account permissions. A root account is the user name or account that by default has access to all commands and files on a Linux or other Unix-like operating system. It is also referred to as the root account, root user, or the superuser. If you select Yes in this setting, the Error Message setting under Require Root is enabled. |
Error Message |
Specify an error message to appear if the installer is run with a non-root account. This field is enabled when Yes is selected from the Require Root drop-down list. |
Modify Text File Action Enhancement
The Modify Text File actions have been enhanced to allow you specify both the source file that is being opened and read as well as the destination file that is being saved after it has been modified. To account for this change, the previous File Encoding field has been replaced with the following two fields:
• | Source File Encoding |
• | Destination File Encoding |
In previous versions of InstallAnywhere, there were instances where leaving the File Encoding field blank resulted in a loss of characters when saving the destination file as a result of Java not being able to easily detect what kind of encoding the file was actually using. Therefore, with this enhancement you can now explicitly specify the source file and destination file encoding to ensure no loss of characters are experienced in the process. Now, the encoding that is applied is dependent solely upon the destination file encoding provided irrespective of the source file encoding. The following table provides example of the file encoding that is applied in cases where the destination file coding is left blank, is invalid, or is unsupported.
Source File Encoding |
Destination File Encoding |
Encoding Applied |
empty |
empty |
UTF-8 |
invalid (eg. Hello) |
empty |
UTF-8 |
unsupported (cp1047) |
empty |
UTF-8 |
empty |
invalid |
Platform default |
empty |
unsupported |
Platform default |
This enhancements applies to the following actions:
• | Modify Text File - In Archive Action |
• | Modify Text File - Multiple Files Action |
• | Modify Text File - Single File Action |
Support for Croatian Local Added
Edition • The Premier edition of InstallAnywhere includes default run-time strings in 31 supported languages. The Professional edition includes default run-time strings in 9 languages.
InstallAnywhere has added support the Croatian locale. You can now specify Croatian as a locale you want your installation to support. For information about specifying a locale to your installer, refer to the “Generating Multilanguage Installers” topic in the InstallAnywhere help library.
This resolves issue IOJ-1753909.
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.
Project Upgrade Alerts
Rules View Changed to Installer Rules View
The Rules view on the Project page has been renamed to the Installer Rules view. The Installer Rules view is used to add logic that executes prior to items in the pre-install sequence.
Installer UI Page Look & Feel Settings View Changes
With the addition Customizable Advanced Runtime UI Themes in InstallAnywhere 2017, the following Look & Feel Settings have been moved to a new area accessible by clicking the Custom UI Designer button in the UI Panel Settings area in the Look & Feel view of the Installer UI page:
• | Installer Background Image settings (that were previously available under General UI Settings) |
• | Installer Frame settings (that were previously available under General UI Settings) |
• | Installer Steps settings |
• | Install progress Panel settings |
Install Linux RPM Install Action Changed to Install Linux Package
The Install Linux RPM install action has been changed to be named Install Linux Package. as described in Ability to Install RPMs and DEBs from Install Linux Package Action.
File Encoding Setting on Modify Text File Actions Changed
As described in Modify Text File Action Enhancement, the File Encoding setting that appears when you add a Modify Text File action has now been replaced by two actions:
• | Source File Encoding |
• | Destination File Encoding |
Resolved Issues
This section lists the customer issues that were resolved in the following versions of InstallAnywhere:
• | InstallAnywhere 2017 SP1 |
• | InstallAnywhere 2017 |
InstallAnywhere 2017 SP1
The following issues have been resolved in InstallAnywhere 2017 SP1:This section lists the customer issues that were resolved in InstallAnywhere 2017.
Issue Number |
Issue Summary |
IOJ-1759620 |
A Preview option has been added to the Custom Code panel. |
IOJ-1770331 |
Installer with NonFatalError running under Simplified Chinese locale creates installation log entires without formatting errors. Previously, this scenario resulted in extra space before the comma or missing commas in the log entries. |
IOJ-1779193 |
The required disk space for a Copy Folder action is now being calculated correctly by the installer on a SUSE Linux operating system. |
IOJ-1802112 |
Names are now provided for each GUI element for a generated installer which can be used to automate the installation experience through an enhanced GUI Automation Fixture. |
IOJ-1806309 |
The Test Automation API now can fetch values of GUI elements allowing for validation of the data that is being displayed on the GUI panels. Users can know the identifiers of the GUI elements in terms of a tooltip by running the installer with a special command line: install.exe -Diashowtooltip=true |
IOJ-1807247 |
When adding locales to an installer, all languages now appear correctly on the Language Selection dialog when running with the appropriate system locale. Previously, some of the languages were failing to appear. |
IOJ-1812326 |
When running an installer in console mode and selecting to customize the Install Set, the correct chosen Install Set is displayed in the console. Previously, if Customize was chosen when selecting to customize Features to be installed, the Custom Install Set was not being displayed. |
IOJ-1736920 |
The default time for a billboard to be displayed has been changed to 3 seconds from 0.5 seconds. Billboards are the images that appear in the large right pane of the installer while files are being installed. |
IOJ-1799239 |
When building a project after removing the InstallAnywhere Uninstall component but keeping the Create Uninstaller Action, exceptions are no longer being added in the debug log and the project is able to build successfully upon reopening the project. Previously, after removing the InstallAnywhere Uninstall Component, a java.lang.ArrayIndexOutOfBoundsException was appearing when building the project after closing then reopening the InstallAnywhere IDE. |
IOJ-1804351 |
When using Project Automation to save and upgrade a project created with a previous InstallAnywhere version, the Project Automation Java class successfully loads, saves, and upgrades the project without any Java errors or exceptions. Previously, this scenario was resulting in a the Project Automation Java class generating a Java stack trace resulting in control to the command prompt not being returned. |
IOJ-1804938 |
If you choose to have a border on the Inner Installer Frame, a border will be included around the features in the Install Set section and a border will be included around the Description section on the Choose Product Features dialog. |
IOJ-1805145 |
When performing a silent installation in Linux machine, no custom files are being left behind. Previously, a file with the name ‘custom’ was being created in the installer launch directory when performing a silent installation in Linux machine. |
IOJ-1806479 |
An issue has been resolved with regards to the default selected features differing between the GUI mode and Console mode on the Choose Features Console Panel. The GUI Mode behavior was not matching the Console Mode behavior but now match. |
IOJ-1779755 |
An invalid unzip command found message on Linux now only displays in debug mode. The installer no longer displays this console message when running the installer when debug output is not captured. |
IOJ-1801493 |
Lines with echo $DISTRO_NAME in the laxunix.sh script now use double quotes around "$DISTRO_NAME" to avoid awk input limit issues. |
IOJ-1807471 |
Scaling issues in the Prompt field on he Get User Input Panels have been resolved. Previously, the control which displays the "Prompt" field on the Get User Input Panels was not scaled correctly when the display was scaled beyond 100%, which resulted in the control to be condensed too short and a vertical scrollbar was being added in order to display all of the text. |
IOJ-1809562 |
InstallAnywhere variables are now being resolved correctly in the Manage Instances Dialog Box. Previously, when modifying a custom_xx locale file (e.g., custom_en) to make text changes to the Manage Instances Dialog Box, InstallAnywhere variables were failing to be resolved. This was also happening when modifying Installer.instanceManagement.console in console mode. |
IOJ-1810071 |
CPU usage inconsistencies between similar installers have been resolved. Previously, setting the Inner Panel background color to anything other than no color was resulting in increased CPU usage with installers built using InstallAnywhere 2017. |
IOJ-1738254 |
The LAX_VM parameter can be used to specify an alternate VM to use so that if bundled VM extraction fails, installer cannot be run with LAX_VM. Previously, a failure to extract the VM was causing the LAX_VM to be ignored on *nix. |
IOJ-1735191 |
The Choose Java VM Panel now contains a default selection, allowing the installer to be correctly verify whether the target java.exe is valid. Previously, the Choose Java VM Panel did not have default selection, causing the installer to create a LaunchAnywhere launcher that did not target a valid JVM on Windows. |
IOJ-1812244 |
Installers built with InstallAnywhere 2017 no longer incorrectly return successful exit code of 0 if an installer fails to launch on Linux when no tar command is found. |
IOA-000037887 |
To account for instances where you may have constraints regarding the Installer Frame Size, a vertical scroll bar can be added if the number of installer steps exceed what can be aligned in the Installer Frame. |
IOJ-1782049 |
An issue has been resolved where the image set for Installer Steps was not being displayed properly in run time panels on High DPI displays. |
IOJ-1805000 |
The Installer Steps Frame Height is no longer static and changes dynamically with regards to the image size used in the frame. |
IOJ-1748704 |
The “Determining Whether an Installation Was Successful” help topic has been updated with descriptions of error code types (SUCCESS, WARNING, NONFATAL_ERROR, and FATAL_ERROR). |
IOJ-1803443 |
The Language Selection Dialog no longer defaults to English instead of non-English locale that the operating system is running under. |
IOJ-1781151 |
The Locales tab now shows the number of locales that have been selected in the Build > Locales tab. |
InstallAnywhere 2017
The following issues have been resolved in InstallAnywhere 2017:.
Issue Number |
Issue Summary |
||||||
IOJ-1772897 |
When you change the Installer Title Image to be a custom icon, InstallAnywhere displays it properly. Previously, the default iaIcon.png was being displayed on Linux platforms. |
||||||
IOJ-1770679 |
The "Configuring Build-Time Variables Using a Property File" topic in the InstallAnywhere Help library has been updated now includes clarifications about setting Build-Time Variables with the .properties file. |
||||||
IOJ-1770331 |
An installer that generates a NonFatalError running under the Simplified Chinese locale creates installation log entries properly without extra spaces or missing commas. |
||||||
IOA-000057847, |
InstallAnywhere has been updated so that the JAWS (Job Access With Speech) computer screen reader program for Microsoft Windows is now able to correctly read the following sections of the IDE:
|
||||||
IOJ-1763648 |
A global registry file no longer gets created when a merge module is included with an installer and the Update the Product Registry setting is set to No for both parent and merge module projects. Previously, In InstallAnywhere 2013 and later, a .com.zerog.registry.xml file was being created under C:\Users\<USERNAME> with entries created for the parent project. |
||||||
IOJ-1761719 |
A note has been added to the "Adding JRE VM Packs for Your Installers to Your Development and Build Machines" Help topic to clarify where to place JRE VM Pack (.vm) files for use by the InstallAnywhere IDE. The default location for JRE VM packs is: <InstallAnywhere>\resource\installer_vms\ Note • <InstallAnywhere> does not refer to the project directory containing the InstallAnywhere project (.iap_xml) file. This refers to the location where InstallAnywhere was installed on the build machine. |
||||||
IOJ-1761500 |
Applying InstallAnywhere security hotfix IOJ-1756928 to InstallAnywhere 2012 SP1 correctly fixes a vulnerability issue previously experiences with installers run on Windows Server 2008 R2. |
||||||
IOJ-1758386 |
The Disk Space Information on the Pre-Install summary is now right-aligned, making it easier to compare values. |
||||||
IOJ-1756863 |
When the Set System Environment Variable Install action value is configured to set an environment variable to a value with a space and configured to prepend or append the value, the /etc/profile entry now includes the correct number of quotation around the environment variable value that was set. Previously, in InstallAnywhere 2014 SP1 and later this scenario led to extra quotation marks being added around the environment variable value that was set. |
||||||
IOJ-1756590 |
In the InstallAnywhere Help library, all references to the predefined source path variables $IA_PROJECT$ have been updated to $IA_PROJECT_DIR$. |
||||||
IOJ-1756379 |
The radio button text on InstallAnywhere’s License Agreement panel now displays correctly when displayed on Windows machines that are set to high contrast mode. Previously, there was an issue with radio button text not displaying correctly when the License Agreement was displayed in high contrast mode on Windows machines. |
||||||
IOJ-1755613 |
When a file association is set up for an InstallAnywhere launcher, double-clicking a file that uses Oracle JVM 7 or later on Mac OS now successfully launches the associated application and loads the file. Previously, this scenario was only working on Mac OS with InstallAnywhere launchers created to run on Apple JRE 6 or earlier. |
||||||
IOJ-1755457 |
The Choose Icons button (or Choose Icons and Fonts button in InstallAnywhere 2017) button functions correctly when the icon referenced by the label of the upcoming step no longer exists. In this scenario, the Choose Label Icons dialog correctly appears. |
||||||
IOJ-1756928 |
The Best Practices to Avoid Windows Setup Launcher Executable Issues article has been added to the Flexera Software Knowledge Base. The associated hot fixes available for previous versions are included in this release. |
||||||
IOJ-1754949 |
The following error message displays in full on all versions of Linux: One or more newer versions of the product are already installed. An upgrade is not applicable. |
||||||
IOJ-1756589 |
Both the Premier and Professional editions of InstallAnywhere include support for the predefined source path variables ($IA_HOME$, $IA_PROJECT$, $USER_HOME$). However, only the Premier edition of InstallAnywhere includes support for custom source path variables. The documentation has been updated to correctly reflect this. |
||||||
IOJ-1754939 |
Installers built with IBM JVM packs run successfully on Solaris SPARC machines. |
||||||
IOJ-1754926 |
The Digital Signing field is disabled on non-Windows operating systems. |
||||||
IOJ-1754925 |
In the Platforms View topic in the InstallAnywhere Help library, a note has been added to the Digital Signing description to call out that digitally signing Windows Installers require the project to be built on Windows. |
||||||
IOJ-1753835 |
After selecting a new search location on the Choose Java VM panel the Choose Java VM panel shows that it is actively searching in the specified search location and populates the VM list if it finds valid JVMs. |
||||||
IOJ-1753384 |
When installing InstallAnywhere 2015 on Windows 10, build-as-invoker.lax is properly installed. |
||||||
IOJ-1753371 |
On Linux machines, when the Set System Environment Variable action is used in the installer, the /etc/profile file is identical to the file before installing and uninstalling and there are no trailing empty lines. Previously, a blank line was being added to the /etc/profile file each time after install then uninstall. |
||||||
IOJ-1753244 |
Disk Space Check reports the correct disk space available for the “/” directory in HP-UX. |
||||||
IOJ-1752536 |
The installer launches successfully with Windows Server 2016 Technical Preview 4 when installer is run with a higher Java version than Java 8 Update 31. |
||||||
IOJ-1751623 |
An upgrade installer correctly launches the base version's uninstaller, and then installs. Previously upgrade installer will launch any executable alphabetically less than and in the same directory as the uninstaller launcher. |
||||||
IOJ-1751514 |
Red Hat Enterprise Linux 7.0 on PPC LE is supported as a target platform. |
||||||
IOJ-1751285 |
The Titles, Labels and InstallAnywhere Logo Color setting modifies the text color of the percent text shown during the Install Progress Panel. |
||||||
IOJ-1745660 |
When Uninstall All Logs is set to No, the installation directory, uninstaller directory, Logs directory, and the install and uninstall logs are not removed by the uninstaller. |
||||||
IOJ-1743223 |
When a French Canada external resource property file is not present, the string from the external resource bundle resolves from the French resource property file when an installation is launched as French Canadian. |
||||||
IOJ-1742759 |
When installing on an NFS mount on Linux and you use the Installer Move Folder action, the installer completes successfully without errors. The Move Folder Action successfully moves the folder as specified. |
||||||
IOJ-1741182 |
InstallAnywhere uses a pop-up text box for secure text input panels when authentication is required on macOS or OS X. The Get User Input - Advanced panel allows a text field to have the input echo character display as shadowed in order to hide the string value being entered by the user. When using a shadowed text field with an authenticated installer, the text field on the pop-up dialog is not readable and is correctly shadowed, as specified. |
||||||
IOJ-1740763 |
The $CHOSEN_INSTALL_SET$ InstallAnywhere variable resolves to Typical (not Custom, as was previously occurring). The Pre-Install Summary Console Panel displays correctly as Typical, not Custom, as the chosen Install Set. |
||||||
IOJ-1740400 |
It is now possible to set Java heap size for a launcher from the Create LaunchAnywhere for Java Application action. The installed launcher correctly uses the Java heap size specified. |
||||||
IOJ-1740304 |
If a value that is being resolved to includes a dot (.), anything after the dot (.) appears on the same line and only wrap if the entire value cannot fit onto the same line. |
||||||
IOJ-1740159 |
When doing a Modify File Action to create a new file, a new line is no longer being added to the end of the file. |
||||||
IOJ-1739959 |
A formatting issue that was appearing on browsers others than Chrome has been resolved with the InstallAnywhere 2015 Help library. |
||||||
IOJ-1739850 |
You can now customize the font style and font size for the locale selection on the locale selection screen. |
||||||
IOJ-1739848 |
There is a setting to change the font size, style, front color, and font size for all the install panels. |
||||||
IOJ-1739437 |
Radio button selections are retained with the selection specified. |
||||||
IOJ-1739427 |
The LaunchAnywhere launcher successfully launches a target application using Java 8 Update 60 on Windows. |
||||||
IOJ-1739055 |
The Modify Text File action correctly applies the specified file encoding. |
||||||
IOJ-1738844 |
In the InstallAnywhere Help library, buildasinvoker.exe has been updated to build-as-invoker.exe. |
||||||
IOJ-1739845, |
Options have been added that let you set runtime UI settings that are used to customize the installer panels and frames. For more information, refer to Customizable Advanced Runtime UI Themes. |
||||||
IOJ-1738351 |
The Get User Input Simple Panel correctly displays a selected option when the option is selected from a drop-down list. |
||||||
IOJ-1738254 |
LAX_VM can be used to specify an alternate VM to use. If a bundled VM extraction fails, the installer can run with LAX_VM. The VM installer launches properly on *nix platforms. |
||||||
IOJ-1738250 |
The Uninstall Complete Panel displays an Unable to uninstall message when applicable. The standard uninstallation log reports a similar message. |
||||||
IOJ-1738026 |
JVM Spec files for Java 8 are present on default out-of-the-box InstallAnywhere installations. |
||||||
IOJ-1736626 |
You can now set the display time on a billboard using project automation code using a global setting found in the Project class of ProjectAutomation. |
||||||
IOJ-1736538 |
If a NonfatalInstallException is thrown from a Custom Code action scheduled to run in the Pre-Uninstall phase with the “Show Indeterminate Dialog” enabled, the uninstaller execution continues without hanging. |
||||||
IOJ-1735705 |
A space now appears between the "Expanding Archive (type)" and the name of the archive in the progress status message in the install panel. |
||||||
IOJ-1735309 |
The default Installanywhere icon is properly displayed on the installer title bar on non-Windows machines. |
||||||
IOJ-1735191 |
The Choose Java VM Panel contains a default selection for a JVM. The installer verifies whether the target java.exe is valid. |
||||||
IOJ-1735026 |
When creating a code-signed installer that requires authentication, the Get User Input - Advanced panel with a directory selection uses a pop-up screen to allow input to the installer panel. The pop-up screen's input field is now extended so that text stays on a single line with no wrapping when displayed on Secure text input panels. |
||||||
IOJ-1733906 |
The icon setting under Maintenance Mode Runtime Panel Label Settings area in the Look & Feel Settings view has been updated so that it can accept a source path to refer to the image file instead of using an absolute path. |
||||||
IOJ-1732296 |
If an NFS drive is mounted on AIX, the uninstaller completes successfully without any errors. |
||||||
IOJ-1732007 |
On Windows, a Project Load Warning message is no longer be displayed when a temporary location (e.g., C:\Temp) does not exist. Instead a message is now displayed in the debug console letting you know that the "System cannot find the path". |
||||||
IOJ-1731435 |
The “Remove if value has not changed option” uninstall option has been updated so that the install or uninstall no longer removes a registry key if its value has changed. |
||||||
IOJ-1731240 |
Including quotations in a Windows Environment Variable for a Source Path no longer breaks the Source Path. Quotations are now parsed out before the value of the environment variable is considered as a source path. |
||||||
IOJ-1727646 |
When an Expand Archive (TAR) action is specified with the Existing Archive option, the Delete File action is able to delete the TAR file after the Expand Archive (TAR) is completed. |
||||||
IOJ-1727428 |
When an Execute Target File action is used to launch a LaunchAnywhere application on OS X, the initiated application name is shown on the dock when the application is launched. |
||||||
IOJ-1724815 |
The Create Uninstaller action works on OS X when the Product Name and Installer Title are different and the Uninstaller name includes a variable. |
||||||
IOJ-1724734 |
If a Copy File Action is placed in Post Install or Pre Uninstall phase, the install completes successfully and no error is reported in the log. Previously, the installer was reporting errors even though the file was being copied correctly. |
||||||
IOJ-1721370 |
If a JVM Spec file is created that does not reference valid JVMs under PATH_HINT in the JVM Spec file, the installer will find a JVM based on the JVM Spec file and launch successfully. |
||||||
IOJ-1700753 |
On OS X 10.10, authenticated installer no longer launches a second time after clicking Done from the installation. |
||||||
IOJ-1700076 |
Uninstallers that are created using InstallAnywhere 2014 contain the newest and most accurate properties. |
||||||
IOJ-1666034 |
When modifying the Installer Title Image, the icon that shows up on the top left of the panel also changes to the modified image for the Choose Language Panel. The selected Title Image is reflected correctly for every panel of the install. |
||||||
IOJ-1662904 |
You can successfully build a project consisting of System i(i5/OS) actions. Previously, unexpected behavior was occurring on Linux machines. |
||||||
IOA-000124792 |
Functionality has been add to Import Dynamic Merge Module (Sequence > Merge Module) and Install Merge Module actions to configure whether a JVM is installed for a Dynamic Merge Module if the parent installer is configured to have the JVM installed. |
||||||
IOA-000124207 |
Support has been added to allow you to add a custom icon for the uninstaller title image and taskbar icon when the uninstaller is run. |
||||||
IOA-000084658 |
When you choose to install Bundled JVM, the installation now reports no errors or warnings when it has successfully completed, including instances when not installing LaunchAnywhere. |
||||||
IOA-000082032 |
Translation of strings in install logs for the Russian locale have been corrected. |
||||||
IOA-000081028 |
When the DPI size of the text is increased on the System, the installer is rendered with higher definition, ensuring optimal readability on higher resolution displays. |
||||||
IOA-000080805 |
InstallAnywhere Installers no longer display a negative value for Required Disk Space. |
||||||
IOA-000080669 |
macOS and Mac OS X installers can now run in silent mode when launching from terminal. The -i silent command line argument is supported. |
||||||
IOA-000074162 |
On MAC OS, Oracle JRE 7 is properly detected by an installer created using InstallAnywhere 2011 SP4. The installer executes successfully using Oracle JRE 7. |
||||||
IOA-000073384 |
The Expand Archive (TAR) action waits for the TAR command to complete. Once the Post-Install Summary Panel displays, then all of the files have been extracted from the TAR file and no new files are created in $USER_INSTALL_DIR$. |
||||||
IOA-000074698 |
The Uninstall Task Categories (Files, LaunchAnywheres, etc.) are localized and displayed in non-English text, as applicable. |
||||||
IOA-000074929 |
In console mode, if you try to go back while the first console is being displayed, the message that is written is now localized based on the locale in which the installer is being run. |
||||||
IOA-000073867 |
When an installer does not create an uninstaller and a Modify Text File Action is included in the post-Install sequence, the installer exits without error and sets an exit code of 0, indicating that it was successful. |
||||||
IOA-000034607 |
With the Modify Text File actions, when the “Substitute Install Anywhere Variables in file" option is checked, InstallAnywhere correctly substitutes variables and no longer removes references to UNIX variables in the file. If a text file contains a known variable whose value is blank, then it will be replaced with a blank in the text file. |
||||||
IOA-000069526 |
When copying and pasting a rule, the ID of the new rule is incremented so that the new rule ID is unique. |
||||||
IOA-000026826 |
An issue where InstallAnywhere was using cached shortcut icons has been resolved that allows InstallAnywhere to correctly update shortcut icons on subsequent installs. |
||||||
IOA-000054050 |
When "Suspend installation until process completes" and "Show indeterminate dialog" actions are both are selected under properties, a "Please wait", <executing> message is displayed in console mode. |
||||||
IOA-000063834 |
If a newer version of a product is installed to the same location that an older version is already installed, the version displayed in Add/Remove Programs is displayed with an incremental value, such as 1.1.0.0. |
||||||
IOA-000060260 |
Strings written to the console (such as Preparing to install...,Extracting the installation resources from the installer archive...,Configuring the installer for this system's environment...,Launching installer..., etc.) are now localized. |
||||||
IOA-000057361 |
InstallAnywhere allows you to set the icon in the top left corner of the install panels. |
||||||
IOA-000057770 |
The Size field in Add/Remove Programs correctly shows the size for the product installed by an InstallAnywhere installer on Windows 7 platform. |
||||||
IOA-000055321 |
Using the Modify Text File action no longer adds a blank line at the end of the file. |
||||||
IOA-000055076 |
Corrected an issue where there's conflicting message displayed in the title and panel area when 'Not Enough Disk Space' is encountered. |
||||||
IOA-000054235 |
In the Choose Java Virtual Machine panel, the default selection for GUI mode has been changed to “Use the Java VM installed with this application” in GUI mode. |
||||||
IOA-000054227 |
In console mode, while using input method as single choice, the prompt displays properly and no longer contains an additional colon. |
||||||
IOC-000068013 |
Additional timestamps have been added to actions in the installation log. |
System Requirements
The following are the system requirements for InstallAnywhere 2017:
• | Requirements for Systems That Are Running InstallAnywhere (Authoring Environment) |
• | Requirements for Docker Images |
• | Requirements for Target Systems (Installer Run-Time Environment) |
• | Supported Java Virtual Machines |
• | Requirements for Virtual Appliances |
• | Supported Hypervisors and Platforms for Virtual Appliances |
Requirements for Systems That Are Running InstallAnywhere (Authoring Environment)
RAM
256 MB; 512 MB preferred
Hard Disk Free Space
500 MB
Color
High color (16-bit color depth)
Resolution
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 |
|
|||||||||||||||||||||||||||||||||||||||
Apple |
|
|||||||||||||||||||||||||||||||||||||||
Linux |
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 2017 when Docker is installed on the platforms below.
Item |
Description |
|||||||||
Docker Version Supported |
Docker 1.7.1 |
|||||||||
Platforms |
Windows |
|
||||||||
Linux |
|
|||||||||
Apple |
|
Requirements for Target Systems (Installer Run-Time Environment)
RAM
64 MB
Color
High color (16-bit color depth)
Resolution
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 |
Windows-based target systems must also support the SSE2 instruction set. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Apple |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Linux |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Solaris |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||
HP-UX |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||
AIX |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||
IBM |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Other |
|
Supported Java Virtual Machines
InstallAnywhere supports the following Java virtual machines:
Manufacturer |
Supported 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
The following are requirements for virtual appliances:
• | System Requirements for Building and Auto-Deploying Virtual Appliances |
• | Supported Hypervisors and Platforms 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 |
|
|||||||||
Amazon EC2 |
|
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 |
|
||||||||||||||||||||||||
Amazon EC2 |
|
Known Issues
For a list of known issues, see the InstallAnywhere 2017 Known Issues knowledge base article.
Legal Information
Copyright Notice
Copyright © 2017 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.