eagle license management

5/20/2018 EAGLE License Management

1/42

EAGLE L icense Management

EAGLE LICENSE MANAGEMENT

1 Feb 2014

A Product of Raytheon Company1997-2013 Raytheon Company

ALL RIGHTS RESERVEDU.S. Patents 5,457,792; 5,493,679; 5,737,532

4,847,795

Made in the U.S.A.

Enhanced

AutomatedGraphical

Logistics

Environment


2/42


COPYRIGHT 1997-2014 RAYTHEON COMPANY

UNPUBLISHED WORK - ALL RIGHTS RESERVED.

This document shall not be published, or disclosed to others, or duplicated in

whole or in part without written permission of Raytheon Company.

All other company and product names used herein may be the trademarks or

registered trademarks of their respective companies.

Information in this manual may change without notice and does not represent a

commitment on the part of Raytheon Company and its subsidiaries.

Revision History

Printed September 1 2009 First Edition

Revised September 1 2009

Revised September 2 2009Revised December 13, 2010

Revised May 9, 2011

Revised September 20, 2011

Revised April 13, 2012Revised August 1, 2013

Revised February 1, 2014

Printed August 2013


3/42


TABLE

OF

CONTENTS


4/42


5/42

EAGLE LICENSE MANAGEMENT TABLE OF CONTENTS

v

TABLE OF CONTENTS

SECTION 1 OVERVIEW OF LICENSE MANAGEMENT ................................... 1-3

1.0INTRODUCTION ............................................................................................................... 1-3

1.1OVERVIEW ............................................................................................................................ 1-31.2LICENSE MANAGEMENT IN EAGLE ..................................................................................... 1-3

1.3FLEXNET PUBLISHER LICENSE MANAGEMENT SYSTEM...................................................... 1-3

1.4HOW FLEXNET PUBLISHER AFFECTS THE EAGLEEXPERIENCE......................................... 1-3

1.5FLOATING LICENSES............................................................................................................. 1-3

1.6COMPLICATIONS WITH FLOATING LICENSES......................................................................... 1-4

1.7FIXED LICENSES.................................................................................................................... 1-4

1.8THE LICENSE FILE ................................................................................................................ 1-4

SECTION 2 THE LICENSE FILE ............................................................................. 2-3

2.0INTRODUCTION ..................................................................................................................... 2-3

2.1DECIDE BETWEEN FLOATING OR FIXED LICENSES................................................................ 2-3

2.2NOTES ON DESKTOP VIRTUALIZATION SOFTWARE............................................................... 2-4

2.3FIXED LICENSES.................................................................................................................... 2-4

2.4FLOATING LICENSES............................................................................................................. 2-7

SECTION 3 TROUBLESHOOTING ........................................................................... 27


6/42


7/42


LIST

OF

ILLUSTRATIONS


8/42


9/42

EAGLE LICENSE MANAGEMENT LIST OF ILLUSTRATIONS

ix

LIST OF ILLUSTRATIONS

FIGURE PAGE

Figure 1. Obtaining Required HOSTID Information. .................................................................... 2-4

Figure 2. FLEXnet License Finder. .............................................................................................. 2-5

Figure 3. Specifying the License File Location. ............................................................................ 2-6

Figure 4. Finder Completed. .......................................................................................................... 2-6

Figure 5. Unable to Locate License. .............................................................................................. 2-7

Figure 6. Choose an Installation Folder. ........................................................................................ 2-8

Figure 7. Upgrading a Previous Installation of FLEXnet Publisher License Server Manager....... 2-8

Figure 8. Confirm Details. ............................................................................................................. 2-9

Figure 9. Install Visual C++ 2005 SP1 Redistributable Package. .................................................. 2-9

Figure 10. Microsoft Visual C++ 2005 SP1 Redistributable Package License Terms. ............... 2-10

Figure 11. Configuring HTTP and License Server Port Numbers. .............................................. 2-11

