learn more at altairhyperworks - altair forum

Learn more at altairhyperworks.com

Copyrights, Trademarks, Patents and Third Party Licenses

Intellectual Property Rights Notice:

Copyrights, Trademarks, Trade Secrets, Patents & Third Party Software Licenses

Altair® HyperWorks® v.2017

A Platform for Innovation®

Copyright© 1986-2016 Altair Engineering Inc. All Rights Reserved.

Special Notice: Pre-release versions of Altair software are provided ‘as is’, without warranty of any kind. Usage is strictly limited to non-production purposes.

HyperWorks® 2017 Products

HyperMesh® 1990-2016; HyperCrash® 2001-2016; OptiStruct® 1996-2016; RADIOSS® 1986-2016; HyperView® 1999-2016; HyperView Player® 2001-2016; HyperMath® 2007-2016; HyperStudy® 1999-2016; HyperGraph® 1995-2016; MotionView® 1993-2016; MotionSolve® 2002-2016; HyperForm® 1998-2016; HyperXtrude® 1999- 2016; Process Manager™ 2003-2016; Templex™ 1990-2016; TextView™ 1996-2016; MediaView™ 1999-2016; TableView™ 2013-2016; BatchMesher™ 2003-2016; HyperWeld® 2009-2016; HyperMold® 2009-2016; Manufacturing Solutions™ 2005-2016; solidThinking Inspire® 2017 2009-2016; solidThinking Evolve® 2017 1993-2016; Durability Director™ 2009-2016; Suspension Director™ 2009-2016; AcuSolve® 1997-2016; AcuConsole® 2006-2016; SimLab® 2004-2016; Virtual Wind Tunnel™ 2012-2016; FEKO® (©1999-2014 Altair Development S.A. (Pty) Ltd.; ©2014-2016 Altair Engineering, Inc.); ConnectMe™ 2014-2016.

Additional Altair Products:

Multiscale Designer™ 2011-2016; Flux™ v.12.2 1983-2016; InCa3D v.3.1 1996-2016; CDE v.2 2012-2016; Got-It v.3 2002-2016; WinProp v.14 2000-2016

Altair Packaged Solution Offerings (PSOs) Copyright© 2008-2016

Automated Reporting Director™ 2008-2016; GeoMechanics Director 2011-2016; Impact Simulation Director™ 2010-2016; Model Mesher Director™ 2010-2016; Model Verification Director™ 2013-2016; NVH Director™ 2010-2016; Squeak and Rattle Director™ 2012-2016; Virtual Gauge Director™ 2012-2016; Weight Analytics™ 2013-2016; Weld Certification Director™ 2014-2016

Altair Simulation Cloud Suite:

Simulation Manager™ 2003-2016; Compute Manager™ 2003-2016; Display Manager™ 2003–2016; and Process Manager™ 2003-2016.

Altair PBS Works™:

Compute Manager™ 2012-2016; Display Manager™ 2013-2016; PBS™ 1994-2016; PBS Pro™ 1994-2016; PBS Professional® 1994-2016; PBS Application Services™ 2008-2016; PBS Analytics™ 2008-2016; and PBS Desktop™ 2008-2012; e-Compute™ 2000-2010; OpenPBS® 1994-2003 and Personal PBS® 2008-2012.

Software products of solidThinking, Inc., a wholly owned subsidiary of Altair Engineering:

solidThinking Inspire® 2017 2009-2016; solidThinking Evolve® 2017 1993-2016; solidThinking Compose™ 2017 2007-2016; solidThinking Activate™ 2017 1989-2016; solidThinking Embed™ 2017

1989-2016; solidThinking Embed™ SE 2017 1989-2016; Click2Extrude™ Metal 2017 1996-2016; Click2Extrude™ Polymer 2017 1996-2016; Click2Cast® 14.0 2011-2016; Click2Form™ 2017 1998-2016; Envision™ 2013-2016.

ALTAIR ENGINEERING INC. Proprietary and Confidential. Contains Trade Secret Information.

Not for use or disclosure outside of Altair and its licensed clients. Information contained in Altair software shall not be decompiled, disassembled, “unlocked”, reverse translated, reverse engineered, or publicly displayed or publicly performed in any manner. Usage of the software is only as explicitly permitted in the end user software license agreement. Copyright notice does not imply publication.

Third party software licenses

AcuConsole contains material licensed from Intelligent Light (www.ilight.com) and used by permission.

Software Security Measures:

Altair Engineering Inc. and its subsidiaries and affiliates reserve the right to embed software security mechanisms in the Software for the purpose of detecting the installation and/or use of illegal copies of the Software. The Software may collect and transmit non-proprietary data about those illegal copies. Data collected will not include any customer data created by or used in connection with the Software and will not be provided to any third party, except as may be required by law or legal process or to enforce our rights with respect to the use of any illegal copies of the Software. By using the Software, each user consents to such detection and collection of data, as well as its transmission and use if an illegal copy of the Software is detected. No steps may be taken to avoid or detect the purpose of any such security mechanisms.

Technical Support

Altair provides comprehensive software support via web FAQs, tutorials, training classes, telephone, and e-mail.

Altair Support on the World Wide Web

The Altair web site is a valuable online companion to Altair software. Visit www.altairhyperworks.com for tips and tricks, training course schedules, training/tutorial videos, and other useful information.

Altair Training Classes

Altair training courses provide a hands-on introduction to our products, focusing on overall functionality. Courses are conducted at our main and regional offices or at your facility. If you are interested in training at your facility, please contact your account manager for more details. If you do not know who your account manager is, please send an e-mail to [email protected] and your account manager will contact you.

Telephone and e-mail

When contacting Altair support, please specify the product and version number you are using along with a detailed description of the problem. Many times, it is very beneficial for the support engineer to know what type of workstation, operating system, RAM, and graphics board you have, so please have that information ready. If you send an e-mail, please specify the workstation type, operating system, RAM, and graphics board information in the e-mail.

To contact an Altair support representative, reference the following table or the information available on the HyperWorks website:

http://www.altairhyperworks.com/ClientCenterHWSupportProduct.aspx

Location Telephone e-mail

Australia 64.9.413.7981 [email protected]

Brazil 55.11.3884.0414 [email protected]

Canada 416.447.6463 [email protected]

China 86.400.619.6186 [email protected]

France 33.1.4133.0992 [email protected]

Germany 49.7031.6208.22 [email protected]

India 91.80.6629.4500 1.800.425.0234 (toll free)

[email protected]

Italy 39.800.905.595 [email protected]

Japan 81.3.5396.2881 [email protected]

Korea 82.70.4050.9200 [email protected]

Mexico 55.56.58.68.08 [email protected]

http://www.altairhyperworks.com/

mailto:[email protected]

New Zealand 64.9.413.7981 [email protected]

North America 248.614.2425 [email protected]

Scandinavia 46.46.460.2828 [email protected]

Spain 34.910.810.080 [email protected]

South Africa 27.21.8311500 [email protected]

United Kingdom 01926.468.600 [email protected]

For questions or comments about this help system, send an email to [email protected].

In addition, the following countries have resellers for Altair Engineering: Colombia, Czech Republic, Ecuador, Israel, Russia, Netherlands, Turkey, Poland, Singapore, Vietnam, Indonesia

Official offices with resellers: Canada, China, France, Germany, India, Malaysia, Italy, Japan, Korea, Spain, Taiwan, United Kingdom, USA

See www.altair.com for complete contact information.

mailto:[email protected]

Contents

1 Introduction................................................................................................................... 3

1.1 About HyperWorks...........................................................................................................41.2 HyperWorks 2017 Licensing..............................................................................................51.3 HyperWorks 2017 Software and Hardware Release Notes..................................................... 6

2 Preparing to Install HyperWorks............................................................................ 10

2.1 Installation Media.......................................................................................................... 112.1.2 Configuring Non-US Keyboards................................................................................. 12

3 Installing HyperWorks...............................................................................................13

