Emlab: Installation Guide

FEMLAB
Installation Guide
V ERSION
3.0a
How to contact COMSOL: Denmark

COMSOL A/S Rosenkret 11C DK-2860 Sborg Phone: +45 39 66 56 50 Fax: +45 39 66 56 20 info@comsol.dk www.comsol.dk Fax: +49-551-99721-29 info@femlab.de www.femlab.de
United States
COMSOL, Inc. 8 New England Executive Park Suite 310 Burlington, MA 01803 Phone: +1-781-273-3322 Fax: +1-781-273-6603 info@comsol.com www.comsol.com COMSOL, Inc. 1100 Glendon Avenue 17th Floor Los Angeles, CA 90024 Phone: +1-310-689-7250 Fax: +1-310-689-7527 info@comsol.com www.comsol.com For a complete list of international representatives, visit www.comsol.com/contact
Norway
COMSOL AS Verftsgata 4 NO-7485 Trondheim Phone: +47 73 84 24 00 Fax: +47 73 84 24 01 info@comsol.no www.comsol.no
Finland
COMSOL OY Lauttasaarentie 52 FIN-00200 Helsinki Phone: +358 9 2510 400 Fax: +358 9 2510 4010 info@comsol.fi www.comsol.fi
Sweden
COMSOL AB Tegnrgatan 23 SE-111 40 Stockholm Phone: +46 8 412 95 00 Fax: +46 8 412 95 10 info@comsol.se www.comsol.se
France
COMSOL France 19 rue des bergers F-38000 Grenoble Phone: +33 (0)4 76 46 49 01 Fax: +33 (0)4 76 46 07 42 info@comsol.fr www.comsol.fr
United Kingdom
COMSOL Ltd. John Eccles House Robert Robinson Avenue The Oxford Science Park Oxford OX4 4GP Phone:+44-1865-338-036 Fax: +44-1865-338-106 info.uk@comsol.com www.uk.comsol.com
Company home page

www.comsol.com
Technical support
support@comsol.com
Germany
FEMLAB GmbH Berliner Str. 4 D-37073 Gttingen Phone: +49-551-99721-0
Product suggestions
suggest@comsol.com
FEMLAB Installation Guide COPYRIGHT 1994 - 2004 by COMSOL AB. All rights reserved Patent pending
The software described in this document is furnished under a license agreement. The software may be used or copied only under the terms of the license agreement. No part of this manual may be photocopied or reproduced in any form without prior written consent from COMSOL AB. FEMLAB is a registered trademark of COMSOL AB. Other product or brand names are trademarks or registered trademarks of their respective holders.
Version:
April 2004
FEMLAB 3.0a
C O N T E N T S
Chapter 1: Installation Guide
General Tips FEMLAB Quick Start and Online Help . . . . . . . . . . . . . . . Technical Support . . . . . . . . . . . . . . . . . . . . . . System Requirements General Requirements . . . . . . . . . . . . . . . . . . . . . System Requirements for Microsoft Windows . . . . . . . . . . . . System Requirements for UNIX/Linux . . . . . . . . . . . . . . . System Requirements for Mac OS X . . . . . . . . . . . . . . . Installing FEMLAB on Windows Before You Begin . . . . . . . . . . . . . . . . . . . . . . . Installing FEMLAB 3.0a . . . . . . . . . . . . . . . . . . . . . 2 2 2 3 3 3 4 5 6 6 7
Removing (Uninstalling) the FEMLAB Installation . . . . . . . . . . . 13 Running FEMLAB on Windows 15
Running FEMLAB . . . . . . . . . . . . . . . . . . . . . . . 15 Running FEMLAB with MATLAB . . . . . . . . . . . . . . . . . 16 Running FEMLAB 2.3 . . . . . . . . . . . . . . . . . . . . . 16 Installing FEMLAB on UNIX/Linux 17
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . 17 Installing FEMLAB 3.0a . . . . . . . . . . . . . . . . . . . . . 17 Optional FEMLAB 2.3 Installation. . . . . . . . . . . . . . . . . 18 Removing (Uninstalling) the FEMLAB Installation . . . . . . . . . . . 19 Running FEMLAB on UNIX/Linux 20
Running FEMLAB . . . . . . . . . . . . . . . . . . . . . . . 20 Running FEMLAB with MATLAB . . . . . . . . . . . . . . . . . 20 Running FEMLAB 2.3 . . . . . . . . . . . . . . . . . . . . . 20
CONTENTS
|i
Installing FEMLAB on Mac OS X
21
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . 21 Installing FEMLAB 3.0a . . . . . . . . . . . . . . . . . . . . . 22 Removing (Uninstalling) the FEMLAB Installation . . . . . . . . . . . 22 Running FEMLAB on Mac OS X 23
The FEMLAB Applications . . . . . . . . . . . . . . . . . . . 23 Running FEMLAB from a Terminal Window . . . . . . . . . . . . . 24 Running FEMLAB 2.3 . . . . . . . . . . . . . . . . . . . . . 24 License Manager Installation 25
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . 25 License Manager Installation on PC/Windows . . . . . . . . . . . . 27 License Manager Installation on UNIX/Linux . . . . . . . . . . . . 29 License Manager Installation on Mac OS X . . . . . . . . . . . . . 33 Running FEMLAB Client/Server 37
Advantages of Using FEMLAB Client/Server. . . . . . . . . . . . . 37 Running FEMLAB Client/Server . . . . . . . . . . . . . . . . . 37 Optimizing Memory Use Mounting the CD-ROM on HP-UX Login Information and Security Login Information 40 41 42
. . . . . . . . . . . . . . . . . . . . . . 42
Client/Server Security Issues . . . . . . . . . . . . . . . . . . 42 Troubleshooting Graphics 43
Chapter 2: License Agreement

COMSOL Software License Agreement INDEX 48 I-1
ii | C O N T E N T S
Installation Guide
Gen er al T ip s
Welcome to FEMLAB 3.0a! Use this Installation Guide to install your copy of FEMLAB and start working with this package. If you already have installed FEMLAB 3.0, you can upgrade to FEMLAB 3.0a from the COMSOL web site at www.comsol.com/support/updates . There you will also find additional models for download. See the FEMLAB 3.0a Release Notes for more information. In addition to this manual, we supply many other resources to help you get the most out of FEMLAB. Among them are:
FEMLAB Quick Start and Online Help

The easiest way for new users to get an overview of FEMLABs capabilities and how to use them is to read the FEMLAB Quick Start manual. Further, the full FEMLAB documentation set is available in the FEMLAB help resources and as a set of PDF files.
Technical Support
If any questions arise regarding FEMLABwhether concerning installation, licensing, modeling, applications, or other technical questionsdo not hesitate to contact your local FEMLAB representative or send your questions to support@comsol.com. Further, at www.comsol.com/support you can find a broad range of technical support resources including the searchable FEMLAB Knowledge Base.
2 |
CHAPTER 1: INSTALLATION GUIDE
Sy s te m R equ ir e ment s
General Requirements
These requirements are common to all platforms: A CD-ROM drive for installation TCP/IP on all platforms when using a license server Adobe Acrobat Reader 3.0 or greater to view and print the FEMLAB documentation in PDF format The actual disk space needed varies with the size of the partition and the optional installation of online help files. The FEMLAB installer informs you of hard-disk space requirements for a particular installation.
GENERAL SYSTEM RECOMMENDATIONS
For modeling large 3D models we recommend at least 512 MB of memory, and be aware that some examples in the model libraries require as much as 1 GB.
FLO ATING NETWORK LICENSES
Floating network licenses are supported on heterogeneous networks of Windows, Linux, UNIX, and Mac OS X computers. Both the license manager and the FEMLAB application can run on either UNIX, Windows, or Mac OS X, and a single computer can run both of them.
System Requirements for Microsoft Windows

SYSTEM REQUIREMENTS
Windows NT 4.0 (Service Pack 5, 6, or 6a), Windows 2000, Windows XP, Windows ME, or Windows 98. Pentium II or later OpenGL 1.1 from Microsoft or an accelerator that supports OpenGL 1.1, or DirectX version 8.0 or later (see section PC/Windows Graphics Rendering Solutions on page 44) At least 256 MB of memory
SYSTEM REQUIREMENTS
OPT IONA L MATL AB A DD-ON RE QUI RE MENT S
The FEMLAB interface to MATLAB requires MATLAB 6.5 or MATLAB 6.5.1.
System Requirements for UNIX/Linux

SYSTEM REQUIREMENTS
At least 256 MB of memory. See the table below for additional system requirements on the supported Linux and UNIX platforms:
PLATFORM OPERATING SYSTEM PROCESSOR
Linux Sun HP
Linux 2.4.x kernel, glibc-2.2.5 or later Solaris 8, 9 HP-UX 11.0, Sept. 2003
Pentium II or later UltraSPARC II or later PA-RISC 2.0
In addition, see the graphics requirements in the following sections.
Linux Graphics Requirements

You can use any of the following XFree86 and graphics driver configurations: XFree86 4.1 or later with XFree86's Mesa library and DRI (Direct Rendering Infrastructure) XFree86 4.1 with NVIDIA driver 1.0-2880 or later XFree86 4.1 with ATI Fire GL2/3/4 drivers X4.1.0-1.9.16 or later. In order to get hardware acceleration with the Fire GL2/3/4 driver, set the environment variable LD_PRELOAD=/usr/lib/libGL.so before starting FEMLAB (for example, LD_PRELOAD=/usr/lib/libGL.so femlab). According to ATI, this step is not necessary starting with the 1.9.19 driver, or XFree86 4.1 with an official Mesa library (not XFree86's library). You can obtain it at http://www.mesa3d.org/. Use this configuration if you cannot or do not want to use DRI. XFree86 3.3.6 with Mesa 3.1 or later.
Solaris Graphics Requirements

Frame Buffer with OpenGL support (XVR-500, XVR-1000, XVR1200, XVR-4000, Expert3D, Elite3D, Creator3D, and PGX). OpenGL 1.2.2 for Solaris or later. Depending on type of frame buffer, a higher OpenGL version might be needed, such as XVR-1000 requires OpenGL 1.2.3.
4 |
HP-UX Graphics Requirements

HP graphics card with OpenGL support. The HP-UX 700 OpenGL Graphics Runtime Environment (B6268AA).
O P T I O N A L M AT L A B A D D - O N R E Q U I R E M E N T S
The FEMLAB interface to MATLAB requires MATLAB 6.5 or MATLAB 6.5.1.
System Requirements for Mac OS X

