TOSCA Structure 7.0. Installation Notes

Transcription

1 TOSCA Structure 7.0 Installation Notes FE-DESIGN GmbH, Karlsruhe June

2 TOSCA Structure 7.0 Installation Notes Content 1 General...Fehler! Textmarke nicht definiert. 1.1 Installation Successful Installation Installation Procedure...Fehler! Textmarke nicht definiert. 3 Licensing FlexLM Node Lock license Floating license Obtain license and license server files Modify license file License server installation Troubleshooting...Fehler! Textmarke nicht definiert Determination of the FlexLM hostid Test of the license server installation Note Appendix Configuration File: tosca_ctrl.cfg Troubleshooting Configuration Licensing Unix TOSCA Structure Invocation

3 1 Installation 1.1 General TOSCA Structure makes use of several third party products. It is recommended to gather the information about the installation paths of the products you want to use with TOSCA Structure before starting with the installation. 1.2 Installation The installation application is based on Install Anywhere from Macrovision. The installer of TOSCA Structure provides an integrated help functionality. During the installation you query additional information about the current configuration dialog by selecting the Help button. Note: The Installer is a self extracting Java application. A Java virtual machine is not required on the target machine. The virtual machine needed for the installation and the use with the TOSCA Structure graphical user interface will be extracted to a temporary filesystem at the beginning of the installation and installed into the installation directory of TOSCA Structure. This means you need to make sure to provide enough space on the temporary filesystem to extract the Java virtual machine (up to 150 mb). You can define the directory where the installer extracts the temporary file system by setting the environment variable IATEMPDIR: i.e. for tcsh setenv IATEMPDIR /scratch or for sh/ksh/bash IATEMDIR=/scratch export IATEMPDIR Note: On Unix systems you can execute the installation from a remote machine, but the installer depends on forwarding the X11 screen to your local host. So the DISPLAY environment variable must be set correctly. 1.3 Successful Installation After the installation has finished successful you will find the following on your computer: General TOSCA Structure installation directory This directory contains all the components of TOSCA Structure. Windows Programs Folder TOSCA Structure 7.0 in the Windows Start Menu, this folder contains links to start TOSCA Structure. Unix Symbolic links ( default: /usr/bin) in a directory defined during the installation. These symbolic links are required to launch TOSCA Structure. 3

4 2 Licensing 2.1 FlexLM FlexLM offers two different types of licenses: node lock licenses that are only valid on enabled computers and network licenses that are accessible from all computers in a network. In this chapter, only a description of the special features pertaining to the FE-DESIGN implementation and the delivered tools will be given. A detailed description of the Flex License Manager may be found in the enduser documentation of Macrovision (see <TOSCA_Structure>/docu/FLEXlm_enduser.cfg). 2.2 Determination of the FlexLM hostid The FlexLM host ID is required in order to apply for a license. It contains a unique ID of your license server. To determine the host ID use the lmtools graphical user interface or the command line utility lmutil. 2.3 Node Lock license If TOSCA Structure is to be used with a node locked license, you need to determine the FlexLM hostid of your system and send it to FE-DESIGN. FE-DESIGN will generate the appropriate license file. This license file can be supplied during the installation of TOSCA Structure or copied to <Tosca Structure>\licence\license.dat afterwards. 2.4 Floating license Obtain license and license server files First you decide which computer should be used as the FlexLM server. Determine the FlexLM hostid of the system and sent it to FE-DESIGN to get an appropriate license file. The FlexLM server packages for different operating systems are found on the Download page of TOSCA Structure Modify license file When you obtained the license file it must be modified to reflect your configuration and requirements. The header of the file must contain the correct SERVER entry. A SERVER line has the following entries: SERVER <Server Name> <FlexLMid> <Server TCP/IP Port> Note: TOSCA Structure uses the standard port It is useful to define the port in such a way that TOSCA Structure does not conflict with other FlexLM authorized software applications. The license file from FE-DESIGN contains the following line SERVER YourLicenseServerName 00b0d0090b85 To start the license server in the machine fed-pc14 and the TCP/IP Port 1234 you have to modify the following entries: SERVER fed-pc14 00b0d0090b For special license server configurations the VENDOR line can be modified as well. All other lines (FEATURE) must not be edited! 4