3.1 Local Installation........................................................................................................... 143.1.1 Installation Files......................................................................................................143.1.2 GUI Mode.............................................................................................................. 153.1.3 Console Mode......................................................................................................... 373.1.4 Silent Mode............................................................................................................40

3.2 Client/Server Installation................................................................................................ 453.2.1 Requirements......................................................................................................... 453.2.2 GUI Mode.............................................................................................................. 453.2.3 Silent Mode............................................................................................................56

4 Connecting to the Altair License Management System 13.0............................ 58

4.1 Requirements................................................................................................................ 594.2 Node Locked Licenses.................................................................................................... 60

5 Starting HyperWorks Applications..........................................................................61

5.1 Starting on Windows......................................................................................................62Changing the Default Working Directory on Windows...........................................................62

5.2 Starting on Linux...........................................................................................................63Obtain a List of Arguments for an Application on Linux........................................................66

6 Setting up HyperWorks Help................................................................................... 68

1

6.1 Starting Help from the Application Menu.......................................................................... 706.2 Starting Help from the altair/scripts Directory on Linux...................................................... 716.3 Accessing Help Installed on a Server on Windows............................................................. 72

7 Seting up the CAD Translators................................................................................73

7.1 UG Environment Variable Settings................................................................................... 747.2 CATIA V5 License.......................................................................................................... 76

8 Uninstalling...................................................................................................................77

8.1 Uninstalling: Windows.................................................................................................... 78Windows Silent Uninstalls Using a Response File................................................................. 78

8.2 Uninstalling: Linux......................................................................................................... 80

2

Introduction 11 Introduction

This chapter covers the following:

• 1.1 About HyperWorks (p. 4)

• 1.2 HyperWorks 2017 Licensing (p. 5)

• 1.3 HyperWorks 2017 Software and Hardware Release Notes (p. 6)

This guide provides instructions for the installation and operation of HyperWorks software on supportedplatforms. This includes the procedures for connecting to an Altair HyperWorks licensing managementsystem, execution of the applications and connecting the application clients to existing HyperWorkshelp, including local, networked and web help.

The details of installing RADIOSS HMPP, OptiStruct SPMD, and configuration of AcuSolve products aredocumented in the HyperWorks 2017 Advanced Installation Guide.

HyperWorks 2017 uses InstallAnywhere 2015 SP1 as its installation tool. The HyperWorks 2017installers are InstallAnywhere web installers. InstallAnywhere provides a consistent look and feel of theHyperWorks installation wizard across all platforms supported by Altair HyperWorks products.

In order to run HyperWorks 2017 applications, you need to connect the applications to the AltairLicense Management System 13.0 (or higher, using the latest version is recommended). Detailsof the installation and how to start the Altair License Manager can be found in the Altair LicenseManagement System 13.0 Installation Guide. The license packages are available on the Altair web site(altairhyperworks.com) or Altair Connect (connect.altair.com).

HW Installation Guide 4

1.1 About HyperWorks

HyperWorks® is the most comprehensive open-architecture simulation platform, offering best-in-classtechnologies to design and optimize high performance, efficient and innovative products.HyperWorksincludes finite element modeling, analysis and optimization for structures, fluids, multibody dynamics,electromagnetics and antenna placement, model-based development, and multiphysics. Users have fullaccess to a wide suite of design, engineering, visualization, and data management solutions from Altairand its technology partners.

The HyperWorks 2017 suite offers many new functionalities in areas such as model-based development,electromagnetism, composites structures analysis, efficient modeling and meshing, multiphysics andmulti-disciplinary analysis, structural optimization and design exploration.


1.2 HyperWorks 2017 Licensing

HyperWorks 2017 licensing is based on HyperWorks Units (HWUs). HyperWorks Units licenses areserver licenses. Customers can launch any application within the HyperWorks suite as long as there aresufficient HyperWorks Units to grant the license check out.

To invoke HyperWorks 2017 applications, after completing the HyperWorks 2017 installation, you needto point the applications to an activated Altair License Manager or a valid node stand-alone license bysetting the proper environment variable.

The HyperWorks 2017 package does not include the license package that sets up the Altair LicenseManager. Download the Altair license package from the Altair web site and follow the Altair LicenseManagement System 13.0 Installation and Operation Guide to install and activate the Altair LicenseManager properly.

In some cases, Altair provides “feature” based licenses, which allow a particular application to run aslong as the feature exists in the license file. A feature license is a standalone license that does notconsume HyperWorks Units.

Questions regarding the software and license installation may be directed to Altair Support. See theTechnical Support page for further contact information.


1.3 HyperWorks 2017 Software and Hardware ReleaseNotes

Various changes have been made to the HyperWorks 2017 software package including the HyperWorksproducts, hardware support, installation, and invoking process.

Note: Changes to the Altair Licensing System are detailed in the Altair HyperWorksLicensing Release Notes.

New ApplicationsClick2Extrude Metal

solidThinking® Click2Extrude Metal™ is a simulation environment designed to help extrusioncompanies meet the ever increasing demands to produce complex profiles with tight tolerances,quality surface finishes, and high strength properties at reduced cost. Click2Extrude Metal isa virtual press where users can visualize material flow and temperature inside a die duringextrusion and make necessary changes to ensure balanced flow, while identifying and eliminatingproduct defects.

Click2Extrude PolymersolidThinking® Click2Extrude Polymer™ is a simulation environment designed to help extrusioncompanies meet the ever increasing demands to produce complex profiles with tight tolerances,quality surface finishes, and high strength properties at reduced cost. Click2Extrude Polymeris a virtual press where users can visualize material flow and temperature inside a die duringextrusion and make necessary changes to ensure balanced flow, while identifying and eliminatingproduct defects.

Click2Form

solidThinking® Click2Form™ is a virtual environment for early stamping feasibility analysis basedon part or tooling geometry. It allows you to look at thinning and formability issues as well asestimate blank shape and maximize material utilization via blank fitting and nesting utilities.

Altair ConnectMeAltair ConnectMe is a tool that provides a window based launcher, Altair software update alerts,and Altair news. It provides a single place to search, filter, launch, and update Altair products.

Hardware and Platform ChangesOperating Systems Additions

Support for the following platforms has been added:

• Windows 10

• Red Hat Enterprise Linux 7.2

• SUSE Linux Enterprise Server 12 Service Pack 1


• CentOS Linux 7.2

Discontinued Hardware Platform Support SystemsSupport for the following platforms has been dropped across all HyperWorks applications:

• Windows Server 2008

• CentOS Linux 5.9

• Red Hat Enterprise Linux 5.9

• Mac OS X (all)

InstallationThe HyperWorks 2017 suite contains several independent product packages. This gives you theflexibility to download desired packages as needed. Any HyperWorks 2017 standalone (SA) updatepackage can be installed either on top of an existing 2017 installation, or can be installed independentlywithout the prerequisite of a 2017 base. Multiple product SA updates can now be installed concurrentlywith or without the 2017 base.

HyperWorks 2017 brings with it the robust capabilities and features of HyperWorks 2017 installers, aswell as additional support for HotFix installers. These HotFix installers are quick patch type installersthat are used to install on top of a prerequisite base installation, unlike the other full installers. Theseare marked with the word “hotfix” in the installer name and bring with them the quick fixes andfeatures to better suit your needs.

Software ChangesInstallation and Packaging

• Added Altair digital signature to key executable files in HW Desktop and Solvers.

• Added Click2Extrude Metal product for Windows.

• Added Click2Extrude Polymer product for Windows.

• Added Click2Form product for Windows.

• Upgraded the HyperWorks installers to InstallAnywhere 2015 SP1 web installers.

• Improved the Windows uninstallers.

• Improved error logging when the Master Installer is used.

• Standardized MPI implementations: The versions of the Message Passing Interface (MPI)have been standardized across FEKO, AcuSolve, RADIOSS, and OptiStruct. The Intel, IBMPlatform, Microsoft, and MPICH MPI implementations are now included. End users can stilluse their own MPI implementation.

Invoking

• Added file associations for .hm, .mdl, and .mvw to open in HyperWorks Desktop.