SYSTEM REQUIREMENTS
Mac OS X 10.3.1 Java 1.4.1 or later (part of Mac OS X installation) Java 3D and Java Advanced Imaging BSD Subsystem (part of Mac OS X installation) At least 256 MB of memory
O P T I O N A L M AT L A B A D D - O N R E Q U I R E M E N T S
The FEMLAB interface to MATLAB requires MATLAB 6.5.1 and X11.
SYSTEM REQUIREMENTS
In stal li ng FE M LAB on Wi nd ow s
Before You Begin
Check that your system meets all applicable requirements (see System Requirements for Microsoft Windows on page 3). Have your FEMLAB passcode or license file ready. A passcode has a form similar to:
ABA-CUSV-123456-1234567-123456789
New users can find the passcode or the license file in an email or letter from your sales representative. If you have not received a passcode or a license file, contact your local FEMLAB representative. Some FEMLAB license types require that you also install a license manager before running FEMLAB. If you are installing with a passcode, no license manager is needed. If you are installing with a license file, you must install and start the license manager before running FEMLAB (with the exception of licenses using a dongle). See License Manager Installation on page 25 for instructions. You can install FEMLAB and the license manager in any order. If your PC contains an old FEMLAB installation, the FEMLAB 3.0a installer does not remove it; it merely removes the MATLAB path to the old FEMLAB version. You can keep the old version if desired as well as uninstall it before or after installing FEMLAB 3.0a. For details on how to run several versions of FEMLAB see Running FEMLAB 2.3 on page 20.
Note: Use a username that contains ASCII characters only when installing on
Japanese Windows versions.
6 |
Installing FEMLAB 3.0a

1 Insert the installation disk into the CD-ROM drive. The Introduction window
should appear automatically; if not, run the file setup.exe from the Windows\VM directory on the installation CD.
2 Click Next.
3 Once you have read the license agreement, click the I accept the terms of the License Agreement button and then click Next.
INSTALLING FEMLAB ON WINDOWS
4 Indicate whether you have a passcode or a license file and then click Next.
5 If you have a license file, enter the path to an existing license file or click Choose to
select the file license.dat. If you have a passcode, type it into the supplied fields.
Note: The passcode is case sensitive.
8 |
6 Click Next. 7 Enter your user information: name and company.
8 Click Next.
9 Choose the install setTypical, Minimal, or Customand then click Next.
1 0 If you choose Custom, select the features to install.
Choose which products to install and whether to include models and documentation
1 1 Click Next . 1 2 Choose whether or not you want the ability to run FEMLAB using the MATLAB
interface. Select Yes only if MATLAB 6.5 is installed. If you select No, proceed to Step 15.
10 |
13 If the installer cannot find MATLAB 6.5, it asks you to specify the path to the
MATLAB root folder.
14 Click Next. 15 Specify the path to the FEMLAB installation directory.
16 Click Next.
11
1 7 Review the preinstallation summary.
1 8 Click Next . If your computer has insufficient disk space a Warning window appears.
You then have the option to free up some space or to click Previous and then remove some components previously selected for installation. When enough space becomes available, the Warning window changes to a Ready to Proceed window, allowing you to click Next .
1 9 The installer now copies files to the specified folder (this process might take several
minutes). Afterward the Install Complete window appears. If errors occur during installation this window issues a notification. The installer also generates a log to the text file FEMLAB30a_InstallLog.log located in the specified installation directory.
12 |
Restart your computer before running FEMLAB if the installation program asks you to do that.
Note: If you want to run both FEMLAB 3.0a and FEMLAB 2.3 on your system,
always install FEMLAB 2.3 before you install FEMLAB 3.0a. Only this installation order will make sure that the MATLAB paths are set up correctly.
Removing (Uninstalling) the FEMLAB Installation

To remove a FEMLAB installation from your system, use the FEMLAB uninstaller program (uninstall.exe) .
Note: The uninstaller deletes all FEMLAB 3.0a files and directories on the system.
13
STARTING THE UNINSTALLER
To start the FEMLAB uninstaller, use either of these methods: On the Start menu, point to Programs and then point to FEMLAB 3.0a. Click Uninstall FEMLAB 3.0a. On the Start menu, point to Settings , then click Control Panel. Double-click Add/ Remove Programs. Select FEMLAB 3.0a from the list.
RUNNING THE UNINSTALLER
Click Uninstall to start removing the installation.
Note: If you run FEMLAB with MATLAB 6.5, close MATLAB before starting the
uninstaller. If MATLAB is active, some files cannot be removed directly. The FEMLAB uninstaller will alert you about this issue and remove the files after restarting the computer.
14 |
R unn in g F EM LA B o n Wi ndo w s
The installer adds the folder FEMLAB 3.0a to the Start menu under the Programs item. That folder contains these entries: FEMLAB: Opens FEMLAB. A corresponding shortcut is added to the desktop. FEMLAB with MATLAB: Starts MATLAB 6.5, sets up all necessary FEMLAB paths, and then opens the FEMLAB graphical user interface. To start the FEMLAB GUI from within MATLAB, run femlab at the command prompt. A corresponding shortcut is added to the desktop. FEMLAB Client: Starts a FEMLAB client for connecting to a FEMLAB server. See the section Running FEMLAB Client/Server on page 37. FEMLAB Server: Starts a FEMLAB server that a FEMLAB client can connect to. See the section Running FEMLAB Client/Server on page 37. Uninstall FEMLAB 3.0a. Movies: Holds FEMLAB movies (if you selected this option during installation). Optional: If you have FEMLAB 2.3 installed, a menu item for starting it gets added. You must use this menu item to start FEMLAB 2.3. The original shortcuts and menu items for starting FEMLAB 2.3 no longer work following a FEMLAB 3.0a installation.
Running FEMLAB
You can run FEMLAB by double-clicking the FEMLAB 3.0a icon on the desktop.
Alternatively, to activate FEMLAB from the Start menu, point to Programs and then go to FEMLAB 3.0a and click FEMLAB.
RUNNING FEMLAB ON WINDOWS
15
Running FEMLAB with MATLAB

You can run FEMLAB with MATLAB by double-clicking the FEMLAB 3.0a with MATLAB icon on the desktop.
Alternatively, start FEMLAB with MATLAB from the Start menu by pointing to
Programs and then to FEMLAB 3.0a and select FEMLAB with MATLAB .
THE CLASSPATH FILE AND ITS LOCATION
The classpath.txt file is a file that is used to specify which Java class path to use inside MATLAB. When starting FEMLAB with MATLAB, FEMLAB copies classpath.txt from the toolbox\local directory under your MATLAB installation to the directory that is specified as the Start in directory for the FEMLAB with MATLAB shortcut. It then writes some extra lines to this file to include Java class paths that FEMLAB needs. To change the Start in directory:
1 Right-click the FEMLAB with MATLAB shortcut and choose Properties. 2 On the Shortcut page, type the path to the directory to start in into the Start in edit
field.
3 Click OK.
Running FEMLAB 2.3

After the installation of FEMLAB 3.0a, the original shortcuts and menu items for starting FEMLAB 2.3 do not work. To start FEMLAB 2.3, use the FEMLAB 2.3 command in the FEMLAB 3.0a folder on the Start menu.
16 |
I ns t al l i ng F EM LA B on UN I X/ Li nu x
Before You Begin
Check that you have a license file license.dat. You should have received this by email. If you have not received a license file, contact your local FEMLAB representative. The license manager must be installed and started before running FEMLAB with the exception of trial licenses, which do not require a license manager. See License Manager Installation on page 25 for instructions. You can install FEMLAB and the license manager in any order. The installation program is an X-Windows application, and thus needs access to an X-Windows display to run the installation program. Make sure that your DISPLAY variable is set up correctly and that you have access to your X-Windows display. Try the command xclock to test that your X-Windows display is working properly. To install FEMLAB in a system directory such as /usr/local you might need to run the installation program as the root user. The FEMLAB installer on UNIX/Linux does not modify any files on your system outside the FEMLAB installation directory.

1 Insert the distribution disk into the CD-ROM drive. 2 To start the installation, type one of the following commands
sh /mnt/cdrom/Solaris/VM/setup.bin sh /mnt/cdrom/Linux/VM/setup.bin sh /mnt/cdrom/HPUX/VM/setup.bin
depending on the platform type and where /mnt/cdrom is the mount point of the CD-ROM drive. If the CD is not mounted automatically, use the mount command to mount it. For mounting the CD-ROM on HP-UX systems, see the section Mounting the CD-ROM on HP-UX on page 41.
3 Read the license agreement, select I accept the terms of the license agreement, and
then click Next .

4 Give the path to the license file, license.dat , that you received by email. 5 Select the platforms and click Next . 6 Choose the install set: Typical, Minimal, or Custom and then click Next .
INSTALLING FEMLAB ON UNIX/LINUX
17
7 The installer now prompts you to specify the path to the MATLAB root directory
(the directory containing the subdirectory toolbox).

8 If you chose Custom in step 6, select the desired features to install. 9 Specify the path to the FEMLAB installation directory. 1 0 Review the preinstallation summary and click Next. If the disk has insufficient space,
a Warning window appears. You have the option to free up some disk space or click
Previous and remove some components previously chosen for installation. When
enough space becomes available, the Warning window changes to a Ready to Proceed window, allowing you to click Next. The files are now copied to the specified folder (this might take several minutes). When this process is finished, the Install Complete window appears. If errors occurred during installation, this window issues a notification. The installer also writes a log entry into the text file FEMLAB30a_InstallLog.log, which resides in the specified installation directory. The file browser in the doc directory attempts to run a web browser by starting common browsers. Edit the file to adjust your web browser choice.
Note: To make sure all FEMLAB users can easily start FEMLAB, include the
FEMLAB30a/bin directory in all users path or make a symbolic link from /usr/ local/bin/femlab to the femlab command.
Note: The installation program does not automatically remove the MATLAB 6.5
paths from earlier FEMLAB installations. You must remove these paths manually. Remove any FEMLAB-related modifications to the files /opt/matlab/toolbox/ local/pathdef.m or /opt/matlab/toolbox/local/matlabrc.m, where /opt/ matlab is the MATLAB 6.5 installation directory. You can still run FEMLAB 2.3 with MATLAB 6.5 by following the instructions in the following section.
Optional FEMLAB 2.3 Installation

You can continue to run FEMLAB 2.3 after the installation of FEMLAB 3.0a. Check the script template femlab23 in the FEMLAB30a/bin directory. The installation program makes an attempt to install suitable defaults for the FEMLAB 2.3 and
18 |
MATLAB directories. Edit the installation directory of MATLAB as MLROOT and the installation directory of FEMLAB 2.3 as FLROOT. To make sure all FEMLAB users can easily start FEMLAB 2.3, include the FEMLAB30a/bin directory in all users path or make a symbolic link from /usr/local/bin/femlab23 to the femlab23 command.

The FEMLAB 3.0a installation adds files only in the FEMLAB30a directory. To remove the FEMLAB installation, delete the FEMLAB30a directory including all subdirectories.
INSTALLING FEMLAB ON UNIX/LINUX
19
Run ni ng FE ML AB on UN I X/L in ux
Running FEMLAB
Run the femlab command. If it is not available, ask your system manager to make the femlab command available to you.
Running FEMLAB with MATLAB

Run the following command:
femlab matlab
The script femlab creates a file classpath.txt that MATLAB requires and places that file in the current directory. Therefore you must have write access to this directory when starting MATLAB using the femlab command.
Additional Options to the FEMLAB Command

femlab Starts FEMLAB. femlab client Starts a FEMLAB client that can connect to a FEMLAB server. See the section Running FEMLAB Client/Server on page 37. femlab server Starts a FEMLAB server that can be connected to by a FEMLAB client. See the section Running FEMLAB Client/Server on page 37. femlab matlab Starts MATLAB with FEMLAB paths set up and starts FEMLAB in
MATLAB.
femlab matlab path Starts MATLAB with the FEMLAB path set up. femlab matlab server Starts MATLAB with the FEMLAB path set up and starts a
FEMLAB server.
Running FEMLAB 2.3

