Deployment Guide - JMP Software from SAS · Deployment Guide 1 Installation ... SAS, replace the SID file in the origin al set of installation files that you received from SAS. This

JMP, A Business Unit of SASSAS Campus DriveCary, NC 27513

“The real voyage of discovery consists not in seeking newlandscapes, but in having new eyes.”

Marcel Proust

Deployment Guide

The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2012. JMP® 10 Deployment Guide for Annually Licensed Windows and Macintosh Versions. Cary, NC: SAS Institute Inc.

JMP® 10 Deployment Guide for Annually Licensed Windows and Macintosh Versions

Copyright © 2012, SAS Institute Inc., Cary, NC, USA

SAS® Publishing provides a complete selection of books and electronic products to help customers use SAS software to its fullest potential. For more information about our e-books, e-learning products, CDs, and hard-copy books, visit the SAS Publishing Web site at support.sas.com/publishing or call 1-800-727-3228.

SAS® and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. ® indicates USA registration.

Other brand and product names are registered trademarks or trademarks of their respective companies.

Technology License Notices

Scintilla is Copyright © 1998-2003 by Neil Hodgson <[email protected]>. NEIL HODGSON DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL NEIL HODGSON BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

XRender is Copyright © 2002 Keith Packard. KEITH PACKARD DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL KEITH PACKARD BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

ImageMagick software is Copyright © 1999-2011, ImageMagick Studio LLC, a non-profit organization dedicated to making software imaging solutions freely available.

bzlib software is Copyright © 1991-2009, Thomas G. Lane, Guido Vollbeding. All rights reserved.

FreeType software is Copyright © 1996-2002, The FreeType Project (www.freetype.org). All rights reserved.

http://support.sas.com/publishing

http://www.freetype.org

ContentsDeployment Guide

1 InstallationSystem Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Delivery of the Installation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

License Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Staging a JMP Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

License Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Installing JMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Running JMP the First Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Dividing a Software Depot with Multiple JMP Installers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Adding Custom Files to a Software Depot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Excel Add-in and JMP Installers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Silent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2 Renewing and UpgradingRenewing Your JMP License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Upgrading Your JMP License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Customizing the Expiration Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3 Frequently Asked QuestionsFrequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4 AppendixExtra Folder Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2 1

Chapter 1Installation

Annually Licensed Windows and MacIntosh Versions

This guide is for standalone versions of JMP and JMP Pro, Version 10. For clarity, this guide uses JMP to refer to both JMP and JMP Pro. If you are using any previous release, please refer to the JMP Deployment Guide for that release (This document was previously known as the Administrator’s Guide).

This guide describes how site administrators can install, deploy and renew annually licensed versions of JMP. 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 permission 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:

1. Acquire the JMP installation files. See “Delivery of the Installation Files” on page 5.

2. Adjust the license files (optional). See “License Information” on page 5.

3. Stage the installation files. See “Staging a JMP Installation” on page 6.

4. Notify the users of license file location if necessary. See “License Control” on page 6.

5. Notify the users of the location of the installation files. See “Installing JMP” on page 7.

6. Each user installs and runs JMP. See “Running JMP the First Time” on page 7.

Based on how the administrator sets up the license, the user might need to point JMP to either a SAS Install Data (SID) file or a JMP.PER file in order to run JMP.

Prior to deploying JMP, review the additional information located here: http://www.jmp.com/administrator/.

System Requirements

Windows

OS: Windows XP w/ SP2 (32-bit or 64-bit* versions)

Windows Vista (except Vista Home Basic edition)

Windows 7 (except Windows 7 Starter and Windows 7 Home Basic editions)

CPU: 32-bit: x86 class processor

64-bit*: x64 processor

RAM**: 32-bit systems: 1 GB minimum, 2 GB or more recommended

64-bit systems*: 4 GB or more recommended

http://www.jmp.com/administrator/

http://www.jmp.com/administrator/

4 Installation Chapter 1System Requirements

Check http://www.jmp.com/support/system_requirements_jmp.shtml to ensure you have the most up-to-date list of system requirements.

