2.3. Post-Installation Instructions

After you have installed the ANSYS License Manager, you may want to complete some post-installation steps in order to optimize the performance of the ANSYS License Manager at your site.

We recommend that you set your license manager to boot at system startup. Other optional post-installation tasks are included here. You will only need to configure your license server machine and configure your client machines if those steps were not completed during the product or license server installation processes.

2.3.1. Start the ANSYS License Manager at System Boot Time

On Windows systems, the license manager is set to start up automatically at system reboot. On Linux machines, you can set the license manager to start automatically at system boot time. This task is optional but is recommended and should be done regardless of which type of license server configuration you use.

Table 2.2: License Manager Automatic Startup Instructions details the steps that must be performed on each license server to start the license manager automatically when the Linux system is rebooted. Substitute your platform name (see Supported Hardware Platforms) wherever you see <platform>.


Note:  The procedure described in this section starts the license manager at boot time as root. It is not essential that the license manager be started by the root user; it may be run by a non-privileged user, depending on your preference. If you do not want the license manager to be started by root, modify LMUSER in the init_ansysli boot script to include the user name you want to use at boot time.


Table 2.2:  License Manager Automatic Startup Instructions

PlatformInstructions
Linux: Red HatRemove existing license manager startup information. Edit the file /etc/rc.d/rc.local.

Issue the new license manager startup instructions:

cp /ansys_inc/shared_files/licensing/init_ansysli /etc/init.d 
chmod 555 /etc/init.d/init_ansysli 
chkconfig --add init_ansysli 
chkconfig init_ansysli on
Linux: SuSERemove existing license manager startup information. Edit the file /etc/rc.d/boot.local.

Issue the new license manager startup instructions:

cp /ansys_inc/shared_files/licensing/init_ansysli /etc/init.d 
chmod 555 /etc/init.d/init_ansysli 
chkconfig --add init_ansysli 
chkconfig init_ansysli on
CentOS-7Remove existing license manager startup information. Edit the file /etc/rc.d/rc.local.

Issue the new license manager startup instructions:

cp /ansys_inc/shared_files/licensing/init_ansysli /etc/init.d 
chmod 555 /etc/init.d/init_ansysli 
chkconfig --add init_ansysli 
chkconfig init_ansysli on

Once the procedure is in place for starting the license manager automatically at boot time, reboot the system to verify that the automatic boot procedure is working correctly.

When the system comes back up, check to see that the license manager is running by typing the appropriate ps command and looking for ansyslmd and ansysli_server in the resulting display under the column labeled COMMAND. For example:

ps -ef|grep ansysli; ps -ef|grep ansyslmd

Next, check the license.log and the ansysli_server.log files in the licensing directory for error messages. These files contains a history of ANSYS product activity across the network when this computer is chosen as the master license server by the licensing software. They also contain start-up messages and possibly error messages.

Removing the Automatic Startup Information

If you remove the license manager server installation from a machine and need to remove this capability, follow the instructions below.

Table 2.3:  Removing License Manager Automatic Startup Instructions

PlatformInstructions
LinuxIssue the following commands:
/etc/init.d/init_ansysli stop
chkconfig --del init_ansysli
rm /etc/init.d/init_ansysli

2.3.2. Starting the ANSYS Licensing Tomcat Server at System Boot Time

You can set Tomcat to start automatically at system boot time on Linux machines. This task is optional but is recommended and should be done regardless of which type of license server configuration you use. The License Management Center runs using the Tomcat web server.  You can set Tomcat to start automatically at system boot on Linux machines.  This task is required to be able to run the License Management Center.

Table 2.4: Tomcat Automatic Startup Instructions details the steps for each Linux hardware platform that must be performed on each license server to start Tomcat automatically when the system is rebooted.


Note:  The procedure described in this section starts Tomcat at boot time as root. It is not essential that Tomcat be started by the root user; it may be run by a non-privileged user, depending on your preference. If you do not want Tomcat to be started by root, modify the LMUSER value in the init_ansyslm_tomcat boot script to include the user login name you want to use at boot time. This user must have read/write access to all files contained in the following directories:

<Install Directory>/shared_files/licensing/tools/tomcat/conf

<Install Directory>/shared_files/licensing/tools/tomcat/logs

<Install Directory>/shared_files/licensing/tools/tomcat/bin


Table 2.4:  Tomcat Automatic Startup Instructions

PlatformInstructions
Linux: Red Hat, SuSE and CentOS

Issue the Tomcat startup instructions:

cp /ansys_inc/shared_files/licensing/init_ansyslm_tomcat /etc/init.d 
chmod 555 /etc/init.d/init_ansyslm_tomcat 
chkconfig --add init_ansyslm_tomcat 
chkconfig init_ansyslm_tomcat on

Once the procedure is in place for starting Tomcat automatically at boot time, reboot the system to verify that the automatic boot procedure is working correctly.

When the system comes back up, check to see that Tomcat is running by typing the appropriate ps command and looking for init_ansyslm_tomcat in the resulting display under the column labeled COMMAND. For example:

ps -ef|grep tomcat

Removing the Tomcat Automatic Startup Information

If you remove the license manager server installation from a machine and need to remove Tomcat Automatic Startup capability, follow the instructions below.

Table 2.5:  Removing Tomcat Automatic Startup Instructions

PlatformInstructions
Linux: Red Hat, SuSE and CentOSIssue the following commands:
/etc/init.d/init_ansyslm_tomcat stop
chkconfig --del init_ansyslm_tomcat
rm /etc/init.d/init_ansyslm_tomcat

2.3.3. Modifying the Tomcat Port Number


Note:  The following procedure can only be used with a default Tomcat installation. This procedure cannot be used when Tomcat is installed as part of the secure connection option. For more information, see, Enabling Secure Connections to the Web Server (Optional).


By default, the ANSYS License Manager installation sets the Tomcat port number to 1084. To manually change this value, you must modify the server.xml file located in the following directory:

Windows:

<install_dir>\Shared Files\Licensing\tools\tomcat\conf

Linux:

/ansys_inc/shared_files/licensing/tools/tomcat/conf

To change the Tomcat port number:

  1. Open the server.xml file.

  2. Locate the line that starts with

    <Connector port="1084" protocol="HTTP/1.1"

  3. Change the port number from 1084 to your desired number.

  4. If Tomcat is already running, the new port value will not be used until Tomcat is restarted. This can be done in the following manner:

    Windows:

    Open the Windows Services applet and stop and restart the ANSYS Licensing Tomcat service (ANSYSLicensingTomcat). The Windows Services applet can be started by issuing the command services.msc from an administrator command prompt window.

    Linux:

    1. Stop the Tomcat server process by executing the stop_lmcenter script.

    2. Start the Tomcat server process with the new port number by executing the start_lmcenter script.

      These scripts can be found in the following directory:

      /ansys_inc/shared_files/licensing


      Note:  Starting the Tomcat server process will also open ANSYS License Management Center.


2.3.4. Configuring the License Server Machine(s)

If you did not complete the configuration tasks when you installed the license manager on your license server machines, you should complete the steps below to register your license server information.

  1. If you do not have a license file, follow these steps:

    1. Open the ANSYS License Management Center. For Windows, click Start>All Programs>ANSYS, Inc. License Manager>ANSYS License Management Center and for Linux run the /shared_files/licensing/start_lmcenter script.

    2. Click the Get System Hostid Information option to display your system ID code(s).

    3. Select the system ID you wish to use and click SAVE TO FILE.

      A text file containing your system ID information is created.

    4. Forward this text file to your ANSYS sales representative so that a license file can be created for you.

  2. Add your license file(s)

    Add your license files though the ANSYS License Management Center. For these steps, see Adding a License.

    If you are running in a three-server environment, the license file must reside on all three servers and must match on all three servers. Therefore, install the same license file on each machine.

2.3.5. Modify License Manager Startup Options