Figure 12. License Service Options ............................................................................................. 2-11

Figure 13. Installation Confirmed. ............................................................................................... 2-12

Figure 14. The FLEXnet License Administrator Dashboard. ...................................................... 2-13Figure 15. Selecting the Vendor Daemon Configuration Tab. .................................................... 2-14

Figure 16. Accessing the License Import Function. .................................................................... 2-15

Figure 17. The Import License File Screen.................................................................................. 2-16

Figure 18. The Vendor Daemons Screen. .................................................................................... 2-17

Figure 19. The Vendor Daemon: EAGLELM Screen. ................................................................ 2-18

Figure 20. RUNNING_PENDING Status. .................................................................................. 2-19

Figure 21. Reread License Files................................................................................................... 2-20

Figure 22. Successfully Installed License File and Vendor Daemon........................................... 2-21

Figure 23. FLEXnet License Finder. ........................................................................................... 2-22Figure 24. Specifying the License Server Location. .................................................................... 2-22

Figure 25. Successfully Located License Server. ........................................................................ 2-23Figure 26. Network Connectivity Message. ................................................................................. 2-23

Figure 27. Unable to Locate License. .......................................................................................... 2-24


10/42


11/42


SECTION 1

OVERVIEW

OF LICENSE

MANAGEMENT


12/42

EAGLE LICENSE MANAGEMENT SECTION 1: OVERVIEW OF LICENSE MANAGEMENT

1-3

SECTION 1 OVERVIEW OF LICENSE MANAGEMENT

1.0INTRODUCTION

This section outlines the concept of license management.

1.1Overview

In todays software industry, software is not purchased. Instead of purchasing software,one generally purchases the right to use a piece of software in a specific way. This right is called a

software license. License management is the mechanism that ensures software is being used

according to the terms of the software license agreement. Flexibility in software licensing

agreements allow software to be sold and priced in several different ways; e.g., perpetual,

subscription, per-seat, per-user, etc.

1.2License Management in EAGLE

EAGLE usage rights are currently offered under a perpetual license, with either site or

per-seat licensing models.

1.3FLEXnet Publisher License Management System

It is important to note that the usage rights to EAGLE have not changed; for most users,

EAGLE has always been offered as a perpetual license, with either per-site or per-seat usage

rights. EAGLE incorporates a license management system that assures the user they are not in

violation of the terms of their license agreement. This license management system is calledFLEXnet Publisher.

1.4How FLEXnet Publisher Affects the EAGLE Experience

Each time EAGLE is launched, it will attempt to verify that, if run, it will not violate the

terms of the license agreement. It achieves this by checking out a license for use. The licensecan be obtained from one of two places: The hard drive of the local machine, or a license server.

1.5Floating Licenses

Obtaining a license from a license server is referred to as floating, or concurrent

licensing. The license server is a central repository for all of the EAGLE licenses purchased by anentity. Any computer that can connect to the license server over a network can obtain a license

from the license server. A special piece of software (the licensing service) is installed on the

license server that keeps track of which workstations are using licensed products and how many

more licenses are available for use.


13/42

EAGLE LICENSE MANAGEMENT SECTION 1: OVERVIEW OF LICENSE MANAGEMENT

1-4

1.6Complications with Floating Licenses

Floating licenses are the most flexible licensing configuration offered by RaytheonEAGLE. The cost of a floating license is the same as a fixed licenseso floating licenses are

recommended when they are practical. However, there are situations where floating licenses

cannot be used, such as the lack of a suitable license server or a complex IT configuration in

which it may not be guaranteed that each workstation is able to connect to the license server. Inthis situation, the licenses may be split among several license servers or fixed licenses may be

used.

1.7Fixed Licenses

A fixed or node-lockedlicense is appropriate when the software is intended to be used

on a specific workstation. In the case where floating licenses are impractical, an equivalent

number of fixed licenses for the software may be issued instead.