*64-Bit editions of JMP and JMP Pro only.

**JMP is an in-memory analysis tool. Your memory requirements depend on the amount of data being analyzed.

***JMP does not support the FileMaker Pro® database on Windows.

Drive Space: 600 MB (plus up to 250 MB for additional software below, if not already installed)

Browser: Microsoft Internet Explorer 7.0 or higher

Recommended Display: True (24-bit or more) color with resolution of 1024x768 or greater; video card with hardware accelerated 2-D and 3-D drivers recommended

Database***: Unicode compliant ODBC 3.0 or higher (required only if connecting to database)

Additional Required Software (included with JMP installer):

Microsoft .NET Framework 4 Client Profile

Microsoft Visual C++ 2010 Redistributable

Microsoft Visual C++ 2008 Redistributable

Sun JRE 1.6

Other Compatible Software (not required):

SAS 9.1.3 SP4

SAS 9.2

SAS 9.3

R open-source statistical software releases 2.9.1 to 2.11.1

MacIntosh

OS: Mac OS X 10.5 or higher, including 10.7 (Lion)Online Help, SAS connections require Mac OSX 10.6 (Snow Leopard) or higher

CPU: 32-bit systems: Mac computer with an Intel processor

64-bit systems*: Mac computer with a 64-bit Intel processor

RAM**: 32-bit systems: 1 GB minimum, 2 GB or more recommended

64-bit systems*: 4 GB or more recommended

Drive Space: 500 MB of available disk space

Database: Unicode compliant ODBC 3.0 or higher (required only if connecting to database)

Other Compatible Software (not required):

SAS 9.1.3 SP4

SAS 9.2

SAS 9.3

R open-source statistical software releases 2.9.1 to 2.11.1

Chapter 1 Installation 5Delivery of the Installation Files

Delivery of the Installation Files

The set of installation files is delivered to you from SAS in one of two ways:

• Most customers use Electronic Software Delivery (ESD).

• Others receive installation files on DVD.

You can discuss these options with your JMP account manager. Either way that you receive the files, they are configured in the same way. 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.

The JMP and JMP Pro annual license installers contain the files needed to run in 32-bit mode and in 64-bit mode. The communication that you receive from SAS might indicate 64-bit, but note that the installers contain both 32-bit and 64-bit.

Windows: On 32-bit PCs, the installer installs only 32-bit files. On 64-bit PCs, you are prompted to install either 32-bit or 64-bit files.

Macintosh: The installer installs a binary with both 32-bit and 64-bit executables.

If you are installing JMP or JMP Pro on a 64-bit version of Windows operating system, you will be prompted to install either the 32-bit or 64-bit version of JMP. Please be aware of the following consequences when considering which version of JMP to install:

• Database ODBC drivers (such as MicroSoft Access, SQL Server, and Oracle) need to have the matching 32-bit or 64-bit version of the ODBC driver installed, to match the bit version of JMP.

• JMP graphics performance degrades on older Intel processors with MMX technology. Installing JMP Pro 64-bit version results in slower performance if your computer has an older Intel processor with MMX technology. This is due to the unavailability of 64-bit drivers for the Intel MMX processor.

License Information

