{"id":947,"date":"2017-12-02T06:34:34","date_gmt":"2017-12-02T06:34:34","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/?p=947"},"modified":"2020-01-09T09:25:10","modified_gmt":"2020-01-09T09:25:10","slug":"advanced-designer-in-installanywhere","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/advanced-designer-in-installanywhere\/","title":{"rendered":"Advanced Designer in InstallAnywhere"},"content":{"rendered":"

msiexpert created the topic: Advanced Designer in InstallAnywhere<\/strong>
\nAdvanced Designer
\nWhile the Project Wizard leads developers through a few simple steps to create an
\ninstaller, the Advanced Designer gives greater precision, enabling developers to access
\nall the powerful features of InstallAnywhere. With the Advanced Designer developers
\ncan assign files and actions to feature sets, allowing the user to define which files are
\ninstalled; rules can be added which selectively install different files or different
\ninstallation locations dependent on the target platform. With the Advanced Designer
\ndevelopers have precise control over all the design options of an installation project.
\nThe Advanced Designer contains several tasks and subtasks which are displayed on
\nthe left hand side of the Advanced Designer development environment. The tasks are
\nbroken down into discrete subsets of the installer creation process.<\/p>\n

Project
\nThe Project task displays InstallAnywhere project information, configures, provides
\noptions to bundle or define acceptable VMs, and defines product, file installation, and
\nlocalization options. The Project task includes the following subtasks:
\n?? Info
\n?? Description
\n?? File Settings
\n?? Platforms
\n?? Locales
\n?? Rules
\n?? Config
\n?? Java<\/p>\n

Info
\nUse the Info subtask to define basic information about the installer, including the
\ninstaller title and name, build location, and installation log.<\/p>\n

Description
\nUse the Description subtask to enter vendor and product information to uniquely
\nidentify your product in the product registry. For the target operating systems, the
\nproduct registry is essentially a product configuration database which keeps track of
\nfeatures and components of products and accomplishes tasks such as associating file
\nname extensions with applications. You must set the Product ID and Version correctly
\nfor the Find Component in Registry action to work. InstallAnywhere finds the
\nlocations of components in the Registry by checking the Product ID.<\/p>\n

File Settings
\nUse the File Settings subtask to define timestamps of installed files and the
\noverwrite behavior for installed files that already exist in the targets install locations.
\nTimestamps are considered when an installation file already exists on the target
\nsystem.<\/p>\n

Platforms
\nUse the Platforms subtask to define default settings unique to each target operating
\nsystem. While InstallAnywhere runs on any Java enabled platform, there are features
\nthat should be defined separately for each target operating system.
\nThe default settings for Windows include default locations for install and shortcut
\nfolders.
\nThe default settings for Mac OS X include default locations for install and alias folders,
\ndefault Java VM used for LaunchAnywhere, whether authentication is required for
\ninstallation, and permissions for files and folders created on the target system.
\nThe default settings for Linux include default locations for install and link folders,
\ndefault user interface mode, permissions for files and folders created on the target
\nsystem, and RPM (RedHat Package Management) settings for Linux installations.<\/p>\n

Locales
\nUse the Locales subtask to define the languages for the installer. A locale is enabled
\nwhen it is checked.
\nAll enabled locales generate a locale file that is placed in a folder that is in the same
\ndirectory as the InstallAnywhere project file. To customize a locale, customize this file.
\nSee Localization for more information about locales and localization.<\/p>\n

Rules
\nUse the Rules subtask to add tasks to the installer before any installation tasks, even
\nPre-Install tasks. Use this option to check if this is a proper platform for this
\ninstallation, or if the user is logged into the root, or has the necessary permissions to
\nperform the installation.
\nConfig
\nUse the Config subtask to define a valid list of Java VMs the installer can use and set
\nthe heap size for the VMs. Use this subtask to enable debug output and select if it
\nshould be sent to a file or to a live console, and also set additional commands to the
\nJava VM other than those which the installer already sets.<\/p>\n

Java
\nUse the Java subtask to fine tune the classpath settings and decide whether to install
\nthe bundled Java VM. You may choose not to install a VM, Install the VM only while
\nperforming the installation, or to leave the VM on the target system. If you choose to
\ninstall the VM, the VM Install folder pull down list provides a variety of locations.<\/p>\n

msiexpert replied the topic: Re: Advanced Designer in InstallAnywhere<\/strong>
\nGood Articles<\/p>\n

remold replied the topic: Re: Advanced Designer in InstallAnywhere<\/strong>
\nHi,
\nThis is vinay pls call me to this no 9035759227…<\/p>\n","protected":false},"excerpt":{"rendered":"

msiexpert created the topic: Advanced Designer in InstallAnywhere Advanced Designer While the Project Wizard leads developers through a few simple steps to create an installer, the Advanced Designer gives greater… <\/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":[236],"class_list":["post-947","post","type-post","status-publish","format-standard","hentry","category-general","tag-installanywhere"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/947","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=947"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/947\/revisions"}],"predecessor-version":[{"id":948,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/947\/revisions\/948"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=947"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=947"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=947"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}