HyperWorks_11.0_Quick_Install_Guide

Altair HyperWorks 11.0 Quick Installation Guide

For Windows, Unix and Linux

This guide provides instructions for the quick installation of Altair HyperWorks, modes of installation and the use of properties response files.

HyperWorks 11.0 uses InstallAnywhere 2010 as its installation tool. The HyperWorks 11.0 installers are based on InstallAnywhere web installers. InstallAnywhere provides the tools required to have a consistent look and feel for the HyperWorks installers across all supported platforms.

HyperWorks Installation Modes

I.Graphical user Interface (GUI) Mode

II.Console Mode

III.Silent Mode

IV.Response Files

V.Windows Network Server install – Client NETSETUP installs

VI.Connecting to the Altair License Management System

VII.Uninstalling of HyperWorks

VIII.K nown Issues and Limitations

I.Graphical User Interface (GUI) Mode

1.Download the HyperWorks package according to the preferred platform. Below are the installer

packages listed by name and platform type:

Installer Filename Platform Type

hw11.0_win32.exe Windows 32‐bit

hw11.0_win.exe Windows ‐bit

hw11.0_linux32.bin Linux 32‐bit

hw11.0_linux.bin Linux ‐bit

hw11.0_batch_aix.bin IBM AIX 5.3 ‐bit (batch and solvers only)

Help Files Filename Platform Type

help11.0_win32.exe Windows 32‐bit

help11.0_win.exe Windows ‐bit

help11.0_linux32.bin Linux 32‐bit

help11.0_linux.bin Linux ‐bit

help11.0_aix32.bin IBM AIX 5.3

NOTE: How to install Help Files:

a.Download and place the Help Files executable file in the same residing directory as the

main HyperWorks installer.

b. Select Help Files for complete Help, tutorials and demo files or a combination of the

three options. Reference step 9 below.

2.On Windows:

a.Double click the installer executable file to start the installer

NOTE: If UAC (User Account Control Enabled) is enabled then a prompt will be displayed for

elevated permissions. Click “Yes” to continue with installer.

On Linux/Unix:

a.Run the ‘sh’ command on the installer binary. Example, sh hw11_linux.bin

3.The HyperWorks installer will now extract the JVM (Java Virtual Machine) and the install

modules to the TMP location of the machine.

4.The multi‐language selector prompt will be displayed. Select the proper locale and click “OK” to

continue. The default locale setting is specific to the install machine regional settings.

NOTE: The language selection only corresponds to the installer settings not to the HyperWorks product language settings. Altair HyperWorks products are in English.

5.The “Introduction” and “Copyright” panels are going to be displayed for viewing. Click “Next” to

continue.

6.(Windows only) The “Choose Installation Type” panel is displayed. Choose install type, either

Local or Server type installs and click “Next”.

NOTE: HyperView Player, SolidThinking/Inspired and AcuSolve/CFD integration is not available in the server type installs.

7.The “Choose Install Folder” panel is displayed. Choose install path and click “Next”.

a.The default path is “C:\\Program Files\\Altair\\11.0” for Windows and the user’s home

folder and installer version on Linux/Unix.

b.The installer does not allow the use of characters # and ;

c.Installing to a root drive is not permitted, example C:\

8.(Windows only) The “Choose Shortcut Folder” panel is displayed. This allows for users to

customize:

a.Start Menu Folder name. The default is “Altair HyperWorks 11.0 (‐bit)”, where the bit

type is dependent on the version of the installer.

b.Pick to install Desktop shortcuts. The default option is set to not install desktop

shortcuts.

Choose preferred options and click “Next” to continue.

NOTE: For Windows Server type installs the “Choose Shortcut Folder (Server)” panel also allows for more customizability for users to choose the shortcut folder install location, which defaults to the “All Users” shortcut folder location. For Server and Client installs the word Server and

Client will be pre‐appended to the bit type, example Altair HyperWorks 11.0 (Server ‐bit).

9.The “Choose Install Set” panel is displayed. Select “Complete” or “Custom” installer types and

click “Next” to continue.

a.Selecting Custom will allow for choosing selective products and help files install

