Main Support:       Knowledge Center
Documentation:   MQA English Doc   >  Previous Supported Releases   >  MQA 2017   >  MQA 2017 Quick Install and License Setup   >  MQA 2017 Quick Install-Windows

This document contains references to Agilent Technologies. Agilent's former Test and Measurement business has become Keysight Technologies. For more information, go to www.keysight.com.


Quick Install - Windows

MQA can be installed on a Windows machine after downloading the installation file from the Keysight EEsof EDA website, as illustrated.



                       

Obtain MQA License File

MQA requires a license to run. You can either apply for an Evaluation or a Purchased license. Once the license request is approved, a license file (with .lic extension) is sent as an email attachment. Save this file on your computer at C:\Program Files\Keysight\EEsof_License_Tools\bin\licenses .

Supported Platforms

For details on Supported Platforms, refer to the Supported Platforms section.

 

System Requirements

The following are Keysight recommended configurations:

RAM

Minimum 2 GB RAM recommended

Hard Disk Space

Minimum 1GB for a complete installation

CPU

Minimum Single-core

Dispaly

1024x768 or higher

Download MQA Installer

Click http://www.keysight.com/find/eesof-mqa-latest-downloads to download MQA.

Install MQA

To install MQA, run the downloaded MQA.exe installer. Follow the guided tour to complete the installation. During installation, the MQAHOME environment variable is added to the User Variables on your machine. You may want to verify that MQAHOME environment variable is set to the correct MQA installation folder. Right-click on the My Computer icon on your Windows desktop, select Properties and then Advanced system settings. Click *Environment Variables and look under User Variables for MQAHOME. It should be set to the installation folder of MQA on your machine, for example, C:\Keysight\MQA_2013_01.

MQA License Setup

License setup involves establishing a license server to serve the licenses and configuring the machine that runs MQA to checkout licenses from the license server. The machine on which license server is configured is known as license server machine, and machine which runs MQA and checks out licenses is known as the client machine.

Node-locked License

A node-locked license locks the software to a local machine. Both license server manager (lmgrd) and vendor daemon (agileesofd) run on the local machine for which the license is issued.

You must have system administrator privileges to setup node-locked licenses (Only) on Windows 7 machines.

To set up a node-locked license, follow the 2-step process:

Step 1: Start License Server Managers ( lmgrd and agileesofd )

Method 1

  1. Open the MS-DOS command prompt and change directory to the following path: C:\Program Files\Keysight\EEsof_License_Tools\bin.
  2. Run the following command by specifying the full path and location of the license file and the license log file, respectively:
    lmgrd.exe -c <license file path> -l <license log file path>
    where,
    • <license file path> specifies one or more full path-names to the license file(s).
    • <license log file path> is the full path-name to the debug log file.

Example
lmgrd.exe -c "C:\Program Files\Keysight\EEsof_License_Tools\licenses\license.lic" -l "C:\Program Files\Keysight\EEsof_License_Tools\my_server_log.txt"

Method 2

An alternative method is to:

  1. Create a file using Notepad and add the following command line:
    lmgrd.exe -c "C:\Program Files\Keysight\EEsof_License_Tools\licenses\license.lic" -l "C:\Program Files\Keysight\EEsof_License_Tools\my_server_log.txt"
  2. Save the file as autostart.bat.
  3. Double-click autostart.bat to start the license server.

Whenever the license server machine restarts, you need to run the lmgrd command manually to restart the license server.

Alternatively, you can configure the program to start automatically with the computer using the following steps:

  1. Select Start > All Programs > Startup , right-click the Startup folder and then click Open.
  2. Copy the autostart.bat file which generated in the Method 2 to the popup folder.

Be sure to allow the program to run automatically next time when you restart the computer. The configuration on the server is now complete.

Step 2: Set Product Environment Variable

For MQA to run successfully, it must be able to find the license server and checkout a license. Set the MQA_LICENSE_FILE environment variable that MQA uses to find the license server and request a license.

Right-click on My Computer, select the Properties menu, and then click the Advanced tab or Advanced system settings. Click the Environment Variables button. Add the MQA_LICENSE_FILE variable and append the value using the format port@host.domain. Here, host can be either the hostname or IP address of the license server computer, for example, @127.0.0.1, @localhost, or 27001@myServer.myCompany.com).

Floating License

In a floating license, license server manager (lmgrd) and vendor daemon (agileesofd) run on the license server machine, while MQA runs on the client machine.

Setting up floating license on Linux is a 2-step process where both server-side setup and client-side setup are needed.

Step 1: Server-side setup

  1. Install Keysight EEsof Licensing Tools
    Download Keysight EEsof Licensing Tools for Windows to setup your licenses to run MQA. To install, run the downloaded Keysight EEsof Licensing Tools Software and follow the on-screen instructions. By default, Keysight EEsof Licensing Tools is installed at C:\Program Files\Keysight\EEsof_License_Tools.
  2. Start License Server Managers ( lmgrd and agileesofd )
    Follow the step 1 as described in Node-locked License section.

Step 2: Client-side setup

Once the license is configured successfully, configure each client machine to point to the network license server or license server machine. You can perform this step manually by setting up product environment variables. For details, refer to step 2 of Node-locked License Setup section.

Launch MQA

To run MQA, select Start > Programs > MQA <release_number> > MQA <release_number>.

Please help us improve
Please help us improve
Was this topic helpful?