<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />For large organizations it is often easier to centralize the location of the JMP license file rather then deploy to each client.
This allows the organization to control who is accessing the software and to remove access if an employee leaves the organization or department.
The details for managing the JMP license file via an active directory group.
The simplest solution would be to place the respective JMP.per file on a common non-http file share.
IT:
- Create a folder for each version of JMP and place the respective JMP.per file in the folder.
- Create an active directory group for each JMP version if analysts are different or restricted by version with read permission.
- Add members to each of the respective active directory groups.
Each Analyst:
- File—>Preferences—>File Locations
- Select License File path and click the browse button to navigate to the shared file system and point to the appropriate license file.
Done!
Specifically, page 11 of the JMP 12 Deployment Guide—
"Alternatively, you can choose to place a single JMP.PER file in a secured, shared network location for all users to use. Each user must select the file when prompted the first time JMP is launched.”
To find the currently installed location of the license file and overwrite or replace with new location—
- You can read the “JMPPerPath" registry key (HKEY_CURRENT_USER\Software\SAS Institute Inc.\JMPPro\12.0\Options) to identify the location of the JMP.per file and place the new JMP.per in that location (overwrite) OR
- Edit the registry key with the new path location for the license file and place the new JMP.per file in that location (modify) OR
- Delete the “JMPPerPath” registry key and place the JMP.per file in same folder location as the JMP.exe (replace)