• Added thumbnail preview for .hm files.


• Added better font size management for the HyperWorks Desktop applications, includingHyperMesh under Linux user environment where the default size is set to a 9 point fontinstead of using a pixel font size.

• Added Linux launch icons to HyperWorks applications.

• Updated Linux Compatibility Tool: A Linux utility for system diagnostics to help troubleshootLinux issues.

• Added better version information to the shortcuts for the Windows 8.1/10 Start menu andMetro style Start menu.

Resolved Issues

• Improved the Start menu folder removal portion of the HyperWorks uninstallers.

• Resolved an issue where the Help Configuration panel was skipped when clicking thePrevious button from the Pre-Installation Summary panel.

• Resolved an issue where Start menu shortcuts were not overwritten on Windows 7 whenoverwriting an existing HyperWorks installation and Start menu folder.

• Improved the Linux console mode installations.

• When installing using the Master Installer, you can now cancel your installation at any time.

• On Linux during a console mode install, the installer will now allow you to go back past theInstall Pick List panel.

• On Linux, when installing using the console mode, the Help Configuration prompt will nolonger add another set of double quotes on the user-defined path to installed help if theback command is used.

• On Linux, there are no longer duplicate progress install bars when the back command isused from the Summary panel.

• Corrected Linux “read + execute” permissions of the sub installers are set when using theMaster Installer.

• Resolved graphics issues on Optimus based video card setups.

Known Limitations in HyperWorks Installer 2017

• Using the Back/Previous option during an installation may not reset the installer variablescorrectly if changes are made and the install session is continued.

• On Linux, installing in a directory with spaces is not supported.

• On Linux, during a console mode install, when using a response file output command -r theHelp Configuration in the response file may not write out correctly.

• If there is not enough TMP/TEMP space on the main drive (for example, C: under Windows),then the installer will prompt for user input to a new location. Some Java TMP/TEMP spacewill still try to go to the main drive even when selecting this new location.

• When clicking Cancel to stop an installation, the Master Installer does not clean up thealready installed files, but does clean up the files in the TMP/TEMP folder. You will need touninstall/delete the installed files from the chosen install folder manually if Cancel was used.


• When clicking Cancel to stop an installation, the Add/Remove uninstaller icon may no longerfunction correctly and manual removal of the installed files would be necessary.

• The HyperWorks installers do not support the use of the default InstallAnywhereinstaller.properties files. We request that a unique name is used when using aresponse file; for example, installer_hw2017.properties, and to use it with the -f<path_to_file>/<filename> command line option.

• For NETSETUP client installs from a server installation of HyperWorks, a UNC path must beused to get to the server installation path through Windows Explorer or Windows Network.

Note: Using mapped drive letters or variables is not currently supported in theclient installer.

• On Linux, there is an issue with using the Master Installer with the IATEMPDIR variable, tospecify a custom temporary directory location. All sub-installers will try to use /tmp from themachine running the installers for temporary installer files.

• With some versions of Gnome, there is a bug where the Linux icons are not placed in ahierarchy. Instead, they are placed in “Other” with a flat layout, meaning that all the iconsappear at the same folder level in “Other.”

• The installer does not run the Linux icon installation by default; the user must run the iconinstaller.

• On Windows 8, desktop and Start menu icons are blank for server and client installations.This can be resolved by changing the Windows File Explorer policy to “Allow the use ofremote paths in file shortcut icons”.

• When the Master Installer is used, desktop shortcuts, if any, will not be removed duringuninstallation.

Preparing to Install HyperWorks 22 Preparing to Install HyperWorks

This chapter summarizes the items required and procedures needed to install and successfully runHyperWorks applications on supported platforms.


• 2.1 Installation Media (p. 11)

Before starting installation, make sure you have everything you need.

• HyperWorks 2017 and Altair License Manager software, delivered from Altair in USB/DVD formator HyperWorks 2017 image packages downloaded from Altair Connect.

• A USB compatible input port on the machine or a DVD compatible drive.

• Access to an activated and running HyperWorks 13.0 license server or a node locked license.

• A compatible machine that contains the minimum hardware/software requirements to runHyperWorks applications. Reference the Altair HyperWorks 2017 Platform Support document forfurther details.

• Sufficient disk space for install: The full suite of HyperWorks 2017 applications and help filesneeds 6 GB of temp space. The temp files are removed after successful completion of aninstallation.

Reference the Altair HyperWorks 2017 Platform Support documentation for operating systems andminimum requirement considerations, and the HyperWorks 2017 Hardware Recommendations andCertifications document for further hardware inquiries.

General steps for installing HyperWorks are:

1. Install and activate an Altair License Manager (the latest version) if one does not already exist.Alternatively, use a node locked license.

2. Install HyperWorks 2017 on the designated machine(s).

3. Set an environment variable that points the HyperWorks 2017 application to an activated andrunning Altair license server. Alternatively, set the environment variable to point to a node lockedlicense.

4. Set up HyperWorks online help, if needed.

5. The software to install the Altair License Manager is a separate package from the HyperWorks2017 application packages. Download the Altair license package from the Altair website and followthe Altair® License Management System 13.0 Installation and Operation Guide to install and startthe Altair License Manager properly.

https://connect.altair.com/CP/downloads.html?suite=HyperWorks


2.1 Installation Media

The HyperWorks 2017 software package you received from Altair includes a set of DVDs or a USBthumb drive containing HyperWorks 2017, the Altair License Manager and documentation.

The software is available for registered customers to download from Altair Connect.

Download the images for the platforms on which you expect to launch HyperWorks. There are thirteenpackages required for a complete HyperWorks installation on Windows, and eight for Linux. Here is anexample list of the Master Installer and product sub-installers for Windows:

1. HyperWorks Master Installer

2. HyperWorks Desktop

3. HyperWorks Solvers

4. AcuSolve

5. solidThinking (sTDesign)

6. SimLab

7. Virtual Wind Tunnel (VWT)

8. FEKO

9. Click2Extrude Metal

10. Click2Extrude Polymer

11. Click2Form

12. HyperWorks Desktop Help

13. HyperWorks Solvers Help

The two Help sub-installers together make up a complete HyperWorks 2017 Help installation.

2.1.1 USB Hardware Keys (License Dongles)

Altair supports a subset of the available HOSTID values from X-Formation as well as hardware licensedongles (USB keys) on some platforms. In order to use a dongle, you must have a free/open USB porton the machine that will be your license server.

If you have purchased a hardware dongle to use for licensing, you must obtain the dongle ID via thesoftware before requesting your license file. Hardware dongles are supported on Windows and Linuxplatforms.

In order for the dongle to function properly, you must first install the correct drivers for your platform.These drivers are available from Aladdin, the manufacturer of the key. Download and install the driveraccording the directions available at the following URL:

http://www.aladdin.com/support/hasp/enduser.aspx

http://www.aladdin.com/support/hasp/enduser.aspx


Once the driver is installed and the dongle is in place, use the almutil –hostid command to query forall the HOSTIDs on the machine and report the dongle HOSTID.

2.1.2 Configuring Non-US Keyboards

HyperWorks ships with the keyboard configuration set for a US keyboard. Other countries (Germany, forexample) use extended keyboards to generate native characters not present in the US ASCII characterset. Use the following instructions for your operating system to install a local keyboard configuration.

Configuring Non-US Keyboards on Windows 8/8.1/10

Follow these instructions to configure your non-US keyboard on Windows 8, 8.1 or 10:

1. From the Start menu, select Control Panel.

2. Select Clock, Language, and Region.

3. Select Language.

4. Click Advanced Settings and select the proper one from the drop-down list.

5. Click Save.

Configuring Non-US Keyboards on Windows 7

Follow these instructions to configure your non-US keyboard on Windows 7:

1. From the Start menu, select Control Panel.

2. Select Region and Language.

3. Select the Keyboard and Languages tab.

4. Click Change keyboards and select the proper one from the drop-down list.

5. Click OK.

6. Click OK to close the dialog.

