Concepts

Tasks

Manually Binding an Activation Key to the APM Database

As a server-based application, APM honors the SELECT activation key of the machine that hosts the APM application server. The Smart Client component does not check for SELECT activation locally; it relies on the server’s activation. Thick client (that is, administrator) deployments use the local machine’s activation key.

APM stores a copy of the SELECT activation key in the database in order to provide consistent behavior regardless of who is connecting. The first time that a thick client or server accesses an APM database, its activation key is “bound” to the database. After that, if an APM thick client or server instance attempts to connect to the database with a different key, the other key is accepted if it includes the same number of products or more. If the other key includes fewer products than the bound key, the client is not able to run and a message informs the user.

It is possible to manually bind an activation key to the database, replacing the existing key. You might need to do this if the wrong key was entered previously or if you wish to replace the key for another reason. From then on the database is bound to that key unless you explicitly re-bind it to a new one.

Warning: The Bind Current Action Key menu option does not ask for confirmation before executing, and it cannot be undone. Administrators can control access to this feature using APM security profiles.

Tip: To test a thick client or server/service instance’s activation key against the activation key binding in the database, open the APM Configuration window and select the instance. Then select the Test Instance tab and click Run Tests. The SELECTserver Licensing settings are shown in the test window.

Some important points:

•	The bound activation key does not replace the requirement to activate machines running the APM application server (or thick clients).

•	The bound activation key drives which modules are available within the system. This is one of the primary roles of putting it in the database – ensuring a consistent set of modules regardless of where you connect from.

•	A machine running APM (either server or thick client) with a different activation key than is bound to the database faces some restrictions:

•	If the activation key has fewer modules than the bound one, the software will not start.

•	If the activation key has the same or more modules than the bound key, the software runs but only allows the modules included in the bound key. The user will not be able to change which modules are used at each Site.

•	A machine running APM (either server or thick client) with no activation key will be treated as in trial, regardless of whether there is a bound activation key or not.

•	Products with the status of Trial and offline will be treated normally as if they are active until the trial expires or the offline status reaches the threshold value of 30 days.

•	The database can be bound to a different activation at any time by the server or thick client. Security settings can restrict this function.

To Manually Bind an Activation Key to the APM Database

1.	From the Site window, click on the tool bar. The Enterprise window appears.

2.	Click the Administration menu and then Bind Current Activation Key. The current key is bound to the database immediately.