It is possible to setup a command to run FEMLAB 2.3 also after the FEMLAB 3.0a installation. To run FEMLAB 2.3 use the command femlab23 .
20 |
I ns t al l i ng F EM LA B on Ma c O S X
Before You Begin
Check that your system meets all applicable requirements (see System Requirements for Mac OS X on page 5). Have your FEMLAB passcode or license file ready. A passcode has a form similar to:
ABA-CUSV-123456-1234567-123456789
New users can find the passcode or the license file in an email or letter from your sales representative. If you have not received a passcode or a license file, contact your local FEMLAB representative. Some FEMLAB license types require that you also install a license manager before running FEMLAB. If you are installing with a passcode, no license manager is needed. If you are installing with a license file, you must install and start the license manager before running FEMLAB. See License Manager Installation on page 25 for instructions. You can install FEMLAB and the license manager in any order. If your Macintosh contains an old FEMLAB installation, the FEMLAB 3.0a installer does not remove it; it merely removes the MATLAB path to the old FEMLAB version. You can keep the old version if desired as well as uninstall it before or after installing FEMLAB 3.0a. For details on how to run several versions of FEMLAB see Running FEMLAB 2.3 on page 24.
Installing Java 3D and Java Advanced Imaging

FEMLAB requires Java 3D and Java Advanced Imaging from Apple. You can download this software update from
http://www.apple.com/downloads/macosx/apple/ java3dandjavaadvancedimagingupdate.html
To install after the download:

1 Double-click the disk image file Java3D_and_JAI.dmg to mount the disk image if this
was not done automatically after the file was downloaded.

2 Double-click the file Java3D_and_JAI.mpkg to launch the installer. Follow the
instructions to install the software update.
INSTALLING FEMLAB ON MAC OS X
21
Note: The FEMLAB installation software provides an option to go to the download

web page for Java 3D and Java Advanced Imaging.
Installing the BSD Subsystem

FEMLAB requires the BSD Subsystem of Mac OS X 10.3. This is part of the default OS installation, but can be installed separately if it is not already installed on your computer.
1 Insert Install Disc 1 of the Mac OS X 10.3 installer in the CD drive. 2 Open the folder Optional Installs. 3 Double-click the file BSD Subsystem and follow the instructions to install it.
Note: FEMLAB will not work if the path to the FEMLAB folder, or the name of the
FEMLAB folder itself, contains spaces.
1 Insert the installation disk into the CD-ROM drive. Open the Mac OS X folder and
launch the Femlab Installer application. The Introduction window should now appear.
2 To proceed, see the instructions for Windows in the section Installing FEMLAB
3.0a on page 7. The procedure is the same on Mac OS X.
Note: If you want to run both FEMLAB 3.0a and FEMLAB 2.3 on your system,
always install FEMLAB 2.3 before you install FEMLAB 3.0a. Only this installation order will make sure that the MATLAB paths are set up correctly.

The FEMLAB 3.0a installation adds files only in the FEMLAB30a folder. To remove the FEMLAB installation, trash the FEMLAB30a folder including all subfolders
22 |
R unn in g F EM LA B o n Ma c O S X
The FEMLAB Applications
There are four application which can be used to run FEMLAB. They are described in the following section.
Note: None of the FEMLAB applications will work if they are moved outside the
FEMLAB folder. Create an alias if you, for example, want an icon on the desktop.
FEMLAB APPLICATION
The FEMLAB application is the primary application to run FEMLAB. It launches FEMLAB as a standalone application.
F EML AB WITH MATL AB A PPL ICATI ON
Use the FEMLAB with MATLAB application when you want to use the interface between FEMLAB and MATLAB. This application first launches MATLAB and then the FEMLAB graphical user interface. If you quit FEMLAB you can launch it again by typing femlab at the MATLAB command prompt.
Note: The FEMLAB with MATLAB application requires that you use Apples X11
application together with MATLAB. The X-Windows application OroborOSX is not supported.
FEMLAB CLIENT APPLICATION
The FEMLAB Client application launches a FEMLAB client for connecting to a FEMLAB server. See the section Running FEMLAB Client/Server on page 37.
F EM L AB SE R VE R AP P LI C ATI O N
The FEMLAB Server application launches the Terminal application and starts a FEMLAB server in a terminal window. See Running FEMLAB Client/Server on page 37.
RUNNING FEMLAB ON MAC OS X
23
Running FEMLAB from a Terminal Window

You can also launch FEMLAB from a terminal window using the shell script FEMLAB30a/bin/femlab. See the section Running FEMLAB on UNIX/Linux on page 20 for available options to the femlab script. To easily run the femlab script include the FEMLAB30a/bin directory in the path or make a symbolic link from /usr/bin/femlab to the femlab script. If you have administrator privileges, you can create a symbolic link with the command
sudo ln -s /Applications/FEMLAB30a/bin/femlab /usr/bin/femlab
assuming FEMLAB is installed in the Applications folder. This command asks for your password before creating the link.
Note: The femlab script must not be moved from the FEMLAB30a/bin folder. This
script is used by the FEMLAB applications.
Running FEMLAB 2.3

The M-file femlab23.m found in the FEMLAB30a folder lets you run FEMLAB 2.3 without having its path saved permanently in MATLAB. Before using the M-file, open it in a text editor and set the variable femlab23 to the path to your FEMLAB 2.3 installation. If you have FEMLAB 2.3 installed inside your MATLAB 6.5.1 folder this path would be
femlab23='/Applications/MATLAB6p5p1/femlab23';
The femlab23.m script adds the path to all modules. You can remove the lines adding the path to the modules you do not have installed. Put femlab23.m somewhere in your MATLAB path. You can then type femlab23 in your MATLAB workspace to tun FEMLAB 2.3.
24 |
Li cen s e Man age r Instal l ati on

The license manager supports a heterogeneous network of Windows, UNIX, and Mac OS X computers. Both the license manager and the FEMLAB application can run on either UNIX, PC/Windows, or Mac OS X platforms. We refer to the computer where the license manager is installed as the license server and any computers where the FEMLAB application is installed as clients . FEMLAB can be installed anywhere, typically on a local PC or on a file server where FEMLAB is accessed by users over a network. A single computer can function as a license server and a client, holding both the license manager and FEMLAB. The FEMLAB license manager does not require a MATLAB license manager. To install a license manager, start by following the instructions given in Before You Begin. Then, depending on the platform, go to the following sections:
LICENSE MANAGER INSTALLATION SECTIONS
License Manager Installation on PC/Windows on page 27 License Manager Installation on UNIX/Linux on page 29 License Manager Installation on Mac OS X on page 33
You can install the license manager or FEMLAB in any order. You will not be able to do a full test of the installation until you have installed both of them. FEMLAB uses the FLEXlm license manager (v7.2) from Macrovision Corporation to manage floating network licenses.
Before You Begin

SYSTEM REQUIREMENTS
Check that your system meets all necessary requirements before you start the installation process (see page 3.) The system requirements are crucial for the FEMLAB application whereas the license manager only needs the correct hardware and operating systemfor the license manager you do not have to consider memory and graphics requirements. The FEMLAB license manager is completely independent of the MATLAB license manager.
LICENSE MANAGER INSTALLATION
25
Obtaining a FLEXlm License File

To install a FEMLAB license manager you need a FLEXlm license file, license.dat. It looks something like this:
SERVER my_server 00b0d05d1635 1716 VENDOR FEMLAB USE_SERVER FEATURE SERIAL FEMLAB 3 permanent uncounted VENDOR_STRING=C,BBB \ HOSTID=DEMO SN=123456789 SIGN=123456789ABC INCREMENT FEMLAB FEMLAB 3 permanent 10 DUP_GROUP=UHD \ SIGN=123456789ABC INCREMENT ChEM FEMLAB 3 permanent 5 DUP_GROUP=UHD \ SIGN=123456789ABC INCREMENT CEM FEMLAB 3 permanent 5 DUP_GROUP=UHD \ SIGN=123456789ABC INCREMENT SME FEMLAB 3 permanent 5 DUP_GROUP=UHD \ SIGN=123456789ABC
As noted earlier, you should have received a FEMLAB license.dat file with the FEMLAB package. If you have not received it, contact your local FEMLAB representative or send a request to support@comsol.com. In the license.dat file, the text on the SERVER line should contain the license server name my_server, the hostid of the license server, and an optional port number (any unused port number between 1025 and 64000 is valid). Make sure that the license server name is the actual name of your license server; otherwise, change it by editing the file.
Note: You must not change anything else in the license.dat file or your license will
not work.
The VENDOR line defines the name of the vendor daemon binary, FEMLAB. The SERIAL line contains license information. The INCREMENT (can also be FEATURE) lines contain a product name, version, expiration date, and the number of available licenses. The example file above shows that the user has a permanent FEMLAB 3.0a license allowing ten concurrent users of FEMLAB and five concurrent users of the Chemical Engineering Module, the Electromagnetics Module, and the Structural Mechanics Module, respectively. The number after SIGN= at the end of each INCREMENT line contains a license key. Long lines can be broken up using the continuation character (\).
26 |
In case you have not received the license.dat file, you must provide the hostid of your license server (see Obtaining a Hostid on page 35 for instructions) and preferably your license server name. Please have them ready when contacting your local FEMLAB representative.
License Manager Installation on PC/Windows

The license server requires these components: FEMLAB License Manager files (FLEXlm) License file (license.dat )
FEMLAB LICENSE MANAGER FILES (FLEXLM)
The license manager consists of four components: License manager daemon (lmgrd.exe) Vendor daemon (femlab.exe) FLEXlm Utility program (lmutil.exe ) FLEXlm Control Panel (lmtools.exe) The two daemons (lmgrd.exe and femlab.exe ) run on the license server. When a user starts FEMLAB on a client computer, communication is established through the network from the client to the license server and the lmgrd.exe daemon. That daemon in turn makes a request to the vendor daemon (femlab.exe), which releases licenses according to information in license.dat. The Utility program and Control Panel handle license server management. For more information on FLEXlm management, see Chapter 7 in the FLEXlm End Users Guide, available as a part of the FLEXlm documentation.
INSTALLING THE LICENSE MANAGER FILES
Install the license manager only on the host(s) listed in license.dat . If you want to install FEMLAB on the same host as the license manager, first perform a complete FEMLAB installation because that procedure installs the license manager files along with FEMLAB. See the section Installing FEMLAB on Windows on page 6 for installation instructions. When finished, skip the remainder of this section and continue with Starting the License Manager on page 28. To install only the FEMLAB license manager files, follow these instructions:
1 Insert the distribution disk into the CD-ROM drive.
27
2 Follow the installation instructions starting on page 7 until you reach the Choose Install Set screen. 3 Choose Custom for a customized installation. Click Next. 4 In the list of products to install, select only the License check box. 5 Click Next , which brings up the Choose Install Folder screen. Specify the FEMLAB
3.0a root directory. The license manager files are copied to the license\win32 directory in the FEMLAB 3.0a directory.
6 Continue from the Choose Install Folder screen in the installation instructions (page
11) to complete the license manager file installation.

STARTING THE LICENSE MANAGER
You can start the license manager manually or it can run automatically as a service at boot.
Starting the Manager Automatically as a Service