Installing HyperWorks 33 Installing HyperWorks

Two procedures are necessary to enable HyperWorks. First, using the installation configuration youselected in Preparing to Install HyperWorks as a guide, install the HyperWorks software on yourmachine(s). Secondly, you must be able to point to an activated license server that allows HyperWorksapplications to draw license units.


• 3.1 Local Installation (p. 14)

• 3.2 Client/Server Installation (p. 45)

Important: You should not mix installers of different major release versions, for example– 2017 with 14.0 installers, updates and hotfixes. Placing the major installer versions inseparate folders prior to starting the installation will help alleviate issues and conflicts withversioning during installation.

HyperWorks 2017 can be installed via a Graphical User Interface (GUI) mode, silent mode, or consolemode. The following sections describe how to install the software via each method.

The HyperWorks 2017 Help is a browser-based HTML system that uses ActiveX on Windows and JavaScript on Linux. It can be installed with the applications or installed alone behaving as an online helpserver.

For Help installations on a network server, make sure to have the Help UNC or network path prior torunning the installer. You will be prompted for this information during the install.


3.1 Local Installation

3.1.1 Installation Files

HyperWorks 2017 has the ability to install the individual product installers separately from one another,referenced as sub-installers in this document, while also giving you an option to install all of them atonce via the Master Installer in a batch-like mode (recommended). The Windows installers have addedthe Altair Engineering, Inc. digital signatures for enhanced security.

Reference Table 1 for specific file names and details on the product groups per individual sub-installers.

The HyperWorks Master Installer, for example hw2017_win64.exe for Windows, is a quick and easysetup installer allowing for various combinations of the independent sub-installers to be installed atone time. It is done without the need to wait for all the packages to extract prior to setting up theinstallation, which should allow for a quick setup to install a complete HyperWorks 2017 installation.Using the Master Installer is the recommended method for installing HyperWorks 2017 products.

Table 1: HyperWorks 2017 Installer File Names

Installer Name Description

hw2017_win64.exe

hw2017_linux64.bin

Master Installer, used to setup and installthe separate individual HyperWorks installerssimultaneously. You can select which products toinstall, or install them all at once.

hwAcuSolve2017_win64.exe

hwAcuSolve2017_linux64.bin

Installer of the AcuSolve suite of products.

hwDesktop2017_win64.exe

hwDesktop2017_linux64.bin

Installer of the HyperWorks Desktop suite ofproducts (includes most GUI applications, such asHyperView, HyperMesh HyperGraph, HyperStudy,and so on).

hwSolvers2017_win64.exe

hwSolvers2017_linux64.bin

Installer of the HyperWorks Solvers suiteof products (includes RADIOSS, OptiStruct,MotionSolve, and so on).

hwDesktopHelp2017_win64.exe

hwDesktopHelp2017_linux64.bin

Installer of the HyperWorks Desktop Help content.

hwSolversHelp2017_win64.exe

hwSolversHelp2017_linux64.bin

Installer of the HyperWorks Solvers Help content.


hwFEKO2017_win64.exe

hwFEKO2017_linux64.bin

Installer for FEKO GUI and solver products.

hwSimLab2017_win64.exe

hwSimLab2017_linux64.bin

Installer of the SimLab product.

hwVirtualWindTunnel2017_win64.exe Installer of the Virtual Wind Tunnel product.

sTClick2ExtrudeMetal2017.1_win64.exe

sTClick2ExtrudePolymer2017.1_win64.exe

Installers of the Click2Extrude Metal andClick2Extrude Polymer products.

sTClick2Form2017.1_win64.exe Installer of the Click2Form product.

sTDesign2017.1_win64.exe

sTDesign2017.1_macosx64.zip

Installer of the solidThinking product suite(includes Inspire and Evolve).

To install Help along with the application, download and place the Help files sub-installershwDesktopHelp and hwSolversHelp files, which are executable files on Windows and bin file types onLinux, in the same residing directory as the HyperWorks Master Installer. Help files contain the helpand tutorial model files. The user has the option to select and install complete Help and tutorials or acombination of the two options.

3.1.2 GUI Mode

Windows Installation

Complete the following steps to extract and install the software.

1. Log in to the machine on which the software is to be installed, then insert the USB/DVD, or placethe downloaded files in a temporary directory.Example of a directory with all the required sub-installers for a complete HyperWorks 2017installation on a Windows 64-bit platform, with the Master Installer listed at the top:


Figure 1:

For a base Help Files install both the hwDesktopHelp and hwSolversHelp sub-installers will needto be installed together using the Master Installer. For Manufacturing Solutions or EngineeringSolutions to be installed, the Master Installer will have to be used together with the hwDesktopand hwSolvers sub-installers.

Note: Please make sure that the downloaded files have “read + execute”permissions before continuing with an installation. Use Windows Explorer fileproperties to change the permissions.

2. Double-click the hw2017_win64.exe Master Installer executable file to start the installer.

3. If UAC (User Account Control) is enabled, then a prompt displays showing the Altair Engineering,Inc. digital signature for elevated permissions. Click Yes to continue with installer.


Figure 2:

4. In the multi-language selector prompt, select the proper locale and click OK to continue.

The default locale setting is specific to the install machine regional settings. The languageselection only corresponds to the installer settings not to the HyperWorks product languagesettings. Altair HyperWorks products are in English.

5. In the Introduction panel, click Next to continue.

6. From the Sub-Installer List of installers picked up in the same residing directory as the MasterInstaller, verify the list to make sure that the packages you wish to setup for installing arepresently available and registered within the installer. Click Next to continue.

7. In the Choose Installation Type panel, choose Local install or Server install and click Next.

8. In the Choose Install Folder panel, choose the HyperWorks install directory and click Next.

Note:

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

• Installing to a root drive is not permitted, for example C:\

9. In the Change Shortcut Folder (Local) panel, choose a Start menu name for the HyperWorksinstall and select whether desktop shortcuts are created. There are options on this panel toassociate HyperWorks file types to products, and to generate thumbnail previews for HyperMeshfiles. Both are set by default. Once options are chosen, click Next to continue.

10. In the Choose Install Set panel, select the products to install. Click Next to continue.

Products that do not have sub-installer present or were not picked up by the Master Installer inthe residing directory will be listed as (Unavailable) and are not available to be installed.


Note: Manufacturing Solutions and Engineering Solutions require both thehwDesktop and hwSolvers sub-installers to be present. The Help Files requires boththe hwDesktopHelp and hwSolversHelp sub-installers to be present.

11. If Help was NOT selected to be installed, the Help Configuration panel is displayed. Select one ofthe options:

• Connect to a network installed Help location: Input the path, either UNC or drive path,to where the Help was installed to create the product link.

• Connect to the Altair website Help: Allows the products to connect to the Altair websiteHelp. A working Internet connection is needed for this functionality.

• Set up Later: Allows for a post Help install over the current installation. This option willdefault to the website help if an Internet connect is established.

12. In the Pre-Installation Summary panel, review the Product Features list, Install Folder and diskspace requirements. Click Install to continue.

Note: Install times are machine hardware dependent. Anti-virus software maylengthen the install times. The HyperWorks sub-installer and Master Installer mayneed to be allowed through any third party firewalls or virus scanning software inorder to not be prompted during install time to allow them access to be installed.

13. Once the installation completes, click Done to exit the installer.

Linux Installation


HyperWorks install directories with spaces are not supported on Linux.

1. Run the BASH sh command on the installer binary.


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





Note:


• Installing to a root drive is not permitted, for example C:/








Note: A valid Linux web browser will need to also be defined in this panel(HW_MSG_BROWSER).





Detailed Installation Steps



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


Figure 3:




Figure 4:


Figure 5:



Figure 6:



Figure 7:


Note:




Figure 8:

8. In the Change Shortcut Folder (Local) panel, choose a Start menu name for the HyperWorksinstall and select whether desktop shortcuts are created. There are options on this panel toassociate HyperWorks file types to products, and to generate thumbnail previews for HyperMeshfiles. Both are set by default. Once options are chosen, click Next to continue.


