STAR-CCM+ Installation Guide
This guide contains instructions on how to install STAR-CCM+ and the CAD Clients on Windows, and STAR-CCM+ on Linux.
Contents  
Installation Changes in STAR-CCM+ v11.06
What Are the Requirements?
STAR-CCM+ Licensing Requirements
Downloading STAR-CCM+
What Gets Installed?
Installing STAR-CCM+
Launching STAR-CCM+
Uninstalling STAR-CCM+
Setting Up Licensing
Getting Support
Finding Additional Information
Glossary
Installation Changes in STAR-CCM+v11.06
This section describes changes to the current STAR-CCM+ installation.
Change to the Installation Path
When the installation process is complete, you now have component directories under a single installation directory that is labeled with the version number, for example 11.06.###/STAR-CCM+11.06.###. For more details, see What Gets Installed?.
MPICH No Longer Supported
The MPICH MPI distribution is no longer supported by STAR-CCM+.
What Are the Requirements?
Before you install STAR-CCM+, make sure that your system meets the various requirements.
Contents  
Hardware
Certified Platforms for STAR-CCM+ v11.06
Supported Platforms for STAR-CCM+ v11.06
Software
Help System
STAR-View+
Hardware
These are the recommended hardware requirements to run STAR-CCM+ and the CAD Clients. You can improve performance by using better specifications than those listed.
Contents  
Typical Memory Requirements for STAR-CCM+
Typical Memory Requirements for STAR-CCM+
This topic contains typical memory requirements for building and running a case in STAR-CCM+.
The following examples are rough estimates only and may vary significantly between models with different characteristics.
Memory requirements for meshing:
*
*
*
As an example, a workstation with 48 GB of memory can build a 50 million cell model (polyhedral) or a 100 million cell model (trimmed cells). The memory requirements for solving in serial with a two-equation turbulence model are displayed below. On average, polyhedral cells require roughly twice the amount of memory per million cells.
Certified Platforms for STAR-CCM+v11.06
Certified platforms are combinations of hardware and software that are subjected to thorough testing.
STAR-CCM+ is available on all supported and certified platforms in mixed and double precision.
1. The CAD client functionality is not supported with CATIA V5-6R2014 (R24), Inventor 2015, Creo Parametric 2.0, and NX9 on Windows Vista.
2. The CAD client functionality is not supported with CATIA V5-6R2014 (R24) on Windows 8/8.1.
A minimum LSB (Linux Standard Base) level of LSB 3.0 is required to run licensing components on Linux machines.
Virtual Machines
STAR-CCM+, the CAD Clients, and STAR-View+ are not warranted for use on virtual machines. It is expected that most features will function correctly, but there have been reports of some specific problems.
Supported Platforms for STAR-CCM+v11.06
Supported platforms are combinations of hardware and software where some testing has been performed and/or compatibility is expected.
* While this version of Glibc may be appropriate for installing STAR-CCM+, Glibc 2.12 or greater is required for installing STAR-View+.
STAR-CCM+ is available on all supported and certified platforms in mixed and double precision.
A minimum LSB (Linux Standard Base) level of LSB 3.0 is required to run licensing components on Linux machines.
Virtual Machines
STAR-CCM+, the CAD Clients, and STAR-View+ are not warranted for use on virtual machines. It is expected that most features will function correctly, but there have been reports of some specific problems.
Software
This section contains the software requirements for running STAR-CCM+.
Compilers
All Linux ports of STAR-CCM+ are built with the gnu 4.8 compiler. All Windows ports are built with the Intel 15.0 compiler and Visual Studio 2013. The version of the Microsoft C Runtime Library is 10.00.30319.1. The compiler and its libraries do not need to be installed unless you are implementing User Code, and then only on the node(s) where the libusr.so file is created.
Java
STAR-CCM+ and the CAD Clients require the Java SDK (Software Development Kit) version 1.7.0_75. The SDK is installed automatically by the STAR-CCM+ installer. It is also available from the Oracle download site at: http://www.java.com/en/download/manual.jsp
On Windows, if you want to force STAR-CCM+ to look in a custom location for your Java installation, set the STARCCM+_JAVA_HOME environment variable to point to the custom directory. You can also use the STAR_JAVA_HOME environment variable if you require an alternative name. If STARCCM+_JAVA_HOME is not found, STAR-CCM+ checks for STAR_JAVA_HOME.
STAR-View+, the standalone interactive results viewer for STAR-CCM+, also checks the STARCCM+_JAVA_HOME environment variable when it starts.
OpenGL
STAR-CCM+ requires that you have OpenGL 2.1 or higher installed on your machine. STAR-View+ also requires OpenGL 2.1 as minimum.
Help System
To view the Help system, you must use a web browser that supports HTML 4 and Cascading Style Sheets. JavaScript must be enabled in your browser.
STAR-View+
This section contains the requirements for installing and using STAR-View+.
Requirements for Windows
*
*
*
Requirements for Linux
*
*
*
*
STAR-CCM+ Licensing Requirements
STAR-CCM+ is licensed software. Installing and configuring the license is part of the installation process. You cannot run the software until you configure the licensing correctly.
There are two licensing models available for STAR-CCM+:
*
*
Contents  
Obtaining a License File on Linux
Obtaining a License File on Windows
FlexNet License Server
The licensing operates through a license server, which is a separate process that runs continuously on a machine you choose. In general, only one machine on your network is required to act as a license server, although you can set up multiple machines to provide redundancy in case of machine failure. The FlexNet license server uses licensing data that is stored in a text file called the license file, (license.dat), which CD-adapco creates for you. You must obtain a license file from your CD-adapco representative before you can configure the FlexNet license server correctly. Your CD-adapco representative requires a hostid identifier which you get by running a downloadable utility program. More information on obtaining a license file is provided in the following sections:
*
*
Once you have the license file, the installation process can automatically configure and run the license server for you. If you need to configure the license server after your initial installation, refer to Setting up a Single Server Floating License. Other instructions are provided for alternative configurations.
Power-on-Demand License Server
The Power-on-Demand licensing model allows you to use a STAR-CCM+ Power Session from a CD-adapco public license server rather than a license server on your own network. Your organization can purchase credit to use with the CD-adapco license server. Individual users are provided with Power-on-Demand keys for their sessions. For more information, refer to the Power-on-Demand Licensing section of the STAR-CCM+ user guide (Using STAR-CCM+ > STAR-CCM+ Licensing > Power-on-Demand Licensing). You can access the STAR-CCM+ user guide by clicking the Documentation tab in the Steve Portal. If you do not have your Steve Portal account information, contact your CD-adapco representative.
The CD-adapco Power-on-Demand license server is located outside your firewall. Ports 1999 and 2099 must be open to allow communication traffic between your machine and the Power-on-Demand license server. For more information on how to check whether these ports are open, refer to the Which Ports Are Used in a Power-On-Demand Session? section of the STAR-CCM+ user guide (Using STAR-CCM+ > STAR-CCM+ Licensing > Power-on-Demand Licensing > Which Ports Are Used in a Power-On-Demand Session?).
Obtaining a License File on Linux
To obtain a license file on Linux:
1.
2.
% ./lmutil lmhostid
The host ID of the machine is displayed in the command prompt:
The FlexNet host ID of this machine is "1803054gf548"
3.
% ./lmutil lmhostid -hostname
The host name of the machine is displayed in the command prompt:
The FlexNet host ID of this machine is "HOSTNAME=entelea"
4.
You will receive a license file.
5.
Obtaining a License File on Windows
To obtain a license file on Windows:
1.
2.
To open a command prompt in a specified directory:
a.
b.
While holding down the <Shift> key, right-click on a blank area in the directory and select Open command window here.
3.
> lmutil.exe lmhostid
The host ID of the machine is displayed in the command prompt:
The FlexNet host ID of this machine is "1803054gf548"
4.
> lmutil.exe lmhostid -hostname
The host name of the machine is displayed in the command prompt:
The FlexNet host ID of this machine is "HOSTNAME=entelea"
5.
You will receive a license file.
6.
Downloading STAR-CCM+
You can download STAR-CCM+ from the Steve Portal at http://steve.cd-adapco.com.
To download STAR-CCM+:
1.
If you do not have your account information, contact your CD-adapco representative.
2.
In the Steve Portal, click Products > Downloads.
By default, STAR-CCM+ is the selected product. A list of available downloads for the chosen version is displayed under Application Downloads.
3.
Click the Download link next to the desired platform.
The double precision version of STAR-CCM+ is generally intended for cases that involve physical phenomena of vastly differing scales. Examples include wave propagation in water, three-dimensional microstructure battery modeling, electrodynamics simulations, and multiphase flows.
4.
What Gets Installed?
Several software components are installed for STAR-CCM+ and the CAD Clients.
These components are:
*
STAR-CCM+ module
*
*
*
*
Some of these components are optional and you can choose whether or not to install them while installing STAR-CCM+.
When the installation process is complete, you have the following directories under the initial target location:
*
11.06.###/STAR-CAD11.06.### contains the constituent applications of the CAD Clients (Windows only).
*
11.06.###/STAR-CCM+11.06.### contains the STAR-CCM+ module.
*
11.06.###/STAR-View+11.06.###
*
11.06.###/FLEXlm (Windows) or FLEXlm_11.13 (Linux) contains the FLEXlm 11.13 Utilities. This directory contains platform specific licensing tools, including lmadmin,lmutil, lmgrd, and cdlmd. The Licensing Administration Guide is also included as a PDF file.
*
Installing STAR-CCM+
This sections contains instructions for installing STAR-CCM+ on Linux and Windows platforms.
Contents  
Installing STAR-CCM+ on Linux
Installing STAR-CCM+ on Windows
Installing STAR-CCM+ on Linux
This section contains information on installing STAR-CCM+ on Linux.
Contents  
Extracting the Installer
Installing Using the Interactive Installer
Installing from the Command Line
Problems with Disk Space
Extracting the Installer
Once you download the compressed file from the Steve Portal, you must extract it before you can run it.
To run the installer:
1.
% tar -zxvf STAR-CCM+11.06.###_[OS].tar.gz
where [OS] is the name of the operating system.
2.
% ./STAR-CCM+11.06.###_[OS].bin
When the installer launches correctly, you are presented with a series of screens to guide you through the process. These steps are itemized in the next section.
Remember to export the DISPLAY of the server to your workstation if you require a GUI-based installation. If the display variable is not set, the installer defaults to a console (non-GUI) installation.
Installing Using the Interactive Installer
There are two installation methods that you can use to install STAR-CCM+:
*
Express Install - installs STAR-CCM+ on a single machine with the most common options. Select this option if you have a license file or if you want to set up Power-on-Demand licensing.
*
Custom Install - installs STAR-CCM+ with advanced options.
Express Install
The express installation uses the most common options to install STAR-CCM+ on a single machine, and to configure the license server. Select this option if you have a license file or if you want to set up Power-on-Demand licensing.
To perform an express installation:
1.
Select Setup Language: if you have a Chinese or Japanese operating system, choose your required language and click OK.
This option gives you the choice to run the STAR-CCM+ installer either in English or in your native language.
2.
License Notice: read the agreement and choose to accept. Click Next to continue.
3.
Choose Installation Method: select the Express (Recommended) option. Click Next to continue.
4.
Choose License Type: this screen presents two licensing options:
?
POD: configures the machine to use CD-adapco’s Power-on-Demand license server.
?
Local: installs and configures a local license server on the current machine.
5.
Select Install Location: click Next to accept the default location, otherwise enter a custom directory location. Note that when creating a new folder in Linux, you must include the whole path. You may also need to press <Enter> to create the folder.
6.
Setup Licensing: this screen appears if no existing licensing information is found on the current machine. If you require a license file, you must get this from CD-adapco after obtaining the necessary hostid. Browse to the license file and when complete, click Next.
7.
Pre-Installation Summary: this screen shows a summary of what will be installed on your machine. Click Next to proceed with the installation.
8.
Installing: this screen shows the current progress of the installation process.
9.
Install Complete: this final screen indicates the end of the STAR-CCM+ installation process. If any errors were encountered during installation, a message is displayed here prompting you to check the installation log file.
Custom Install
The custom installation lets you customize the installation and licensing to your needs.
To perform a custom installation:
1.
Select Setup Language: if you have a Chinese or Japanese operating system, choose your required language and click OK.
This option gives you the choice to run the STAR-CCM+ installer either in English or in your native language.
2.
License Notice: read the agreement and choose to accept. Click Next to continue.
3.
Choose Installation Method: select the Custom (Advanced) option.
4.
Choose Install Type: this screen presents the components that are available for installation on your system. Select the desired components and click Next.
The following options are available:
STAR-CCM+ and related components > Install STAR-CCM+ on local or shared NFS location: installs STAR-CCM+ on the current machine or in a location of your choice.
FLEXNet License Manager: choosing this option will provide two further options in a subsequent step where you can choose to either use an existing license server on the network, or to install and configure a FlexNet license server on the host machine.
If this setting is not selected, then the license server will have to be setup manually. See the licensing guide below.
If you want to use PoD (Power-on-Demand) licensing, activate this option.
5.
Choose STAR-CCM+ Components: choose the components to install.
The following components are available:
STAR-CCM+: installs STAR-CCM+ on your system.
STAR-CCM+ Documentation: installs the STAR-CCM+ documentation on your system.
STAR-View+: installs STAR-View+.
6.
Choose License Type: select the licensing method that you want to use and click Next.
?
Network: configures the current machine to access a network license server. If you want to connect to the CD-adapco Power-on-Demand license server, or another existing license server in your organization, select this option and follow the step below:
FlexNet Client Configuration: enter the hostname and port number of your organization's license server using the format: port@host. If you are using Power-on-Demand licensing, enter 1999@flex.cd-adapco.com. You can add additional redundant servers if your network is set up to support this. Click Next to continue.
?
Local: installs and configures FlexNet publisher on the current machine. If you choose this option, follow the relevant steps below:
FlexNet License Server Configuration: enter the Web Port Number and License Port Number, otherwise click Next to keep the default values.
Select license file: browse to the license that you obtained from CD-adapco and click Next.
7.
Select Install Location: enter a custom directory for the STAR-CCM+ installation, otherwise click Next to accept the default location.
8.
Select Additional Tasks: select the additional tasks you want the installer to perform:
The following tasks are available:
Add application directories to your system path: activate this option if you generally launch software from a command prompt window, and you only wish to use this latest version of STAR-CCM+. If you want to run STAR-CCM+ by typing the full path, deactivate this option.
9.
Pre-Installation Summary: this screen shows a summary of what will be installed on your machine. Click Next to proceed with the installation.
10.
Installing: this screen shows the current progress of the installation process.
You may see additional windows appearing during the installation process, depending on the selections you made. In particular, if you chose to install the bundled Java JDK, you will be presented with windows from the Java Installer. Respond to the prompts as appropriate.
11.
Start a browser: this page appears if you selected the Local license option in the Choose License Type screen. If you select Start browser now, a web browser launches and displays the license details in lmadmin. If this is not required, click Next without changing anything.
12.
Install Complete: this final screen indicates the end of the STAR-CCM+ installation process. If any errors were encountered during installation, a message is displayed here prompting you to check the installation log file.
Installing from the Command Line
You can run the STAR-CCM+ installer from the command line to allow for an unattended installation.
This type of installation supports the following arguments:
*
-i console runs the installer in console mode, which installs STAR-CCM+ with the default settings (as used in the Express install). Output from this installation is shown in the console window. Note that you are required to accept the license agreement and choose the location for the installation in the console.
*
-i silent performs a silent installation. No console or dialog windows appear. Information on installation process is stored in the log file.
*
-f "filename" instructs Setup to load the settings from the specified file after having checked the command line. Use quotes if the filename contains spaces.
*
-r "filename" instructs Setup to save installation settings to the specified file. Use quotes if the filename contains spaces.
*
-DINSTALLDIR=<path> provides an alternative location for the STAR-CCM+ installation.
*
-PCMPIINSTALLDIR=<path> provides an alternative location for the IBM Platform MPI installation.
*
-D<PARAMETER>=true/false provides additional installation options, where <PARAMETER> can be:
INSTALLFLEX controls whether the license server is installed and configured. If you do not want to install the license server, set this argument to false.
ADDSYSTEMPATH adds the application directories to your system path. If you generally launch software from a shell, and you only wish to use this latest version of STAR-CCM+, set this argument to true. Note that by default this value is set to true and your user profile file (.cshrc or.profile files, for example) are modified. If you do not want your profile to be modified, set this argument to false.
NODOC controls whether or not the STAR-CCM+ documentation is installed. If you do not want to install the STAR-CCM+ documentation, set this argument to true.
An example command is provided below. Using this command, STAR-CCM+ is installed in console mode without installing the FlexNet license server.
% ./STAR-CCM+11.06.###_[OS].bin -i console -DINSTALLFLEX=false
where [OS] is the is the name of the operating system.
Problems with Disk Space
By default, the Linux installer can use up to 4Gb of space in /tmp. Make sure that there is enough disk space available. If space is not available on the root of the physical drive, use the IATEMPDIR environment variable to change the location of the temporary directory to a drive with sufficient free space:
*
% IATEMPDIR=/your/free/space/directory
% export IATEMPDIR
*
% setenv IATEMPDIR /your/free/space/directory
If there is not enough free disk space, you will receive a warning message.
Also, note that the auto mounting utility, autofs, that is supplied with certain Linux distributions can cause the disk space check to fail, and raise the “not enough free disk space” error. If this happens, turn off the disk space check using the following environment variable:
*
% CHECK_DISK_SPACE=OFF
% export CHECK_DISK_SPACE
*
% setenv CHECK_DISK_SPACE OFF
Installing STAR-CCM+ on Windows
Administrator privileges are required for the standard installation of STAR-CCM+ and the CAD Clients on Windows. Alternatively, you can use the -NOADMIN option from the command line to install without administrator privileges.
Contents  
Extracting the Installer
Installing STAR-CCM+ Using the Interactive Installer
Installing from the Command Line
Installing on a Windows Cluster
Installing on a Central Network Server
Finding the Log File
Extracting the Installer
Once you download the compressed file from the Steve Portal, you must extract it before you can run it.
To run the installer:
1.
2.
3.
4.
5.
Navigate to the STAR-CCM+_CadClients-11.06.### sub-directory and double-click on STAR-CCM+_CadClients11.06.###_[OS].exe, where [OS] is the name of the operating system.
When the installer launches correctly, you are presented with a series of screens to guide you through the process. These steps are itemized in the next section.
Installing STAR-CCM+ Using the Interactive Installer
There are two installation methods that you can use to install STAR-CCM+:
*
Express Install - installs STAR-CCM+ on a single machine with the most common options. Select this option if you have a license file or if you want to set up Power-on-Demand licensing.
*
Custom Install - installs STAR-CCM+ with advanced options.
Express Install
The express installation uses the most common options to install STAR-CCM+ on a single machine, and to configure the license server. Select this option if you have a license file or if you want to set up Power-on-Demand licensing.
To perform an express installation:
1.
Select Setup Language: if you have a Chinese or Japanese operating system, choose your required language and click OK.
This option gives you the choice to run the STAR-CCM+ installer either in English or in your native language.
2.
License Notice: read the agreement and choose to accept. Click Next to continue.
3.
Choose Installation Method: select the Express (Recommended) option. Click Next to continue.
4.
Choose License Type: this screen presents two licensing options:
a.
POD: configures the machine to use CD-adapco’s Power-on-Demand license server.
b.
Local: installs and configures a local license server on the current machine.
5.
Setup Licensing: this screen appears if no existing licensing information is found on the current machine. Browse to the license file and when complete, click Next.
6.
Pre-Installation Summary: this screen shows a summary of what will be installed on your machine. Click Next to proceed with the installation.
7.
Installing: this screen shows the current progress of the installation process.
8.
Install Complete: a final screen appears to indicate the end of the STAR-CCM+ installation process. If any errors were encountered during installation, a message is displayed here prompting you to check the installation log file.
9.
Custom Install
The custom installation lets you customize the installation and licensing to your needs.
To perform a custom installation:
1.
Select Setup Language: if you have a Chinese or Japanese operating system, choose your required language and click OK.
This option gives you the choice to run the STAR-CCM+ installer either in English or in your native language.
2.
License Notice: read the agreement and choose to accept. Click Next to continue.
3.
Choose Installation Method: select the Custom (Advanced) option.
4.
Choose Install Type: this screen presents the components available for installation on your system. Once the desired components have been selected click Next.
The following options are available:
STAR-CCM+ and related components: Two following options are available:
Install STAR-CCM+ on this machine or a network location: installs STAR-CCM+ on the current machine or on a location of your choice.
Configure this machine to use an existing STAR-CCM+ network installation: configures the current machine to use an existing installation of STAR-CCM+ from a shared network directory. This options does not install STAR-CCM+. Use this option for a compute node on a cluster, for example. The installer asks you to locate the STAR-CCM+ and STAR-View+ installation directories. These directories must be shared. For each case, point to the folder that contains the STAR-CCM+ or STAR-View+ executables:

> \\[server_name]\star-ccmplus
11.06.###
> \\[server_name]\star-viewplus11.06.###
STAR-View+ must be installed in order for you to use this option.
FLEXNet License Manager: choosing this option presents two further options in a subsequent step where you choose to either use an existing license server on the network, or to install and configure a FlexNet license server on the current machine.
If you do not activate this option, you must set up and configure the license server manually. Refer to the licensing guide.
If you want to use PoD (Power-on-Demand) licensing, activate this option.
5.
Choose STAR-CCM+ Components: choose the components to install.
The following components are available:
STAR-CCM+: installs STAR-CCM+ on your system.
STAR-CCM+ Documentation: installs the STAR-CCM+ documentation on your system.
STAR-CAD Clients: installs the CAD Clients for the CAD packages that the installer detects on your system. This option does not install STAR-CCM+.
The following CAD Clients are available:
STAR-View+: installs STAR-View+.
Microsoft VC runtimes: installs the Microsoft Visual C++ runtimes. This option is deactivated if the installer detects that the appropriate Microsoft runtimes are already installed on your machine. Avoid manually reinstalling these runtime libraries.
6.
Choose License Type: select the licensing method that you want to use and click Next.
?
Network: configures the current machine to access a network license server. If you want to connect to the CD-adapco Power-on-Demand license server, or another existing license server in your organization, select this option:
FlexNet Client Configuration: enter the hostname and port number of your organization's license server using the format: port@host. If you are using Power-on-Demand licensing, enter 1999@flex.cd-adapco.com. You can add additional redundant servers if your network is set up to support this. Click Next to continue.
?
Local: installs and configures FlexNet on the current machine. If you choose this option, follow the relevant steps below:
FlexNet License Server Configuration: enter the Web Port Number and License Port Number, otherwise click Next to keep the default values.
Select license file: browse to the license that you obtained from CD-adapco and click Next.
Service Configuration: configures the License Manager service. A default name, CD-adapco_License_Server, is provided for this service. If this service already exists, enter a new name. Activate the Start license server now option if you want this service to start automatically once the installation completes. Click Next to continue.
7.
Select Install Location: enter a custom directory for the STAR-CCM+ installation, otherwise click Next to accept the default location.
8.
Select Additional Tasks: select the additional tasks you want the installer to perform.
The following tasks are available:
Update Windows firewall to allow STAR-CCM+ to run: adds a rule to the Windows firewall to permit socket communication on the specified ports. By default, the Windows firewall may block this communication.
You must manually add exceptions to third-party firewall software.
Share install directory: shares the installation directory so that others can access it. This option is useful for parallel runs.
Create a desktop icon: creates a desktop icon on the current machine.
Create shortcuts for current user only: creates shortcuts to CD-adapco products for the current user only.
9.
Pre-Installation Summary: this screen shows a summary of what will be installed on your machine. Click Next to proceed with the installation.
10.
Installing: this screen shows the current progress of the installation process.
You may see additional windows appearing during the installation process, depending on the selections you made. Respond to the prompts as appropriate.
11.
Start a browser: this page appears if you selected the Local license option in the Choose License Type screen. If you select Start browser now, a web browser launches and displays the license details in lmadmin. If this is not required, click Next without changing anything.
12.
Install Complete: this final screen indicates the end of the STAR-CCM+ installation process. If any errors were encountered during installation, a message is displayed here prompting you to check the installation log file.
13.
Installing from the Command Line
You can run the STAR-CCM+ installer from the command line to allow for an unattended installation. This type of installation supports the following arguments:
*
-i console runs the installer in console mode, which installs STAR-CCM+ with the default settings (as used in the Express install). Output from this installation is shown in the console window. Note that you are required to accept the license agreement and choose the location for the installation in the console.
*
-i silent performs a silent installation. No console or dialog windows appear. Information on installation process is stored in the log file.
*
-f "filename" instructs Setup to load the settings from the specified file after having checked the command line. Use quotes if the filename contains spaces.
*
-r "filename" instructs Setup to save installation settings to the specified file. Use quotes if the filename contains spaces.
*
-DINSTALLDIR=<path> provides an alternative location for the STAR-CCM+ installation.
*
-PCMPIINSTALLDIR=<path> provides an alternative location for the IBM Platform MPI installation.
*
-DCOMPUTE_NODE=<true> only installs the dependencies that are required to run STAR-CCM+. Does not install the full package. This option is intended for use in cluster installations where the full package is installed on the head node only.
*
-D<PARAMETER>=true/false provides additional installation options, where <PARAMETER> can be:
INSTALLFLEX controls whether the license server is installed and configured. If you do not want to install the license server, set this argument to false.
CURRENTUSERONLY creates a desktop shortcut for the current user only. If you want to create shortcuts for the current user only, set this argument to true. This applies to CD-adapco products only.
SHARE controls whether to share the installation directory so that others can access it. This is useful for parallel runs. The installation directory is shared by default. If you do not want to share the installation directory, set this argument to false.
FIREWALL controls whether to add an exception to the Windows firewall to allow STAR-CCM+ to run. The Windows firewall may attempt to block socket communication. By default, a rule is added by the installer to permit this communication. If you do not want this to happen, set this argument to false. Note that you must manually add exceptions to third-party firewall software.
DESKTOPICONS controls whether to create desktop icons for the installed components. By default, the installer creates desktop icons. If you do not want the desktop icons, set this argument to false.
NOADMIN allows the installation and execution of STAR-CCM+ without administrator privileges. You must choose an installation location that is not protected by administrator privileges. If you set this argument to true, additional directories are created in the STAR-CCM+ server directory which contain all required Microsoft run-times. Systems administrators can use the NOADMIN mode to install STAR-CCM+ on a central server and run on Windows clients without installing additional components. Note that only sequential or shared memory IBM Platform MPI parallel runs are supported when you perform a NOADMIN installation.
NODOC controls whether or not to install the STAR-CCM+ documentation. If you do not want to install the STAR-CCM+ documentation, set this argument to true.
An example command is provided below. Using this command, STAR-CCM+ is installed in console mode without installing the FlexNet license server.
> STAR-CCM+_CadClients11.06.###_[OS].exe -i console -DINSTALLFLEX=false
where [OS] is the is the name of the operating system.
Installing on a Windows Cluster
For running in parallel on a cluster, you only have to install the full STAR-CCM+ package on the head node. Compute nodes only require the necessary dependencies for running the STAR-CCM+ executable.
To install STAR-CCM+ on the head node, use the interactive or command line installer. Ensure that the installation directory is shared amongst all compute nodes. Also make sure that the CDLMD_LICENSE_FILE environment variable is configured correctly on all compute nodes.
*
> cluscfg listenvs
*
If no CDLMD_LICENSE_FILE environment variable is defined, enter the following command:
> cluscfg setenvs CDLMD_LICENSE_FILE=<port>@<licserver>
Installing on Compute Nodes
This installation is not required for Windows Server 2008 or Windows Server 2012.
To install STAR-CCM+ on compute nodes, use either the clusrun (Windows HPC Server) command or psexec command in conjunction with the -DCOMPUTE_NODE=true parameter.
An example psexec command is shown below:
> psexec @machinefile -accepteula -u username -p password "\\netshare\path\
STAR-CCM+_CadClients
11.06.###_win64_intel12.1.exe" -i silent -DCOMPUTE_NODE=true
where @machinefile contains a list of host names or network addresses. You can use the -DINSTALLDIR parameter to override the default installation directory.
An example of the clusrun command would be:
headnode> clusrun /all "\\netshare\path\
STAR-CCM+_CadClients
11.06.###_win64_intel12.1.exe" -i silent -DCOMPUTE_NODE=true
On Windows HPC Server, you can also use the HPC Cluster Manager to select the compute nodes:
1.
Start an Action, and choose to Run Command.
2.
Run the STAR-CCM+ installer with the -i silent option:
> "\\netshare\path\
STAR-CCM+_CadClients
11.06.###_win64_intel12.1.exe" -i silent -DCOMPUTE_NODE=true
Installing on a Central Network Server
If you are a network administrator, you can create a central installation of STAR-CCM+ on your network for use by client workstations. Workstations using this central installation do not require a full STAR-CCM+ package on their local disks.
To setup a central network installation:
1.
Use the command line installer to install STAR-CCM+ on the central server. You must use the -DNOADMIN=true option when running the installer.
2.
3.
On each client workstation, run the STAR-CCM+ PowerShell script, STAR-CCM+.ps1, which is located in the root directory of the shared STAR-CCM+ installation.
You do not need to register the JAVA_HOME and MPI_ROOT environment variables on the local client workstations. Copies of the Java installation and the MPI installations are contained in the STAR-CCM+ installation directory on the central server. STAR-CCM+ searches for these variables on the server when you launch it on a client workstation. The Java SDK is installed implicitly within a pre-defined directory structure.
Running the PowerShell Script on Client Workstations
To run the PowerShell script, follow the steps outlined below:
1.
On each client machine that needs to run STAR-CCM+, launch a Windows PowerShell command window:
2.
Click on the <Start> button and enter PowerShell in the search field. Select Windows PowerShell from the list that appears.
3.
STAR-CCM+11.06.###\STAR-CCM+.ps1 -cdlicserver <port@host>
Where <host> and <port> are replaced with the relevant parameters for your license server.
STAR-View+11.06.###\STAR-View+.ps1
If your client workstation already has STAR-CCM+ licensing configured, you can omit the -cdlicserver option. No licensing is required for STAR-View+.
Parallel Simulations
When working with this type of installation, parallel simulations on client machines must run using IBM Platform MPI in shared memory mode only. To activate IBM Platform MPI, include -mpi platform in the argument list for the STAR-CCM+ server launch command.
Finding the Log File
The package installer creates a log file, STAR-CCM+11.06.###_InstallLog.log, in your STAR-CCM+ installation directory.
The information contained in the log file is technical in nature, but may be of use when contacting CD-adapco support about installation problems.
The log file is only created after you click the Finish button in the STAR-CCM+ Installer.
Launching STAR-CCM+
Once the installer has successfully installed STAR-CCM+, you can launch it. A directory containing STAR-CCM+ is created for you in the location that you specified during the installation.
Contents  
Launching STAR-CCM+ on Linux
Launching STAR-CCM+ on Windows
Starting the CAD Clients
Launching STAR-CCM+ on Linux
Once the installation is complete, you can launch STAR-CCM+.
To launch STAR-CCM+:
1.
% starccm+
For reference, the full path to the STAR-CCM+ executable is: /[install]/STAR-CCM+[version]/star/bin/starccm+.
STAR-CCM+ is ready for you to use. If you are using STAR-CCM+ for the first time, work through the introductory tutorial.
Launching STAR-CCM+ on Windows
Once the installation is complete, you can launch STAR-CCM+.
To launch STAR-CCM+:
1.
Double-click the STAR-CCM+ icon that was created on your Windows desktop.
STAR-CCM+ launches.
2.
Alternatively, from the Start menu, click the STAR-CCM+ icon in All Programs > CD-adapco.
STAR-CCM+ is ready for you to use. If you are using STAR-CCM+ for the first time, work through the introductory tutorial.
Starting the CAD Clients
To run the CAD clients, follow the steps outlined below. If you are having trouble starting the CAD clients, refer to the CAD client user guide (CAD Clients > Using CAD Clients > Working With [CAD client] > Introducing [CAD client] > Getting Started > Launching [CAD client] Manually)
*
CATIA -- During installation a STAR-CAT5 R XX Y YY YYY icon is created on the desktop, or in the CATIA folder in the All Programs menu. Double click this icon to start STAR-CAT5. Open a CATPart or CATProduct and start STAR-CAT5 from the Analysis and Simulation menu.
*
NX -- STAR-NX loads automatically when you launch NX. A STAR-NX menu appears in the NX menu bar.
*
*
Inventor -- STAR-Inventor loads automatically when you launch Inventor. The STAR-Inventor ribbon appears in the Inventor user interface.
If you wish to use CAD Clients with Power Session or Lite Session licenses, open the Preferences Dialog within your CAD client interface and select the appropriate option. Instructions on doing this are provided in the STAR-CCM+ User Guide.
Uninstalling STAR-CCM+
You can uninstall STAR-CCM+ using the STAR-CCM+ installer.
Contents  
Uninstalling STAR-CCM+ From Linux
Uninstalling STAR-CCM+ from Windows
Increasing the Java Heap Size
Uninstalling STAR-CCM+ From Linux
To uninstall STAR-CCM+:
1.
% [DIR]/STAR-CCM+11.06.###/Uninstall
where [DIR] is the installation directory you used during installation.
The uninstaller automatically detects the installed components and launches the uninstallation wizard. In this page, you can choose to keep the license manager.
During uninstallation, the entire contents of the STAR-CCM+ and STAR-View+ folders are removed. All contents are removed even if you made changes within the folders since the time of installation.
If you encounter an “out of memory” error while uninstalling STAR-CCM+, refer to Increasing the Java Heap Size for information on how to resolve this.
On some Linux systems the STAR-CCM+11.06.### folder may remain after uninstallation completes. This folder typically contains a log file as well as an empty jre sub-folder. You can remove this folder by using the following command:
% rm -rf STAR-CCM+11.06.###
Uninstalling STAR-CCM+ from Windows
You can uninstall STAR-CCM+ using the Programs and Features panel. The CAD clients are also uninstalled when you uninstall STAR-CCM+.
To uninstall STAR-CCM+:
1.
Click <Start> and enter Add or remove programs in the search field.
2.
Select Add or remove programs from the search results.
3.
In the dialog that appears, locate the STAR-CCM+ and CAD Clients entry and click Uninstall/Change.
The uninstaller automatically detects the installed components and launches the uninstallation wizard. During this process, you can choose to keep the license manager.
During uninstallation, the entire contents of the STAR-CCM+, STAR-View+, and STAR-CAD folders are removed. All contents are removed even if you made changes within the folders since the time of installation.
If you configured you machine to use an existing STAR-CCM+ network installation, the shortcuts may remain on the desktop and Start menu of your machine after uninstalling. In this case, delete the shortcuts manually. You may need to do this to remove the CD-adapco group, after removing all existing STAR-CCM+ installations.
If you encounter an “out of memory” error while uninstalling, refer to Increasing the Java Heap Size for information on how to resolve this.
Increasing the Java Heap Size
When uninstalling STAR-CCM+, you may receive an “out of memory” error as shown in the following example:
Invocation of this Java Application has caused an InvocationTargetException. This application will now exit. (LAX)