To set up the license manager as a service from the FLEXlm Control Panel:
1 Run lmtools.exe from the license\win32 directory. 2 On the Service/License File tab choose Configuration using Services. Note that you
must perform this step every time you start the FLEXlm Control Panel.
3 Click the Configure Services tab. 4 Make an entry in the Service Name edit field, for example, FEMLAB License
Manager.
5 Specify the full path to lmgrd.exe , license.dat, and the debug log file of your
choice.
28 |
6 Select the Use Services check box (this might not be possible on all platforms, but it
is recommended) and then the Start Server at Power Up check box.
7 Click Save Service. The license manager now starts at boot. If you prefer, start the
license manager directly by choosing Start Server on the Start/Stop/Reread page.
Starting the Manager Manually

To start the license manager manually, cd to the license\win32 directory. Type in a command window
lmgrd -c ..\license.dat -l ..\femlab30a.log
The license manager is now ready to distribute licenses over the network. It writes debug information to the log file license\femlab30a.log.
STARTING FEMLAB
After the installation is complete and the license manager daemons are running on the license server(s), you can start using FEMLAB.
License Manager Installation on UNIX/Linux

You need the following components on the license server: FEMLAB License Manager files (FLEXlm) License file (license.dat ).
29
The license manager consists of three components: License manager daemon (lmgrd) Vendor daemon (FEMLAB) FLEXlm Utility programs (lmutil and others) The two daemons (lmgrd and FEMLAB) run on the license server. When a user starts FEMLAB on a client computer, communication is established through the network from the client to the license server and the lmgrd daemon. The lmgrd daemon in turn makes a request to the vendor daemon (FEMLAB) to release a license. The vendor daemon releases licenses according to the information contained in license.dat. The Utility programs are used for license server management. For more information on FLEXlm management, see Chapter 7 in the FLEXlm End Users Guide, available as a part of the FLEXlm documentation.
The license manager should be installed only on the host(s) listed in license.dat. If you want to install FEMLAB on the same host as the license manager, first perform a complete FEMLAB installation because that procedure automatically installs the license manager files along with FEMLAB. See the section Installing FEMLAB on UNIX/Linux on page 17 for installation instructions. When finished, skip the remainder of this section and continue at Starting the License Manager on page 31. If you want to install only the FEMLAB license manager files, follow these instructions:
1 Insert the distribution disk into the CD-ROM drive. 2 To start the installation, enter one of the following commands
/mnt/cdrom/Solaris/VM/setup.bin /mnt/cdrom/Linux/VM/setup.bin /mnt/cdrom/HPUX/VM/setup.bin
depending on the platform type and where /mnt/cdrom is the mount point of the CD-ROM drive.
3 Continue according to the installation instructions on page 22 until the step where
you see the Choose Install Set screen.

4 Choose Custom for a customized installation. Click Next. 5 In the list of products to install, select only the License check box.
30 |
6 Click Next, which brings up the Choose Install Folder screen. Specify the FEMLAB
3.0a root directory. The installer copies the license manager files to the license/
$arch directory, where $arch is glnx86 (Linux), sol2 (Sun), or hpux (HP)
depending on platform.
7 Pick up at the installation instructions with the Choose Install Folder screen (page 18)
to complete the license manager file installation.

NAMED SINGLE USER LICENSE
If you are installing a Named Single User License, you must perform the two steps listed below. If you are installing any other license type, skip this section and go directly to Starting the License Manager on page 31.
1 Create an options file, FEMLAB.opt . The options file should include the username
of the person that will run FEMLAB. We recommend that you name the options file FEMLAB.opt and place it in the license directory. Below is an example of an options file for a user david, who has access to FEMLAB with all three modules.
INCLUDE INCLUDE INCLUDE INCLUDE FEMLAB USER david CEM USER david ChEM USER david SME USER david
Each INCLUDE row has a corresponding FEATURE row in the license.dat file. The second item on each FEATURE row is either FEMLAB , CEM, ChEM, or SME. You only need to add the items listed in license.dat to your options file.
2 Edit the VENDOR row in the license.dat file located in the license directory. The
path to the options file is indicated by the options keyword. Change the path so that it points to the location of the FEMLAB.opt file you generated. If your options file is placed here:
/opt/FEMLAB30a/license/FEMLAB.opt
the VENDOR row in license.dat should read:

VENDOR FEMLAB options=/opt/FEMLAB30a/license/FEMLAB.opt
You are now ready to start the License Manager.

You can start the license manager manually or it can run automatically at boot.
Starting the License Manager Manually

To start the license manager manually, make the license/$arch directory the current directory and type
31
./lmgrd -c ../license.dat -l /var/tmp/femlab30a.log
The server is now ready to distribute licenses over the network. It writes any debug information to the log file /var/tmp/femlab30a.log.
Starting the License Manager Automatically at Boot

Add Bourne shell commands to the appropriate boot script. You must be a superuser (root) to edit boot scripts.
Note: We do not recommended that you start the daemons as a superuser for security
reasons. Instead, use an actual username to start the license manager.
The procedure for editing boot scripts on each platform appears in the following table:
TABLE 1-1: BOOT SCRIPT PROCEDURES PLATFORM PROCEDURE
Solaris (sol2)
Copy the file FEMLAB30a/license/sol2/rc.lm and paste it at the beginning of /etc/init.d/lmgrd. Create this file if it does not already exist. Edit /etc/init.d/lmgrd, replacing dir in the code fragment with the full path to the sol2 platform directory, and replace username with an actual username. If the file (link) /etc/rc3.d/S171lmgrd does not exist, create it with the commands
cd /etc/rc3.d ln -s /etc/init.d/lmgrd S171lmgrd
Linux, glibc2 (glnx86)
Copy the file FEMLAB30a/license/glnx86/rc.lm and paste it at the end of

/etc/rc.d/rc.local.
Replace dir in the code fragment with the full path to the glnx86 platform directory, and replace username with an actual username. HP-UX 11.0 (hpux) In the FEMLAB30a/license/hpux directory, type the commands
cp rc.lm /sbin/init.d/femlab30lm chmod 555 /sbin/init.d/femlab30lm
Edit /sbin/init.d/femlab30lm, replacing dir with the full path to the hpux platform directory, and replace username with an actual username. Now create the following links
cd ln cd ln /sbin/rc3.d -s /sbin/init.d/femlab30lm S900femlab30lm /sbin/rc2.d -s /sbin/init.d/femlab30lm K100femlab30lm
32 |
STARTING FEMLAB
After the installation is complete and the license manager daemons are running on the license server(s) you can start using FEMLAB.
License Manager Installation on Mac OS X

You need the following components on the license server: FEMLAB License Manager files (FLEXlm) License file (license.dat ).
The license manager consists of three components: License manager daemon (lmgrd) Vendor daemon (FEMLAB) FLEXlm Utility programs (lmutil and others) The two daemons (lmgrd and FEMLAB) run on the license server. When a user starts FEMLAB on a client computer, communication is established through the network from the client to the license server and the lmgrd daemon. The lmgrd daemon in turn makes a request to the vendor daemon (FEMLAB ) to release a license. The vendor daemon releases licenses according to the information contained in license.dat. The Utility programs are used for license server management. For more information on FLEXlm management, see Chapter 7 in the FLEXlm End Users Guide, available as a part of the FLEXlm documentation.
The license manager should be installed only on the host(s) listed in license.dat . If you want to install FEMLAB on the same host as the license manager, first perform a complete FEMLAB installation because that procedure automatically installs the license manager files along with FEMLAB. See the section Installing FEMLAB on Mac OS X on page 21 for installation instructions. When finished, skip the remainder of this section and continue at Starting the License Manager on page 34. If you want to install only the FEMLAB license manager files, follow these instructions:
1 Insert the distribution disk into the CD-ROM drive.
33
2 Follow the installation instructions starting on page 22 until you reach the Choose Install Set screen. 3 Choose Custom for a customized installation. Click Next. 4 In the list of products to install, select only the License check box. 5 Click Next , which brings up the Choose Install Folder screen. Specify the FEMLAB
3.0a folder. The license manager files are copied to the license/macosx folder in the FEMLAB 3.0a folder.
6 Continue from the Choose Install Folder screen in the installation instructions (page
7) to complete the license manager file installation.

The license manager can be started either manually or it can run automatically at startup.
Starting the License Manager Manually

To start the license manager manually, perform the following steps:
1 Launch the Terminal application. 2 Change directory to the license/macosx directory
cd /Applications/FEMLAB30a/license/macosx
3 Then type
./lmgrd -c ../license.dat -l /var/tmp/femlab30a.log
The server is now ready to distribute licenses over the network. It writes any debug information to the log file /var/tmp/femlab30a.log.
Starting the License Manager Automatically at Startup

There is a folder FEMLABLmgr in the folder FEMLAB30a/license/macosx with a script which can automatically start the license manager when you start your computer. By installing and configuring this folder, the license manager will not have to be started manually.
1 Go to the top level /Library folder on your startup disk. 2 In the Library folder, create a folder StartupItems , if it does not already exist. 3 Move or copy the folder FEMLABLmgr to the StartupItems folder. 4 Open the file FEMLABLmgr in a text editor, for example, TextEdit. 5 Edit the line
FP=<FEMLABPATH>
by replacing <FEMLABPATH> by the path to the FEMLAB folder. If FEMLAB is
34 |
installed in the Applications folder this path is

FP=/Applications/FEMLAB30a
6 Edit the line

USERNAME=<username>
by replacing <username> by your username. To test the license manager installation, restart your computer. During the startup a message Starting FEMLAB License Manager should appear.
STARTING FEMLAB
After the installation is complete and the license manager daemons are running on the license server(s) you can start using FEMLAB.
Obtaining a Hostid
If FEMLAB is already installed on your license server, you can determine the hostid by executing the lmhostid command
FEMLAB30a/license/$arch/lmhostid
where $arch is either win32 (PC/Windows), glnx86 (Linux), sol2 (Sun), hpux (HP), or macosx (Mac OS X). If FEMLAB is not installed, you must obtain a hostid using operating system commands as described in the following table:
TABLE 1-2: HOSTI DS FOR THE SUPPORTED PL ATFORMS HARDWARE PLATFORM HOSTID TYPE THIS COMMAND ON THE LICENSE SERVER: EXAMPLE
HP
32-bit hostid Ethernet address
uname -i and convert to hex, or prefix with # lanscan (station
778DA450 or #2005771344 0000F0050185
address without the leading "0x")

/sbin/ifconfig eth0 and remove 00400516E525
Linux
Ethernet address
colons from HWaddr

00:40:05:16:E5:25
Sun
32-bit hostid
hostid
170a3472
35
TABL E 1- 2: H OS TIDS FOR THE SUPPOR TED PLATFORMS HARDWARE PLATFORM HOSTID TYPE THIS COMMAND ON THE LICENSE SERVER: EXAMPLE
Windows
Ethernet address
ipconfig /all
00500284A328
(remove hyphens from the physical address 00-50-02-84-A3-28) see below