Figure 9:





Figure 10:






Figure 11:




Figure 12:



Figure 13:

Linux Installation


HyperWorks install directories with spaces are not supported on Linux.

1. Open a command terminal window/prompt.

a) cd – change directory – to the location where the installer executable resides.

b) Execute the sh command on the installer binary, for example sh hw2017_linux64.bin.

The HyperWorks installer extracts the JVM (Java Virtual Machine) and the install modules to theTMP location of the machine and launches the installer.

sh hw2017_linux64.bin

Preparing to install...Extracting the JRE from the installer archive...Unpacking the JRE...Extracting the installation resources from the installer archive...Configuring the installer for this system's environment...


Launching installer...

Note: If the /tmp location on the machine is full, the installer will try to use theuser’s home folder for temp files or the user can set the environment variableIATEMPDIR to a custom specified TMP location.



Figure 14:



Figure 15:



Figure 16:


Note:




Figure 17:





Figure 18:

7. In the Help Configuration panel, input the path of the internet browser to be used with theHyperWorks Help. Click Next to continue.





Note: A valid Linux web browser will need to also be defined in this panel(HW_MSG_BROWSER).


Figure 19:




Figure 20:


Registering the HyperView Player Plugin

The HyperView Player plugin for Microsoft Office documents and Internet Explorer is installed andregistered by default with the HyperView Player installation. In case of multiple HyperView/HyperViewPlayer installations, the user may need to manually register the latest HyperView Player plugin followingthe steps below.

1. Click Start > All Programs > Altair HyperWorks 2017 > Tools.

2. Right click on Register HVPControl and select Run as administrator.

3. Invoke the currently installed HyperView Player either using the Start menu shortcut, or from thefollowing location: <InstallDirectory>\hw\bin\win64\hvp.exe

On Linux, please reference the web or local Help section for detailed information.


3.1.3 Console Mode

Console mode installations mimic the default Graphical User Interface steps provided by theHyperWorks installer but use only the standard input and output. The advantage to console modeinstallation is that Linux users no longer need 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 anyformatting, clearing of the screen, or positioning of the cursor.

1. To trigger a console mode installer from the command line, append the following commandparameter to the installer: -i console.Example console mode install call:

hw2017_linux64.bin –i console

The Linux console mode is only supported on the HyperWorks Linux installers. Just follow the onscreen instructions to complete the installation.

Console Mode: Linux

1. Open a command terminal window/prompt.

a) cd – change directory – to the location where the installer executable resides.

b) Execute the sh command on the installer binary with the additional parameter "-i console",for example sh hw2017_linux64.bin -i console .

The HyperWorks installer extracts the JVM (Java Virtual Machine) and the install modules to theTMP location of the machine and launches the installer.

sh hw2017_linux64.bin

Preparing to install...Extracting the JRE from the installer archive...Unpacking the JRE...Extracting the installation resources from the installer archive...Configuring the installer for this system's environment...

Launching installer...

Note: If the /tmp location on the machine is full, the installer will try to use theuser’s home folder for temp files or the user can set the environment variableIATEMPDIR to a custom specified TMP location.


2. In the multi-language selector prompt, select the proper locale and click Enter to continue.


==============================================================================Choose Locale...---------------- 1- Bahasa Indonesia 2- Català 3- Dansk 4- Deutsch ->5- English 6- Español 7- Euskara 8- Français 9- Français (Canada) 10- Italiano 11- Nederlands 12- Norsk 13- Português 14- Português (Brasil) 15- Suomi 16- Svenska

CHOOSE LOCALE BY NUMBER: 5

3. In the Introduction panel, click Enter to continue.

4. From the Sub-Installer List of installers picked up in the same residing directory as the MasterInstaller, verify the list to make sure that the packages you wish to setup for installing arepresently available and registered within the installer. Click Enter to continue.

5. In the Choose Install Folder panel, choose the HyperWorks install directory and click Enter.

Note:



6. In the Choose Install Set panel, choose the products you wish to unselect and enter the number inthe line provided and press Enter. The “X” next to the product selects it to be installed. By default,all the available products are selected and marked to be installed. Products which do not havesub-installer present or picked up by the Master Installer in the residing directory will be listed as(Unavailable) and not be able to be installed.



Choose Install Set------------------

ENTER A COMMA_SEPARATED LIST OF NUMBERS REPRESENTING THE FEATURES YOU WOULD LIKE TO SELECT, OR DESELECT. TO VIEW A FEATURE'S DESCRIPTION, ENTER '?<NUMBER>'. PRESS <RETURN> WHEN YOU ARE DONE:

1- [X] HyperWorks 2- |-[X] Desktop Application v2017 3- |-[X] HyperWorks Desktop 4- |-[X] HyperStudy 5- |-[X] HyperMath 6- |-[X] Solvers v2017 7- |-[X] Manufacturing Solutions v2017 8- |-[X] Engineering Solutions v2017 9- |-[X] AcuSolve v2017 10- |-[X] SimLab v2017 11- |-[X] FEKO v2017 12- |-[X] Help Files - Desktop v2017 / Solvers v2017 13- |-[X] Help 14- |-[X] TutorialsPlease choose the Features to be installed by this installer.:

7. If Help was NOT selected, to be installed, the Help Configuration panel is displayed. Select one ofthe options:




8. In the Choose Web Browser for Help panel, input the path of the web browser to use withHyperWorks help. Press Enter.

9. In the Pre-Installation Summary panel, review the Product Features list, Install Folder and diskspace requirements. Click Enter to continue.



10. Once the installation completes, click Enter to exit the installer.

3.1.4 Silent Mode

Silent mode enables the installer to run without any user interaction.

A near-silent mode is possible on Windows.

InstallAnywhere and HyperWorks end-user-defined variables may be set through command lineparameters or a properties response file.

Response files are created and 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 filefrom which the installer retrieves the values for various InstallAnywhere and HyperWorks variables usedto control the install.

The installer automatically checks the residing directory for a file called installer.properties,however, this file name and type is NOT supported by the HyperWorks installers and cannot reside inthe same folder as our installs.

The response file will need a unique name in order to work properly with the HyperWorks installers,example, hw2017_installer.properties, will work with the HyperWorks installer.

1. You can generate a response file from the installer by running through the installer with thefollowing command line syntax:

-r "[FullPath]\hw2017_installer.properties"

The file will get created once the installer is complete. To trigger a silent installer from thecommand 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]\hw2017_installer.properties”

An example of running a silent install using a properties response file located in C:\ResponseFiles called hw2017_installer.properties on Windows 64-bit:

hw2017_win64.exe –i silent –f "C:\ResponseFiles\hw2017_installer.properties"

Note: Use quotes around any directory and pathnames that may contain spaces.

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.

#Choose Installation Type#------------------------LOCAL_INSTALLATION=1SERVER_INSTALLATION=0

#Choose Install Folder#---------------------USER_INSTALL_DIR=C:\\Program Files\\Altair\\2017

#Change Shortcut Folder (Local)#------------------------------SET_START_MENU_FOLDER=Altair HyperWorks 2017INSTALL_DESKTOP_SHORTCUTS=0DONOT_INSTALL_DESKTOP_SHORTCUTS=1CREATE_HWD_FA=1DONOT_CREATE_HWD_FA=0CREATETHUMBNAILSCHKD=1

#Choose Install Set#------------------CHOSEN_FEATURE_LIST=HW,DKTOP,HWD,HST,HWX,SLVR,MFS,ES,sT,AS,SL,VWT,FEKO,C2F,C2XM,C2XP,HWFhelp,helpHW,tutsHWCHOSEN_INSTALL_FEATURE_LIST=HW,DKTOP,HWD,HST,HWX,SLVR,MFS,ES,sT,AS,SL,VWT,FEKO,C2F,C2XM,C2XP,HWFhelp,helpHW,tutsHW

CHOSEN_INSTALL_SET=Custom

