Linux Installation Guide

In this tutorial you will learn about:

  • How to install MCalibration and PolyUMod on a Linux computer

Overview

  • This Linux installation tar-gz package contains the following components:
  1. PolyUMod
  2. MCalibration
  3. Veryst Material Model Database
  4. Veryst license server

A floating license may be served locally on Linux or remotely on Linux or Windows (Unlike a floating license, a node-locked license requires no license server software, just a license file). This document only describes installation procedures for Linux; for the installation or update of the Windows license server, please use the Windows software installer and documentation.

The components in this package have been tested on the following LInux versions:

  1. Red Hat/ CentOS 6.10
  2. Red Hat/CentOS 7.6

This document provides instructions for manually installing and using the components of this package.

Conventions used in this document:

  • The computer’s prompt is shown as user> or root> based on whether the command generally needs to be executed with normal or root privileges, respectively.
  • Responses from the computer are shown the in the same format, but without the user> or root> prefix.
  • Material enclosed in [square] brackets represents optional material.
  • Material enclosed in <angle> brackets represents parts of a command where you should substitute your specific information.
  • Note: all Linux commands, variables and filenames are case-sensitive; the file thing.txt is not the same file as THING.txt.

All the necessary files are contained in PolyUMod_Installer_Lin64_v5.2.0.tar.gz which you can download using the link that was provided to you. Send us a message if you need link again.

 

Install PolyUMod and MCalibration

You will need the proper permissions to write to the installation area, to the root for shared areas such as the /opt tree, or to the owner for private areas such as /home/mydir. The shell used for these commands is the native shell for the operating system which here is assumed to be bash.

  1. Archive any pre-existing installation and create a new directory to house the new installation, setting permissions for global read and execute:
    root> cd /opt
    root> mv PolyUMod PolyUMod_old
  2. Uncompress and untar the installation package
    root> cd /opt
    root> mkdir Veryst
    root> chmod 755 Veryst
    root> cd Veryst
    root> tar xzf <path>/PolyUMod_Installer_Lin64_v5.2.0.tar.gz
    root> mv PolyUMod_Installer_Lin64_v5.2.0/files/* .
    root> rm -rf PolyUMod_Installer_Lin64_v5.2.0
  3. Read the license agreement found at Veryst_License_Agreement.txt. Continuing with the installation means that you have accepted the agreement.
  4. The completed installation should appear as shown below. You may leave the installer directory in place until you’ve completed the full installation, or remove it if you don’t need to work with the license server.

Set up a user and test the installation

  1. Each user’s path should include the MCalibration executable directory. This may be done in the setup files for your shell, or interactively at the shell prompt. For ease of invocation, users might also want to alias the MCalibration invocation as shown below:
    user> export PATH=/opt/Veryst/MCalibration:$PATH
    user> which MCalibration
    /opt/Veryst/MCalibration/MCalibration
  2. [Optional] Each user who wants to activate PolyUMod for use with Abaqus will need to modify the Abaqus setup file abaqus_v6.env. You can find instructions for making that modification here.
  3. [Optional] Each user who wants to activate PolyUMod for use with ANSYS will need to ensure that the ANSYS library environment variable, ANS_USER_PATH, is pointing into the Veryst installation rather than the default ANSYS installation. These steps are documented here.
    Note: The ANSYS installation scripts modify ANS_USER_PATH, so each time you update ANSYS, you will need to update the ANS_USER_PATH to point back to PolyUMod.
  4. Test the MCalibration installation by typing the command MCalibration. If there is no license local to the installation or the invocation directory (node-locked license type), or there is no license installed and running (floating license type), the tool will first show a warning then default to Reader Mode:

Obtain a license using an Activation Key

If you have an activation key, have already installed the software and MCalibration is in your executable path, you may create a license for that machine by invoking the /opt/Veryst/MCalibration/Activate_License executable. The example shown here will get a node-locked license for MCalibration, but these steps are the same for both node-locked and floating licenses.

user> Activate_License &

 

You may select the name and location you prefer for the license file. In this example, we accept the default setting.

 

 

Setup and Use a Node-Locked License

If you are using node-locked licenses, copy each license file into the installation. The file extension must be .lic and the license file must be either in the same directory as the executable or in the invocation directory. Multiple license files may exist in the same directory.

user> cp ~/license.lic /opt/Veryst/MCalibration/thing.lic

To update a node-locked license in an existing installation, simply copy the new license file into that installation or into your invocation directory.

If you don’t want to overwrite the old license, you may give it a different name as long as its suffix remains .lic.

In the following example, if license.lic contains a corrupt or expired license and thing.lic contains a new, correct license, MCalibration will simply do the right thing and consume the .lic file with a working license.

user> ls *lic
license.lic	thing.lic

 

Install or Update the Software for a Floating License Server

Some useful information about how to install, start, and manage the license server is contained in the installation: <installdir>/README_license_server.txt. Some of that information is reproduced here.

The license server software consists of three files in the License subdirectory of the Veryst Engineering installation tree. You may simply copy the files from a user’s installation, or unwrap the original tar file. You may place these files in a fresh area (preferred), or overlay them on an existing area. 

root@srvr> cd /opt
root@srvr> mkdir Veryst
root@srvr> chmod 777 Veryst
user@srvr> mkdir Veryst/License
user@srvr> cp <tarfilePath>/files/License/* Veryst/License/.

Manage a Floating License Server

Some useful information about how to install, start, and manage the license server is contained in the installation, <installdir>/License/README_license_server.txt. Some of that information is reproduced here.

To start a license server, you first copy the license file into the License directory. Then use the rlm executable provided here as shown:

user> cp <path>/mylicense.lic <installdir>/License/license.lic 
user> cd <installdir>/License
user> /rlm –dlog /tmp/rlm.log &

Once it has been started, you may manage the license server through an html interface: http://localhost:5054/home.asp

From this page you can check the status, look at the log file, re-read the license file, read a new license file, stop the server, etc.

Alternatively, to check the status of the license server, you may examine the log at /tmp/rlm.log.

Finally, online documentation for license servers can be viewed at http://www.reprisesoftware.com/RLM_Enduser.html

Use a Floating License

To use the floating licenses, Linux users will need to set an environment variable to point to the license server, as shown below. The environment variable is veryst_LICENSE (case-sensitive), and it should point to <port>@<host>. The default <port> is 5053, and the <host> may be localhost (if run on the local machine), a hostname, or an IP address (e.g., 10.0.0.45). A remote host may be Linux or Windows.

user> export veryst_LICENSE=5053@localhost

It is possible to use redundant license servers by chaining these variables and files, separated by colons (“:”) as follows:

user> export veryst_LICENSE=5053@localhost:/opt/LicenseFiles/somefile.lic:5053@svr2:5053@10.4.48.123