The introductory tutorial builds an installer using the Project Wizard, which does not allow configuring Pre-Install or Post-Install Actions. It is possible to build a basic installer with the Project Wizard in six steps and about five minutes. The following tutorial teaches how to build an installer for a sample Java application, called “Office Suite for Java,” which is included in the InstallAnywhere folder.<\/p>\n
Create New Project<\/p>\n
To create a new project:
\n1. Launch InstallAnywhere.
\n2. On the first screen, the Create New Project option should already be selected.
\n3. Click Save As to save and name the project. The Save New Project As dialog box
\nappears. By default the project is named My_Product, but any name could be
\nused.
\n4. Click Save to confirm the name and close this dialog box.
\n5. Click Next to move to the next step of the Project Wizard. Set Info defines basic
\ninformation about the installer, such as the product name (as displayed on the
\ninstaller), the name of the installer to be produced, the name of the destination
\nfolder, and the application name.
\n6. Type the information in the appropriate textboxes.
\n7. For this tutorial, use the following:
\nProduct Name: OfficeSuite
\nInstall Folder Name: OfficeSuite
\nApplication Shortcut Name: OfficeSuite
\n8. Click Next to move to the next step in the Project Wizard.<\/p>\n
Install Tasks<\/p>\n
To install tasks:
\n1. Click Add Files. The Add Files to Project dialog box appears.
\n2. Browse through the list to find the OfficeSuiteSourceFiles folder. The
\nOfficeSuiteSourceFiles folder is within the InstallAnywhere installation folder.
\n3. Click Add All to add the ImagesAndDocs and OfficeSuite2000 folders, which are
\ninside the OfficeSuiteSourceFiles folder. These files should appear in the Files to
\nAdd list.
\n4. Click Done. The selected files should appear in the File\/Folder Hierarchy.
\n5. Click Next to move to the next step in the Project Wizard.
\n6. Choose Main Class.<\/p>\n
Build Installer<\/p>\n
The first several items on the Build Installer screen, from Mac OS X through Unix (All), represent installers that are double-clickable on their respective platforms. The final option, Other Java-Enabled Platforms, is a “pure” Java installer that can be invoked from the command line on any Java-enabled platform. Developers may also choose to build installers with an embedded Virtual Machine.<\/p>\n
Installers that are built without VMs are smaller, and download faster than installers bundled with one. The InstallAnywhere Web Install process will allow end-users to choose the appropriate installer for their system. To build the installer, pick the appropriate destination platforms and click Build. The installer folder will be placed in the same location as the project file. This location cannot be changed.<\/p>\n
Test
\nNow that an installer has been built, it can be tested.<\/p>\n
To test an installer:
\n1. Click Try It.
\n2. After deploying the sample installer:
\nOn Windows, go to the OfficeSuite program group and choose OfficeSuite.
\nOn Unix, “cd” to the directory where the program was installed and type OfficeSuite.
\nOn Mac OS X, double-click the OfficeSuite icon on the desktop.<\/p>\n
3. After launching Office Suite for Java, quit by selecting Exit from its File menu.
\n4. Run the completed installer.<\/p>\n
When building for a platform other than that on which the installer is being developed, transfer that installer, and run it manually. By default, installers will be located in the Build_Output directories found in the same folder as the .iap_xml project file. Within the Build_Output folder, will be Web_Installers, and or CDROM_installers. From within each of these directories, choose the platform to test. For the CDROM installer, transfer the entire contents of the CDROM_Installers folder.<\/p>\n","protected":false},"excerpt":{"rendered":"
The introductory tutorial builds an installer using the Project Wizard, which does not allow configuring Pre-Install or Post-Install Actions. It is possible to build a basic installer with the Project… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[49],"tags":[327],"class_list":["post-1347","post","type-post","status-publish","format-standard","hentry","category-general","tag-building"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/1347","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=1347"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/1347\/revisions"}],"predecessor-version":[{"id":1348,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/1347\/revisions\/1348"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=1347"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=1347"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=1347"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}