#Command Line Feature List#-------------------------CL_CHOSEN_FEATURE_LIST=HW,DKTOP,HWD,HST,HWX,SLVR,MFS,ES,sT,AS,SL,VWT,FEKO,C2F,C2XM,C2XP,


HWFhelp,helpHW,tutsHW

Figure 21: Example: Properties Response File

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

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

Note: The installer will use double backslashes “\\” on Windows platforms for thedirectory names.

Spaces should not be used between the VARIABLE=VALUE statements in the response files

Sample Response File with Descriptions of Variables

Below is a pre-defined response file to be used with the HyperWorks 2017 Installers and describes thevariables and their functions.

Please make sure to use a unique name for the response file and not the generalinstaller.properties file name structure, since the generic name is not supported in HyperWorksinstallers.

# SAMPLE response file for HyperWorks 2017 Windows installers# Modifying the below variables will allow for customized installation of HyperWorks

# Replay feature output # This file was built by the Replay feature of InstallAnywhere.# It contains variables that were set by Panels, Consoles or Custom Code.

# Binary format is used to activate and deactivate variables - 1 is "on" and 0 is "off"

# INSTALLER_UI sets the user interface and the options are console, GUI and silent# The below example is using a silent install methodINSTALLER_UI=silent# Uninstall information only to be used with silent uninstalls are INSTALL_CLEANUP_ALL and FEATURE_UNINSTALL# INSTALL_CLEANUP_ALL=1# will set the uninstall to completely remove all files and folders from an install Note: backup any files before uninstalling# FEATURE_UNINSTALL=COMPLETE# This will uninstall all features installed. The only method used with the HyperWorks installer.

# Choose Installation Type - Setting this will variable to the appropriate option will install


# HyperWorks as a local install compared to a server install.#------------------------# The below example will install HyperWorks as a local installLOCAL_INSTALLATION=1SERVER_INSTALLATION=0

# Choose Install Folder - This is the location where the HyperWorks installation will be placed. # The directory will be created if it does not exist. # Note: "\\" are always used to separate directory trees #---------------------# The below example will install HyperWorks into the default location for a Windows installUSER_INSTALL_DIR=C:\\Program Files\\Altair\\2017

#Change Shortcut Folder (Local) - This section will install Shortcuts for the Windows Start Menu and Desktop. # The below example shows the default Start Menu directory and the Desktop shortcuts being installed as well.#------------------------------SET_START_MENU_FOLDER=Altair HyperWorks 2017INSTALL_DESKTOP_SHORTCUTS=0DONOT_INSTALL_DESKTOP_SHORTCUTS=1CREATE_HWD_FA=1DONOT_CREATE_HWD_FA=0CREATETHUMBNAILSCHKD=1

#Choose Install Set - Installs the chosen HyperWorks products, either Custom or Complete. # This depends on the selection and the availability of the product installer package#------------------# IMPORTANT: The below CL_CHOSEN_FEATURE_LIST is a required variable in HyperWorks 2017 installers# and needs to be set to the same CHOSEN_FEATURE_LIST content.

CHOSEN_FEATURE_LIST=HW,DKTOP,HWD,HST,HWX,SLVR,MFS,ES,sT,AS,SL,VWT,FEKO,C2F,C2XM,C2XP,HWFhelp,helpHW,tutsHWCL_CHOSEN_FEATURE_LIST=HW,DKTOP,HWD,HST,HWX,SLVR,MFS,ES,sT,AS,SL,VWT,FEKO,C2F,C2XM,C2XP,HWFhelp,helpHW,tutsHWCHOSEN_INSTALL_FEATURE_LIST=HW,DKTOP,HWD,HST,HWX,SLVR,MFS,ES,sT,AS,SL,VWT,FEKO,C2F,C2XM,C2XP,HWFhelp,helpHW,tutsHWCHOSEN_INSTALL_SET=Custom

# This is the list of the features, according to the Choose Install Set GUI panel picks# HW - HyperWorks# DKTOP - Desktop Applications# HWD - HyperWorks Desktop Desktop# HST - HyperStudy# HWX - HyperMath # SLVR - HyperWorks Solvers products# MFS - Manufacturing Solutions# ES - Engineering Solutions# sT - solidThinking Inspire/Evolve# AS - AcuSolve products# SL – SimLab# VWT - Virtual Wind Tunnel# FEKO – FEKO products# C2F – Click2Form# C2XM – Click2Extrude Metal# C2XP – Click2Extrude Polymer# HWFhelp - HyperWorks Help Files# helpHW - Help# tutsHW - Tutorials


#Help Configuration - this panel is to set Help options for populating the file hwhelp.cfg in the install directory.#------------------# 0 is false/off and 1 is true/on in the variables below.# The HELP_CONNECT_NETWORK will require the MW_MSG_HELP_WIN variable to be set.#HELP_CONNECT_NETWORK=0

# Setting the HW_MSG_HELP_WIN variable will try to install the Help locally.#HW_MSG_HELP_WIN=C:\\Program Files\\Altair\\2017\help

# The HELP_CONNECT_ALTAIR variable, when active will point to the Altair Web Help - internet connection required#HELP_CONNECT_ALTAIR=1

# The HELP_SETUP_LATER will not set anything in the hwhelp.cfg file but will try to access help from the Altair Web site when chosen.#HELP_SETUP_LATER=0


3.2 Client/Server Installation

3.2.1 Requirements

This section describes how to set up the client machine if a server type installation is chosen.

Requirements for a NETSETUP client install include:

• Existence of an Altair HyperWorks network server install

• The UNC paths of the location of the HyperWorks network server installs (or use Networks onWindows 7 /8.1/10 to get to the NETSETUP client installer directory).

Virtual Wind Tunnel, solidThinking products (including Inspire and Evolve), and FEKO are not availablein the server type installs.

Note: The installer does not allow for the use of drive letter or mapped drive letter paths.

3.2.2 GUI Mode

This section describes the client NETSETUP of a HyperWorks network server install on Windows only.

The NETSETUP supports the GUI and silent installation modes. The example below is shown for a GUINETSETUP client Windows 7 64-bit install.

1. From the Control panel, go to Networks.

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

3. Go to the NETSETUP folder.

4. Go to the win64 folder.

5. Click on the NETSETUP.bat file.A command prompt terminal window will be displayed showing that the installer is unpacking onthe client machines. The locale language selection prompt will then be displayed.

6. Select the locale language and click OK to continue.The HyperWorks Install Desktop Shortcuts options panel is displayed.

7. Make changes if needed and click Next to continue.The HyperWorks Pre-Installation Summary panel is displayed.

8. Review the summary and click Install to complete the HyperWorks NETSETUP client install.The appropriate Start menu and Desktop Shortcuts are created on the client machine.

9. Once it completes, click Done to exit the Install wizard.


Detailed Installation Steps



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


Figure 22:




Figure 23:


Figure 24:



Figure 25:



Figure 26:


Note:




Figure 27:

8. In the Change Shortcut Folder (Server) panel, choose a Start menu name for the HyperWorksinstall and select whether desktop shortcuts are created. Once options are chosen, click Next tocontinue.


Figure 28:





Figure 29:

10. If the Install folder was not provided, enter the UNC path in the UNC (Uniform NamingConvention) mount point panel and click Next to continue.

Note: User input should be in UNC standard form to be accepted. For example, \\MachineName\SharedFolder\InstallFolder


Figure 30:






Figure 31:




Figure 32:



Figure 33:

3.2.3 Silent Mode

Follow these steps to create a properties file for the client NETSETUP installer. This step only needs tobe done once in order to establish the defaults for the installer.

1. From the Control panel, go to Networks.

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

3. Go to the NETSETUP folder.

4. Go to the win64 folder.

5. Click on the NETSETUPproperties.bat file.A command prompt will be displayed to make sure the end user has write permissions to theNETSETUP network location, where the properties response file gets created.


Figure 34:

6. Click Y and press Enter to continue.A command prompt terminal window will be displayed showing that the installer is unpacking onthe client machines. The locale language selection prompt will then be displayed.

