User Manual

i.LON SmartServer 2.0 Programming Tools User’s Guide 147
demonstrates the structure of the <PredefinedFeatures> element and the properties you can define in it
is provided after the table.
Property Description
Company
CompanyName Specify the name of your company.
ShortCompanyName Specify the name of your company or an abbreviated name. Legal
characters are those that would be legal for file names on the
SmartServer. You should only use letters, numbers or the underscore
character. Do not include spaces in this name.
The ShortCompanyName will appear at the beginning of the name of
your FPM license file.
LonMarkID Specify your company’s LONMARK manufacturer identifier (MID).
The LonMarkID will appear after the ShortCompanyName in the
name of your FPM license file. If you do not have a L
ONMARK ID,
you can use an arbitrary number.
This field prevents license naming collisions from occurring because
of a common company name. It is useful for scenarios in which a
large company has multiple divisions that each have their own
LONMARK ID.
Company/Feature
FeatureName Specify a descriptive name that uniquely identifies the FPM. For
example, you can specify “FPM Math Functions” or “FPM HVAC
Controller” for the math and HVAC examples used in this guide.
The specified value will be listed in the Feature Name field of the
FPM application license.
The first feature you specify in the configuration file and the
specified default values of its associated properties will appear in the
i.LON License Generator by default.
The values that appear in the i.LON License Generator are based on
the selected FeatureName.
ShortFeatureName Specify a condensed or abbreviated name for your FPM. The same
constraints and recommendations about legal characters from the
ShortCompanyName also apply to this field.
For example, you can specify “Math” or “HVAC” for the math and
HVAC examples used in this guide.
The ShortFeatureName will appear after the LonMarkID in the name
of your FPM license file.
AlgorithmIndex Specify an index corresponding to an algorithm index in your license
security source file. This index determines which security algorithm
in the security DLL file is run. You will probably only have one
algorithm, in which case an index of 0 or 1 would be appropriate.
The specified AlgorithmIndex will appear in the Secure Algorithm
Index field of the i.LON License Generator when its associated
feature is selected in the Feature Name field.
The sample security DLL file uses an algorithm that has an index of
0. If you plan on using the sample security DLL file, you must
specify 0 in the AlgorithmIndex property or else the i.LON License
Generator will not be able to generate an FPM license. See
Building
the Security DLL File for more information on using algorithm