About intranet licensing

You can choose to set up an intranet with a master site that controls licensing for other sites on the intranet. This consolidates license administration and validation at the master site. One license document applied on the master site can service all of the sites enabled for intranet licensing on that intranet. All named user and concurrent login license checks at each of the participating sites are redirected to the master site for validation.

You can use the Intranet Shared User Tables feature, which requires Intranet Licensing, to create and administer all users for the intranet from the master site. If you select Intranet Licensing but you do not use the Intranet Shared User Tables feature, users must be created at each participating site, and all users from all participating sites must be created at the master site as well.

A named user is allowed one login at each participating site on the intranet. If a named user tries to log into the same site that he is already logged into, the system requires the user to cancel the existing session first.

A user with a concurrent license can log in as many times on as many sites as needed, up to the license limit. Each of those concurrent logins consumes a license token.

Intranet licensing requires reliable connectivity between all participating sites. If connectivity between an intranet licensing site and its master site goes down, then all subsequent license checks will fail until connectivity is restored, so users will not be able to log in at non-master sites.

After intranet licensing has been turned on for a site, you should not turn it off without good reason. If you do, you must apply license documents to each site where you turn it off. In addition, custom objects at that site may then have incomplete licensing, if the site is not either the master site or the site at which the objects were originally created, because the appropriate licensing records for the object will not exist in the application database at that site.

License information is not replicated and no tables need to be shared specifically for intranet licensing. However, the sites on the intranet must replicate the Site Admin category, in order to recognize the master site. Information about how many sites are logged on using a particular license is stored in the SiteConnectionInformation table, which is kept up-to-date only at the master site.

The Session Management form reflects only the sessions for the local site. If the current site is enabled for intranet licensing, the License Modules per User Connection form shows license module use across all participating sites.

The License Management and User Modules forms are disabled at participating sites other than the master site.