7. Select the locale language and click OK to continue.The HyperWorks Install Desktop Shortcuts options panel is displayed.

8. Make changes if needed and click Next to continue.The HyperWorks Pre-Installation Summary panel is displayed.

9. Review the summary and click Install to complete the HyperWorks NETSETUP client install.The appropriate Start menu and Desktop Shortcuts are created on the client machine.

10. Once it completes, click Done to exit the Install wizard.The installer creates a file under the NETSETUP platform folder calledNETSETUP_installer.properties. This will be used for future client NETSETUP installs.

To run the silent NETSETUP installer on other machines using the selected defaults from the abovesetup, go to the NETSETUP folder and click on the NETSETUPsilentinstall.bat file.

Connecting to the Altair License

Management System 13.0 44 Connecting to the Altair License Management System 13.0

The Altair License Management System 13.0 (ALMS) provides a common units-based licensing modelfor all Altair software related to CAE, on-demand computing, and business intelligence.


• 4.1 Requirements (p. 59)

• 4.2 Node Locked Licenses (p. 60)

This new system has been designed to enable HyperWorks Partner Products (selected third partyproducts) to be licensed via HyperWorks Units as well.

The ALMS is comprised of two components: the License Server and the Usage Reporting System (URT).The license system is based on X-Formation's LM-X license server. The URT is a java application thatreports anonymous transactional logs to Altair. As part of the license agreement that enables partnersoftware to be used, product usage must be reported to Altair.

Version 13.0 of the ALMS is based on X-Formation’s LM-X License Management System Version 5.


4.1 Requirements

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

A few examples of license paths:

On Windows:

[email protected]_LICENSE_PATH=6200@srv1;6200@srv2;6200@srv3ALTAIR_LICENSE_PATH=c:\Program Files\Altair\Licensing13.0\altair_lic.dat

On Linux:

[email protected]_LICENSE_PATH=6200@srv1:6200@srv2:6200@srv3ALTAIR_LICENSE_PATH=/usr/local/altair/licensing13.0/altair_lic.dat

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

Examples of license paths:

BASH shell (.profile, .bashrc):

export [email protected]

C shell (.tchsrc, .cshrc):

setenv ALTAIR_LICENSE_PATH [email protected]


4.2 Node Locked Licenses

For node-locked license (a license that is locked to a local machine), you can either place the license filein the <install_dir>/altair/security/ directory named as altair_lic.dat, or set the environmentvariable, ALTAIR_LICENSE_PATH, to point to the appropriate location where the license file resides.

The preferred method is to save your license to a location separate from HyperWorks installations andset the environment variable to point at this license.

Starting HyperWorks Applications 55 Starting HyperWorks Applications


• 5.1 Starting on Windows (p. 62)

• 5.2 Starting on Linux (p. 63)


5.1 Starting on Windows

The installation process creates a HyperWorks group available from the Start menu. The foldercontaining the applications receives a default name by the Altair HyperWorks Installation wizard.Most applications can be started using the following instructions. The example below uses the defaultsettings.

1. Click Start > Programs > Altair HyperWorks 2017.

2. From the list, select the name of the program to run.

Changing the Default Working Directory on Windows

The default working directory specified by a HyperWorks application is C:\Users\[UserID]\Documents.

Note: If you create a shortcut directly from the <install_location>\application\bindirectory, the start in directory of the shortcut will be from that directory. We recommendthat you change the start in path to: "%userprofile%\documents" or any directory youprefer.

Perform the following steps to change the default working directory.

1. Click Start > Programs > Altair HyperWorks 2017.

2. Right-click on the HyperWorks application for which you want to set the working directory.

3. From the menu, select Properties.

4. Select the Shortcut tab.

5. In the Start in text box, enter the explicit path name of the folder from which you want to run theHyperWorks application.

6. Click OKYour user files are created in the directory specified in Step 5. For example, if you had selectedHyperMesh, the command.tcl and hmmenu.set would go to this directory.


5.2 Starting on Linux

All HyperWorks applications start by running the appropriate script from the <install_location>/altair/scripts directory.

The scripts directory contains the launch procedure for each HyperWorks application, and tools such ashvtrans. In addition, it contains the /invoke sub-directory where various sub-procedures used by thelaunch procedures are stored.

1. The general start command to enter at the terminal prompt is:

<install_location>/altair/scripts/<script name>

where <script name> is the script name associated with the particular application and theoptional [file name] applies to the applications that require an input file when they start.

For example, to start HyperMesh you would enter the following at the prompt:

<install_location>/altair/scripts/hm

The following scripts are used to launch HyperWorks applications:

Command Options Description

acusim Launch AcuSolve productenvironment

basicfea Launch BasicFEA profile

blanknest Launch BlankNesting

cadfeko Launch CADFEKO - modelcreator (geometry, mesh,configuration)

editfeko Launch EDITFEKO - advancedtext based model creator

es_aerospace Launch Engineering Solutions/Aerospace profile

es_basicfea Launch EngineeringSolutions/BasicFEA profile



es_cfd Launch Engineering Solutions/CDF profile

es_crash Launch Engineering Solutions/Crash profile

es_droptest Launch Engineering Solutions/Drop Test profile

es_nvh Launch Engineering Solutions/NVH profile

feko_help Launch FEKO help

feko_update Launch command line FEKOupdater

feko_update_gui Launch GUI FEKO updater

hc Launch HyperCrash

help Launch Help from commandline

hfsolver Launch ManufacturingSolutions/RADIOSS 1 Step

hg Launch HyperGraph

hm Launch HyperMesh

hmath Launch HyperMath

hmathbatch Launch HyperMath in batchmode

hmathserv Launch HyperMath ResultsVisualization Services

hmbatch -c<command filename>

-tcl <file>

Launch HyperMesh in batchmode

hmdesktop Launch HyperMesh client fromHyperWorks Desktop

hst -studyfile= <filename> Automatically read the fileafter launching HyperStudy



hstbatch Launch HyperStudy usingbatch mode

hv Launch HyperView

hvvh Launch HyperWorksVerification and ValidationHarness

hvp Launch HyperView Player

hw_batchmesh Launch the BatchMesheruser interface where youcan interactively set up therequired entries

hx Launch HyperXtrude solver

mdl_batch -c<session filename> Launch MotionSolve usingbatch mode

mfs_forging Launch ManufacturingSolutions/Forging application

mfs_hf Launch ManufacturingSolutions/HyperFormapplication

mfs_hx Launch ManufacturingSolutions/HyperXtrudeapplication

mfs_hypermold Launch ManufacturingSolutions/HyperMoldapplication

mfs_hyperweld Launch ManufacturingSolutions/HyperWeldapplication

mit Launch Model IdentificationTool

motionsolve Launch MotionSolve

motionsolve_subroutine_builder Launch MotionSolve SubroutineBuilder tool



mview Launch MotionView

optfeko Launch OPTFEKO -optimization engine

optistruct Launch OptiStruct

ossmooth Launch OSSmooth

pmstudio Launch Process Studio

postfeko Launch POSTFEKO - solutionvisualizer (post-processor)

prefeko Launch PREFEKO - model pre-processor

queuefeko_gui Launch QUEUEFEKO

radioss Launch RADIOSS

resmap Launch HyperWorks ResultsMapper

runfeko Launch the FEKO solver

SimLab2017 Launch SimLab

templex Template.tpl <output> Launch Templex

On Linux, running a Window Manger, the products can be invoked from an icon type shortcut by doubleclicking the icon of the product you wish to launch.

You will need to install the shortcut icons by using the script:

<install_location>/altair/LinuxMenu/install_menu.sh

with the –i option to install or –u to uninstall the shortcut icons for that installation.

Obtain a List of Arguments for an Application on Linux

1. To obtain a list of arguments and their descriptions, add -help to the start command.


For example, to obtain a list of arguments for HyperMesh, enter the following at the commandprompt:

<install_location>/altair/scripts/hm –help

The application returns a list of the available arguments and what they do.

Setting up HyperWorks Help 66 Setting up HyperWorks Help