5 2.4.3 License server installation Extract the obtained FlexLM server package in the directory you want install the license server and place the license file beside the lmgrd binary. The FlexLM license server is started by the submitting following command: lmgrd c license.dat If this command is submitted from the command line the FlexLM server starts and the licenses are available. This works for Windows and Unix. But if the license server machine is rebooted the license server will not start automatically. On Windows systems the FlexLM server must be added to the system services and on Unix machines the FlexLM server must be added to the start scripts. An appropriate installation can be done either with the Windows FlexLM gui lmtools.exe or the command line tool installs.exe. Both tools are delivered with the FlexLM server package for Windows. For details see the FlexLM enduser manual and the online help of installs.exe. On Unix systems there is a sample start script provided in the archive flexlm_unix_start.tar.gz that is available on the TOSCA Structure download page. In order to use this script some required information must be specify in the configuration section at the top of the script. i.e.: If TOSCA Structure FlexLM is installed in /opt/tosca/flexlm and the license.dat file resides in /opt/tosca/license/license.dat the header of the script has to be: # PATH to the FlexLM installation directory FED_FLEXLM_HOME=/opt/Tosca/FlexLM # Name of the FlexLM license file FED_FLEXLM_LICENSE_FILE=/opt/Tosca/license/license.dat This file must be integrated in the startup folders of your system. Please see your system documentation on how this is accomplished Test of the license server installation A check as to whether the license server works correctly may be done with the FlexLM utilities. The lmtools.exe utility can be used on Windows systems. Command line tools (e.g. Unix systems) are also available. The command line lmutil lmdiag -c <path_to_license.dat> may be used to check if the installed licenses are available. A detailed description of all other FlexLM utilities can be found in the FlexLM enduser documentation Note FlexLM saves information regarding the licensing order in the running server processes. This leads to a loss of information in case of a license server shutdown. After a restart of the vendor daemon, the license server has no information about the licenses which have been checked out. This may lead to problems in a situation of concurrence where a running TOSCA Structure process and a queued or newly-started process are looking for the same license. 5

6 When starting, TOSCA Structure determines the running time of the FED process. If the vendor daemon is running less than 150 sec, TOSCA Structure waits 150 sec until the license has been checked. This ensures that all running processes restore the connection to the licensed server before the new license requests are served. 3 Appendix 3.1 Configuration File: tosca_ctrl.cfg The configuration file of the TOSCA Structure optimization control program is completely implemented in PERL syntax and is interpreted at the beginning of the optimization procedure. All variables that are embedded in ampersands (&VAR&) are replaced during the installation procedure. Single parameters are documented in the Commands Manual of the TOSCA Structure documentation. Example: MSC.Nastran Configuration: During the start of optimization, the fe_solver variable is defined. In the configuration the different solver configuration settings are enclosed in if - elsif - else - endif statements. ###### MSC NASTRAN ###### }elsif (${fe_solver} eq "mscnastran") { # The tosca_interface variable defines the interface $ENV{"tosca_interface"} = "${tosca}/mscnastran"; The TOSCA Structure variable $fe_solver_exe is set to the full path name of Nastran. This value is defined during the installation and TOSCA Structure verifies the existence of this executable or startscript at the beginning. e.g. for Windows systems : C.\Program files\msc\msc2001\i386\nastran.exe ${fe_solver_exe} = "&IA_PATH_MSCNASTRAN_WIN&"; Additionally Nastran command line parameters are set to the $fe_solver_call variable. These parameters are used for the start of Nastran within TOSCA Structure. ${fe_solver_cmdline} = "${modelname}.${inp_ext} notify=no old=no"; Common information is set outside the platform specific blocks. ${res_ext} = "op2"; ${fe_solver_add_call} = "";... The full configuration file can be found in the installation bin-directory and is called tosca_ctrl.cfg : Unix: <TOSCA62>/bin/tosca_ctrl.cfg Windows: <TOSCA62>\bin\tosca_ctrl.cfg 6