00039377F4AC
Mac OS X
Ethernet address
FLEXlm uses different machine identifications for different architectures. For example, all Sun Microsystems machines have a unique hostid whereas other machines do not. For this reason, some machine architectures use an Ethernet address (also called a MAC address) as the hostid. An Ethernet address has six bytes, each with two hexadecimal digits. Be sure to specify all twelve hex digits when using an Ethernet address as a hostid. For example, if the Ethernet address is 8:0:20:0:5:ac specify 0800200005ac as the hostid.
OBTAINING THE HOSTID ON MAC OS X
1 Launch the application System Profiler found in the Applications/Utilities folder. 2 Select Network in the Contents pane to the left. 3 Select Ethernet in the list to the upper right. 4 The hostid is the Ethernet Address , which is displayed below, with the colons
removed.
36 |
R unn in g F EM LA B C li en t /Serve r
The FEMLAB graphical user interface can run in a separate process as a client to a FEMLAB server. The FEMLAB client uses a TCP/IP connection to connect to the FEMLAB server. The FEMLAB client and the FEMLAB server need not run on the same platform. You need a floating network license to run the FEMLAB server and the FEMLAB client on separate computers. You can also use FEMLAB client/server when running FEMLAB with MATLAB. Start a FEMLAB client on a separate computer and connect to a FEMLAB server started from within a MATLAB process.
Advantages of Using FEMLAB Client/Server

By using FEMLAB client/server, you can free your desktop computer of lengthy computations, dispatching your jobs to a dedicated computer. The computer where you run the FEMLAB server can be equipped with more memory and a faster CPU than your desktop computer. By running the FEMLAB server and the FEMLAB client separately on the same computer you can increase the total memory available to solve your problems. This is particularly interesting because the 32-bit limit on addressable memory can be the limiting factor. The FEMLAB server components do not use the memory required for the graphical user interface, freeing memory for the actual computation on the server.
Running FEMLAB Client/Server

STAR TING FEMLAB SERVER
When you have access to the Windows desktop, start the FEMLAB server from the Start menu. Select FEMLAB 3.0a under Programs and then Client/Server. When you are starting the FEMLAB server from a terminal window in Windows you can start it using the command C:\FEMLAB30a\femlabserver. On UNIX and Linux, use the femlab server command to start a FEMLAB server. On Mac OS X, use the FEMLAB Server application, or if you are logging on to the Macintosh from another computer, use the femlab server command in the terminal window.
RUNNING FEMLAB CLIENT/SERVER
37
STARTING FEMLAB CLIENT
On Windows, use the Start menu to start a FEMLAB client. Select FEMLAB 3.0a under Programs and then Client/Server. On UNIX and Linux, use the femlab client command to start a FEMLAB client. On Mac OS X use the FEMLAB Client application.
ACCESSING THE FEMLAB SERVER COMPUTER
On UNIX, Linux, and Mac OS X, just login on the server computer by using ssh, rlogin , or telnet, and enter the femlab server command. When running the FEMLAB server within MATLAB on UNIX and Linux, you need access to the X-Windows display pointed to by the DISPLAY variable. On Mac OS X, you need to have access to the Mac desktop, that is, you must be logged on from the Mac OS X login window in order to run the FEMLAB server within MATLAB. On Windows, you can access the server computer in several ways. If the server computer is dedicated to a single person, you can sit down by the computer and login on it. You can also connect to the server computer by using Netmeeting, Remote Desktop (Windows XP) or VNC. Start the FEMLAB server from the Start menu. If several persons want to access a single Windows computer to run FEMLAB server, you must use Windows Terminal Server or another tool that allows multiple users to login on the same Windows server. In some Windows versions, Microsoft provides a Telnet Server that you can use to log in with a terminal window. When using a terminal window to login on Windows, use the femlabserver command to start the FEMLAB server.
INITIALIZING THE FEMLAB SERVER
The first time you start a FEMLAB server on a computer it asks for a username and password in a dialog box. When using a terminal window without access to a display you cannot open this dialog box. Therefore you cannot use a terminal window when logging on the server computer the first time. The easiest way is to sit down by the computer and login on it the first time that you start the FEMLAB server. Enter a username and password. Select the Remember password check box. The next time that you want to run the FEMLAB server you can connect using a terminal window.
PO R T N U M BE R
The FEMLAB server requires that each user logs in and starts the FEMLAB server manually. The FEMLAB server prints a port number in the terminal window. Provide the computer name and port number on the Settings tab in the Model Navigator in the FEMLAB client. If you have identical home directories on the server and client and you start the FEMLAB client after the FEMLAB server has been started, the FEMLAB
38 |
client can obtain the computer name and port number from the .femlab directory in your home directory. If the FEMLAB client has not determined the computer name and port number, you must enter them manually.
R U N N I N G T H E F E M L A B S E R V E R W I T H I N M AT L A B R E M O T E L Y
On Windows and Mac OS X you need to have access to a display to run MATLAB. Thus to run the FEMLAB server within MATLAB on a remote Windows or Mac OS X computer, you must sit down by the computer and log in, or you need a remote login tool with display capabilities such as Netmeeting, Remote Desktop, or VNC. On UNIX/Linux you can start MATLAB remotely as long as you have access to a display pointed to by the DISPLAY variable. Start the FEMLAB server within MATLAB by typing femlab server. You must start MATLAB using FEMLAB with MATLAB on the Start menu in Windows, by the FEMLAB with MATLAB application on Mac OS X, or by the FEMLAB command femlab matlab on UNIX/Linux.
U SI NG A WI NDOWS XP PROF E SS ION AL TEL NE T SE R VER
The Telnet Server setup is a bit different in different Windows versions. The Telnet Server is available in Windows XP Professional. You cannot use a terminal window such as Telnet to run a FEMLAB server within MATLAB on Windows. You first need to enable a Telnet Server daemon on the computer where you intend to run the FEMLAB server.
1 Start the Telnet service. Open the Services dialog box. Right-click on the Telnet service and select Start. 2 Add the user group TelnetClients if it does not already exist. Open Groups and select New Group. Type TelnetClients in the edit field. 3 Create/modify user accounts. The Telnet user and FEMLAB server user must be a
member of TelnetClients group. Remember that you have to initialize the femlab server by entering username and password from a Windows session with access to the Windows desktop. Do not forget to select the Remember password check box when doing it. After initializing the FEMLAB server you can login with a Telnet session from the remote computer and start the FEMLAB server by typing the command C:\FEMLAB30a\femlabserver. You might need the port number displayed by the FEMLAB server.
RUNNING FEMLAB CLIENT/SERVER
39
Op ti mizing Me mory Use

The Java engine in the graphical user interface and in the FEMLAB server component reserves a fixed amount of memory for its heap. There are several ways of increasing the available memory for the solvers. Reducing the Java heap size will make more memory available for the solvers. Also always try to select a solver that minimizes memory usage. See the section Solving the Model in the FEMLAB User's Guide. When running FEMLAB, you can decrease the maximum Java heap size. On Windows, modify the file FEMLAB30a/lib/win32/femlab.opts and on UNIX/ Linux/Mac OS X, modify the file FEMLAB30a/bin/femlab. Decrease the value of parameter MAXHEAP=256m from 256MB to a lower value, say 128, by changing to MAXHEAP=128m . By default, you get more memory available in a FEMLAB server. Connect to the FEMLAB server from a FEMLAB client. You can also modify the Java heap size on a FEMLAB server: On Windows, modify the file FEMLAB30a/lib/win32/ femlab.opts and on UNIX/Linux/Mac OS X, modify the file FEMLAB30a/bin/ femlab. Decrease the value of parameter MAXHEAPSERVER=128m from 128MB to a lower value, say 64, by changing to MAXHEAPSERVER=64m. If you run out of memory during postprocessing, you can increase the maximum Java heap size. On Windows, modify the file FEMLAB30a/lib/win32/femlab.opts and on UNIX/Linux/Mac OS X, modify the file FEMLAB30a/bin/femlab. Increase the value of parameter MAXHEAP=256m from 256MB to a higher value, say 512, by changing to MAXHEAP=512m. To run a FEMLAB server and a FEMLAB client on different computers, you need a floating network license. All FEMLAB licenses allow you to run a FEMLAB server and a FEMLAB client on the same computer.
STA CKS IZE A ND T HE DI RE CT CHOL ES KY (TAU CS) S OL VER
To run large problems with the Direct Cholesky (TAUCS) solver, you might need to increase the size of the Java stack. On Windows, modify the file FEMLAB30a/lib/ win32/femlab.opts and on UNIX/Linux/Mac OS X, modify the file FEMLAB30a/ bin/femlab . Change the parameter STACKSIZE=2m from 2MB to a higher value, say 4MB, by changing to STACKSIZE=4m . In the Solver Parameters dialog box, click the Settings button and double the setting in the Maximum recursion depth edit field for the Direct Cholesky (TAUCS) solver before solving.
40 |
M ou nti ng th e C D-R O M on HP -UX

The instructions below show how to use the pfs daemons to mount the FEMLAB installation CD using the Rockridge extensions to the ISO9660 format. If you do not mount the CD-ROM with Rockridge extensions, for example, by using the option cdcase to the standard mount program, the installation process will appear to start normally, but will end with several error messages. Since the process of mounting the CD-ROM is complicated, it might actually be preferable to mount the CD-ROM on another computer type and export the CD-ROM using nfs to the HP-UX computer. Make sure your HP-UX system is updated according to the system requirements: install all patches up to September 2003. This will imply that the patches necessary to mount the CD-ROM are available. Applying these patches also ensures that FEMLAB will run without problems. Make sure rpcbind is running by starting the nfs client. To start these, make sure you have set NFS_CLIENT=1 in /etc/rc.config.d/nfsconf. Then type
/sbin/init.d/nfs.core start /sbin/init.d/nfs.client start
Enter the following line in /etc/pfs_fstab

/dev/dsk/c1t2d0 /cdrom pfs-rrip xlat=rrip 0 0
You might have to replace the device name /dev/dsk/c1t2d0 with the actual device of the CD-ROM drive on your computer which you should be able to determine by running
ioscan -fnC disk
Also make sure that the directory /cdrom exists. Then start the pfs daemons:
nohup pfs_mountd & nohup pfsd 4 &
Then mount the CD-ROM by

pfs_mount /cdrom
Install FEMLAB. Then unmount the CD-ROM:

pfs_umount /cdrom
M O U N T I N G T H E C D - RO M O N H P - U X
41
Logi n Informa ti on an d S ecuri ty

Login Information
When starting FEMLAB for the first time, the Set Login Information window appears. Select a username and a password, which FEMLAB then uses in communications between the FEMLAB user interface and the server. You must also specify a matching username and password on the Settings page in the Model Navigator, which opens when you start FEMLAB. This login information is written in the directory .femlab/fl30/ login in your home directory. On Mac OS X this login information is located in Library/Preferences/FEMLAB/fl30/login in your home directory.
Client/Server Security Issues