This ANSLIC_ADMIN utility option (Set Site Preferences>Modify Startup Options) writes an ansyslmd.ini file in the licensing directory. This file contains any changes to the default values as well as your license server specifications and other settings (such as log file locations). Use this ANSLIC_ADMIN utility option to change the default values.

For a detailed description of the settings that you can change with this option, see Modify Startup Options.

2.3.6. Create a Group (Linux Only)

You may want to create a group of users with specific usage capabilities, such as users with licensing administrative privileges, or users who are authorized to shut down the license manager. An lmadmin group is the most common type of group.

To specify a list of users with access to licensing administrative options, you need to create an lmadmin group on computers from which license administration will be performed. If you create an lmadmin group, you must include root in order for root to continue to have access to these functions. For more details on using an lmadmin group, see the FlexNet License Administration Guide (accessible from the ANSYS License Management Center). This option is available for Linux platforms only.

Follow the instructions below for your hardware platform to create an lmadmin group.

Linux Add a line to the file /etc/group as follows:

lmadmin:*:nn:root,user1,user2,user3...usern

where nn represents any unique group number and user1, user2, user3, ..., usern represent a list of n users in the group.

2.3.6.1. Defining Group Restrictions for the Licensing Interconnect

On Linux machines only, you can also specify who can shut down the ANSYS License Manager by using the ANSLIC_ADMIN utility's Modify Startup Options. By default, anyone can stop the license manager. You can restrict shutdown capabilities to only the user who started it, or to a group, such as lmadmin. If you choose group, you will need to specify the name of the group. Note that the user who started the license manager will still be able to shut it down, even if he is not part of a group with shutdown capabilities.

If you specify a group restriction, any users in that group who want to perform that operation must have the specified group as their primary group. For example, adding the following restriction:

RESTRICT_SHUTDOWN=GROUP:lmadmin

restricts the ability to shut down the license manager to only members of the lmadmin group. Any user who is a member of the lmadmin group and wants to shut down the license manager must have lmadmin as his primary group:

machineabc{user1}: groups
other testing dev1 lmadmin

In the above example, user1 is a member of the groups other, testing, dev1, and lmadmin, where other is the primary group and testing, dev1, and lmadmin are secondary groups.

To change a group from a secondary to a primary group, issue the newgrp (or equivalent) command:

machineabc{user1}: newgrp lmadmin

In this example, user1 now has lmadmin as his primary group and will be able to shut down the license manager:

machineabc{user1}: groups
lmadmin other testing dev1

2.3.7. Specify User Privileges

Establish user privileges by editing the FlexNet Options file. The options file allows you, the license administrator, to control various operating parameters of FlexNet:

  • Allow or deny the use of features based on user, hostname, display name, group, etc.

  • Reserve licenses based on user, hostname, display name, group, etc.

  • Control the amount of information logged about license usage.

By using the options file, you can be as secure or as open with licenses as you like.

The default location of the options file, ansyslmd.opt, is in the license_files directory. If you have a three-server system, the options file must match exactly on all three servers.

If you are using an options file, you must specify the pathname to the file on the VENDOR line in the license file, unless it uses the default name, ansyslmd.opt, and resides in the same directory as the license file. On Linux systems, the VENDOR line would look like this for an options file named my.opt:

VENDOR ansyslmd options=/ansys_inc/shared_files/licensing/license_files/my.opt

On Windows systems, if the path has spaces in it, you must enclose it in quotes:

VENDOR ansyslmd options="c:\Program Files\ANSYS Inc\Shared Files\Licensing\license_files\my.opt"

2.3.8. Specifying the License Server and License Files

ANSYS products need to be able to locate and communicate with the license server for your ANSYS, Inc. products to run correctly. The license server and license files should be specified correctly during the product and license manager installations. Use the Specify the License Server Machine option of the Client ANSLIC_ADMIN utility only if you need to change the settings already specified.

The Specify the License Server Machine option of the ANSLIC_ADMIN utility creates a file named ansyslmd.ini in the licensing directory. The ansyslmd.ini file contains your license server specification. For more information on specifying the license server, see Specify the License Server Machine in License Administration Using ANSLIC_ADMIN.