1.8 The License File

The significant terms of the license agreement are configured by Raytheon EAGLE

through the use of a text file called a license file. In the case of a floating license configuration,

each license server will have a single license file which contains information about the numberand type of software licenses that server has the ability to check out. In the case of a fixed

license configuration, each workstation intended to run the EAGLE software will need its own

license file. The next section contains information about obtaining the proper license file(s) from

the Raytheon EAGLE Help Desk.

NOTE: PLEASE DO NOT UPGRADE YOUR EXISTING EAGLE DATABASE

WITHOUT OBTAINING AND TESTING YOUR LICENSE FILE(S). It can be very difficult to

return your database to a working state if an upgrade-related license management problem

prevents EAGLE from running. The license file(s) are tested by installing the upgraded client and

launching the EAGLE software. If the log-in screen appears, then the license file(s) is/are

working correctly.


14/42


SECTION

THE

LICENSE

F ILE


15/42

EAGLE LICENSE MANAGEMENT SECTION 2: THE LICENSE FILE

2-3

SECTION 2THE LICENSE FILE

2.0Introduction

This section provides a set of instructions for obtaining a license file from the EAGLE

Help Desk.

2.1Decide Between Floating or Fixed Licenses

Raytheon EAGLE recommends using floating licenses whenever possible; however, to

do so will require the use of a license server, which is a networked computer that can be contacted

by each workstation intended to run the EAGLE software.

The license server must be one of the following Windows platforms:

Microsoft Server 2008, including SP2

Windows Server 2003, including SP1 and R2.

Windows 7 Business, Enterprise or Ultimate

Windows Vista, including SP2Business, Enterprise or Ultimate

If floating licenses are not practical, then fixed licenses can be used. This means that a

separate license file will be issued for each workstation.

For either fixed or floating licenses, certain information must be sent to the EAGLE Help

Desk about each machine that will host a license file.

STEP To obtain a license file from the EAGLE Help Desk (refer toFigure 1):

Contact the EAGLE Help Desk to obtain the license management package. Inside the package, run the lmtools.exe executable. Click the SYSTEM SETTINGS tab. In the lower right corner, click the SAVE HOSTID INFO TO A FILE button. You are prompted with a Save As window. Save the information file and send it

to the EAGLE Help Desk ([email protected]). When doing so, please

note whether you are requesting a fixed or a floating license, and whether you will

require EAGLE 8.x compatibility (license files were simplified starting with EAGLE

9.0).
mailto:[email protected]:[email protected]:[email protected]:[email protected]


16/42


2-4

Figure 1. Obtaining Required HOSTID Information.

2.2Notes on Desktop Virtualization Software

If your IT configuration requires EAGLE users to connect via desktop virtualization

software (e.g., Citrix or Microsoft Terminal Services), it is generally required that the

virtualization server be a license server or have connectivity to a valid license server (See2.1 for

requirements). Ensure that the virtualization server allows connectivity to the license service from

within the virtualized desktop (e.g., that the server does not block the network resource or port).

A fixed license (see2.3below) can be provided for a virtualization server if necessary.

However, please be advised that as a fixed license it can only allow one copy of EAGLE to run at

a time, regardless of which user is utilizing it.

2.3Fixed Licenses

If you have requested a fixed license, you will receive a license that activates EAGLE for

the workstation corresponding to the information file you sent to the EAGLE Help Desk. Save

this file in a convenient, easily remembered location. Please note this will be the permanent

location of the license file.

NOTE: We recommend placing the license file in the default directory located in the common

application data folder. For example, in Windows XP, the default license file directory would be

C:\Documents and Settings\All Users\Application Data\EAGLE\Licenses. Please seeTable 1

below for a list of default locations.


17/42


2-5

Table 1. Default License File Locations

Platform License File Location

Windows XP x86 and x64 C:\Documents and Settings\All Users\Application Data\EAGLE\Licenses