The HyperWorks help system is a browser-based HTML help system. This section describes how to setup and access HyperWorks help system.


• 6.1 Starting Help from the Application Menu (p. 70)

• 6.2 Starting Help from the altair/scripts Directory on Linux (p. 71)

• 6.3 Accessing Help Installed on a Server on Windows (p. 72)

The HyperWorks help system can be installed with applications or installed alone on a server.

Help systems for AcuSolve, FEKO, SimLab, and Virtual Wind Tunnel are always installed on the localmachine with applications.

In order for the help to work properly from applications, you must set up a valid Internet browser anda valid path to the HyperWorks help installation if help is not installed with the application. Help can beinstalled via different ways:

• On a local machine along with the HyperWorks software

• Pre-installed on a shared network location

• Use Altair website help

In order for HyperWorks help to work properly, you must set up a valid browser on the machine fromwhich the application is launched. For Windows, HyperWorks uses the default Windows browser. ForLinux, the valid browser is set during the installation time. You can verify the browser setting storedin the hwhelp.cfg file. The hwhelp.cfg file is located in the <installation directory>/altair/directory on Linux, and the top-level installation directory on Windows.

If Help is pre-installed on a shared network location, the information will be stored in the hwhelp.cfgfile as well. A typical hwhelp.cfg file should contain the following information:

HW_MSG_BROWSER /usr/bin/firefox

HW_MSG_HELP <install_dir>/altair/help

If HW_MSG_HELP is not set in the hwhelp.cfg file, HyperWorks application will connect to the Altairwebsite help automatically.


Important: The help server on Linux platforms does not support tilde (~) completionof paths. Please make sure that you use the full path for the items HW_MSG_HELP andHW_MSG_BROWSER if you set them as environment variables, or in hwhelp.cfg. For example,use /path/to/help_user/my_help instead of ~help_user/my_help.


6.1 Starting Help from the Application Menu

Before you begin, set up the browser and help environment before starting the application as describedin Setting up HyperWorks Help

The steps to start help from within an application via the Help menu are similar for most applications.

1. Start the application.

2. Click the Help menu and choose the help for the selected application.

Once the online help has been launched, you can use the Index, Contents, or Search tabs to locate thehelp for a specific topic. The context sensitive help works as well.


6.2 Starting Help from the altair/scripts Directory onLinux

1. Each HyperWorks Help book can be invoked via command prompt by running the following script:

altair/scripts/help


6.3 Accessing Help Installed on a Server on Windows

If you have chosen the Server setup type described in Installing HyperWorks: Client/Server Installation,each client is installed through NETSETUP as described in GUI Mode. HyperWorks applications will beavailable from the Start menu.

If both the HyperWorks application and help are installed on the software server, help can be accessedon this client as long as a valid browser is installed on the client machine.

Seting up the CAD Translators 77 Seting up the CAD Translators


• 7.1 UG Environment Variable Settings (p. 74)

• 7.2 CATIA V5 License (p. 76)


7.1 UG Environment Variable Settings

Since the UG reader needs to use the UGOpen library during the run time, it requires that a valid UG

installation and UG license1 be present and available to the user with the assemblies, gateway andsolid_modeling modules.

The UG installation must be the same bit-level and platform as the version of HyperMesh (thus, 64-bitHyperMesh must be used with 64-bit UG).

Windows Environment VariablesThe following environment variables must be set prior to starting:UGII_BASE_DIR

Must point to the UG installation directory2.UGI_ROOT_DIR

Must point to the UG installation UGII directory2.PATH

Must include the %UGII_BASE_DIR%\UGII\ directory3.SPLM_LICENSE_SERVER

Must point to the UG license server1.UGS_LICENSE_SERVER

Must point to the UG license server1.UGS_LICENSE_BUNDLE

Must specify the UG license bundle1.

For example, an UG installation located at C:\Program Files\UGS\NX 6.0:UGII_BASE_DIR

C:\Program Files\UGS\NX 6.0

UGI_ROOT_DIR%UGII_BASE_DIR%\UGII\

PATH%UGII_BASE_DIR%\UGII\

UGS_LICENSE_SERVER28000@licsrv

UGS_LICENSE_BUNDLENXPTNR100

Linux Environment VariablesThe following environment variables must be set prior to starting:


UGII_BASE_DIR

Must point to the UG installation directory2.UGI_ROOT_DIR

Must point to the UG installation bin directory2.SPLM_LICENSE_SERVER

Must point to the UG license server1.UGS_LICENSE_SERVER

Must point to the UG license server1.UGS_LICENSE_BUNDLE

Must specify the UG license bundle1.

For example, an UG installation located at /soft/usr/ugs060:UGII_BASE_DIR

/soft/usr/ugs060

UGI_ROOT_DIR/soft/usr/ugs060/bin

UGS_LICENSE_SERVER28000@licsrv

UGS_LICENSE_BUNDLENXPTNR100

1 When using UG versions prior to NX6, a UG license is not required. UG versions 9.0 and later utilizethe SPLM_LICENSE_SERVER variable, while older versions utilize UGS_LICENSE_SERVER

2 UG is very sensitive about the environment variables. You should NOT have '/' at the end ofUGII_BASE_DIR path and you MUST have '/' at the end of UGII_ROOT_DIR path.

3 It is advisable to specify %UGII_BASE_DIR\UGII\UGOpen directory at the beginning of PATHenvironment variable to avoid DLL version conflict.


7.2 CATIA V5 License

HyperMesh supports import of CATIA V5 models with .CATPart, .CATProduct and .cgr extensions.

If you intend to import CATIA V5 models, or CATIA V4 models embedded in CATIA V5 models, you mustobtain a HyperWorks license file with the FEATURE CatiaV5Reader from Altair Engineering.

It is no longer necessary to install, update or manage the third-party library license file.

Uninstalling 88 Uninstalling


• 8.1 Uninstalling: Windows (p. 78)

• 8.2 Uninstalling: Linux (p. 80)


8.1 Uninstalling: Windows

The HyperWorks uninstaller will only Remove All files from the install. Please note that any modifiedfiles or added files, like the altair_lic.dat file, will also be removed from within that particular installlocation. Backup any and all files you wish to save prior to running the uninstaller. There is no partialuninstaller available.

1. Choose one of the following methods:

• From the Start menu, click Altair HyperWorks 2017 > Tools >Uninstall_HyperWorksMasterInstaller2017

• From the Control Panel, click Add/Remove or Uninstall a Program to launch theHyperWorks uninstaller.

2. Select the Removal option.

Windows Silent Uninstalls Using a Response File

Silent uninstalls for HyperWorks only allows for complete uninstalls of the products, this includes allfolders, directories and files of the HyperWorks install.

1. Backup any important files before proceeding with a silent uninstall.

2. A response file is necessary for using the silent uninstall capabilities. Create a response file addingthe following three variables within it and save it as hw2017_silent_uninstaller.properties.

INSTALLER_UI=silent

FEATURE_UNINSTALL=COMPLETE

INSTALL_CLEANUP_ALL=1

3. Open a command prompt (Administrative elevation is recommended to bypass any User AccountControl prompts as shown in image below):

Figure 35:


4. Run the HyperWorks Uninstaller executable with the hw2017_silent_uninstaller.propertiesfile using the syntax in the example below (where <INSTALL_PATH> is the path used to installHyperWorks and <RESPONSE_PATH> is the path where the response file resides):

C:\<INSTALL_PATH>\2017\uninstalls\Uninstall_HyperWorksMasterInstaller2017\Uninstall_HyperWorksMasterInstaller2017.exe” –f

C:\<RESPONSE_PATH>\hw2017_silent_uninstaller.properties

This will remove the HyperWorks install completely in silent mode.

Note: Files in the installation directory and the Start menu folder will be removed,but any Desktop Shortcuts may remain and need to be manually deleted.


8.2 Uninstalling: Linux

1. Run the command rm –Rf install_directory to uninstall the product, whereinstall_directory is where the HyperWorks installation you would like to remove resides.