FEMLAB is able to operate in a client/server mode, where FEMLAB is run as a separate client and a server. FEMLAB uses a TCP/IP connection to send data between the server and the client. Always make sure that untrusted users cannot access the FEMLAB login information. Thus you must protect the file .femlab/fl30/login in your home directory. This is particularly important when you are using the client/server feature of FEMLAB. When you start a FEMLAB server, a person that has access to your login information could potentially connect to your FEMLAB server. By default, only a single FEMLAB client can connect to a server. If you disconnect from the server, you need an additional femlab server command to make further connections. When a FEMLAB client connects or disconnects from a remote computer, the FEMLAB server displays a message. The connection from the client to the server is made with the TCP protocol. The server and client are mutually authenticated using a challenge handshake authentication protocol. This means that the login information cannot easily be obtained by someone eavesdropping the network communication. The TCP connection between the client and the server is otherwise not encrypted. If you require encryption of the TCP connection, you can use third-party software based on protocols such as SSH or IPSEC.
42 |
Tr o ub le s hoo t in g G rap hi cs
FEMLAB relies on hardware acceleration for 3D graphics rendering. This section describes symptoms and solutions related to graphics rendering and the graphics drivers that FEMLAB uses.
Symptoms for Graphics Rendering Problems

FEMLAB uses hardware acceleration for graphics rendering throughout all 3D application modes and for mesh plots and postprocessing in the 1D and 2D application modes. FEMLAB might thus appear to work properly for a while when you draw the geometry and set physical properties in 1D or 2D, while failing later on when displaying the mesh or the solution. This is when the drivers for the hardware acceleration are loaded. The following three items indicate that there are problems with 3D rendering: FEMLAB displays the message Failed to Initialize 3D Graphics. FEMLAB crashes when you open a model. You can create the geometry and set physical properties in 1D or 2D but FEMLAB crashes when you initialize the mesh or solve the problem. The next two items indicate general graphics driver problems: Gray shadows of the menus are left behind after you have used them. Dialog boxes appear completely gray not showing any contents. The following item indicates that your graphics card has too little memory for your current screen resolution and color depth: FEMLAB crashes when you resize or maximize its graphical user interface. The following problem indicates that your graphics card is configured with too small color depth: The graphical user interface in FEMLAB appears in strange colors all the time or only when the graphical user interface is not in focus.
TR O U B L E S H O O T I N G G R A P H I C S
43
PC/WINDOWS GRAPHICS REN DERIN G SO LUTIO NS
When you experience one or several of the symptoms from the previous section we suggest that you try out the following steps to alleviate the problem. The first two items below are simple to try out for a start. Lower the hardware acceleration of your graphics card. This item often resolves the problems for newer graphics cards: Click the Advanced button on the Settings tab in the Display Properties dialog box, for example, by double-clicking Display in the Control Panel. This opens a dialog box that is specific to your graphics card. This dialog box often has a Troubleshooting page where you can lower the hardware acceleration. Lower the color depth or the screen area of your graphics card. This item often works for older graphics cards with less than 16 MB on-board graphics memory. Click the Settings tab in the Display Properties dialog box to find the screen resolution and color quality settings. The following two items involve downloading and installing software. Running the latest graphics drivers is important for greater stability and performance. Thus it could be worth implementing these items even if you do not experience any graphics rendering problems. Update to the latest version of DirectX. FEMLAB requires at least version 8.0, but a later DirectX version can imply greater performance and stability. To determine the DirectX version on your computer, run the command dxdiag.exe. Download the latest driver from www.microsoft.com/directx or use windowsupdate.microsoft.com. Update the drivers for your graphics card. Most graphics card and graphics chip vendors have web sites where you can download up-to-date stable drivers. Microsoft also provides graphics card driver updates at windowsupdate.microsoft.com. By default FEMLAB uses DirectX for 2D software rendering and OpenGL for 3D hardware rendering. If you cannot find stable OpenGL drivers for your graphics card, you can use DirectX also for 3D hardware rendering, which may result in a slight degradation in FEMLAB graphics quality. Switch to using the DirectX version of Java3D with FEMLAB. To switch to DirectX, do the following:
1 Make sure FEMLAB is not running.
44 |
2 Double-click on the file win32_3d_dx.exe in the root directory of your FEMLAB
installation.
3 Click Unzip to apply the change. 4 A new dialog box should open; click OK and then click Close.
The next time you start FEMLAB it will be using DirectX instead of OpenGL for the hardware graphics acceleration. If you want to return to using OpenGL, do the following:
1 Double-click the file win32_3d_ogl.exe in the in the root directory of your
FEMLAB installation.
2 Click Unzip to apply the change. 3 A new dialog box should open; click OK and then click Close.
PC/LINUX SOLUTIONS
You need to have OpenGL drivers installed to run FEMLAB on Linux. Use vendor graphics drivers when available. Both NVIDIA and ATI provide drivers for their recent graphics cards on their web sites. See www.nvidia.com and www.ati.com. Other graphics card vendors may provide similar services. If you cannot find hardware accelerated OpenGL drivers for your graphics card, you can use software OpenGL rendering. Software OpenGL drivers are often provided with the Linux distribution. As an alternative, you can use the ones provided with FEMLAB. Untar the file mesa.tar in the FEMLAB30a installation directory and modify the line
LIBGLPATH=
in FEMLAB30a/bin/femlab to include the path to the mesa drivers, for example,

LIBGLPATH=/usr/local/FEMLAB30a/mesa
assuming that you installed FEMLAB in the /usr/local directory.

SOLARIS SOLUTIONS
Make sure you have one of the supported graphics cards from the system requirements in the section Solaris Graphics Requirements on page 4. Also make sure that you have at least OpenGL 1.2.2 for Solaris or later installed. To find your current version, use the command pkginfo -l SUNWglrt. OpenGL for Solaris is available at http://www.sun.com/solaris/opengl.
TR O U B L E S H O O T I N G G R A P H I C S
45
Sometimes X-Windows is configured with too small color depth. Use the command m64config -propt to determine the display settings. Use m64config -depth 24 to set 24 bit color depth.
Problems During Startup on Windows

If FEMLAB fails during startup (meaning that the Model Navigator screen does not appear), there might be a problem with the DirectX drivers. You should either update these drivers or disable FEMLAB from using DirectX entirely. If you cannot or do not want to update the DirectX drivers, an alternative is to disable DirectX. To do so, edit the file lib\win32\femlab.opts in the installation directory and remove the first (comment) character on the line following the line:
# Uncomment line below to disable DirectX graphics acceleration
Adjusting the Polygon Offset

Some OpenGL graphics card do not render touching edges and faces correctly in FEMLAB. This makes the edges in mesh plots appear dashed or dotted. To improve their appearance, follow these steps:
1 Click the Draw Mode toolbar button. 2 Go to the Options menu and choose Preferences. 3 In the Preferences dialog box, click the Visualization tab. 4 Adjust the value in the Polygon offset edit field to a larger integer. 5 Click Apply.
Polygon offset settings affect only 3D rendering when using OpenGL and are not applicable when using FEMLAB with DirectX.
46 |
License Agreement
47
COMSO L Software L ice nse Agre emen t