Windows Vista x86 and x64 C:\ProgramData\EAGLE\Licenses

Windows 7 x86 and x64 C:\ProgramData\EAGLE\Licenses

Windows Server 2003 x86 and x64 C:\Documents and Settings\All Users\Application Data\EAGLE\Licenses

Windows Server 2008 x86 and x64 C:\ProgramData\EAGLE\Licenses

When launching EAGLE for the first time, you will receive a dialog box as shown inFigure 2.

Figure 2. FLEXnet License Finder.

Choose SPECIFY THE LICENSE FILE and click NEXT. You will then be prompted

to locate the file (Figure 3). If you remember the path name, you can type it in directly or choose

BROWSE and browse for the file.


18/42


2-6

Figure 3. Specifying the License File Location.

Once you have selected the license file, click NEXT. A confirmation message will

appear (Figure 4). EAGLE will then attempt to launch and utilize the license in the license file. Ifyou are successful, the EAGLE Login Screen will appear.

Figure 4. Finder Completed.

If, for some reason, you were unsuccessful, you will receive an error message (Figure 5).

Please create a screen shot of this error message and forward it to the EAGLE Help Desk for

resolution.


19/42


2-7

Figure 5. Unable to Locate License.

2.4Floating Licenses

To implement floating licenses, you must install the lmadmin utility on the machine thatwill be used to serve the licenses. If you do not already have the lmadmin utility, it can be

obtained from the EAGLE Help Desk.

NOTE: If you already have a FLEXnet server (previously referred to as a Flex LM

Server), you may not need to install a new license server. Please contact the EAGLE Help Deskif you would like more information on utilizing a previously existing FLEXnet Server.

Prerequisites:

Java 1.5 or higher

STEP To install the lmadmin utility:

Obtain the executable from the EAGLE Help Desk. You must be able to run the executable as an Administrator. If you have

administrator privileges, launch the executable. Read the introduction screen and click Next. On the next screen (Figure 6), choose the install location. This will probably be

where you will want to store your license file(s) also.


20/42


2-8

Figure 6. Choose an Installation Folder.

The following screen is useful if you have chosen to upgrade a previous version of

the FLEXNet License Server (e.g., Flex LM License Server). If you wish to do this,

enter the path of the previous installation here and check the YES IMPORT

checkbox. Otherwise, just click NEXT.

Figure 7. Upgrading a Previous Installation of FLEXnet Publisher License Server Manager.


21/42


2-9

Confirm your details on the next screen (Figure 8)and click INSTALL.

Figure 8. Confirm Details.

Toward the end of the installation, you will be asked to install the Visual C++ 2005

SP1 Redistributable Package (Figure 9). Click the INSTALL VISUAL C++

REDISTRIBUTABLE PACKAGE check box and click NEXT.

Figure 9. Install Visual C++ 2005 SP1 Redistributable Package.


22/42


2-10

Read and accept the license agreement for Microsoft Visual C++ 2005

Redistributable Package (Figure 10).

Figure 10. Microsoft Visual C++ 2005 SP1 Redistributable Package License Terms.

You are now given the opportunity (Figure 11)to configure the HTTP Port Number

(used to access the License Server console) and the License Server Port Number

(which EAGLE will use to contact the license server and obtain a license). If you

choose to change them from the default, do so here and make a note of your changes.

In this manual, the default values will be used.


23/42


2-11

Figure 11. Configuring HTTP and License Server Port Numbers.

In a typical case, the license server is installed as a service in the Windows Services

control panel, and starts up the EAGLE License Server automatically. The followingscreen (Figure 12)offers you the opportunity to customize the service name (as it

appears in the Services control panel) and the delay before starting. If you choose

not to run the server as a service, uncheck the RUN AS A SERVICE check box. In

this case, the license server will need to be started manually (not recommended).

Figure 12. License Service Options


24/42


2-12