Each major version of JMP (version #.0) requires its own license file. The license file works for all subsequent maintenance releases (version #.0.#). Each operating system that JMP runs on also needs its own license file. The license is enforced by an expiration date.

JMP accesses a customized license file (JMP.PER) for validation of license terms every time JMP is launched. We suggest that each user store this file in the folder in which JMP is installed. However, JMP also supports storing this file in a single, centralized location for all users to access.

The license information needed to create the JMP.PER file is within a text file called a SAS Installation Data (SID) file. The SID file is shipped to you on the media (ESD or DVD) in the sid_files folder.

The license file is validated each time JMP is launched. All of the items in the license file are checked in the validation process. The operating system is checked (for example, a Windows license file will not work on a Macintosh and vice versa), and the expiration date is checked against the system date.

The first time you receive your software from SAS, your license file might expire after 90 days. If so, you will receive an updated SID file from SAS in an e-mail. After receiving the updated license (a SID file) from SAS, replace the SID file in the original set of installation files that you received from SAS. This ensures that

6 Installation Chapter 1Staging a JMP Installation

all new installations use the new license. You also need to update any already-installed copies of JMP. See “Renewing Your JMP License” on page 17 for details.

Your license gives you a grace period of 90 days to renew. 45 days into the 90 days, you are prompted to renew the license every time you start JMP. After the grace period is over, JMP will not run without a new license.

Staging a JMP Installation

You can stage the JMP installation files in one of several ways:

• Copy the entire set of files from either the software depot or the original DVD to a shared network space. All users can install JMP from that single location.

• Copy the entire set of installation files from either the software depot or the original DVD to a CD or DVD, and then distribute these discs to your users.

• Send the original DVD (or a single copy that you make from the software depot) around for each user to install JMP.

License Control

The JMP installer on Windows either copies a JMP.PER file if found, or creates a JMP.PER file if a SID file is found. This JMP.PER file is placed in the user’s JMP installation folder.

The JMP installer on Macintosh creates a JMP.PER file if a SID file is found. This JMP.PER file is placed in the /Applications/JMP 10.app folder that is created by the installer.

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.

Note: We suggest that the JMP.PER file be stored in the folder in which JMP was installed on the user’s computer.

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.

Chapter 1 Installation 7Installing JMP

Installing JMP

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. If you ordered multiple versions of JMP, such as Windows and Macintosh, they are all in this software depot.

The software depot has a folder structure for the installers based on operating system and version of JMP. The installer files to launch are as follows:

If a license file is not applied during installation, the user is asked to select the license file when JMP is launched the first time.

An installation can be challenging when a software depot contains JMP software for multiple operating systems. To rearrange the installer files into separate structures to allow for creation of physical media and proper installation, see “Dividing a Software Depot with Multiple JMP Installers” on page 8. To add custom files to the software depot, see “Adding Custom Files to a Software Depot” on page 12.

Running JMP the First Time

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. We suggest saving the file in the same folder JMP is installed (for example, on Windows, C:\Program Files\SAS\JMP\10\JMP.PER).

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.

JMP on Windows <SAS Software Depot>\JMP\JMP\10_0\Windows\JMP\setup.exe

JMP on Macintosh <SAS Software Depot>/JMP/JMP/10_0/Macintosh/JMP-10.dmg

JMP Pro on Windows <SAS Software Depot>\JMP\JMP_Pro\10_0\Windows\JMP\setup.exe

JMP Pro on Macintosh <SAS Software Depot>/JMP/JMP_Pro/10_0/Macintosh/JMP-10.dmg

8 Installation Chapter 1Running JMP the First Time

Dividing a Software Depot with Multiple JMP Installers

A challenge can occur when a software depot contains JMP software for multiple operating systems. The JMP software in the SAS software depot can be split up manually. You can rearrange the installer files into separate structures to allow for the creation of physical media and proper installation. You can manually copy files from the software depot into different locations for your users to access depending on which operating system they have and products they have purchased (two for Windows (JMP and JMP Pro) and two for Macintosh (JMP and JMP Pro)).

Each of the sub-depots needs the appropriate JMP\JMP <Pro>\<version>\<OS>\JMP\setup.exe (or Mac equivalent, JMP-10.dmg) structure with access to the licensing file. The corresponding license file for that particular installation should be in the sid_files folder.

You now have a separate set of installation and license files for Macintosh and Windows. These folders can be copied to a staging area for user installation or copied to physical media for use.

Locating the Various JMP Installers in a SAS Software Depot

This section details how to locate the various software installers within the SAS Software Depot that are needed for JMP and JMP Pro. The SAS Software Depot has multiple folders at the root level, including a folder named JMP. The JMP folder contains all of the possible JMP installers for your order. The root level of the SAS Software Depot contains some or all of these folders.

Figure 1.1 SAS Software Depot Folder

Inside the JMP folder of the SAS Software Depot, the JMP installers are located in folders with names based on <JMP product name>, <version number>, and <operating system>. Figure 1.2 displays an expanded view of the <software depot>\JMP folder containing JMP products.

Chapter 1 Installation 9Running JMP the First Time

Figure 1.2 SAS Software Depot Root Levels

Your depot can contain up to four distinct installers:

• JMP – Macintosh

• JMP – Windows

• JMP Pro - Macintosh

• JMP Pro – Windows

All of the JMP installers are found in the <software depot>\JMP folder. All other installers in the depot are SAS installers and cannot be used outside of the depot structure. The only installers that can be copied from the depot are the JMP installers under the <software depot>\JMP folder.

With SAS 9.3, the Visual Data Discovery and Visual BI products include JMP. You will need to install from the JMP directory and the installer will install 32-bit JMP on a 32-bit PC and will allow the choice of 32-bit or 64-bit installation on a 64-bit PC.

Double-clicking the installer (setup.exe on Windows and JMP-10.dmg on Macintosh) launches the installer.

Table 1.1 Location of JMP Installer Files in a SAS Software Depot

JMP Product Installer Contains Installer Filename

JMP Windows 32-bit and 64-bit <depot>\JMP\JMP\10_0\Windows\JMP\setup.exe

JMP Macintosh 32-bit and 64-bit <depot>/JMP/JMP/10_0/Macintosh/JMP-10.dmg

JMP Pro Windows 32-bit and 64-bit <depot>\JMP\JMP_Pro\10_0\Windows\JMP\setup.exe

JMP Pro Macintosh 32-bit and 64-bit <depot>/JMP/JMP_Pro/10_0/Macintosh/ JMP-10.dmg


The following instructions detail how to break up the software depot with multiple installers. The first two steps are done by the administrator while the last two steps are performed by a user.

To divide the depot:

Administrator

1. Copy the installer from the depot. Copy the entire folder from:

<software depot>\JMP\JMP\10_0\Macintosh

<software depot>\JMP\JMP\10_0\Windows\JMP

<software depot>\JMP\JMP_Pro\10_0\Macintosh

<software depot>\JMP\JMP_Pro\10_0\Windows\JMP

to the desired location(s) that is accessible to your users.

2. Copy the license file from the depot.

The license file for JMP and JMP Pro is a text file in the <software depot>\sid_files folder. Each JMP will have a unique license file. It is important that you locate the correct file to use with each installer that you copy from the depot.

– Open <software depot>\install_doc\<order_number>\soi.html

– Locate the "Tech Support Site Number" line in the section that matches the Product(s) Ordered (JMP, JMP Pro) and the Operating System (Windows or Macintosh).


Figure 1.3 Technical Support Site Numbers

From the Software Order Information (SOI), the Tech Support Site Numbers are:

– JMP – Macintosh - 70087272

– JMP – Windows - 70087271

– JMP Pro – Macintosh - 70101280

– JMP Pro – Windows - 70101279

– The license files in the <software depot>\sid_files folder are:


Figure 1.4 License Files

Locate the file that has the Tech Support Site Number in the filename. The JMP and JMP Pro annual license installers contain the files needed to run in 32- and 64-bit mode.

– Copy that file to a location that will be accessible by the user after they install JMP and JMP Pro.

User

3. Install JMP.

A user can now install JMP and JMP Pro from the location that you created in step 1.

4. Apply the license to JMP.

After installation, users can launch JMP and JMP Pro. After launch, you will be prompted to provide your JMP license file. Click Open License and navigate to the location that you secured in step 2.

– Windows: After validation of the license file, you may be prompted for a location to store the license file. We recommend that you store the license file in the same location where JMP was installed.

– Macintosh: After validation of the license file, the license file will be saved as JMP.PER in the application bundle.

Adding Custom Files to a Software Depot

On Windows, 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 (*.*)

Place the custom files in a folder named custom.

1. Create the custom folder in the following location:

– JMP (Windows only): <SAS Software Depot>\JMP\JMP\10_0\Windows\JMP\custom

– JMP Pro (Windows only): <SAS Software Depot>\JMP\JMP_Pro\10_0\Windows\JMP\custom

2. Within the custom folder, create subfolders named scripts, pfs, and addins. Files will be copied from these folders.

Note: Any subfolders in the add-ins folder will also be copied.


The files are copied to:

• Windows XP: C:\Documents and Settings\All Users\Application Data\SAS\JMP\

• Windows Vista or Windows 7: C:\ProgramData\SAS\JMP\

Note: Scripts and preferences files are placed in a version # folder. Add-ins are placed in a folder called addins.

If you have only a DVD and have not downloaded the Software Depot, you need to copy the entire contents of the DVD to a location that is editable. This location can then be treated as your <Depot>. The JMP administrator can now add the files that will then be copied during installation.

Excel Add-in and JMP Installers

The installers for the JMP Excel Add-in files are built separately and differently than the JMP installers. The Excel Add-in installers are built as MSI installers and launched silently from the JMP installer.

Note that the Office 2003/2007 Primary Interop Assemblies (PIA) redistributables (o2003pia.msi and o2007pia.msi) are Microsoft Windows Installer packages that contains the Primary Interop Assemblies for Office 2003/2007 products. These are provided and installed by the JMP installer to ensure they are on the user’s PC.

Excel Add-in File Locations

The JMP Excel Add-in files are placed in the same folder as other JMP installed pieces, with one exception.

If the user chooses an installation folder other than the default, then all files, including Excel Add-in files, are installed in their selected location.

As part of the installation of the Excel Add-in files, any existing JMP Excel Add-in files are first uninstalled.

Table 1.2 Excel Add-in File Locations

OS JMP Excel JMP Folder (default) Excel Add-in Folder (default)

32 32 32 C:\Program Files\SAS\JMP\10 C:\Program Files\SAS\JMP\10

64 32 32 C:\Program Files (x86)\SAS\JMP\10 C:\Program Files (x86)\SAS\JMP\10

64 32 64 C:\Program Files (x86)\SAS\JMP\10 C:\Program Files (x86)\SAS\JMP\10

64 64 32 C:\Program Files\SAS\JMP\10 C:\Program Files (x86)\SAS\JMP\10

64 64 64 C:\Program Files\SAS\JMP\10 C:\Program Files\SAS\JMP\10


Excel Add-in Process - Part of JMP Install

The following is a list of Excel Add-in related files in the \Extra folder in a JMP software depot. These files are used during the installation of JMP.

• o2003pia.msi

• o2007pia.msi

• JMPProfilerCoreSetup.msi

• JMPProfilerCore_x64.msi

• JMPProfilerGUISetup.msi

• JMPProfilerGUI_2k3Setup.msi

• JMPProfilerGUISetup_x64.msi

The first two files are acquired from Microsoft. The remaining files are built at SAS and are used to install the add-in logic that allows Microsoft Excel and JMP to connect via a JMP add-in to Excel. The JMP installer searches for Excel and only runs these installs if Excel 2003, 2007 or 2010 is found.

If Excel 2003 is found, the following installers are silently launched, in this order:

• o2003pia.msi


• JMPProfilerGUI_2k3Setup.msi

If Excel 2007 is found, the following installers are silently launched, in this order:

• o2007pia.msi



If Excel 2010 is found, a further check is made to determine whether Excel 2010 is 32-bit or 64-bit.

If 32-bit Excel 2010, the following installers are silently launched, in this order:



If 64-bit Excel 2010, the following installers are silently launched, in this order:

• JMPProfilerCore_x64.msi

• JMPProfilerGUISetup_x64.msi

These files are found in software depots of JMP and JMP Pro. If you are confident that these files are not needed, there is no harm in deleting these files from the software depot before installation.


Excel Add-in Process - Outside of JMP Install

As part of the normal JMP install, files are included allowing you to install the Excel Add-in at a later time. This might be needed if a user did not install Excel at the time JMP was installed or if they need to uninstall/re-install the Excel Add-in files.

Install

These files are used to install the add-in logic that allow Microsoft Excel and JMP to connect via the JMP add-in to Excel. The installer files needed are located in <install_folder>\JMP\10\ExcelAddin.

Figure 1.5 Installer Files

Uninstall

1. In Windows, navigate to the uninstall program window under Control Panel.

2. Uninstall JMP Profiler Core.

3. Uninstall JMP Profiler GUI.

Silent Installation

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 for the Windows installers, which can be scripted for silent installation purposes. There are no silent installation capabilities for the JMP installers on the MacIntosh.


Note: Ensure Microsoft .NET is installed and all other system requirements are met before performing a silent installation.

To install JMP using a silent setup:

1. Create a response file (using .ISS extension).

setup.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:\, execute the following statement:

setup.exe -r -f1c:\silent.iss

2. To install JMP using silent setup, run the setup again using the response file:

setup.exe -s -f1{response filename}

Note that there is not a space between the -f1 parameter and the filename. For example, if you want to use the response file named silent.iss that resides on C:\, execute the following statement:

setup.exe -s -f1c:\silent.iss

Chapter 2Renewing and Upgrading

JMP License

This chapter describes how to renew or upgrade your JMP license. When it is time for your license to be renewed, you will receive an e-mail from SAS with the new license data in the form of a text file attachment. This text file should be saved and used to update the license.

Renewing Your JMP License

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 it 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.

To update JMP:

1. 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 choosing “Run as Administrator.”

2. Click Open License.

3. Continue with the instructions below for updating with either a SID file or a JMP.PER file.

To update JMP with a SID file:

1. At the prompt, navigate to where you saved the SID file sent to you in the e-mail from SAS.

2. Click Open.

3. (Optional) Fill in the Administrator Name and Department.

4. Click OK.

18 Renewing and Upgrading Chapter 2Upgrading Your JMP License

To update JMP with a JMP.PER file:

1. At the prompt, navigate to the new JMP.PER file.

2. Click Open.

Upgrading Your JMP License

If you have JMP installed on a multi-user operating system, JMP limits the number of concurrent JMP sessions based on the number of users your license supports.

After receiving a new SID file from SAS, replace the SID file in the original set of installation files that you received from SAS. This ensures that all new installations in the future use the latest license.

1. 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 choosing “Run as Administrator.”

2. Open a JMP script window.

3. Enter this line in the window and run it:

Renew License();

4. At the prompt, navigate to where you saved the new SID file sent to you in the e-mail from SAS.

5. Click Open License.

6. (Optional) Fill in the Administrator Name and Department.

7. Click OK.

Customizing the Expiration Message

You can create a text file whose contents are displayed in the warning message during your grace period before your JMP license expires. This ensures that all of your users can see information that you want them to know (such as contact information for the system administrator).

1. Create a text file named expirationMessage.txt. The name must match this exactly, including case. Otherwise, it is ignored.

2. In this text file, you can enter up to 512 characters.

3. Place this file in the same directory as the JMP.PER file. If you use a single network JMP.PER, place this text file there. Otherwise, you need to place this file on each user’s computer.

Chapter 3Frequently Asked Questions

JMP Installation

This chapter provides some frequently asked questions about JMP that you might find useful.

Frequently Asked Questions

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 Vista and Windows 7 operating systems. 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 choosing “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.

1. Connect your laptop to the network.

2. Start JMP to ensure that JMP on your laptop has access to the latest license file on the network.

3. 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, or else JMP will not run when disconnected.

How do I obtain maintenance upgrade to JMP software?

Maintenance upgrades are available from the JMP Web site (http://www.jmp.com/support/downloads/

jmp_software_updates.shtml).

Can I have two different versions of JMP installed on my computer at the same time?

Yes. JMP 10 can be installed on a computer with a previous version of JMP. The installation of JMP 10 does not remove the previous version and both versions are operable.

20 Frequently Asked Questions Chapter 3Frequently Asked Questions

If I have two versions of JMP installed on my computer, can I have the Excel Add-in on both versions?

No. The JMP 10 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 a licensed version of JMP over a demo or trial version of JMP?

No. You must first uninstall the demo version of JMP before installing the licensed 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 Web site (http://www.jmp.com/software/qualitystatement.shtml).

How do I report a problem I am having with JMP?

There are four ways that you can access SAS Technical Support:

• Telephone Support: You can receive telephone support by calling (919) 677-8008 between 9:00 AM and 5:00 PM Eastern Time.

• E-mail Support: You can communicate with SAS Technical Support by sending an e-mail to [email protected]. You can send messages 24 hours a day, seven days a week. You can use this method to report new problems and supply additional information to previously tracked problems.

• Internet Support: JMP Technical Support's Web site (http://www.jmp.com/support/index.shtml)offers a range of tools, tips, and information that is designed to help you solve your problem. You can search our Knowledge Base, browse our FAQ library, and use our FTP site to obtain technical information, fixes, and samples. You can also contact Technical Support by filling out an online Problem Report.

• Fax Support: You can fax your problem to (919)-677-4444. You can fax a problem 24 hours a day, 7 days a week.

If you are an international customer and are in need of technical support, please contact your local SAS international office.

Chapter 3 Frequently Asked Questions 21Frequently Asked Questions

When contacting Technical Support, please have the following information available:

• Your JMP® site or license number.

• The JMP® version that you are using.

• Your operating environment, such as Windows XP or Macintosh OS X.

• 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 under the Help menu on Windows or under the JMP menu on Macintosh.

22 Frequently Asked Questions Chapter 3Frequently Asked Questions

Appendix

This appendix provides supplementary information about JMP that you might find useful.

Extra Folder Files

The following is an alphabetical list of the possible files in the Extra folder in a Windows-based JMP software installer.

1. en_.net_framework_4_client_profile_x86_x64_508946.exe

2. ExtractPER32.exe

3. ExtractPER64.exe

4. JMPIconRefresh.exe

5. JMPProfilerCore_x64.msi

6. JMPProfilerCoreSetup.msi

7. JMPProfilerGUI_2k3Setup.msi

8. JMPProfilerGUISetup.msi

9. JMPProfilerGUISetup_x64.msi

10. jre-6u24-windows-i586.exe

11. jre-6u24-windows-x64.exe

12. o2003pia.msi

13. o2007pia.msi

14. vcredist_x64.exe

15. vcredist_x64_2010.exe



18. wic_x64_enu.exe

19. wic_x86_enu.exe

.NET Framework

1. en_.net_framework_4_client_profile_x86_x64_508946.exe

This file is from Microsoft® and it installs the needed operating system framework files needed to run applications developed using the latest software tools. JMP 10 needs .NET 4 on the PC to run. The .NET 4 installer included in JMP is the client profile, not the full .NET 4 installer.

24 Appendix

This file installs the needed files on either a 32-bit or 64-bit Windows operating system. During the installation of JMP, the Windows registry is checked to see whether .NET 4 is already installed (HKEY_LOCAL_MACHINE\Software\Microsoft\NET Framework Setup\NDP\v4). If .NET 4 is already installed, the JMP install continues. If .NET 4 is not already installed, the user is prompted with a Yes/No dialog asking to confirm the installation of .NET 4. If Yes, the .NET 4 install takes place silently as JMP continues the installation. If No, the JMP install terminates immediately.

The .NET 4 installation could take 10-20 minutes, so it is strongly suggested that other applications are closed before installation. After installation of JMP, if .NET 4 was installed, you should reboot the PC.

The .NET 4 file is found in software depots of JMP and JMP Pro. If you are confident that this file is not needed, there is no harm in deleting it from the software depot before installation. JMP will not run if .NET 4 is not installed properly.

PER File Extraction

2. ExtractPER32.exe

3. ExtractPER64.exe

The executable converts a license file found in the sid_files folder of the depot from TXT form into the needed JMP.PER file. The program places the JMP.PER file into the installation folder selected by the user.

• ExtractPER32 is the 32-bit version of the program designed for use on a PC with 32-bit operating system.

• ExtractPER64 is the 64-bit version of the program designed for use on a PC with 64-bit operating system.

These files are found in software depots of JMP and JMP Pro. If these files are deleted before installation, the PER file will not be created during the installation and JMP will prompt for the license file when first launched.

Icon Refresh

4. JMPIconRefresh.exe

This program makes a call to the operating system to refresh the desktop and is run at the end of the installation. It was created based on comments that the desktop icon was either not displaying or displaying without the JMP logo. A user can refresh using the F5 key, or this refresh program.

This file is found in software depots of JMP and JMP Pro. If this file is not wanted, there is no harm in deleting the file from the software depot before installation.

Excel Add-In

5. JMPProfilerCore_x64.msi

6. JMPProfilerCoreSetup.msi

7. JMPProfilerGUI_2k3Setup.msi

8. JMPProfilerGUISetup.msi

Appendix 25

9. JMPProfilerGUISetup_x64.msi

12. o2003pia.msi

13. o2007pia.msi

For more information, see “Excel Add-in and JMP Installers” on page 13.

Java

10. jre-6u24-windows-i586.exe

11. jre-6u24-windows-x64.exe

These files are from Oracle®/Sun®. They install the files for Java SE 6 Update 24 (internal numbering of 1.6.24). The OS is checked and jre-6u24-windows-i586.exe runs on a 32-bit OS and jre-6u24-windows-x64.exe runs on a 64-bit OS. The JMP installer does not check for other Java versions.

These files are found in software depots of JMP and JMP Pro. JMP needs Java 6 at a minimum to connect with SAS, so if a previous update of Java 6 is already on the PC, you do not need this update for JMP. If you are confident that these files are not needed because you are not connecting to SAS or already have required JRE, there is no harm in deleting these files from the software depot before installation.

Visual C++ Redistributables





These files are from Microsoft and are needed in JMP 10. They install the necessary Visual C++ Redistributable files. The JMP installer checks the operating system and installs vcredist_x86.exe and vcredist_x86_2010.exe if operating system is 32-bit and will install vcredist_x64.exe and vcredist_x64_2010.exe if operating system is 64-bit.

vcredist_x64.exe - Visual C++ 2008 - also known as Visual C++ 9.0 - 64-bit executable

vcredist_x64_2010.exe - Visual C++ 2010 - also known as Visual C++ 10.0 - 64-bit executable

vcredist_x86.exe - Visual C++ 2008 - also known as Visual C++ 9.0 - 32-bit executable

vcredist_x86_2010.exe - Visual C++ 2008 - also known as Visual C++ 9.0 - 32-bit executable

These files are found in software depots of JMP and JMP Pro. If you are confident that these files are not needed, there is no harm in deleting these files from the software depot before installation. JMP will not run if the proper level of Visual C++ files are not found. Our recommendation is not to delete these files from the depot and to let JMP install them.

Windows Imaging Component

18. wic_x64_enu.exe

19. wic_x86_enu.exe

26 Appendix

These files are from Microsoft and they install the Windows Imaging Component (WIC) files. These files are needed to support graphics framework used in JMP 10.

Starting with Windows XP Service Pack 3, these files were included in the operating systems. The JMP installer checks the operating system and installs these file only if the operating system is Windows XP Service Pack 2 or lower. These files are not executed if the operating system is Windows Vista or Windows 7. If the OS is checked and it is XP SP2 or lower, then wic_x86_enu.exe will run on a 32-bit OS and wic_x64_enu.exe will run on a 64-bit OS.

These files are found in software depots of JMP and JMP Pro. If you are confident that these files are not needed, there is no harm in deleting these files from the software depot before installation. JMP will not run if the proper level of WIC is not found.

Index

AAdding Custom Files 12

DDividing a Software Depot 8

EExcel Add-In 13Expiration Message

customize 18Extra Folder Files 23

FFrequently Asked Questions 19

IInstallation 3, 7

staging 6Installation Files

delivery 5

JJMP Installers

locating 8JMP License 17

renew 17upgrade 18

LLicense Control 6License Information 5

RRenew JMP License 17

Running JMP 7

SSilent Installation 15Software Depot 8System Requirements 3

UUpgrade JMP License 18