combinations.

b.If Help Files is selected then the corresponding help installer executable must reside in

the same directory as the installer to be installed. (See Step 1 for filenames and platform

types)

10.If Help is selected to be installed then continue to next step. If Help is not selected, The “Help

Configuration” panel is displayed. The three alternate Help configurations are:

a.Connect to a network installed Help location.

•This will prompt for the pre‐installed Help location. The variable used is

HW_MSG_HELP in the hwhelp.cfg in the install directory.

b.Connect to Altair website Help (Default)

•Requires internet web access

c.Set Up Later

•Requires manipulation of the hwhelp.cfg file located in the installation folder for manual setup.

NOTE: The default browser setting (HW_MSG_BROWSER) defaults to the Windows default

browser on Windows and on Linux/Unix a browser prompt will request for the path and file of a web browser to use.

11.(Windows Server Install Types Only) The UNC (Uniform Naming Convention) mount point panel

is displayed if:

a.Server install type was selected.

b.The install path used contained a Windows drive letter, example C:\\pathname\\folder

Input the UNC path and click “Next” to continue.

NOTE: The user input needs to be in the form of the UNC standard

\\\\MachineName\\SharedFolder\\InstallFolder to be accepted.

12.The “HyperWorks AcuSolve Notice” prompt message is displayed. Review message and click

“OK” to continue.

13.The “Pre‐Installation Summary” panel is displayed. Review selections and click “Install” to

continue.

NOTE: Install times are machine hardware dependant. Anti‐Virus software may lengthen the

install times.

14.Once the installation completes, click “Done” to exit the installer.

Optional AcuSolve Integration Installation

15.Download and install the AcuSolve CFD solutions installer separately from the above Altair

HyperWorks installer.

16.To start the AcuSolve CFD solutions installer:

a.On Windows, double click the executable to start the installer

b.On Linux:

•Uncompress the *.tgz file. It will uncompress to a folder, example “AcuSolve‐

V1.8a_LINUX”

•Change directory (cd) into the newly uncompressed folder from the step above

•Type ./INSTALL in the terminal and follow the on screen prompts and questions

•Set the environment by sourcing the .acusim file

NOTE: Reference the README.txt file for additional information.

17.After the AcuSolve CFD solutions installer completes, the acuSetHW utility will be executed

automatically to establish the connection between the Altair HyperWorks and the AcuSolve

tools suite.

NOTE: To run AcuSolve, Perl 5.0 or higher must be installed on the system. If not installed, it can be downloaded from http://www.activestate.com/activeperl/downloads

II.Console Mode

Console mode installs mimic the default Graphical User Interface steps provided by the HyperWorks installer but use only the standard input and output. The advantage to console mode is that Linux/Unix user no longer needs X‐windows (X11) to run the installer.

Console mode allows for text to be output to the console terminal line‐by‐line. It does not allow for any formatting, clearing of the screen, or positioning of the cursor. To trigger a console mode installer from the command line, append the following command parameter to the installer: ‐i console An Example console mode install call, hw11.0_linux.bin –i console

The Linux console mode is only supported on the HyperWorks Linux/Unix installers. Just follow the on screen instructions to complete the install.

III.Silent Mode

Silent mode enables the installer to run without any user interaction. A near‐silent mode is possible on Windows and Mac OS X. InstallAnywhere and HyperWorks end‐users‐defined variables may be set through command line parameters or a properties response file.

Response files are created and ten used in silent mode since there is no end user interaction. The installer runs either on the defaults provided by the installer package or by providing a response file from which the installer retrieves the values for various InstallAnywhere and HyperWorks variables used to control the install.

The installer automatically checks the residing directory for a file caller installer.properties. You can generate a response file from the installer by running through the installer with the following command line syntax: ‐r [FullPath]\\installer.properties. The file will get created once the installer is complete. To trigger a silent installer from the command line, type the following:

[installername] –i silent

You may also call a properties response file from the command line by typing:

[installername] –i silent –f [fullpath]\\installer.properties

An Example of running a silent install using a properties response file located in C:\\ResponseFiles called hw11_silent.properties on Windows ‐bit:

hw11_win.exe –i silent –f c:\\ResponseFiles\\hw11_silent.properties

IV.Response Files

Response Files are used with the silent mode installers to give the default values of an install. The files contain text in a simple key=value format. An example of a properties response file is shown below:

#Choose Installation Type

#‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐

LOCAL_INSTALLATION=1

SERVER_INSTALLATION=0

#Choose Install Folder

#‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐

INSTALLER_UI=silent

USER_INSTALL_DIR=C:\\\\Program Files\\\\Altair\\\\11.0

#Change Shortcut Folder (Local)#‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐

SET_START_MENU_FOLDER=Altair HyperWorks 11.0

INSTALL_DESKTOP_SHORTCUTS=1

DONOT_INSTALL_DESKTOP_SHORTCUTS=0

#Choose Install Set

#‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐

CHOSEN_FEATURE_LIST=HWFhelp,SLVR,MFS,HST,HWD,HC,HW,HWX,DesktopApps,sT,ES,helpHW,tuts HW,demosHW

CHOSEN_INSTALL_FEATURE_LIST=HWFhelp,SLVR,MFS,HST,HWD,HC,HW,HWX,DesktopApps,sT,ES,help HW,tutsHW,demosHW

CHOSEN_INSTALL_SET=Complete

The values in the response files are all referenced from user input taken from a HyperWorks install and used as default values toward future installs.

For example, the INSTALLER_UI value in the above example is set to “silent”. This negates the need to use “‐I silent” on the command line as a silent installer switch.

NOTE: The installer will use double backslashes “\\\\” on windows for the directory names and forward slash “/” on Linux/Unix.

V.Windows Network Server Installs – Client NETSETUP Installs

This section describes the client NETSETUP of a HyperWorks network server install on Windows only. The NETSETUP supports the GUI and silent mode installations modes. The example below is shown for a GUI NETSETUP client Windows 7 ‐bit install.

Requirements for a NETSETUP client install:

a.Altair HyperWorks network server install

b.The UNC paths of the location of the HyperWorks network server installs (or use

Networks on Windows 7/Vista or My Network Places on Windows XP to get to the

NETSETUP client installer directory). The installer does not allow for the use of drive

letter or mapped paths.

1.Go to the HyperWorks network server install NETSETUP directory location and run the

NETSETUP.bat file.

a.Go to Networks

b.Click on the machine and install location of the HyperWorks server install

c. Go to the NETSETUP folder

d.Go to the win folder (on a 32‐bit Windows install the folder is win32)

e.Click on the NETSETUP.bat file

2.A command prompt terminal window will be displayed showing that the installer is unpacking

on the client machines. The locale language selection prompt will then be displayed. Select the locale language and click OK to continue.

3.The HyperWorks NETSETUP client Start Menu and Desktop Shortcuts options panel is displayed.

Make changes if needed and select “Next” to continue.

4.The HyperWorks NETSETUP Pre‐Installation Summary panel is displayed. Review summary and

click “Install” to complete the HyperWorks NETSETUP client install.

5.This will create the appropriate Start Menu and Desktop Shortcuts to the client machine. Once it

completes, click “Done” to exit installer.

VI.Connecting to the Altair License Management System

About the Altair License Management System

The Altair License Management System (ALM) provides a common units‐based licensing model for all Altair software related to CAE, on‐demand computing, and business intelligence. This new system has been designed to enable HyperWorks Partner Products (selected third party products) to be licensed via HyperWorks Units as well.

The Altair License Management System is comprised of two components: the License Server and the Usage Reporting System (URT). The license system is based on X‐Formations LM‐X license server. The URT is a java application that reports anonymous transactional logs to Altair. As part of the license agreement that enables partner software to be used, product usage must be reported to Altair.

The ALM is based on X‐Formation’s LM‐X license management system version 3.32. For additional information and details, please download the LM‐X End User Guide from the Altair web site at http://www.altairhyperworks.com, and choose Support > Software Downloads.

Connecting to Altair License Manager (ALS)