CAREFULLY READ THE FOLLOWING TERMS AND CONDITIONS BEFORE INSTALLING OR USING THE COMSOL SOFTWARE. YOUR USE OF THE PROGRAMS AND DOCUMENTATION IS EXPRESSLY CONDITIONED UPON YOUR ACCEPTANCE OF THE TERMS AND CONDITIONS (TERMS) CONTAINED WITHIN THIS SOFTWARE LICENSE AGREEMENT (AGREEMENT). THESE TERMS AND YOUR ACCEPTANCE THEREOF REPRESENT THE ENTIRE AGREEMENT BETWEEN YOU AND COMSOL AB (COMSOL) AND SUPERSEDE ANY AND ALL OTHER COMMUNICATIONS, PRIOR, CONTEMPORANEOUS OR SUBSEQUENT, AND ANY COURSE OF PERFORMANCE OR COURSE OF DEALING. THE TERMS AND THE RELATIONSHIP BETWEEN YOU AND COMSOL SHALL BE GOVERNED BY AND INTERPRETED IN ACCORDANCE WITH THE LAWS OF THE COMMONWEALTH OF MASSACHUSETTS, UNITED STATES OF AMERICA, WITHOUT REFERENCE TO ITS PRINCIPLES OF CONFLICTS OF LAW. THE PARTIES AGREE THAT NEITHER THE U.N. CONVENTION ON CONTRACTS FOR THE INTERNATIONAL SALE OF GOODS NOR THE PROVISIONS OF UCITA AS ADOPTED OR AS MAY BE ADOPTED IN ANY STATE HAVING JURISDICTION OR WHOSE LAW GOVERNS THIS AGREEMENT SHALL APPLY OR GOVERN THIS AGREEMENT OR THE RELATIONSHIP OF THE PARTIES HERETO.
1 License Duration (Term). This Agreement shall continue until the earlier of (a)
termination by COMSOL or Licensee as provided below, or (b) such time as there are no Programs being licensed to Licensee hereunder. For Annual Licenses: LICENSEE UNDERSTANDS AND AGREES THAT EACH ANNUAL LICENSE WILL TERMINATE AFTER EACH ONE (1) YEAR PERIOD, UNLESS LICENSEE RENEWS ITS LICENSE BY REMITTING THE THEN-CURRENT ANNUAL LICENSE FEE. LICENSEE UNDERSTANDS THAT THE PROGRAMS WILL STOP OPERATING UNLESS LICENSEE PAYS THE LICENSE FEE AND IS GIVEN NEW ANNUAL PASSCODES. For Term Licenses: LICENSEE UNDERSTANDS AND AGREES THAT EACH TERM LICENSE WILL TERMINATE AFTER EXPIRATION OF THE LENGTH OF TERM LICENSED, UNLESS LICENSEE RENEWS ITS LICENSE BY REMITTING THE THEN-CURRENT TERM LICENSE FEE. LICENSEE UNDERSTANDS THAT THE PROGRAMS WILL STOP
48 |
CHAPTER 2: LICENSE AGREEMENT
OPERATING UNLESS LICENSEE PAYS THE LICENSE FEE AND IS GIVEN NEW TERM PASSCODES. For Perpetual Licenses: Licensee shall have the right to use the Programs indefinitely, subject to the TERMINATION provisions in this Agreement. LICENSEE UNDERSTANDS AND AGREES THAT THE SOFTWARE MAINTENANCE SERVICE FOR EACH LICENSE WILL TERMINATE UPON EXPIRATION OF THE INITIAL SOFTWARE MAINTENANCE SERVICE TERM OF TWELVE (12) MONTHS INCLUDED WITH THE PURCHASE OF THE LICENSE. Thereafter, the Software Maintenance Service term may be renewed, at the then-current price, as long as COMSOL offers such Software Maintenance Service.
2 License Grant. During the term of this Agreement, COMSOL grants to Licensee a
non-exclusive license to install, run, use, operate and perform (collectively use) the Programs (Programs) and documentation (Documentation) as provided herein.
a Programs. You may license a named single user license (NSL), a CPU-locked
single user license (CPU), or a floating network license version (FNL) of the Programs under this Agreement. The license granted herein is for the number of seats set forth on the purchase order or invoice.
b Object Code. The license granted herein applies only to the object code version
of the Programs. Licensee shall have no rights whatsoever with respect to the source code for the Programs.
c Ownership. All right, title and interest in and to the licensed Programs are, and
shall at all times remain, the exclusive property of COMSOL and/or its licensor, and Licensee shall have no right, title, or interest therein, except as expressly set forth in this Agreement.
d Non-transferable. Licensee may not sell, license, sublicense, rent, or make the
Programs available for use by third parties generally on a time sharing basis. This license is nontransferable without COMSOLs consent, except to a subsidiary, or parent company of Licensee, provided that COMSOL is notified in writing of the transfer and the transferee accepts these same terms and conditions in writing.
e Reservation Of Rights. All other rights with respect to the licensed Programs
whether now existing or which may hereafter come into existence, which are not
COMSOL SOFTWARE LICENSE AGREEMENT
49
expressly granted to Licensee herein, are reserved for COMSOL. Licensee shall not modify or create derivative works of the licensed Programs.
f License Subject To Payment. The license granted in this Section is contingent
upon the timely and complete payment of all amounts due and payable to COMSOL by Licensee pursuant to this Agreement.
g Use. Should you have licensed the NSL version of the Programs, a single named
individual may use at most one concurrent session of a Program. Licensee may replace the named user for the license, on a temporary or permanent basis, provided only one licensed user is designated as the named user at any given time. Should you have licensed the CPU version, a single individual may use one concurrent session of a Program on a single designated computer at any given time. Should you have licensed the FNL version, Licensee may have as many sessions of a Program in use at any given time as it has licensed concurrent users. If the Programs have the ability to run as client and server on separate computers, only the FNL version gives the right to Licensee to utilize the Programs as client and server on separate computers. Licensee shall use the Programs only for its internal operations. For the purposes of this Agreement, Internal operations shall mean use of the Programs by Licensees employees or those of its subsidiaries or parent company, and in the performance of consulting or research for third parties who engage Licensee as an employee or independent contractor. Licensee may allow use of the Programs by consultants, students and/or (in the case of individual licensees) colleagues.
h No Reverse Engineering. Licensee shall not modify, adapt, translate, prepare
derivative works from, decompile, reverse engineer, disassemble or otherwise attempt to derive source code from the licensed Programs or documentation therefor, except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation. All copies of Programs and Documentation shall contain all copyright and proprietary notices as in the original. Licensee shall not remove, obscure, or alter COMSOL copyright notices, trademark notices, or other proprietary rights notices affixed to or contained within the licensed Programs or documentation. In relation to the Programs which Licensee is entitled to use, Licensee shall not decompile, disassemble or otherwise reverse engineer the Programs except with respect to Licensees located in the European Union, whose rights are as follows: EUROPEAN UNION: Licensee may only decompile, disassemble or otherwise reverse engineer the Programs where any such act is necessary to create an independent program which is interoperable with the Programs or with another
50 |
program or to observe, study, or test the functioning of the Programs solely in order to understand the ideas and principles which underlie any element of the Programs (the Permitted Objective) and provided that: (i) this may only be done if the information necessary to achieve the Permitted Objective has not already been made available or has not been provided by COMSOL within a reasonable time of a written request to COMSOL to provide such information; (ii) the compilation, disassembly or reverse-engineering is confined to those parts of the Programs necessary to achieve the Permitted Objective; (iii) the information gained is not used for anything other than the Permitted Objective and is not disclosed to any other person except as may be necessary to achieve the Permitted Objective; and (iv) the information obtained is not used to create a Programs substantially similar in its expression to the Programs including, but not limited to, expressions of the Programs in other computer languages, or for any other act restricted by copyright in the Programs.
i No Alteration. Except as expressly provided by this Agreement, Licensee may not
alter or modify the Programs without the consent of COMSOL. In particular, Licensee may not alter, adapt, translate or convert source code contained in the Programs in order to use those files with any non-COMSOL software, nor may Licensee incorporate or use source code, or any other part of the Programs in or as part of another computer Program. Licensee shall take appropriate action by instruction, agreement, or otherwise with any persons permitted access to the Programs, so as to enable Licensee to satisfy its obligations under the terms of this Agreement.
j Educational Institutions. Programs licensed to degree-granting educational
institutions at COMSOLs educational discount are subject to separate license provisions and are further restricted to use in connection with on-campus computing facilities that are used solely in support of classroom instruction and research activities of students and teaching faculty. The right to use the Programs for commercial purposes is expressly excluded.
k U.S. Government. If Licensee is acquiring the license to the Programs on behalf
of any unit or agency of the U.S. Government, the following shall apply: (i) For units of the Department of Defense: the Government shall have only the rights specified in the license under which the commercial computer software or commercial software documentation was obtained, as set forth in subparagraph
51
(a) of the Rights in Commercial Computer Software or Commercial Software Documentation Clause at DFARS 227.7202-3,therefore the rights set forth herein shall apply; and (ii) For any other unit or agency: NOTICE: Notwithstanding any other lease or license agreement that may pertain to, or accompany the delivery of, the computer software and accompanying documentation, the rights of the Government regarding its use, reproduction, and disclosure are as set forth in Clause 52.227-19 (c)(2)of the FAR.
l License for Third Party Software. COMSOL has been granted licenses to
distribute certain third party software. As a condition of those licenses, COMSOL is required to distribute the software subject to specific terms and conditions, which may be different from or additional to those contained herein for COMSOLs' Programs. Licensee understands and agrees that acceptance of this Agreement also confirms Licensee's acceptance of the applicable provisions for use, including the restrictions on use, of such third party software. The current applicable provisions are available in the about.txt file in the FEMLAB installation directory, and in the directories under java/jre in the FEMLAB installation directory. Licensee may also contact COMSOL to obtain the current applicable provisions. Licensee's breach of the applicable provisions of any third party's license terms shall also be considered a material breach of this Agreement.
3 Delivery and Installation. COMSOL shall deliver to Licensee the licensed Programs
and Documentation in archival form on CD-ROM and or over the Internet. COMSOL shall provide the Licensee with a passcode which specifies the Programs licensed by Licensee. Licensee shall not attempt to access or use Programs which Licensee is not currently licensed to use. Furthermore, Licensee shall not disclose the archive passcode or allow it to be used except for installation of the Programs as provided herein. If Licensee has licensed the NSL version of the programs, Programs may be installed and operated on one or more individual, standalone computers, provided the Programs are only accessible to, and operated by, a single Licensed User designated by the Licensee as the Named User for that License. If Licensee has licensed the CPU version of the Programs, Licensee may install the Programs on a single designated computer. If Licensee has licensed the FNL version of the Programs, Licensee may install the Programs so that the Programs can be used according to 2 (g). The Programs may be installed on a backup computer/ server (while the designated computer/server is disabled) or on a replacement computer/server. Replacements include both permanent and temporary use at the same or different site. Licensee may make backup copies of the Programs and
52 |
Documentation as necessary to support the use of the Programs in accordance with this Agreement.
4 Payment. Licensee shall pay COMSOL the license fee in accordance with the price
set forth on the applicable purchase order. Licensee may receive a full refund if you terminate this Agreement within thirty (30) days of date of delivery by COMSOL (the Acceptance Period).
5 Compliance with Laws. Licensee shall comply fully with all applicable laws and
regulations relating to import and export of technical data and computer software.
6 Maintenance and Support. During any paid Software Maintenance Service Term in
which Licensee has paid maintenance and support subscription fees as set forth in the applicable purchase order, COMSOL shall: (a) provide Licensee with technical support by telephone, telefax or electronic mail regarding the installation and/or use of the licensed Programs and their interaction with hardware, operating environments, and other software products; (b) provide Licensee with subsequent releases of the Programs free of charge; and (c) use reasonable commercial efforts to (i) provide workarounds within a reasonable time for any material programming errors in the current release of the Programs which are directly attributable to COMSOL, and (ii) correct such errors in the next available release, provided Licensee provides COMSOL with sufficient information to identify such errors. COMSOL may, in its sole discretion, discontinue offering maintenance and support subscriptions for any Programs.
7 WARRANTY. a COMSOL warrants: (i) that COMSOL or its licensors has the right to grant the
license rights hereunder; and (ii) that for a period of ninety (90) days from delivery to Licensee the licensed Program shall conform in all material respects to the functional specifications in the Documentation.
b In the event that the Program does not operate as warranted, Licensees exclusive
remedy and COMSOLs sole liability under this warranty shall be (i) the correction or workaround by COMSOL of major defects within a reasonable time, or (ii) should such correction or workaround prove neither satisfactory nor practical, termination of the relevant license and refund of the initial license fee paid to COMSOL for the Programs.
c All requests for warranty assistance should be directed to COMSOL AB,
Tegnrgatan 23, SE-111 40 STOCKHOLM, Sweden.

