# Extracting Features to Create a New Vendor License

Open create-product-from-features.map in the Configuration directory, which is by default in C:\Program Files\OpeniT\Core\Configuration\.

Notice that it contains instructions on how to edit the file.

Specify the features to extract and create as a vendor license with the following syntax:

MAP: <New_VendorLicense>  
Featurename\daemon\LicenseManager\vendorlicense

Empty lines are allowed — any line beginning with # as the first non-whitespace character is considered a comment. Globbing is also supported, allowing you to use several globbing patterns; however, remember that they are slower than exact matches. To make your mapping files more effective and efficient, refer to the Optimize Rules to Speed-up Rename or Mapping page.

In the mapping file, entries are case-insensitive, meaning that capitalization variations, such as 'Feature' and 'feature', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.

MAP: NewVendorLicenseFromFeatures
Feat256\*

This example creates a vendor license named NewVendorLicenseFromFeatures from all the Feat256 features.

Note that there are only two fields in this example: the feature and daemon. You may choose not to provide all fields if one globbing option is sufficient unless you want to find specific matches.

The values for the daemon and license manager can be seen in the Olap Total Use data type. However, the daemon will only be displayed for the autoconfigured vendor licenses. To ensure you have the correct details for this mapping file, please reach out to the Open iT Support Team at support@openit.com for assistance.

You can also include custom configurations in this mapping file, such as default mapping, setting date limits on specific mapping entries, or creating nested maps.

Save the changes.

Open create-product-from-features.map in the etc directory, which is by default in /var/opt/openit/etc.

Notice that it contains instructions on how to edit the file.

Specify the features to extract and create as a vendor license with the following syntax:

MAP: <New_VendorLicense>  
Featurename\daemon\LicenseManager\vendorlicense

Empty lines are allowed — any line beginning with # as the first non-whitespace character is considered a comment. Globbing is also supported, allowing you to use several globbing patterns; however, remember that they are slower than exact matches. To make your mapping files more effective and efficient, refer to the Optimize Rules to Speed-up Rename or Mapping page.

In the mapping file, entries are case-insensitive, meaning that capitalization variations, such as 'Feature' and 'feature', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.

MAP: NewVendorLicenseFromFeatures
Feat256\*

This example creates a vendor license named NewVendorLicenseFromFeatures from all the Feat256 features.

Note that there are only two fields in this example: the feature and daemon. You may choose not to provide all fields if one globbing option is sufficient unless you want to find specific matches.

The values for the daemon and license manager can be seen in the Olap Total Use data type. However, the daemon will only be displayed for the autoconfigured vendor licenses. To ensure you have the correct details for this mapping file, please reach out to the Open iT Support Team at support@openit.com for assistance.

You can also include custom configurations in this mapping file, such as default mapping, setting date limits on specific mapping entries, or creating nested maps.

Save the changes.