{"id":1214,"date":"2017-12-04T05:18:21","date_gmt":"2017-12-04T05:18:21","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/?p=1214"},"modified":"2020-01-09T09:35:22","modified_gmt":"2020-01-09T09:35:22","slug":"organization-in-installanywhere","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/organization-in-installanywhere\/","title":{"rendered":"Organization in Installanywhere"},"content":{"rendered":"

msiexpert created the topic: Organization in Installanywhere<\/strong>
\nOrganization<\/p>\n

The Organization task enables developers to arrange Install Sets, Product Features,
\nComponents, and Merge Modules. Install Sets and Features allow for levels of
\ninstallation options for the end-user of the installer. Components are the smallest
\nwidget that can be selected by a Feature set. Install Sets are groupings of Features, and
\nare an organizational tool for the developer of the installer. Components may be much
\nmore than files, they can be sophisticated actions that are required to install and run
\napplications or features properly.
\nThere is an interaction between the Install Sets, Features, and Components
\nsubtasks, as well as the Install task. If an install set is added in the Install Sets
\nsubtask, features can be assigned to that install set in the Features subtask. If a
\nfeature is added in the Features subtask, components can be assigned to that feature
\nin the Components subtask. If a component is added in the Components subtask,
\nfiles and\/or actions can be assigned to that component after the files and\/or actions
\nare added in the Install task.<\/p>\n

Install Sets
\nInstall Sets are a set of product features. The Install Sets subtask allows developers
\nto add, name, remove, or order Install sets in the installer. In the Install Set List,
\ndevelopers define which install set (or sets) to use as the default option to provide to
\nthe end-user. Features are assigned to install sets in the Features subtask.
\nWhen the installer requests install set information, each install set is represented by a
\ngraphic element. The Choose Image button enables developers to select the graphic
\nelement.
\nRules may be associated with an install set, and that association is created by selecting
\nRules in the customizer and adding rules. The rules for install sets are evaluated
\nbefore the install set is installed. If the rules on the Install Set evaluate to false, the
\nInstall Set will not be displayed.<\/p>\n

Features
\nFeatures are meant to identify distinct parts of the product so the end-user may
\nchoose whether or not to install them. InstallAnywhere Product Features are
\ngroupings of components. It is up to the developer to define the logical grouping of
\ncomponents into features by assigning components to the features in the
\nComponents subtask.<\/p>\n

The Features subtask enables developers to add, name, remove, or order features.
\nRules may be associated with a feature set, and that association is created by selecting
\nRules in the customizer and adding rules. The rules for feature sets are evaluated
\nbefore the feature set is installed. If the rules on the Feature evaluate to false, the
\nFeature will not be displayed.<\/p>\n

Components
\nComponents are the smallest unit of organization when creating an installer. Unlike
\nFeatures and Install Sets, Components may be versioned. Components are uniquely
\nidentified so developers may update a specific component or use the Find Component
\nin Registry action to locate a particular component.
\nThe Key File is a file that must be present in all subsequent versions of the component.
\nThe Key File is used to define the components location when the Find Component in
\nRegistry action is used.
\nThe Components subtask enables developers to add, name, remove, order, identify,
\nand version components.
\nRules may be associated with component sets, and that association is created by
\nselecting Rules in the customizer and adding rules. The rules for component sets are
\nevaluated before the component set is installed.<\/p>\n

Modules
\nThe Modules subtask imports Merge Modules into an InstallAnywhere project.
\nMerge Modules are created as a build output option in the Build task.
\nDIM References
\nThe DIM References subtask supports referencing Developer Installation Manifests
\n(DIMs) in installation projects. DIMs are XML files that describe specific product
\nsubsystems and their requirements. Application developers create DIMs using
\nInstallShield Collaboration, a plug-in module for Eclipse and Microsoft Visual Studio
\n.NET. See Referencing Developer Installation Manifests (DIMs) for more information
\non referencing DIMs in your installation project.<\/p>\n","protected":false},"excerpt":{"rendered":"

msiexpert created the topic: Organization in Installanywhere Organization The Organization task enables developers to arrange Install Sets, Product Features, Components, and Merge Modules. Install Sets and Features allow for levels… <\/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-1214","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\/1214","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=1214"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/1214\/revisions"}],"predecessor-version":[{"id":1215,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/1214\/revisions\/1215"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=1214"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=1214"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=1214"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}