d EXCEPT AS EXPRESSLY PROVIDED BY THIS AGREEMENT (OR AS
IMPLIED BY LAW WHERE THE LAW PROVIDES THAT THE
53
PARTICULAR TERMS IMPLIED CANNOT BE EXCLUDED BY CONTRACT), ALL OTHER CONDITIONS, WARRANTIES, OR OTHER TERMS, INCLUDING, WITHOUT LIMITATION, ANY WARRANTY, EXPRESS OR IMPLIED. AS TO THE CONDITION, MERCHANTABILITY, NON-INFRINGEMENT, DESIGN, OPERATION OR FITNESS FOR A PARTICULAR PURPOSE OF THE LICENSED PROGRAMS. SOME JURISDICTIONS DO NOT ALLOW LIMITATIONS ON THE DURATION OF AN IMPLIED WARRANTY, SO THE ABOVE LIMITATION MAY NOT APPLY TO LICENSEE. THIS WARRANTY GIVES LICENSEE SPECIFIC LEGAL RIGHTS AND LICENSEE MAY ALSO HAVE OTHER RIGHTS WHICH VARY FROM STATE TO STATE.
8 LIMITATION OF LIABILITY. IN NO EVENT SHALL COMSOL BE LIABLE
TO LICENSEE FOR TORT, CONSEQUENTIAL, EXEMPLARY, SPECIAL, INCIDENTAL OR PUNITIVE DAMAGES EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN ANY EVENT, THE LIABILITY OF COMSOL FOR ANY LOSS OR DAMAGES DIRECTLY OR INDIRECTLY (EXCEPT FOR LOSS OF PROFITS, LOSS OF BUSINESS, LOSS OF OPPORTUNITY, AND LOSS OF USE OF ANY COMPUTER HARDWARE OR SOFTWARE) SUFFERED BY LICENSEE AS A RESULT OF THE USE OF THE LICENSED PROGRAMS OR ANY FAILURE, ACT, OMISSION OR BREACH OF THIS AGREEMENT BY COMSOL SHALL NOT IN TOTAL EXCEED THE AGGREGATE AMOUNT PAID TO COMSOL UNDER THIS AGREEMENT IN THE TWELVE MONTH PERIOD PRECEDING THE CLAIM IN QUESTION, FOR THE PROGRAMS WITH RESPECT TO WHICH THE LIABILITY IN QUESTION ARISES, AS INSTALLED IN ACCORDANCE WITH THE PERMITTED INSTALLATION TYPES FOR NSL, CPU, AND FNL FOR WHICH THE PROGRAMS ARE LICENSED HEREUNDER. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE EXCLUSION OR LIMITATION MAY NOT APPLY TO YOU.
9 Indemnification. Licensee agrees to indemnify and hold COMSOL harmless from
and against any loss, liability, cost, expense or damage arising out of any claim, suit action or judgment brought against COMSOL or its Affiliates related to your violation of any provincial, state, federal or other laws or regulations or any third party rights.
54 |
10 Third Parties. Licensee shall give notice to COMSOL of third parties that have
access to or use the licensed Programs on behalf of Licensee. Such notice shall identify the third parties by name and home address.
11 Dispute Resolution. If any dispute arises under this Agreement, the parties shall
make a good faith effort to resolve the dispute before taking any action. The parties shall meet to discuss the dispute no later than thirty (30) days after either party gives written notice to the other party that such a dispute exists. Such meeting may be held telephonically if travel is impractical for either party. At such meeting, Licensee and an officer of COMSOL who has authority to resolve the dispute shall be in attendance. No action, suit, arbitration or other proceeding may be commenced before the parties have met pursuant to this provision unless immediate injunctive relief is being sought, in which case such meeting shall take place at the earliest opportunity after such immediate injunctive relief is sought.
12 Waiver Of Jury Trial. The parties hereby agree to waive their respective rights to a
jury trial of any claim or cause of action related to or arising out of this Agreement. The scope of the waiver is intended to be all encompassing of any and all disputes that may be filed in any court and that relate to the subject matter herein, including without limitation, contract claims, tort claims, breach of duty claims, and all other common law and statutory claims. The parties each acknowledge that the waiver is a material inducement for each party to enter into a business relationship, that each party has already relied on the waiver in entering into this Agreement and that each will continue to rely on the waiver in their related future dealings. Each party further warrants and represents that each has had the opportunity to have legal counsel review the waiver. The waiver is irrevocable, meaning that it may not be modified either orally or in writing, and the waiver shall apply to any subsequent amendments, renewals, supplements or modifications to this Agreement. In the event of litigation, this Agreement may be filed as written consent to a trial by court.
13 Prevailing Party. If any legal action or other proceeding is brought for a breach of
this Agreement or any of the warranties herein, the prevailing party shall be entitled to recover its reasonable attorneys' fees and other costs incurred in bringing such action or proceeding, in addition to any other relief to which such party may be entitled.
14 Independent Contractor. The parties are and have been contracted with each other
as independent contractors. Neither party undertakes by this Agreement, or otherwise, to perform any of obligation of the other. In no way is one party to be construed as an agent, or acting as an agent of the other in any respect.
55
1 5 Export Controls. The Programs may be subject to U.S. export control laws.
Notwithstanding any other term of this Agreement, Licensees rights under this Agreement may not be exercised by any third party in violation of such laws and regulations, nor may this Agreement be transferred to any party where doing so would result in such a violation. The terms of any limitation on the use, transfer or re-export of the Programs and Documentation imposed by COMSOL in any destination control statement or other document for the purpose of export control shall prevail over any term in this Agreement.
1 6 Taxes. Each party shall be responsible for any income and other taxes required under
applicable laws arising out of monies received by each of them pursuant to this Agreement.
1 7 Prior Obligations. Each party represents and warrants that entering into and
performing under this Agreement does not conflict with any prior obligations to third parties.
1 8 Termination. COMSOL may terminate this Agreement, by written notice to
Licensee if Licensee breaches any material term of this license, including failure to pay any license fees due, and Licensee has not cured such breach within sixty (60) days of written notification. Licensee may terminate this Agreement at any time, for any reason. Licensee shall not be entitled to any refund if this Agreement is terminated, except of license fees paid for any Programs for which the Acceptance Period has not expired at the time of termination.
1 9 Effect Of Termination. Upon termination of this Agreement: (a) the license granted
in Section 2 above shall immediately terminate; (b) all rights granted herein shall automatically revert to COMSOL; (c) Licensee shall immediately cease and desist from using the licensed Programs; (d) Licensee shall immediately erase all copies of licensed Programs from Licensees computers; (e) Licensee shall immediately deliver to COMSOL all tangible copies of the licensed Programs; and, (f) Licensee shall immediately pay all amounts due COMSOL pursuant to this Agreement. Within five (5) business days of the termination of this Agreement, Licensee shall provide COMSOL with a written declaration signed under penalty of perjury by Licensee attesting to compliance with the provisions of sub-sections (c), (d) and (e) of this Section.
2 0 Waiver Of Breach. A breach of any provision of this Agreement may only be waived
in writing and the waiver of such breach shall not operate or be construed as a waiver of any subsequent breach.
2 1 Severability. If any provision of this Agreement should, for any reason, be held
invalid or unenforceable in any respect, the remainder of this Agreement shall be
56 |
enforced to the full extent permitted by law. A court of competent jurisdiction is hereby empowered to modify the invalid or unenforceable provision to make it valid and enforceable.
22 Performance Excused. The parties shall be excused from delays in performing or
from any failure to perform hereunder to the extent that such delay or failure results from causes such as war or natural disaster or strike which are beyond the reasonable control of the affected party, provided that, in order to be excused from delay or failure to perform, the affected party must act diligently to remedy such delay or failure. In the event such delay continues for five (5) consecutive days, either party shall have the right to terminate this Agreement.
23 Entire Agreement. This Agreement and the applicable Addendum hereto contain
the entire understanding of the parties and may not be modified or amended except by written instrument, executed by authorized representatives of COMSOL and Licensee.
57
58 |
I N D E X
B
boot script 32 Bourne shell commands 32
initializing 38 running within MATLAB remotely 39 FLEXlm 25 control panel 27 End Users Guide 27, 30, 33 license server 27, 30, 33 management 27, 30, 33 utility program 27, 30, 33 floating network license 25 floating network license support heterogeneous network 3
classpath file on UNIX/Linux 20 on Windows 16 client 25 client/server running FEMLAB as 37 security issues with 42 custom installation 18
daemon license manager 27, 30, 33 starting 32 vendor 27, 30, 33 DirectX 46 disabling 46 updating to latest version 44 documentation 2
G H
graphics requirements, Linux 4 hostid 35 HP 35 in license file 26 Linux 35 Mac OS X 36 of license server 27 Windows 36 HP-UX 4
E F
Ethernet address 36 FEMLAB documentation 2 installing 7, 17 online help 2 running 15, 20 running with MATLAB 16, 20 running with MATLAB as client/server
37
I
initializing a FEMLAB server 38 installation custom 18 floating network license 25 Linux 17 Mac OS X license manager 33 minimal 17 PC license server 27 typical 17 UNIX 17 UNIX/Linux license server 29
Start menu items 15 technical support 2 uninstalling 17, 19 FEMLAB applications on Mac OS X 23 femlab command 20 FEMLAB server accessing 38
L
license file 17, 26 license manager FLEXlm 25 installing files 27
INDEX|
1-1
starting 28, 31, 34 license manager daemon 27, 30, 33 license manager files 27 license manager installation Mac OS X 33 PC/Windows 27 UNIX/Linux 29 license server definition of 25 license server files 27, 30, 33 license.dat 26 Linux graphics requirements 4 hostid 35 installing FEMLAB on 17 lmgrd 30, 33 lmgrd.exe 27 lmhostid 35 lmutil 30, 33 lmutil.exe 27 log file 29, 32, 34 login information 42
M
obtaining a license file 26 online help 2 OpenGL 3, 4, 5
PA-RICS 4 passcode format of 6, 21 Pentium II 3 port number 26 for FEMLAB server 38 processor PA-RISC 4 Pentium II 3 UltraSPARC 4
R S
running FEMLAB 15, 20 security issues in client/server mode 42 Solaris 4 Start menu, FEMLAB folder 15 superuser 32 system recommendations 3 system requirements general 3 Mac OS X 5 UNIX/Linux 4 Windows 3
Mac OS X hostid 36 license manager installation 33 system requirements 5 machine identification 36 MATLAB requirements 4, 5 running FEMLAB with 16, 20 Mesa library 4 Microsoft Windows hostid 36 system requirements 3 Windows 2000 3 Windows NT 4.0 3 Windows XP 3
V U T
TCP/IP 3 technical support 2 Telnet Server setup 39 UltraSPARC 4 uninstalling FEMLAB 17, 19 UNIX installing FEMLAB on 17 system requirements 4 utility program 27, 30, 33 vendor daemon 27, 30, 33
named single user license 31
W Windows. See Microsoft Windows
1-2 | I N D E X

Emlab: Installation Guide

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Emlab: Installation Guide

Diunggah oleh

Hak Cipta:

Format Tersedia

FEMLAB

How to contact COMSOL: Denmark

Company home page

Removing (Uninstalling) the FEMLAB Installation . . . . . . . . . . . 13 Running FEMLAB on Windows 15

Running FEMLAB . . . . . . . . . . . . . . . . . . . . . . . 20 Running FEMLAB with MATLAB . . . . . . . . . . . . . . . . . 20 Running FEMLAB 2.3 . . . . . . . . . . . . . . . . . . . . . 20

Installing FEMLAB on Mac OS X

Client/Server Security Issues . . . . . . . . . . . . . . . . . . 42 Troubleshooting Graphics 43

Chapter 2: License Agreement

FEMLAB Quick Start and Online Help

CHAPTER 1: INSTALLATION GUIDE

System Requirements for Microsoft Windows

OPT IONA L MATL AB A DD-ON RE QUI RE MENT S

The FEMLAB interface to MATLAB requires MATLAB 6.5 or MATLAB 6.5.1.

System Requirements for UNIX/Linux

Pentium II or later UltraSPARC II or later PA-RISC 2.0

In addition, see the graphics requirements in the following sections.

Linux Graphics Requirements

Solaris Graphics Requirements

CHAPTER 1: INSTALLATION GUIDE

HP-UX Graphics Requirements

The FEMLAB interface to MATLAB requires MATLAB 6.5 or MATLAB 6.5.1.

System Requirements for Mac OS X

The FEMLAB interface to MATLAB requires MATLAB 6.5.1 and X11.

CHAPTER 1: INSTALLATION GUIDE

Installing FEMLAB 3.0a

INSTALLING FEMLAB ON WINDOWS

Note: The passcode is case sensitive.

CHAPTER 1: INSTALLATION GUIDE

6 Click Next. 7 Enter your user information: name and company.

9 Choose the install setTypical, Minimal, or Customand then click Next.

INSTALLING FEMLAB ON WINDOWS

1 0 If you choose Custom, select the features to install.

CHAPTER 1: INSTALLATION GUIDE

MATLAB root folder.

14 Click Next. 15 Specify the path to the FEMLAB installation directory.

INSTALLING FEMLAB ON WINDOWS

1 7 Review the preinstallation summary.

CHAPTER 1: INSTALLATION GUIDE

Removing (Uninstalling) the FEMLAB Installation

INSTALLING FEMLAB ON WINDOWS

STARTING THE UNINSTALLER

Click Uninstall to start removing the installation.

CHAPTER 1: INSTALLATION GUIDE

RUNNING FEMLAB ON WINDOWS

Running FEMLAB with MATLAB

Running FEMLAB 2.3

CHAPTER 1: INSTALLATION GUIDE

Installing FEMLAB 3.0a

then click Next .

INSTALLING FEMLAB ON UNIX/LINUX

(the directory containing the subdirectory toolbox).

Optional FEMLAB 2.3 Installation

CHAPTER 1: INSTALLATION GUIDE

Removing (Uninstalling) the FEMLAB Installation

INSTALLING FEMLAB ON UNIX/LINUX

Running FEMLAB with MATLAB

Additional Options to the FEMLAB Command

Running FEMLAB 2.3

CHAPTER 1: INSTALLATION GUIDE

Installing Java 3D and Java Advanced Imaging

To install after the download:

was not done automatically after the file was downloaded.