When you see the following screen (Figure 13), click DONE.

Figure 13. Installation Confirmed.

The new lmadmin service is now set to automatically start when the server is booted.

You may either reboot now, or if this isnt practical, manually start the server as follows:

STEP To start the lmadmin service manually:

Access the Services control panel. Locate the lmadmin service.

Right click on the lmadmin service and choose START.

Once the LMADMIN service has started, the administrator console can be accessed by

opening a browser window on the machine and navigating tohttp://localhost:8080. The console

can also be accessed remotely by navigating tohttp://yourservername:8080,where

yourservername is the actual machine name of the server as found on your network. Pleaseaccess the console at this time. You will be required to log in; the default user name is admin

and the password is admin. After logging in for the first time, you will be requested to change

the default password. Once this is complete, you will be taken to the FLEXnet License

Administrator dashboard (Figure 14).
http://localhost:8080/http://localhost:8080/http://localhost:8080/http://yourservername:8080/http://yourservername:8080/http://yourservername:8080/http://yourservername:8080/http://localhost:8080/


25/42


2-13

Figure 14. The FLEXnet License Administrator Dashboard.

Once LMADMIN has been installed and the license server is running, you will need to

install the EAGLE vendor daemon and the EAGLE License File. Copy the vendor daemon

executable (EAGLELM.exe) into the install directory for the license server manager, e.g.,

C:\Program Files\FLEXnet Publisher License Server Manager by default.

STEP To configure the FLEXnet License Administrator for use with EAGLE:

Start the FLEXnet License Administrator console if it is not up already. Access the ADMINISTRATION functions by clicking on the word Administration

in the upper right corner. Then select the VENDOR DAEMON CONFIGURATION

tab (Figure 15).


26/42


2-14

Figure 15. Selecting the Vendor Daemon Configuration Tab.

Once you have reached the Vendor Daemon Configuration screen, choose the

IMPORT LICENSE button (Figure 16). Your screen may differ slightly from the

figure as it may include the demo vendor daemon. You may remove the demo

vendor daemon (if you wish) by clicking the word DELETE on the demo line.


27/42


2-15

Figure 16. Accessing the License Import Function.

On the IMPORT LICENSE FILE screen (Figure 17), enter the path name of the

license file you received from the EAGLE Help Desk, or use the BROWSE button to

find it. Once you have located the license, click the IMPORT LICENSE button.


28/42


2-16

Figure 17. The Import License File Screen.

NOTE: Certain errors are expected. If you receive a License File Already Exists error, you may

have attempted to import the license file previously and were unsuccessful. In this case, you mayuse the OVERWRITE LICENSE FILE ON LICENSE SERVER check box before importing.

Make sure this is an EAGLE license you are overwriting, and not the license file for another

FLEXnet enabled application. You will also receive the error Unable to start vendor:

EAGLELM and another warning stating that there is a Missing executable for EAGLELMvendor. The next step correctsthis error. Click the OK button.

You will now see the VENDOR DAEMONS screen (Figure 18). Click

ADMINISTER on the EAGLELM vendor daemon.


29/42


2-17

Figure 18. The Vendor Daemons Screen.

On the VENDOR DAEMON: EAGLELM screen (Figure 19), under GENERAL

CONFIGURATION > VENDOR DAEMON LOCATION, enter the location of the

EAGLELM.EXE vendor daemon that you received from the EAGLE Help Desk

then click SAVE. Note that this is typically only required if you have placed theEAGLELM.exe vendor daemon in a non-default location.


30/42


2-18

Figure 19. The Vendor Daemon: EAGLELM Screen.

Now click the START button. You will return to the VENDOR DAEMONS screen

(Figure 20), only now EAGLELM will have a RUNNING_PENDING status. Click

the word ADMINISTER again.


31/42


2-19

Figure 20. RUNNING_PENDING Status.

You will now see the VENDOR DAEMON: EAGLELM screen again (Figure 21).