On Windows server machines, use the Server ANSLIC_ADMIN utility (accessed via Start> All Programs> ANSYS, Inc. License Manager> Server ANSLIC_ADMIN Utility) to modify the ansyslmd.ini file. On client machines, use the Client ANSLIC_ADMIN utility (accessed via Start > All Programs > ANSYS 18.2>ANSYS Client Licensing > Client ANSLIC_ADMIN Utility 18.2). If you have both the server and the client ANSLIC_ADMIN utilities on the same system, use the Client ANSLIC_ADMIN to specify machine-specific (local) settings.

If you want to set your license paths to have a particular license server machine for your use only (not used by others who are running ANSYS products on this machine), you can do so by setting the ANSYSLI_SERVERS and/or ANSYSLMD_LICENSE_FILE environment variables. Use the ANSYSLI_SERVERS environment variable to specify the Licensing Interconnect port number. Use the ANSYSLMD_LICENSE_FILE to specify the FlexNet port number.

If the ANSYSLMD_LICENSE_FILE environment variable is set but the ANSYSLI_SERVERS environment variable is not set, the same server machines will be used to specify the Licensing Interconnect but the port number will be replaced by the Licensing Interconnect default port of 2325. When both variables are set, ANSYSLMD_LICENSE_FILE explicitly defines the FlexNet servers while ANSYSLI_SERVERS explicitly defines the Licensing Interconnect servers.

2.3.9. Specifying Firewall Settings

If you use a firewall at your site and if you run ANSYS products outside the firewall but access the license server within the firewall, you will need to add the Licensing Interconnect and FlexNet port numbers to the exceptions list, as well as the PORT designated on the VENDOR line of the license file. By default, these port numbers are:

Licensing Interconnect: 2325
FlexNet: 1055
PORT designated by PORT=#### on the VENDOR LINE in the ansyslmd.lic file (see VENDOR Lines for information on this PORT number)

2.3.10. Setting Up Redundant (Triad) Servers

Redundant server setup is a network configuration where multiple machines are designated as license servers. Redundancy can be achieved by running any number of license server machines independently, or by running three different machines to work in tandem. We recommend using multiple independent license server machines to achieve redundancy; however, if your site requires the use of three license server machines working in tandem, follow the guidelines in this section to configure the servers.

  1. Install the License Manager on each of the three servers as described in Installing the License Manager. Be sure that each machine meets all of the prerequisites.

  2. Start each of the license servers using the same license file on each machine. The license file for the three-server setup will begin with three SERVER lines:

    SERVER myserver1 00e2463 1055
    SERVER myserver2 00132460b724 1055
    SERVER myserver3 001a246d4e64 1055

    The first SERVER line is the license server you have designated as the primary server followed by the second and third servers, which act as the backup servers.

  3. Always start the primary server first. If not, the second or third server will take over as the master server.

    When you start each license server, you will see a message indicating that the server is starting. The primary server will not be fully started until you start the second or third server, creating a quorum. Until you have a quorum of servers started, the ANSYS License Management Center will show the Licensing Interconnect and monitor running while FlexNet will show as not running. You could see a delay of up to five minutes in the startup of a server's FlexNet component while the communication between all three servers is being established. If a connection cannot be established within the five minutes, the Licensing Interconnect and Licensing Interconnect Monitor will stop. Check the ANSYS License Management Center to verify that all components have stopped before you attempt to restart the ANSYS License Manager on any server.

To stop redundant servers, use the Stop the ANSYS, Inc. License Manager option of the ANSYS License Management Center to manually stop the License Manager on each server. The Stop the ANSYS, Inc. License Manager option stops only the "local" instance of the License Manager, therefore it is necessary for you to stop each instance individually.


Caution:  If you have a three-license server network, we do not recommend that you load ANSYS, Inc. products on a single file server; doing so eliminates the inherent safety of a redundant setup.



Release 18.2 - © ANSYS, Inc. All rights reserved.