Creating InstallAnywhere Installations for Hybrid (32-Bit & 64-Bit) Windows Applications
1 like2,295 views
InstallAnywhere allows you to create a single installation for hybrid applications with both 32-bit and 64-bit components. This is done by installing files to both the 32-bit and 64-bit locations on Windows systems using magic folders. It also lets you bundle both a 32-bit and 64-bit virtual machine with the installation. Rules can check the system architecture and actions, panels, and files can be conditioned based on whether it is 32-bit or 64-bit.
Creating InstallAnywhere Installations for Hybrid (32-Bit & 64-Bit) Windows Applications
- 1. Creating InstallAnywhere Installations W H I T E PA P E R for Hybrid (32-Bit & 64-Bit) Windows Applications
- 2. Creating InstallAnywhere Installations for Hybrid (32-Bit & 64-Bit) Windows Applications Introduction components. It is thus possible to create a single installation This document describes how to create InstallAnywhere™ for all the Windows systems and variations that your installations for hybrid applications, which include both application supports. 32-bit and 64-bit native Windows code. These applications typically require installing files to both 32-bit and 64-bit Installing Files to Both 64-Bit and 32-Bit Locations specific locations on the target system. In addition, this To install files to 32-bit or 64-bit specific locations on may require you to install both a 32-bit and 64-bit virtual a Windows 64-bit system, you’ll need use the new 32- machine within a single installation. InstallAnywhere allows bit and 64-bit specific Magic Folders available in the you to accomplish both of these tasks with a few simple InstallAnywhere customizer. Magic folders and associated steps, described below. InstallAnywhere variables have been created for the following locations. Use Cases 64-bit Windows allows for applications that are a Magic Folder InstallAnywhere Variable mix of 32-bit and 64-bit native code. This scenario is fairly common, as application developers often port Programs Folder (32-bit) $PROGRAMS_DIR_32$ processor-intensive code to 64-bit before porting other Programs Folder (64-bit) $PROGRAMS_DIR_64$ code. Application elements that require only “keyboard System Folder (32-bit) $SYSTEM_32$ performance” may remain as 32-bit code. The result is a hybrid application with components that need to be System Folder (64-bit) $SYSTEM_64$ installed to both the 32-bit and 64-bit areas of the file system and registry. Programs Folders: Example An enterprise database server: • 32-bit tools – Management tools – Analysis tools • 64-bit tools – The core database server – Service Manager – Command line utilities Installing Hybrid Applications with InstallAnywhere With InstallAnywhere, it is possible to create a single installation to install both 32-bit and 64-bit components to a single 64-bit system. The same installation could also be used to install 32-bit components to a 32-bit system. Furthermore, the same installation can install a 32-bit JVM for the 32-bit components, and a 64-bit Java VM for the 64-bit 2 Flexera Software: InstallAnywhere White Paper Series
- 3. Creat ing InstallAnywhere Installat ions for Hybrid (32-Bit & 64-Bit) Windows Applicat ions System Folders: By default, LaunchAnywhere executables added to the project will run against the VM bundled in the Build Task. If you would like your LaunchAnywhere to run against the VM bundled in the Install Task, you’ll need to modify the launcher’s lax file to ensure that it points to the correct VM. Modify LAX File: In order to modify the lax file, you’ll need to highlight the LaunchAnywhere executable and select the Edit Properties button in the Customizer. Installing Both a 32-Bit and 64-Bit VM with Your Installation To be able to bundle multiple VM packs with your installation, you’ll need to bundle one VM pack with your installation via the Build Task, and the other via the Install Task. Once the LaunchAnywhere Properties menu appears, you’ll Build Task: need to add the following Property. Simply enable the With VM option and select the correct VM pack for your installation. If the VM pack does lax.nl.current.vm = <path to java executable> not appear in the dropdown menu, use the Download Additional VM Packs… button to download a VM pack from See the example below. the downloads page on the Flexera Software website. * Do not change this property for the uninstaller as the uninstaller must run against the VM bundled in the Build Task. Rules InstallAnywhere has a rule type called “Check System Architecture”. This allows you to place conditions * The installer & uninstaller will run against the VM bundled via on your actions, panels, and files based on the target the Build Task. system’s architecture. Install Task: Conclusion When adding a VM to the install task, you need to add the With features available in InstallAnywhere you can now files to the file tree as shown in the screen shot below. create installer projects to deploy hybrid (32 & 64-bit) Windows applications. Begin a Free Evaluat ion of InstallAnywhere You can download a free trial version of InstallAnywhere from the Flexera Software Web site at: www.flexerasoftware .com/installanywhere/eval. Want to learn more best practices for building quality installations? Join an InstallAnywhere training class – visit www.flexerasoftware .com/training for available classes. Flexera Software: InstallAnywhere White Paper Series 3
- 4. Flexera Software LLC Schaumburg United Kingdom (Europe, Japan (Asia, For more office locations visit: 1000 East Woodfield Road, (Global Headquarters): Middle East Headquarters): Pacific Headquarters): www.flexerasoftware.com Suite 400 +1 800-809-5659 +44 870-871-1111 +81 3-4360-8291 Schaumburg, IL 60173 USA +44 870-873-6300 Copyright © 2011 Flexera Software LLC. All other brand and product names mentioned herein may be the trademarks and registered trademarks of their respective owners. IA_WP_HybridApps_Oct11