Stack Trace:
java.lang.OutOfMemoryError: Java heap space
To fix this issue:
1.
[INSTALL]/STAR-CCM+11.06.###/Uninstall_STAR-CCM+11.06.###
where [INSTALL] is the installation directory.
2.
Locate and open the Uninstall STAR-CCM+11.06.###.lax file with a text editor of your choice.
3.
lax.nl.java.option.java.heap.size.max=250331648
The value in your file may be different.
4.
5.
6.
Setting Up Licensing
CD-adapco products use the FlexNet Publisher Licensing Toolkit 11.13 from Flexera Software to manage end-user licensing.
The basic setup for a floating license configuration with a single license server is covered initially. This includes:
*
*
*
*
*
*
Further sections are also provided. The CD-adapco specifics section gives additional information on:
*
*
*
Understanding the basics of licensing at the end of this section provides a more technical overview of FlexNet licensing system:
*
*
*
*
*
A troubleshooting guide is also provided.
Contents  
Setting up a Single Server Floating License
CD-adapco Specifics
Understanding the Licensing System
Troubleshooting
Setting up a Single Server Floating License
This section describes the steps necessary to set up a basic floating license configuration using a single server.
1.
2.
This is referred to as the license server host. Guidance on how to choose an appropriate machine can be found in the License Administration Guide (LicenseAdministration.pdf which is copied to the FlexNet utilities directory during installation).
Linux platforms must be LSB Certified to a minimum of LSB 3.0.
3.
If this machine is not the one used during the previous installation steps, or if the FLEXlm 11.13 Utilities were not selected during installation, you must re-run the STAR-CCM+ installer on this machine and choose to install the FLEXlm 11.13 Utilities.
On Windows, these utilities are typically installed in C:\Program Files\CD-adapco\FLEXlm\11_13_0_0\bin.
On Linux, these utilities are installed in [DIR]/FLEXlm_11.13/[Platform]/bin, where [Platform] corresponds to the particular Linux platform.
4.
For more information on obtaining a license file, refer to Obtaining a License File on Linux and Obtaining a License File on Windows. When you have the necessary information, e-mail it to your CD-adapco sales representative and wait for the license file to be returned.
5.
6.
7.
For more complex licensing arrangements, such as managing license files from multiple vendors, refer to the Flexera License Administration Guide.
Contents  
Starting the License Server
Stopping the License Server
Importing a New License File
Setting up Client Machines
Checking the Status of Licenses
Upgrading the FlexNet License Server
Starting the License Server
Typically, you want the license server to start every time the license server host machine is restarted. The procedure is different for Linux and Windows.
Contents  
Starting the License Server on Linux
Starting the License Server on Windows
Starting the License Server on Linux
To start the license server:
1.
Change to the directory containing lmadmin. A typical path is shown below:
% cd [INSTALL_DIR]/FLEXlm/[FLEXlm_Version]/bin
2.
Run the lmadmin utility by typing the following into the command line:
% ./lmadmin
Alternatively, add a line to the start up script. For more information on how to do this, refer to Chapter 9 of the Flexera License Administration Guide.
Starting the License Server on Windows
In a typical case, the license server will be set as a service in the Windows Services control panel during the installation process. The service name is CD-adapco_License_server (unless a custom name was chosen during installation), and is automatically started when the machine is turned on.
To manually start the license server:
1.
Click <Start> and enter services.msc in the search field.
2.
3.
In the Services window, locate the service:
CD-adapco_License_server
4.
Stopping the License Server
If you are upgrading the license server, or if you want to remove it, you must first stop it.
Contents  
Stopping the License Server on Linux
Stopping the License Server on Windows
Stopping the License Server Using lmadmin and Your Web Browser
Stopping the License Server on Linux
You can stop the server using lmadmin and your web browser.
Alternatively, to stop the license server by killing the process:
1.
% ps -ef | grep lmadmin
This will display information about this task, including the PID.
2.
% kill -9 <PID from previous step>
Stopping the License Server on Windows
You can stop the server using lmadmin and your web browser.
Alternatively, you can stop the license server manually.
In a typical case, the license server is set as a service in the Windows Services control panel during the installation process. The default service name is CD-adapco_License_server and automatically starts when the machine turns on. If you gave this service a different name during the installation, in the following example, replace CD-adapco_License_server with the name of your service.
To stop the license server:
1.
Click <Start> and enter services.msc in the search field.
2.
3.
In the Services window, locate the service:
CD-adapco_License_server
or the name of your service.
4.
Stopping the License Server Using lmadmin and Your Web Browser
You can stop the license server using lmadmin in your web browser.
Once you stop the server in lmadmin, you are not able to start it again from within lmadmin.
1.
Launch a web browser and enter http://localhost:[PORT]/ in the address bar, where [PORT] is the web port number you specified during installation.
The default port is 8080.
2.
Click the Administration tab located at the top right of the panel.
The Sign In dialog appears. If this does not appear, ensure that your pop-up blocker is not blocking this page.
3.
Enter admin as both the User Name and Password.
4.
Click Submit to continue.
The System Information tab appears by default.
5.
Click the Server Configuration tab on the left-hand side of the page.
The Server Configuration page appears.
6.
Click Stop Server.
A dialog appears warning you that the license server will be stopped and that you will not be able start it again from the web browser.
7.
Click OK to stop the server.
Importing a New License File
To import a new license file (or to overwrite a license file that has expired), use lmadmin and follow the steps outlined below:
1.
Launch a web browser and enter http://localhost:[PORT]/ in the address bar, where [PORT] is the web port number you specified during installation. The default port is 8080.
2.
Click the Administration tab that is located at the top right of the panel, as shown below.
The Sign In dialog appears. If this does not appear, ensure that your pop-up blocker is not blocking this page.
3.
Enter admin as both the User Name and Password.
4.
Click Submit to continue.
The System Information tab appears by default.
5.
Click the Vendor Daemon Configuration tab on the bottom left of the page.
The Vendor Daemons page appears. The daemons running on this license server are listed here. The daemon for CD-adapco products is cdlmd.
6.
Click Import License to import a new license file.
The Import License File page appears.
7.
Click Browse... and select the license file that you want to add to this server.
If you would like to overwrite the existing license file, activate the Overwrite License File on License Server option.
8.
Click Import License to complete this operation.
A summary page appears informing you of the changes.
The license file is copied to the FLEXlm folder of the STAR-CCM+ installation directory, typically:
C:\Program Files\CD-adapco\FLEXlm\11_13_0_0\bin\licenses\cdlmd
If you used the license file during the installation process, then this is copied to the default FLEXlm directory.
In order for the new license to be picked up, you must stop and restart the license server:
9.
10.
Contents  
Checking Vendor Daemon Information
Checking Vendor Daemon Information
To check the information on the CD-adapco vendor daemon, cdlmd, follow the steps outlined below.
1.
In lmadmin, navigate to the Vendor Daemon page by clicking on the Vendor Daemon Configuration tab.
2.
Click on the cdlmd daemon.
The vendor daemon information page appears, as shown below.
Here, you can see which license files are used by the daemon and their location. You can also start and stop the vendor daemon, as well as reread the license files. Remember to click on Save if you have made any changes that you would like to keep.
Setting up Client Machines
Each client that needs to access the license server must know the hostname and port number of the license server. There are a number of ways to provide this information on each client, but the simplest are as follows:
Linux
For Linux:
1.
Create a .flexlmrc file in each user's home directory with a single line of the form:
CDLMD_LICENSE_FILE=<port>@<server>
where:
<port> is the port number through which communication takes place.
<server> is the name or TCP/IP address of the machine on which the license server is running.
Windows
For Windows, create an environment variable called CDLMD_LICENSE_FILE and set its value to the <port>@<server> for the license server.
To create an environment variable:
1.
Click <Start> and enter environment variables in the search field.
2.
From the search results, select Edit the system environment variables.
3.
In the System Properties dialog, click Environment Variables...
4.
In the System Variables section of the dialog, click New...
The New System Variable dialog appears.
5.
Set Variable name to CDLMD_LICENSE_FILE.
6.
Set Variable value to <port>@<server>.
Where:
<port> is the port number through which communication takes place.
<server> is the name or TCP/IP address of the machine on which the license server is running.
7.
Click OK to close the New System Variable dialog.
8.
Click OK to close the Environment Variables dialog.
9.
Click OK to close the System Properties dialog.
Checking the Status of Licenses
To check the status of the licenses using lmadmin, follow the steps outlined below:
1.
Launch a web browser and enter http://localhost:[PORT]/ in the address bar, where [PORT] is the web port number you specified during installation.
The default port is 8080.
The lmadmin utility appears. The Dashboard tab is displayed by default.
2.
Click Concurrent to display all the registered licenses.
A table containing information on each license feature is displayed. A description of each column is given below:
Notifications about the licenses appear on the left side of the web page. Critical issues can be seen by clicking on the red hexagon; important issues can be seen by clicking on the yellow triangle.
Upgrading the FlexNet License Server
The best approach to upgrading a FlexNet license server is to stop the old license server, remove it if you want to, and then start the new license server.
Upgrading the License Server on Linux
To upgrade the license server on Linux:
1.
?
?
1.
% ps -ef | grep lmadmim
2.
2.
3.
% ./[INSTALL_DIR]/FLEXlm/[FLEXlm_Version]/bin/lmadmin
Upgrading the License Server on Windows
To upgrade the license server on Windows:
1.
2.
?
?
> sc stop <OLD_LICENSE_SERVER_NAME>
Where, <OLD_LICENSE_SERVER_NAME> is the name of your old license server. The default name is CD-adapco_License_server.
3.
> sc delete <OLD_LICENSE_SERVER_NAME>
4.
5.
> sc start <NEW_LICENSE_SERVER_NAME>
CD-adapco Specifics
This section helps you understand more about the FLEXnet licensing system as used by STAR-CCM+ and the CAD Clients:
Contents  
What Licenses Are Checked Out?
What is the Vendor Daemon Name?
What Environment Variables Can I Use?
What Licenses Are Checked Out?
The names of the features that STAR-CCM+ and the CAD Clients check out are detailed below.
What License Features are Used by STAR-CCM+?
STAR-CCM+ checks out the licenses as follows:
*
*
In serial, the STAR-CCM+ server uses a ccmpsuite license. It does not use a starsuite license.
*
In parallel, the master process requires a ccmpsuite to launch and run. Additional processes created by the controller require an hpcdomains, a ccmpsuite, or a DOEtoken license to start and continue solving. As an example, a two-worker parallel job on a dual CPU machine would require one ccmpsuite license and one hpcdomains license.
*
If the Power Session license option is chosen, the ccmppower license is used regardless of whether the session is serial or parallel, and without any limit to the number of worker processes that can be launched.
*
If the Lite Session license option is chosen, the ccmplite license is used if it is available; otherwise the ccmpsuite license is used.
*
For battery modeling, STAR-CCM+ requires a batterysim license in addition to the other license features. Battery Design Studio®, which is supplied for use with the STAR-CCM+ battery modeling capability, requires either a batterysim or a batterydesignstudio license.
*
For DARS model solving, STAR-CCM+ requires a dars-cfd or dars-cfd-hpc license.
*
For importing geometry into STAR-CCM+, you require a JTOpen license for .jt geometries, or a cadexchange license for all other supported CAD formats.
What License Features are Used by the CAD Clients?
When a CAD Client is started, it checks out one license, of the form:
star-<cadpackage>
where <cadpackage> is one of:
*
*
*
*
A second license is checked out at the start of the meshing or simulation stage. This is a ccmplite license (or a ccmpsuite license if ccmplite is not available).
These licenses remain checked out as long as the product is active.
What is the Vendor Daemon Name?
The FlexNet documentation refers to the vendor daemon name. For CD-adapco, the vendor daemon is cdlmd. This name is used in the license file and the environment variable CDLMD_LICENSE_FILE is used to locate the license file if set.
What Environment Variables Can I Use?
The following variables can be set to adjust the behavior of the license manager. Unless otherwise stated, setting the variable to 1 will turn the behavior on, setting it to 0 or not setting it at all will turn it off.
*
STARLICENSELOG When the license routines run, they will write to the file that this is pointing to as well as to standard out. This can be useful if license messages do not appear. This has to be set to the file.
> set STARLICENSELOG=c:\log.txt
% setenv STARLICENSELOG /tmp/log.txt
*
STARLICENSEVERBOSE Causes more verbose messages to be displayed to both the screen and log file.
*
STARNOFLEXLMRC FlexNet will not write to the ~/.flexlmrc file (Linux) or the HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License Manager registry key (Windows).
*
STARNOTIMEOUT FlexNet normally times out after two hours of inactivity. This means that if a machine crashes with a license checked out, the license will return to the server after this time. In cases where no activity for two hours is normal (a queuing system that suspends a job during the day) then this will release the license and the job may fail to get the license when it progresses (another user may have the license). If this variable is set, FlexNet will never time-out and so will avoid this. However, be aware that this may cause licenses, which would otherwise be returned, to remain checked out. Use lmremove to deal with checked out licenses that have not been returned as expected.
*
STARWAIT Normally, FlexNet will return if a license is unavailable and the code will exit. If STARWAIT is set, then FlexNet will wait until a license becomes available. This may be of use in queue or batch systems.
Understanding the Licensing System
This section will help you understand more about the FlexNet system as used by STAR-CCM+ and the CAD Clients.
This information is largely a simplified version of parts of the Flexera License Administration Guide.
Contents  
FlexNet Components
How Does The License Request Process Work?
Using Redundant License Servers
Understanding the Floating License File Format
Specifying the License File Location
FlexNet Components
For served licenses, there are four required FlexNet components:
*
*
The License File (license.dat)
*
*
The last two components comprise the license server system.
In addition to these four FlexNet components, there are three optional components that you can configure:
*
*
Report Log File, created and written by cdlmd for use by FlexNet Manager
*
The diagram below shows the relationship between these components, which are expanded upon in the Component Overview.
Typically, the license server system components (lmadmin and cdlmd) reside on a machine in the network but can optionally reside on the same machine as the CD-adapco applications.
Contents  
Component Overview
FlexNet Licensing Components Shipped by CD-adapco
Component Overview
The License Server Manager (lmadmin)
The license server manager (lmadmin) handles the initial contact with the CD-adapco applications, passing the connection on to cdlmd. It also starts and restarts cdlmd. To configure lmadmin, use a web browser of your choice.
The CD-adapco Daemon (cdlmd)
Counted (floating) licenses are granted by cdlmd, which keeps track of how many licenses are checked out, and who has them.
CD-adapco applications communicate with cdlmd through TCP/IP network communications. The application and the daemon processes (lmadmin and cdlmd) can run on separate machines on your network, across any size of heterogeneous wide-area network. This means the license server system and the computer running an application can be different hardware platforms or even different operating systems.
If cdlmd terminates for any reason, all users lose their licenses, although this does not mean the applications suddenly stop running. Users normally regain their license automatically when lmadmin restarts cdlmd, though they may exit if cdlmd remains unavailable.
The License File
Licensing data is stored in a text file called the license file (license.dat), which is created by CD-adapco, and edited and installed by your license administrator. It contains information about the server machines and CD-adapco daemons, and a line of data for each CD-adapco “feature”. One product may have multiple features to access different aspects of the application, or a product may look for one of several features before starting.
Typical content of a license file is covered in the format overview, and there are multiple ways of specifying the location of the license file.
The FLEXenabled CD-adapco Product
STAR-CCM+ and the CAD Clients are linked with the FlexNet Licensing client library that provides the communication with the license server system (lmadmin and cdlmd). During execution, the application communicates with cdlmd to request a license.
FlexNet Licensing Components Shipped by CD-adapco
The following table provides a list of the essential components that come with CD-adapco products:
How Does The License Request Process Work?
When you run a counted (floating) CD-adapco product, the following occurs:
1.
2.
The application establishes a connection with the license server manager (lmadmin) and tells it that it needs to talk to cdlmd.
3.
lmadmin determines which machine and the TCP/IP port correspond to cdlmd and sends that information back to the CD-adapco application.
4.
The CD-adapco application establishes a connection with cdlmd and sends its request for a license.
5.
cdlmd checks in its memory to see if any licenses are available and sends a grant or denial back to the application.
6.
After successfully checking out a license, STAR-CCM+ spawns a threaded heart beat which is essentially a tiny process that fires a signal to the license server every minute to say that STAR-CCM+ is alive. If the license server doesn’t hear from STAR-CCM+ in 150 seconds then the license server assumes that STAR-CCM+ is dead and retracts the license (unless you specify the STARNOTIMEOUT environment variable, in which case the license server waits forever).
Conversely, if there is no acknowledgement from the license server (as would happen if the server failed or was stopped), the STAR-CCM+ client will note the time and keep trying for 1 hour. STAR-CCM+ will stop iterating if no response is received by then. When this happens, you will still be able to save results and exit, but you will not be able to start iterating again until a license is found.
Using Redundant License Servers
As with all computer systems, it is impossible to ensure that any specific computer is available all the time, and this may result in license denial if the license relies on a single computer. To address this issue, CD-adapco supports redundant license servers which means that a number of computers are involved in the license server process and the process is tolerant to some of the servers being down.
Contents  
Using the Three-Server Redundancy Approach
Using a Simple License File List
Using an Enhanced License File List
Setting up a Two Server Fail Over Mechanism
Using the Three-Server Redundancy Approach
With three-server redundancy, the “server” is in fact three machines. As long as any two of the three servers are up, they have a quorum and can issue licenses. This is a good system for a single site and has the advantage that even if one of the triad is down, the full number of licenses are still available. This has been supported since the first release of STAR-CCM+ with FlexNet and is a standard FlexNet option.
Using a Simple License File List
With a simple license file list, there is a list of servers, such as one in London, one in Detroit, and one in Tokyo. When the license is checked out, each server is tried in turn on the list. Typically users in London will check out from the London server but if the London server is down, they can check out from another server on the list. This is a good system for multiple sites but has some disadvantages:
1.
When one machine is down, the pool of licenses is reduced. So if each machine has 10 copies of ccmpsuite, when London is down, there are only 20 copies of ccmpsuite to share between three sites instead of 30.
2.
3.
Using an Enhanced License File List
To address point 3 of the simple license file list, the license routines have been recoded so that each license request is fullfilled by one or more FlexNet jobs. The advantage of this is that each FlexNet job can be from a different server, so an application can mix and match license requests across the whole license file list.
This is a CD-adapco specific development and is supported by license codes dated 09-Oct-2004 or later.
Setting up a Two Server Fail Over Mechanism
Using an example of two license servers:
*
1999@offal with 2 hpcdomains
*
1999@heraclitus with 1 ccmpsuite and 1 hpcdomain
and starting a simulation using -np 4:

Starting STAR-CCM+ parallel server
MPI Distribution : Platform Computing MPI-09.01.04.02
Host 0 – marlinhead – Ranks 0-3
Process rank 0 marlinhead 26177
Total number of processes : 4

STAR-CCM+
11.06.### (linux-x86_64-2.5/gnu4.8)
License build date: 10 February 2015
This version of the code requires license version 2016.10 or greater.
Checking license file: 1999@marlin
1 copy of ccmpsuite checked out from 1999@marlin
Feature ccmpsuite expires in 288 days
Thu Sep 15 10:12:30 2016
Server::start -host marlinhead.cm.cluster:47830
Loading simulation database: /offal2/philip/polymanifold/polymanifold.sim
Loading module: KeTurbModel
..
2 copies of hpcdomains checked out from 1999@offal
Feature hpcdomains expires in 258 days
1 copies of hpcdomains checked out from 1999@heraclitus
Feature hpcdomains expires in 45 days
Partitioning from Serial into 4 partitions
...
STAR-CCM+ succeeded because of the fail over mechanism which allows it to build up its total request over a number of servers.
Understanding the Floating License File Format
This section provides details of the most common options in a typical license file provided by CD-adapco. The full reference can be found in Chapter 8 of the Flexera License Administration Guide.
License files usually begin with a SERVER line followed by one or more VENDOR lines, followed by one or more FEATURE lines.
An example of a license file that provides floating licenses is:

SERVER lulu 17007ea8 1999
# If the following is uncommented, none of the following lines will be processed
# USE_SERVER
# you may need to append the full path to cdlmd if it is not on you path
# e.g. VENDOR cdlmd /usr/star/version/license/cdlmd
VENDOR cdlmd
FEATURE ccmpsuite cdlmd 1.0 15-jan-2005 20 24D76447DB45 \
vendor_info=3722006928dd6ae3e1d6501005a96cd75fe0f1c50c8340ba31237cd6579dc16989fda96607caef3f5f8d3d352c831afa9a54ac80d89d91cc4744a6d808857a68313b3c55bbad5f72b629a42d941a3f12a0289a
This license file specifies that:
*
are available anywhere on the network that can access the license server machine lulu. lmadmin uses the TCP/IP port 1999.
You can modify the following elements in the license file:
*
*
*
*
*
*
*
Contents  
SERVER Lines
VENDOR Lines
USE_SERVER Line
FEATURE Lines
SERVER Lines
The SERVER line specifies the hostname and hostid of the license server system and the TCP/IP port number of the license server manager (lmadmin). Normally a license file has one SERVER line. The absence of a SERVER line means that every FEATURE line in the license file is uncounted.
The hostids from the SERVER lines are computed into the license key or signature on every FEATURE line. For this reason, make sure you keep SERVER lines together with any FEATURE lines as they were sent from the vendor.
The format of the SERVER line is:
SERVER host hostid [port] [PRIMARY_IS_MASTER] [SERVER_TIMEOUT=seconds]
where:
*
host is the system host name or IP address. On Linux, this is the name returned by the hostname or uname -n command. On Windows, ipconfig /all.
*
hostid is usually the string returned by the lmhostid command. This is set by CD-adapco.
*
port is the TCP/IP port number to use. A valid number is any unused port number between 0 and 64000. On Linux, choose a port number greater than 1024, since those less than 1024 are privileged port numbers. If no TCP/IP port number is specified, one of the default ports in the range of 27000 and 27009 is used. Flexera recommends using port numbers outside the range of 27000 through 27009.
VENDOR Lines
The VENDOR line specifies the daemon name and path. lmadmin uses this line to start the vendor daemon, and the vendor daemon reads it to find its options file. The format of the VENDOR line is shown below.
VENDOR vendor [vendor_daemon_path][[OPTIONS=]options_file_path] [[PORT=]port]
where:
*
vendor Name of the vendor daemon used to serve some feature(s) in the file. This name cannot be changed by the administrator.
*
vendor_daemon_path is an optional path to the executable for this daemon. Generally the license administrator is free to install the daemon in any directory. (It is recommended, however, that it be installed in a local directory on the license server machine.) If omitted, lmadmin looks for the vendor daemon binary in:
The path specified in lmadmin’s $PATH environment variable
in the directory where lmadmin is located
*
If vendor_daemon_path is blank, then any options or TCP/IP port number specifications require the OPTIONS= and PORT= strings.
*
options_file_path is the full path to the end-user options file for this daemon. FLEXnet does not require an options file. If omitted, the CD-adapco daemon looks for a file called cdlmd.opt that is located in the same directory as the license file.
*
port is the vendor daemon TCP/IP port number. The default, if the port number is not specified, it is chosen by the operating system at run-time. Sites with Internet firewalls need to specify the TCP/IP port number the daemon uses. If a TCP/IP port number is specified on the VENDOR line, there may be a delay when restarting the vendor daemon.
USE_SERVER Line
The USE_SERVER line takes no arguments and has no impact on the server. When the application sees USE_SERVER, it ignores everything in the license file except preceding SERVER lines and transfers checkout validation to the vendor daemon. USE_SERVER is recommended since it improves performance when a license server system is used.
FEATURE Lines
A FEATURE line describes the license required to use a product.
Only the first FEATURE line for a given feature is processed by cdlmd. The basic FEATURE line format is:
{FEATURE} feature vendor feat_version exp_date num_lic vendor_info=... [optional_attributes]
The six fields after the FEATURE line keyword are required and have a fixed order:
*
feature Name given to the feature by the vendor.
*
vendor Name of the vendor daemon; also found in the VENDOR line. The specified daemon serves this feature.
*
feat_version Version of this feature that is supported by this license.
*
exp_date Expiration date of license in the format dd-mmm-yyyy, e.g., 07-may-2005. If exp_date is the string permanent or the year is 0 (or 00, 000, 0000) then the license never expires.
*
num_lic is the number of concurrent licenses for this feature.
*
vendor_info= is additional information provided by CD-adapco.
Specifying the License File Location
The license server must know where the license file is located and looks in a number of places. The FLEXenabled CD-adapco software also looks in these locations to find the path to the license server (or to use the license file directly in the case of node-locked licenses). The locations are as follows:
*
use_server format
*
The value of an environment variable (LM_LICENSE_FILE or CDLMD_LICENSE_FILE) that can be specified in two ways:
Contents  
Using the Default Location
Using Environment Variables
What if More Than One Method is Used?
Using the Default Location
On Windows the default location for the license file is:
C:\Program Files\FLEXnet Publisher License Server Manager\licenses\cdlmd\license.dat
and on Linux it is:
/usr/local/flexlm/licenses/license.dat
The license.dat file can be in one of two formats:
*
*
SERVER server hostid port
USE_SERVER
where hostid is the same as the hostid in the original license file
Using Environment Variables
The environment variable can be defined in a number of ways:
*
Using the setenv command at the command line or in your shell startup script
Defining the variable in a ~/.flexlmrc file that contains a single line in the CDLMD_LICENSE_FILE=value format
*
Using the set command at the command line
Setting a variable using Start > Settings > Control Panel > System > Advanced > Environment Variables dialog
Defining a key in the HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License Manager registry branch, where the variable will be the name of the key and the value will be stored in the value of the key
In addition to the multiple ways of setting up the environment variable, there are two variables that can be used to hold a value pointing to the license file:
*
*
All these environment variables will take the form:
VARIABLE=value
where VARIABLE is one of the two options above and value can be the pointer to the license file in one of three formats:
*
*
*
For backward compatibility, CD-adapco products also recognize the STAR_DIR environment variable expecting to find a license file at:
$STAR_DIR/license/license.dat
See Managing Multiple License Files for more information about LM_LICENSE_FILE and Appendix D, FlexNet Licensing Environment Variables in the FlexNet End User Guide for more information.
What if More Than One Method is Used?
If you use more than one of the methods mentioned in the previous two sections to point to a license file, then all of the files will be scanned, and the CD-adapco product will scan all the options in the following sequence and check out the first valid license:
*
The CDLMD_LICENSE_FILE environment variable
*
The CDLMD_LICENSE_FILE registry entry (Windows) or content of the ~/.flexlmrc file (Linux)
*
The LM_LICENSE_FILE environment variable
*
The LM_LICENSE_FILE registry entry (Windows)or content of the ~/.flexlmrc file (Linux)
*
The STAR_DIR environment variable
*
Troubleshooting
This section contains resolutions to common problems encountered while setting up licensing.
Contents  
Vendor daemon can’t talk to lmadmin (Linux)
License server checks for licenses before the network is configured (Windows)
License server returns "Unknown Host" error (Linux and Windows)
Vendor daemon can’t talk to lmadmin (Linux)
Some users may encounter the error, Cannot connect to license server system, -15.xxx (Operation now in Progress). There are two possible approaches to resolving this problem.
Solution 1
As this error is usually caused by a DNS or hosts file issue, you should first verify that your IP address is correctly mapped to your hostname in the /etc/hosts file on your machine. Also ensure that the host name in the /etc/hosts file is the exact hostname in the license.dat file.
To find the correct hostname and IP address for your machine, do the following:
1.
In a terminal window, enter the command, hostname followed by <Return>
2.
Using the returned value, enter the command, ping <hostname> followed by <Return>
This should return information of the form:
PING hostname.company.com (IP_ADDRESS)
The IP_ADDRESS returned above should be the correct IP address for your system. If the error, unknown host <hostname>, is returned, it will be necessary to check the contents of your hosts file. To do this, change directory to /etc and open the hosts file. It should contain at least the following lines:
127.0.0.1 localhost
IP_ADDRESS hostname.domainname hostname
If this is not the case, add these lines (with the assistance of your Systems Administrator) and save the file. You should then open a new terminal window and try launching STAR-CCM+ again.
To verify the IP address, enter
/sbin/ifconfig -a
or
nslookup hostname
and verify that the return value is the same as that contained in the /etc/hosts file.
Solution 2
Another approach is to comment out or delete all IPV6 information in the /etc/hosts file and restart the network services. In the following file, for example, the lines containing ipv6 could be commented out by inserting # at the start of each line.

# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback

fe00::0 ipv6-localnet

ff00::0 ipv6-mcastprefix
ff02::1 ipv6-allnodes
ff02::2 ipv6-allrouters
ff02::3 ipv6-allhosts
License server checks for licenses before the network is configured (Windows)
It is possible that you may encounter FlexNet error -97 when starting your Windows machines. This error occurs when the license server attempts to check a license before the network on the machine has completed the configuration.
A value is added to the registry when the STAR-CCM+ installers installs the license server. This value can add a delay before the license server checks for licenses, giving the machine time to configure the network. By default this value is set to 0 seconds (no delay).
To resolve the above issue, introduce a delay of 15 seconds:
1.
Click Start and type regedit in the search field.
2.
Select regedit.exe from the search results.
The Registry Editor dialog appears.
3.
Navigate to HKEY_LOCAL_MACHINE > SOFTWARE > Wow6432Node > FNPlm > License Server > [Your_CD-adapco_Lic_Server].
4.
Right-click delay and select Modify...
The Edit DWORD (32-bit) Value dialog appears.
5.
Set Base to Decimal.
6.
Set Value data to 15.
7.
License server returns "Unknown Host" error (Linux and Windows)
You may encounter the Unknown Host: <hostname> error.
Typically, this error appears when the host name that is specified in the SERVER line of the license file does not match the host name of the license server. If you have a static IP address, you may still get this error even if the host name of your machine does match that specified in the license file.
To resolve this issue, manually add the IP address and host name to the hosts file:
1.
Open the hosts file in a text editor of your choice.
a.
/etc/hosts
b.
%SystemRoot%\system32\drivers\etc\hosts
The contents of the file should contain something like:
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
2.
192.168.148.134 linuxbox.london.company-name.com
3.
Getting Support
When you need assistance with using STAR-CCM+ , you can first check the CD-adapco support site, The Steve Portal. This site lets you search information and open a support case. Access The Steve Portal at:
*
*
Alternatively, select Help > Steve Portal.
Choose from among the following features on this site:
*
*
*
*
The Steve Portal can guide you through the process of opening a support case. In addition, it can suggest possible solutions that are based on the details of your case, and help you to track the progress of the case through to resolution.
The screenshot below shows the Home page of The Steve Portal. To switch between different areas of the site, use the tabs on the top-level navigation menu.
If the Knowledge Base does not provide the help that you need, contact your local CD-adapco support office. Contact information can be found at http://www.cd-adapco.com/offices.
To help your CD-adapco representative, please prepare appropriately for reporting the issue. Refer to Gathering Information on the Issue for more information.
Contents  
Gathering Information on the Issue
Gathering Information on the Issue
Accurate information is vital for dealing with your issue effectively. Your affected simulation file, if you can provide it, would be a key source of this information. However, due to the large size of the file, the best way to send it is using FTP (file transfer protocol). Discuss the details of this file transfer with your local CD-adapco support contact.
In addition, there are three ways to obtain information, depending on the issue:
*
*
*
Copying Data from the Workspace
Error messages in STAR-CCM+ commonly appear in an exception dialog, which contains extensive information. To access this information, click the Show Details button.
The details appear in the dialog. Highlight the information with your cursor and, when you have reached the end of the text, copy it to the clipboard and paste it into an e-mail message.
In some cases, the error message also appears in the Output window, where you can also highlight and copy information.
Alternatively, you can use the pop-up menu of the Output window to save the full content as a text file.
Getting an External Data File
Various errors cause STAR-CCM+ to generate separate reports. You should send these reports to CD-adapco support along with your query. The details they contain can help resolve your issue much sooner.
The most common external source of information on STAR-CCM+ errors is the messages.log file.
This file can be found in the following locations:
*
On Linux: ~/.star-X.XX.XXX/var/log/messages.log, where ~ is your home directory and X.XX.XXX is the version of STAR-CCM+ , for example 7.04.006
*
On Windows: C:\Users\username\AppData\Local\CD-adapco\STAR-CCM+ X.XX.XXX\var\log\
The file also contains prior error messages, so you may want to delete the earlier material for brevity.
Some errors are known as Java HotSpot errors because they are related to the Java functionality. As a result, a special log file may be generated called hs_err_pidXXXX.log, where XXXX is the process ID.
Look for the report in your main directory:
*
Your home directory on Linux
*
Unlike messages.log, this type of report is generated one time due to a single error. Therefore all of its information pertains to that event.
Retrieving Graphics Driver Information
Some issues may originate with your graphics driver. You may want to get detailed information about that driver and send it to CD-adapco support. At a minimum you should provide the driver version, card model, and operating system.
The technique for obtaining this information depends on your operating system:
*
% glxinfo
This results in detailed output, which you can either paste in the body of your e-mail message or save as a separate text file.
*
*
Alternatively on Windows, right-click the Desktop icon in the object tree of Windows Explorer and select Properties. In the separate dialog that appears, click Display Settings in the list of options under the Personalize appearance and sounds heading. In the separate Display Settings dialog, click the Advanced Settings... button. This activates another dialog with tabs that provide detailed information on the graphics hardware and drivers.
Finding Additional Information
The original download includes this installation guide and the release notes (new features, known issues, and requirements) for STAR-CCM+ and the CAD Clients. The html version of those files is located in the STAR-CCM+_CadSeries11.06.### sub-directory where you unpacked the downloaded zip file (Windows) or tarball (Linux).
Glossary
This section describes some of the terminology that may be unfamiliar to new users of STAR-CCM+ .
*
Path: a path is the name generally used to identify the location of a directory or file in a file system. Some examples of paths are as follows:
C:\Program Files\CD-adapco\STAR-CCM+9.02.005\star\bin\starccm+.exe: this is the full path to the STAR-CCM+ executable. If this path is entered into a command prompt window, STAR-CCM+ will launch.
C:\Workarea\My Simulations\tutorials: this path could represent the directory used to save STAR-CCM+ tutorial simulations.
/usr/local/CD-adapco/starccm+9.02.005/star/bin/starccm+: this is the full path to the STAR-CCM+ executable. If this path is entered into a command prompt window, STAR-CCM+ will launch.
/usr/atilla3/mysims/tutorials: this path could represent the directory used to save STAR-CCM+ tutorial simulations.
*
System path: the system path is a collection of paths that point to those directories (or folders) that contain program executables.
*
Executable: a file that contains program instructions, as opposed to a file that contains only data. Entering the path to an executable file into a command prompt window, and pressing <Return>, will cause the computer to run the program instructions contained within the file.