02.04.2013 Views

Sentinel Hardware Keys Developer's Guide - Customer Connection ...

Sentinel Hardware Keys Developer's Guide - Customer Connection ...

Sentinel Hardware Keys Developer's Guide - Customer Connection ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

For a Loaded Group<br />

Frequently Asked Questions<br />

Contents Glossary Index Troubleshooting<br />

1. In License Manager, click the icon. The Lock\Unlock Group<br />

dialog box appears.<br />

2. Specify the password.<br />

3. Click OK.<br />

Frequently Asked Questions<br />

Question 1 - What is a default feature instance? How does it differ<br />

from other non-default/new feature instances?<br />

When you add a CodeCover or API feature in the License Designer screen,<br />

it is known as the default feature instance. If Add instances later check<br />

box is selected during this process, new feature instances can be created in<br />

the License Manager screen.<br />

These are known as the non-default or new feature instances. The option to<br />

create new feature instances provides the flexibility of changing the licensing<br />

values right-before programming hardware keys, without having to<br />

change the protection strategy (created in the License Designer screen).<br />

The FAQs below provide more information.<br />

Question 2 - What is the difference between “updating the default<br />

instance” and “adding a new instance?<br />

Updating a default feature instance allows you to modify the licensing settings<br />

right-before programming a batch of <strong>Sentinel</strong> <strong>Keys</strong>. This modification<br />

does not affect your protection implementation at the application-level. For<br />

example, you can specify 999 executions instead of 99, without generating<br />

the header file again, or applying the CodeCover protection again, and so on.<br />

However, updating the default instance can be quite tedious when the<br />

licensing values need to be modified quite frequently. Further, the updated<br />

values overwrite the values specified earlier (non-persistent). Therefore, it<br />

might be useful to add different feature instances having different licensing<br />

<strong>Sentinel</strong> <strong>Hardware</strong> <strong>Keys</strong> Developer’s <strong>Guide</strong> 197

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!