This guide is for standalone versions of JMP, JMP Pro, and JMP Clinical, Version 17. For clarity, this guide uses JMP to refer to JMP, JMP Pro, and JMP Clinical. If you are using any previous version, please refer to the JMP Deployment Guide for that version.
This guide describes how site administrators can install, deploy and renew annually licensed versions of JMP on Windows. An annually licensed version of JMP is a protected version that expires at the end of a license period. The version only runs when an appropriate and valid license file is present. This file allows the use of JMP until the expiration date of the license, plus a grace period for renewal.
The basic steps to follow with a new JMP purchase are:
Acquire the JMP installation files. See “Delivery of the Installation Files”.
Adjust the license files (optional). See “License Information”.
Stage the installation files. See “Staging a JMP Installation”.
Notify users of the license file location, if necessary. See “License Control”.
Notify users of the location of the installation files. See “Installing JMP”.
Each user installs and runs JMP. See “Running JMP the First Time”.
Based on how the administrator sets up the license, the user might need to point JMP to either a SAS Installation Data (SID) file or a JMP.PER file in order to run JMP.
Prior to deploying JMP, review the additional information located at jmp.com/administrator.
The set of installation files is delivered to you from SAS by Electronic Software Delivery (ESD).
This set of installation files is referred to as the software depot.
You can discuss this process with your JMP account manager. See the software order e-mail sent to you from SAS for the instructions on how to download the files. You are limited to two ESD downloads.
A validated license file is required for JMP to run. The license file is created during the installation of JMP and is named JMP.PER. The data needed to create the JMP.PER file are within a text file referred to as the SAS Installation Data (SID) file. The SID file is in the sid_files folder inside the software depot.
Each major version of JMP (version #.0) requires its own license file because the contents of the license file changes with each version. The license file for a version works for all subsequent maintenance releases (version #.#) of that version.
We suggest that each user keep JMP.PER in the location in which JMP installed it. However, JMP also supports storing JMP.PER in a single, centralized location for all users to access. See “License Control” for details.
JMP reads JMP.PER for validation of license terms each time JMP is launched. All of the lines in JMP.PER are checked during the validation process. Note that the operating system is also checked because a Windows JMP.PER does not work on macOS and vice versa.
When you receive your software from SAS, your license information might be set to expire after 90 days. If so, you will receive an updated SID file in an e-mail. After receiving the updated SID file, replace the SID file in the original set of installation files that you received. This ensures that all new installations will apply the new license information. You also need to update any previous installed copies of JMP. See “"Renewing Your JMP License” for details.
JMP allows a grace period of 90 days to renew. A prompt to renew the license will appear each time you launch JMP after the 45th day of the grace period. After the grace period is over, JMP will not run until a new license is applied.
You can stage the JMP installation files in one of several ways:
Copy the entire set of files from the software depot to a shared network space. All users can install JMP from that single location.
Copy the entire set of files from the software depot to a DVD, and then distribute this disc to your users.
The JMP installer creates a JMP.PER file from the SID file located within the sid_files folder in the software depot. This JMP.PER file is placed in the user’s JMP installation folder.
If no license information is found during installation, the user is prompted for the location of a license file the first time JMP is launched. The user needs to select either a JMP.PER or a SID file. If the user points to a JMP.PER file, the current location of that file is stored for JMP to use every time JMP is launched. If the user points to a SID file, JMP creates a JMP.PER file and prompts the user for a location to store the file.
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.
Note: Each user who installs JMP must have administrator rights on the machine.
The JMP administrator must notify the users of the location of the installer files. Depending on how the administrator deploys the license, the users might also need to know the location of the license file. Your software depot contains the installer files needed to install JMP. JMP, JMP Pro, and JMP Clinical are in separate software depots. The software depot has a folder structure for the installers based on the operating system and version of JMP.
The installer files to launch JMP, JMP Pro, and JMP Clinical version 17.x are as follows:
| JMP | <SAS Software Depot>/JMP/JMP/17_x/Windows/jmp__17xx__win.exe |
| JMP Pro | <SAS Software Depot>/JMP/JMP_Pro/17_x/Windows/jmppro__17xx__win.exe |
| JMP Clinical | <SAS Software Depot>/JMP/JMP_Clinical/17_x/Windows/jmpclin__17xx__win.exe |
where x corresponds to the version of JMP, JMP Pro, and JMP Clinical.
Right-click the appropriate executable file and select Run as Administrator to install JMP.
The JMP administrator can add custom files to the software depot. The JMP installer copies these files to your computer during the installation process. Once the files are installed, JMP processes these custom files. You can add the following types of custom files:
Scripts (.jsl)
Preferences (a JMP.PFS file)
Add-ins (*.*)
Samples (*.*)
Place the custom files in a folder named custom.:
Create the custom folder in one of the following locations:
JMP: /JMP/JMP/17_0/Windows/custom
JMP Pro: /JMP/JMP_Pro/17_0/Windows/custom
JMP Clinical: /JMP/JMP_Clinical/17_x/Windows/custom
Within the custom folder, create subfolders named scripts, pfs, samples, and addins. Files will be copied from these folders.
Note: Any subfolders in the addins and samples folders will also be copied.
The installer will copy the custom files to one of the following locations:
JMP: C:/ProgramData/SAS/JMP/
JMP Pro: C:/ProgramData/SAS/JMPPRO/
JMP Clinical: C:/ProgramData/SAS/JMPClinical/
Note: Scripts, samples, and preferences files are placed in a version # folder. Add-ins are placed in a folder called addins.
The installer provides a screen of Installation Options.
If the JMP installer finds Microsoft Excel 2013, 2016, 2019, or Excel 365 desktop version, the Excel Add-In option is displayed. This Add-In provides new capabilities when you use Microsoft Excel and JMP together.
Java Runtime Environment
Core integration files
By default, these options are not selected.
If this installation of JMP will connect to SAS on a server for processing, then select SAS Software Integration.
A silent installation does not display message or window dialogs during the installation. It does this by using a script that provides answers and selections to prompts a user sees during a non-silent installation. JMP uses InstallShield® software, which can be scripted for silent installation purposes.
Note: Ensure that Microsoft .NET 4.8 is installed and all other system requirements are met before performing a silent installation.
To install JMP 17.x using a silent setup, follow these steps:
For JMP:jmp__17xx__win.exe -r -f1{response filename}
For JMP Pro:jmppro__17xx__win.exe -r -f1{response filename}
For JMP Clinical:jmpclin__17xx__win.exe -r -f1{response filename}
Note that there is not a space between the -f1 parameter and the filename, and that it is a 1, not a lower case L. For example, if you want to create a file named silent.iss on C:\ for JMP, execute the following statement:jmp__17xx__win.exe -r -f1c:\silent.iss
For JMP:jmp__17xx__win.exe -s -f1{response filename}
For JMP Pro:jmppro__17xx__win.exe -s -f1{response filename}
For JMP Clinical:jmpclin__17xx__win.exe -s -f1{response filename}
Note that there is not a space between the -f1 parameter and the filename, and that it is a 1, not a lower case L. For example, if you want to create a file named silent.iss on C:\ for JMP, execute the following statement:jmp__17xx__win.exe -s -f1c:\silent.iss
If the license file was applied during the installation, no further action is required.
If the license file was not applied during the installation, the user is prompted to select a license file.
If the user points to a JMP.PER file, the location of the JMP.PER file is stored. This means if the JMP.PER file is later moved or deleted, the user is prompted to select a license file. This also means that if the JMP.PER file is stored on a network drive, that drive must be available to run JMP.
If the user points to a SID file, JMP uses the file to create a JMP.PER file and then prompts the user for a location to save the file.
Note: Although both the SID file and the JMP.PER file contain text that appears to be editable using a text editor, do not do so. Altering the SID file in any way destroys the integrity of the file. Once the file is destroyed, JMP cannot create the license file, and you cannot run JMP. Likewise, altering the JMP.PER file renders the file useless and you must use your original SID file to restore the JMP application.
When your license expires, you must renew your license with SAS. SAS e-mails you a new SID file.
After receiving a new SID file as the renewal license from SAS, replace the SID file in the original set of installation files that you received from SAS. This ensures that all new installations from then on use the latest license.
Note: Although both the SID file and the JMP.PER file contain text that appears to be editable using a text editor, do not do so. Altering the SID file in any way destroys the integrity of the file. Once the file is destroyed, JMP cannot create the license file, and you cannot run JMP. Likewise, altering the JMP.PER file renders it useless and you must use your original SID file to restore the JMP application.
All installed copies of JMP must be updated. You can either:
Distribute the SID file to all users.
Create an updated JMP.PER file and distribute it to all users.
Replace your shared network copy of JMP.PER.
To update the JMP license
Start JMP.
Note: Due to enhanced security in Windows operating systems, you might need to run JMP in Administrative mode. This can be done by right clicking the JMP desktop icon and selecting “Run as Administrator.”
If JMP is prompting for a new license, click Open License.
If JMP is not prompting for a new license and you want to renew the license, open a JMP script window. Then, enter this line in the window and run the script:
Renew License();
Continue with the instructions below for updating with either a SID file or a JMP.PER file.
To update the JMP license with a SID file
At the prompt, navigate to where you saved the SID file sent to you in the e-mail from SAS.
Click Open.
(Optional) Fill in the Administrator Name and Department.
Click OK.
To update the JMP license with a JMP.PER file
At the prompt, navigate to the new JMP.PER file.
Click Open.
JMP Installation
Where is the JMP 17 desktop icon?
The desktop icon is not installed by default. To install the icon, select Create desktop shortcut on the last screen of the installer window.
Windows security will not let me update the JMP file in my C:\Program Files folder. What can I do?
This is a result of enhanced security in Windows operating system. To change files in the Program Files folder, you might need to run JMP in Administrative mode. This can be done by right clicking the JMP desktop icon and selecting “Run as Administrator.”
What if I need to run JMP on my laptop away from the network location where the JMP.PER file is kept?
If a single JMP.PER file is kept in a network folder for everyone’s use and you need to run JMP on a laptop without a connection to the network, you can do so for a limited time using a temporary license. Before doing so, you must run JMP on your laptop while connected to the network so that you can point JMP initially to a valid JMP.PER file.
Connect your laptop to the network.
Start JMP to ensure that JMP on your laptop has access to the latest license file on the network.
Close JMP.
Later, when you start JMP away from your network, JMP runs using a temporary license for ninety days. After ninety days, you need to reconnect to the network.
Note: You must run JMP with a valid license file before disconnecting from the network. Otherwise, JMP will not run when disconnected.
How do I obtain maintenance updates to JMP software?
Maintenance updates are available from the JMP website (jmp.com/update).
Can I have two different versions of JMP installed on my computer at the same time?
Yes. JMP 17 can be installed on a computer with a previous version of JMP. The installation of JMP 17 does not remove the previous version and both versions are operable.
If I have two versions of JMP installed on my computer, can I have the Excel Add-in on both versions?
No. The JMP 17 installation removes the Excel Add-in files installed for the previous version of JMP as only one set of JMP Add-in files can be on a computer at one time. The file associations of the JMP files (for example, .JMP, .JSL) are assigned to the last JMP version installed. This can be reset by going to File > Preferences > Windows Specific > Reset Associations in the version of JMP that you want to be active.
Can I install an annual license version of JMP over a demo or trial version of JMP?
No. You must first uninstall the demo version of JMP before installing the annual license version of JMP. This ensures that all of the correct system and license files are installed in the correct location.
Who should I contact when my JMP license expires or is about to expire?
Contact your local internal JMP site representative or support personnel. The site representative should then contact their SAS Contracts representative for an updated license file.
Where can I find a Quality Statement concerning JMP?
JMP uses a variety of methods to see, to the extent possible, that the software produces accurate, reliable and numerically precise results. To assist customer validation or operational qualification (OQ) efforts, JMP provides a set of tests based on the Standards and Technology Statistical Reference Data (StRD) sets in an extensible framework, available for download. JMP also provides a tool for verifying that JMP software has been installed and maintained to the manufacturer’s specifications. This tool verifies the integrity of each installed file and provides a report detailing the results. This information is available from the JMP website (jmp.com/qualitystatement).
How do I report a problem I am having with JMP?
There are different options for reporting problems to JMP. Visit JMP Support to find the communication method that best works for you.
When contacting Technical Support, please have the following information available:
Your JMP site license number.
The JMP version that you are using.
For graphics problems, the brand and model of the graphics card and the version of the graphics driver might be helpful.
How do I locate my JMP site license number?
To obtain the site license number, select About JMP in the Help menu.
On Windows, how does JMP find the PER file to use?
When installed directly from the software depot, the PER file is located at one of the following locations:
JMP: C:\Program Files\SAS\JMP\17\JMP.PER
JMP Pro: C:\Program Files\SAS\JMPPRO\17\JMP.PER
JMP Clinical: C:\Program Files\SAS\JMPCLINICAL\17\JMP.PER
If the user is prompted to point to a license file, the resulting location will be saved in the PFS file located at %APPDATA% location. When launched, the order of search for the PER file is as follows:
location defined in the PFS file
user folder in one of the following locations:
JMP: %APPDATA%\SAS\JMP\17\JMP.PER
JMP Pro: %APPDATA%\SAS\JMPPRO\17\JMP.PER
JMP Clinical: %APPDATA%\SAS\JMPCLINICAL\17\JMP.PER
installation location
A user can run a one-line script to print to the log the exact location of the PER used by JMP.
Show License Path();