Click the REREAD LICENSE FILES button.


32/42


2-20

Figure 21. Reread License Files.

You should now return to the VENDOR DAEMONS screen and have a green notice

at the top of the screen that says The license file was successfully reread.Additionally, the EAGLELM vendor daemon should have a status of RUNNING.

This indicates the license file was successfully installed and the vendor daemon is

running as expected (Figure 22).


33/42


2-21

Figure 22. Successfully Installed License File and Vendor Daemon

NOTE: If you cannot successfully start the license server or the EAGLELM vendor daemon,

please locate the EAGLELM.log and lmadmin.log files and contact the EAGLE Help Desk.These log files are, by default, in C:\Program Files\FLEXnet Publisher License Server

Manager\logs.

You now must instruct your users how to contact the license server. When the userlaunches EAGLE for the first time, they will receive a dialog box as shown inFigure

23.


34/42


2-22

Figure 23. FLEXnet License Finder.

They should choose SPECIFY THE LICENSE SERVER SYSTEM and click NEXT.

They will then be prompted to type in the name of the license server (Figure 24). Have the userenter the name of the license server in this box. Note that depending on the IT configuration, they

may need to enter only the machine name (i.e., my_server), the fully qualified machine name (i.e.,

my_server.my_domain.com, or the IP address (i.e., 255.255.255.255). If the license server is

configured to listen on a port other than those within the default range of 27000-27009, you wouldenter the port number as part of the computer name; e.g., 27010@my_server.my_domain.com.

Figure 24. Specifying the License Server Location.

Once you have selected the license server, click NEXT. If you successfully connect to

the license server, you will receive a confirmation box as shown in (Figure 25).


35/42


2-23

Figure 25. Successfully Located License Server.

If the license finder was unable to locate the license server, you will receive a message

similar to the one shown inFigure 26. This message indicates that the client computer is unable to

contact the license server due to a network connectivity issue that is independent of the EAGLELicense Management system. Ensure that you can ping the license server. If all else fails, using

the IP address instead of the server name usually works on a temporary basis (since many IT

configurations use dynamic IP addressing, in which case the address of the server may change in

the future).

Figure 26. Network Connectivity Message.

If the client computer was able to contact the license server but the request for a license

was rejected, you will receive a different error message such as the one inFigure 27. Please create

a screen shot of this error message and forward it to the EAGLE Help Desk for resolution.

Incidentally, the example error shown indicates that you should log into the administration consoleand ensure that the EAGLELM vendor daemon is started.


36/42


2-24

Figure 27. Unable to Locate License.


37/42


SECTION

TROUBLESHOOTING


38/42


39/42

EAGLE LICENSE MANAGEMENT SECTION 3: TROUBLESHOOTING

SECTION 3TROUBLESHOOTING

LICENSE FILE EXPIRED

If the license file expires while the license server is up, the EAGLE client will display anerror message saying that the license is expired when attempting to check out a license. However,

if the license file expires while the license server is down, the license service will refuse to come

up. In either case, obtain a new license file by contacting the EAGLE Help Desk. Install the new

license file as shown inFigure 17. You will need to check the box labeled OVERWRITE

LICENSE FILE ON LICENSE SERVER.

CANNOT ACCESS LICENSE SERVER CONSOLE

Ensure that the lmadmin service is running.

Ensure that port 8080 (or whichever port was set during installation) is properly

configured in your firewall software.

VENDOR DAEMON STATUS SHOWS DOWN ON ADMINISTRATION CONSOLE

Start the vendor daemon by clicking ADMINISTER, then START.

If the vendor daemon will not stay up, attempt to restart the service using the

Services control panel.

If the vendor daemon still will not stay up, examine the vendor daemon log file,

EAGLELM.log (found in the logs folder under the installation directory). There will

likely be an error message toward the end of the file. The most common problems

are an expired license file or a firewall configuration issue (see LICENSE FILE

EXPIRED or PORT CONFIGURATION INFORMATION).

PORT CONFIGURATION INFORMATION

In a simple license server configuration, there are three components to the EAGLE

license management system: The license server (lmadmin.exe or lmgrd.exe), the vendor daemon

(EAGLELM.exe), and the EAGLE client. The EAGLE client requires communication with thelicense server, and the license server requires communication with the vendor daemon. The

following are the ports required by default:

License administration console (lmadmin only): TCP Port 8080

License service / client communication: TCP Ports 27000-27009 License service / vendor daemon: Random.

The ports for each of the above can be set to a custom value to enable compatibility with

IT rulesets.

License administration console: During installation (seeFigure 11), or through the

administration console (Server Configuration Tab > Web Server Configuration


40/42


heading). Note that resetting the HTTP port through the License Administration

Console will result in disconnection from the console.

License service / client communication: The port must be set on both the license

service and the client.

The license service port can be configured during installation (seeFigure 11)or

through the License Administration Console (Server Configuration Tab >License Server Configuration header). Note that changing the License Server

Manager Port will likely require restarting the license server.

The client can be configured in multiple ways depending upon how the client

was configured to find the license server. Most administrators configure their

clients according to this document (by using the FLEXnet License finder). SeeCLIENT RECONFIGURATION.

License service / vendor daemon communication: This is typically only required

under the strictest IT requirements, as both the license service and the vendor

daemon are typically co-located on the same server. However, the two programs

communicate using TCP even though they are located on the same host. The vendor

daemon port can be configured in the License Administration Console (VendorDaemon Configuration tab > Administer link for EAGLELM > Vendor Daemon

Port. The vendor daemon will likely need to be restarted.

LICENSE FILE EXPIRED

To replace a concurrent or floatinglicense file (i.e., installed on a license server),

follow the instructions for MOVING TO A NEW LICENSE SERVER.

To replace a fixed or node-lockedlicenses (i.e., installed directly on the client

computer), obtain a new license file from the EAGLE Help Desk as described in section 2.1, then

follow the instructions for CLIENT RECONFIGURATION.

MOVING TO A NEW LICENSE SERVER

In the event that the EAGLE License Management service needs to be moved to another

server, obtain a new license file from the EAGLE Help Desk as described in section2.1 thensimply follow the instructions in this document again. After moving the license server, any

existing EAGLE or EAGLE Publishing System clients will need to be updated to seek a license

from the new server. See CLIENT RECONFIGURATION for further instruction.


41/42


CLIENT RECONFIGURATION

If the client is already running, go to Help > Display EAGLE license location / search

path. A dialog box will be presented, and answering Yes to the dialog box will have the effect

of clearing the EAGLE license location / search path. If the client is not running, launch the

client. An error will be displayed informing the user why a license was unable to be checked out.Acknowledging this screen will display the EAGLE license location / search path dialog box.

Answering yes to this dialog box will have the effect of clearing the EAGLE license location /

search path. When the EAGLE license location / search path is empty, the user is presented with

the FLEXnet License Finder as shown inFigure 2. The new computer name (with port number, if

required) may now be specified.


42/42


Enhanced

AutomatedGraphical

Logistics

Environment

Technical support is provided by the EAGLE Team of Raytheon Company. Phone support isavailable Monday through Friday from 8:00 a.m. to 4:30 p.m. Mountain Standard Time. EAGLE

technical support personnel can be reached at (520) 663-6673. Training on the EAGLE product is

available.

Are you ready for EAGLE? Join Team EAGLE and find out what its like to soar. Give yourlogistics software product the EAGLE advantage. For more information on becoming part ofTeam EAGLE, contact:

Raytheon Company

Team EAGLE

(520) 663-6673Email: [email protected]

eagle license management

Documents

overview of license

license file

floating licenses

fixed licenses

icense managementcopyright

product names

respective companies

revision historyprinted