In order for applications to use the ALS, the environment variable, ALTAIR_LICENSE_PATH, must point to the appropriate location. Multiple license paths are allowed and should be separated by a semicolon (;) on Windows and a colon (:) on Unix/Linux. The proper format for a network license location is port@hostname. If you are using a local license file, simply set the value to the full pathname of the file.

A few examples of license paths

On Windows:

HyperWorks 11.0 Quick Install Guide7ALTAIR_LICENSE_PATH=6200@server.foo.bar.com

ALTAIR_LICENSE_PATH=6200@srv1;6200@srv2;6200@srv3

ALTAIR_LICENSE_PATH=c:\\Program Files\\Altair\\Licensing11.0\\altair_lic.dat

On Linux/Unix:

ALTAIR_LICENSE_PATH=6200@server.foo.bar.com

ALTAIR_LICENSE_PATH=6200@srv1:6200@srv2:6200@srv3

ALTAIR_LICENSE_PATH=/usr/local/altair/licensing11.0/altair_lic.dat

For High Availability License (HAL) System and/or Multiple Servers setups, list the three servers in the order: primary; secondary; tertiary.

Node‐Locked License

For node‐locked license (a license that is locked to a local machine), you can either place the license file in the /altair/security/ directory, or set the environment variable,

ALTAIR_LICENSE_PATH, to point to the appropriate location where the license file resides. The default name that Altair products use for this license file is altair_lic.dat.

VII.Uninstalling HyperWorks

On Windows:

1.Go to Altair HyperWorks Start Menu item

a.Go to Start

b.Go to All Programs

2.Go to where the Altair HyperWorks shortcuts are located, defaults to Altair HyperWorks 11.0

(‐bit) or Altair HyperWorks 11.0 (32‐bit) for Windows ‐bit and 32‐bit, respectively.

3.Go to Tools

4.Go to Admin Tools

5.Click on Uninstall_HyperWorks11

6.This will launch the uninstaller to remove the Altair HyperWorks install from the machine.

On Linux/Unix:

1.Open a terminal prompt

2.Go to the installed Altair HyperWorks home location and run the “sh uninstall” command.

Example, the command is: sh /caeapps/hw11/altair/uninstall

Where $ALTAIR_HOME=/caeapps/hw11

VII. Known Issues and Limitations

Installer Issues:

1.On Linux, in order for the installer to work directly off of the DVD‐ROM install media, the DVD‐

ROM device needs executable permissions along with file executable permissions. There are

new security implementations that disable auto‐mounting DVD‐ROM executable device

8 HyperWorks 11.0 Quick Install Guide

permissions under newer Gnome window managers, by default. Manually change the mounting options to include executable permissions on the device or copy the files to the local hard disk before running the installer.

Uninstall Issues:

1.Files may be left behind in the installation directory after uninstaller completes (GUI – Remove

Original Install Files Only, console and silent modes). Manual removal of these files is required.

2.A false warning message may appear at the end of the uninstaller stating that a log file/folder

could not be removed during the uninstall process. The file/folder will be removed a few

moments after pressing the “Done” button within the message window.

Windows Server/Client (only):

1.For Windows network server/client‐based installations, the integration of the AcuSolve CFD

solutions with the HyperWorks framework is not supported.

2.The NETSETUP client installs require that a UNC path be used to get to the server installation

path through Windows Explorer or Windows Network for a NETSETUP client install.

Miscellaneous:

1.On Linux, the Help Configuration prompt will add another set of double quotes if the “back”

command is used under the console mode installer. If new input is used, then the issue does not occur.

2.On Linux, when installing via console mode an extra set of quotes will be added o the help

browser variable HW_MSG_BROWSER listed in the hwhelp.cfg file (e.g. HW_MSG_BROWSER

“”/usr/bin/firefox””). Remove the extra set of double quotes to make the help work correctly.

3.A Java plug‐in is required for Help search on Linux

4.ActiveX is required for Help search on Windows.

5.Help search on local hard disk installs requires access to local files to be allowed in the web

browser. There is not an issue if accessing the Altair web help.

HyperWorks 11.0 Quick Install Guide9