InstallShield 2012 Spring Express Edition User Guide

Table 24-6: Software Identification Tag Settings (cont.)
Setting Description
Features View
Chapter 24: View Reference
Organize Your Setup View
Software Licensor ID Enter the registration ID of the organization that owns the copyright for the software.
This ID helps to differentiate between different legal organizations that have the same
licensor name but are in different countries.
This setting is optional. If you leave this setting blank, InstallShield uses the value of the
Tag Creator ID setting for the software licensor ID.
The convention for the registration ID is as follows:
regid.YYYY-MM.ReversedDomainName,division
The registration ID consists of the following parts:
• regid.—The string regid indicates that the XML portion is a registration ID for a
software identification tag. A period (.) must be included after this string.
• YYYY-MM.—This part of the registration ID identifies the first full month (MM) and
the year (YYYY) in which the domain name was owned by the tag creator. For
example, if you are creating the tag and you purchased the domain name February
15, 1999, you would use 1999-03 in this part of the registration ID, since the first
full month the domain name was owned was March (03), and the year was 1999.
The year and month must be separated by a dash.
• ReversedDomainName—This part identifies the reversed domain name of the
organization that is creating the software identification tag. For example, for the
flexerasoftware.com domain name, the reversed domain name is:
com.flexerasoftware
• ,division—This optional part starts with a comma (,), and is followed by an
additional string. You can enter a string that helps to distinguish between different
divisions or areas of the organization. If you do not want to use this optional
distinguishing part of the registration ID, do not include the comma or an additional
string in your entry.
Features and subfeatures give you almost limitless flexibility in packaging your application and related
accessories for setup. You can create and configure Features from the Features view.
A feature is a building-block of an application from the end user’s perspective. That is, they represent a
specific capability of your product, such as its help files or a part of a product suite that can be installed
or uninstalled based on the end user’s selections. Your entire application should be divided into features
that perform a specific purpose.
To make it easier to lay out a complex application, InstallShield allows you to create both features and
subfeatures. Subfeatures are further divisions of a feature. Since features should be self-contained
elements of an application or application suite that a user can selectively install, it might make the most
sense for you to organize portions of your application as subfeatures of a “parent” feature. Assuming that
the features are all visible, your end user can then select which portions of a feature to install in the
Custom Setup dialog.
The default feature Always Install cannot be renamed or removed from your project, nor can you add
any subfeatures to it. This feature should contain files that must be installed as part of your setup.
InstallShield 2012 Spring Express Edition User Guide ISE-1900-UG00 517