7 3.2 Troubleshooting The following chapters explain possible errors that can occur when starting TOSCA Structure Configuration Finite element solver executables are not defined correctly During the installation process, the pathes to the FE solver executables are requested and entered to the configuration file: <TOSCA Structure>\bin\tosca_ctrl.cfg. In case these entries are empty or incorrect the following error message will appear: TOSCA Structure COMMAND_SHELL ERROR ERROR in TOSCA Structure-module: TOSCA Structure.control Wrong configuration settings. The following configuration variable is not set correctly: Variable_name : $fe_solver_exe Variable_value : Path to fe-solver executable is not set correctly Please check if you have selected the correct FE-solver. Current setting: $fe_solver = Configuration is not set correctly To fix this problem you need to enter the correct paths to the FE solver executables either in the main configuration file or an user specific configuration file in the users HOME directory Licensing Problems with the FlexLM authorisation may occur in two stages of the optimization process. If the license server cannot be accessed or the host ID is not correct, TOSCA Structure will stop at the beginning of the optimization run. The corresponding error messages are printed out to the screen and to the Auth.log file in the start directory of the optimization job. fed-hp2 134: tosca clip -solver mscnastran Authorisation system reports fatal FLEXLM Error: Error description: Server node is down or not responding See the system adminstrator about starting the server, or make sure the you're referring to the right host (see LM_LICENSE_FILE) Feature: TOSCA_CORE Hostname: fed-gulli1 License path: 7777@fed-gulli1 FlexLM error: -96,7 For further information, refer to the FlexLM End User Manual, available at " Tosca ERROR Program will finish now. 7

8 If problems occur concerning the licensed TOSCA Structure functions (e.g. the solver interface is not licensed correctly), TOSCA Structure will be aborted during the optimization procedure. In case of a non-existing interface license, TOSCA Structure will be aborted in the optimisation pre-processing module. The corresponding error messages may be found on the screen and the TOSCA.OUT file in the <jobname>/db_error directory. NAME: /scratch/test/tosca62/abaqus/command.ini #INPUT: FE_PIPE, ALL, ABAQUS ******** TOSCA Structure WARNING ******** Interface : ABAQUS not authorised Hint : LIST, AUTHORISATION -->> see what is allowed #INPUT: OPTIONS #INPUT: READ_TOPO_RESULTS = NODE #INPUT: READ_LOAD = ON #INPUT: END_ The available interfaces may be listed by the LIST, AUTH command AUTHORISATION INFORMATION of TOSCA Structure NAME STATUS Description Available features and interfaces: TOSCA_CORE X Main Feature of authorisation process TOSCA_INT_NASTRAN X Feature for NASTRAN interface TOSCA_INT_ANSYS X Feature for ANSYS interface In addition to the error messages in the TOSCA Structure protocol files, different tools are available to find the cause of the error. On Windows systems the lmtools utility may be used to get detailed information pertaining to the status of the license server and the licenses available Unix TOSCA Structure Invocation On Unix systems TOSCA Structure requires to be called via symbolic links to the TOSCA Structure start script. TOSCA Structure needs to set and unset several environment variables dependent on the called modules. This is achieved by sourcing the configuration script into the launcher scripts of the single TOSCA Structure modules. To provide single points of configuration for the configuration entries this is done in different scripts. When TOSCA Structure.gui is launched directly by calling : <TOSCA62>/bin/os_linux/tosca_gui You will see the following error when starting an optimization task: 8

9 This error occurs because the tosca environment variable, which is set by tosca6_script is not set before the start of TOSCA Structure.gui. If you like to write your own launcher scripts the following settings are required: #!/bin/sh tosca=/opt/tosca62 export tosca. $tosca/bin/common_env.sh $tosca/bin/os_linux/tosca_gui This is necessary for all components of TOSCA Structure you like to call. 9