Federated license servers

A single Teamcenter site can potentially be accessed by multiple users from inside and outside a company. Conversely, a user may need to access multiple sites. Rather than requiring that a user with the same exact name and user ID consume site-specific seat and feature licenses when logging in to different sites, or that all users of a site draw from the same license server, multiple license servers with varying license files can be defined for a site. This capability is referred to as federated license servers. Administrators can define license servers for a site by using the -license_server argument in the site_util utility. They can then use the -user_homesite argument in the make_user utility or select a home site in the Organization application to assign sites to users. Users can then access licenses from the license server associated with their assigned home site, unless further changes are made in configuration. Additionally, administrators can use the -licenseserver argument in the make_user utility or specify a license server in the Organization application to assign a license server to a user. Once the user's license server has been specified, it takes precedence over the license server associated with the user's home site. The following scenarios are some examples in which multiple license servers are used to appropriately provide access. Different business units want control over their own licenses Having separate license files and servers can provide business units better control over licenses, and can help avoid cross charging within a company. Multisite environment A user may generally work in SiteA, but might need to approve a Global workflow in SiteB. The user can be added to SiteB and point to the original license server to get authorized access. Test, Development, and Production environments Similarly to multisite environments, a user can be added to multiple environments and point to and use the single license from the original license server. Note that licenses of type “Test/QA” may not be used in a production environment or for any other purpose. Adding new licenses Say that company ABC has seat and feature licenses for a current set of users. The company wants to add seats and different feature licenses for process planning purposes to a new set of 50 users. In this case, the company can add the new 50 users and assign a new license server that has the required features without having to combine all the licenses into one file.