Installation
Attune is easy to install. There are two components: the license server (Sentinel RMS) and Attune itself.
You can download Sentinel RMS and Attune at www.ata-e.com/software/ata-software.
Sentinel RMS Installation
Sentinel RMS is a robust, commercial client-server-based licensing system from SafeNet that can serve multiple licenses for multiple software products simultaneously. The server typically resides on a central computer. The client software such as Attune will reside on computers that will be utilizing the software. The client computer may or may not be the same as the license server. It can also be on a different software platform than the client.
Sentinel RMS installation is straightforward. Detailed installation instructions are shipped with the Sentinel RMS package available from ATA’s website. This section highlights the basics of the installation process.
Installing Sentinel RMS
On Windows the Sentinel RMS package is an InstallShield application. As such, it must be installed by someone with administrator privileges. ATA recommends that the default selections be used during the installation.
On Unix/Linux the Sentinel RMS package is a gzipped tar file. Extracting this file will create an ata_rms directory with several files. Sentinel RMS does not need to be installed as root, but root privileges are needed to run the server. The Sentinel RMS documentation provides details about the setup process.
Environment Variables
All Sentinel RMS clients need a way to determine where the server is running. By default, the client will scan the subnet that your client system is connected to and will identify any Sentinel RMS servers running on your subnet. It will then contact each until the license request is satisfied or it has run out of servers. You can control the order in which the servers are contacted through an environment variable called LSHOST. Set the environment variable to the hostname of the server, separated by a tilde (~). The server name must be prepended by the name “no-net”. For example, set it to
no-net~server
where “server” is the name of the license server.
If you only have one server and wish to bypass the network scan by the client, you can use the environment variable LSFORCEHOST. This is also required if your license server is on a different subnet from the Attune client computer. ATA recommends using LSFORCEHOST if possible, as it speeds up the initial license checkout. You can only specify a single server with this environment variable. For example, you can set it to
server
By default, the license server and client communicate on port 5093. If your Sentinel RMS server is running on a non-default port, you can configure the client to communicate on this port by setting the LSPORT environment variable to the port number to use.
On Windows, the environment variable can be set in Control Panel, typically in System. On Unix/Linux, you can set the environment variable with setenv or by using export, depending on your shell. Please ask your system administrator or refer to your operating system documentation for more details on how to set environment variables.
Checking Your License Status
You can use the WlmAdmin application included in the top-level IMAT directory to check the status of the licenses. When the GUI opens, open Subnet Servers in the tree on the left. Under each license server, the individual licenses will be listed. Clicking on a license will display statistics about that license, including who is using it and how many are available.
Adding Or Updating Your License File
For a complete set of instructions on adding or updating your license fileperforming this task, please refer to the Sentinel RMS user guide. The instructions here simply demonstrate the basic process.
From Windows, open the RMS License Administration application (WlmAdmin) located in the IMAT installation. It is located in Start | Programs | ATA Engineering | Sentinel RMS Licensing | RMS License Administration. Once the application starts, install the license by right-clicking on the appropriate license server and following the menus as shown in the figure below. The license will be immediately available.
On Linux/Unix, your system administrator can install the license file by adding the license text to the lservrc file in the license server installation directory.
Attune Installation
There are two different versions of Attune, both with their own installers. There is the version that requires MATLAB, and a new standalone version that just requires the MATLAB Compiler Runtime files. Below are the instructions for installing either version.
Matlab Version
Using the Attune Installer to Install Attune for MATLAB
Starting with Attune v1.2.0, Attune can be installed with a standalone installer. This installer prompts for an installation directory and automatically installs Attune into that location. At the end of the installation, the installer will automatically add Attune to the MATLABPATH. Any other instances of Attune that are in this file will be commented out. For reference, the MATLABPATH is stored in /toolbox/local/pathdef.m in the MATLAB root directory. A back-up copy of the path file will be made with the *.bak extension after the change is complete.
You can opt out of this and manually add Attune to your MATLABPATH by unchecking the “Add Attune to MATLAB’s Path” option at the end of the installation. Instructions for manually adding Attune to your path are included below.
If you install Attune into MATLAB’s toolbox directory and you are using the toolbox path cache, you will need to update it. You can do this in MATLAB in File, Preferences. Under the General section at the top of the form, there is a section titled, “Toolbox path caching.” Simply click on the button that says, “Update Toolbox Path Cache.” Alternately, you can also disable the toolbox path cache by unchecking the box labeled, “Enable toolbox path cache.”
It is recommended to avoid installing Attune on a network drive. The VTK initialization at Attune startup requires enough I/O that it will significantly increase the startup time if it has to occur over a network connection.
Attune does not support running from Matlab Online.
Manually Putting Attune in Your Path (setting your MATLABPATH)
To use Attune, you must arrange for the Attune directory to be in your MATLAB search path. This can be done by an individual user, or it can be set up by the system administrator for all MATLAB users. Two methods for setting up the path are given below, and experienced MATLAB users will know of other ways. (In the following instructions, %MATLAB% refers to your top-level MATLAB directory, and %ATTUNE_INSTL% refers to your top-level directory where Attune is installed.)
Option 1 (does not require sysadmin)
Create a file called startup.m (or edit an existing one). Put the following command in this file:
addpath %ATTUNE_INSTL% -end
(but use the actual path in place of %ATTUNE_INSTL%). This will add Attune to the end of your MATLAB path.
Option 2 (requires sysadmin)
Edit the file %MATLAB%\toolbox\local\matlabrc.m and insert the following command in this file (after the default path is set):
addpath %ATTUNE_INSTL% -end
(but use the actual path in place of %ATTUNE_INSTL%). This will add Attune to the end of the MATLAB path for all users. This change will need to be repeated if you update or reinstall MATLAB.
Option 3 (recommended; requires sysadmin)
Edit the file %MATLAB%\toolbox\local\pathdef.m and insert a line for the Attune directory. The new file will look something like this:
function p = pathdef
<lines omitted...>
% PATH DEFINED HERE -- Don't change this line.
p = [...
'$toolbox\matlab\general:',
<lines omitted...>
'$toolbox\matlab\demos:',...
'$toolbox\local:',...
'$toolbox\tour',...
'%ATTUNE_INSTL%:',...
...
];
p = [userpath,p];
Use the actual path name (e.g., C:\matlab\toolbox) for %ATTUNE_INSTL%.
NOTE: A disadvantage of this method is that any MATLAB upgrade or new installation will overwrite this file, so the change will need to be repeated.
Configuring the Java Paths
Attune uses Java for its implementation of the Visualization Toolkit (VTK). The VTK functionality uses two JAR files, vtk.jar and femplotclass.jar. All of these JAR files must be in MATLAB’s Java classpath (classpath.txt; see javaclasspath in MATLAB). If the JAR files are not on the Java classpath, Attune will attempt to add them to the dynamic path at runtime. For better performance, the JAR files should be on the static classpath. See below for instructions on how to add these JAR files to MATLAB’s static Javaclasspath.
In addition, VTK requires that the shared object files that it uses be located on the Java JNI library path (librarypath.txt). This path cannot be added dynamically at runtime; it must be configured in librarypath.txt prior to starting MATLAB.
On Windows, the installer will automatically update the classpath.txt and librarypath.txt files in the MATLAB installation, so no further action is required.
On Linux and Mac, you will need to manually modify the librarypath.txt file. If you modify your MATLAB installation after installing Attune, MATLAB will overwrite the classpath.txt file, and you will need to modify it manually. If you do not have administrator permissions to your MATLAB installation, you can place local copies of classpath.txt and librarypath.txt into your MATLAB startup directory. Please note that starting in MATLAB 2012b (8.0), the local Java classpath files must be named javaclasspath.txt and javalibrarypath.txt.
To add the JAR files to the Java static classpath, add these lines to the bottom of classpath.txt, if you are editing the file located in the MATLAB installation. If you are creating a local file in your MATLAB startup directory, it only needs to contain these lines. You need to replace %ATTUNE_INSTL% with the actual path to your Attune installation, and %PLATFORM% to the actual platform directory. You can verify the correct %PLATFORM% to use by navigating your Attune installation directory to see what is installed.
%ATTUNE_INSTL%\imat\vtklib\%PLATFORM%\vtk.jar
%ATTUNE_INSTL%\imat\vtklib\%PLATFORM%\femplotClass.jar
To add the shared object directory to the Java static JNI library classpath, add this line to the bottom of librarypath.txt.
%ATTUNE_INSTL%\imat\vtklib\%PLATFORM%\
Standalone Version
Starting with Attune v2.0.2, a version of Attune can be installed which does not require MATLAB. Like the MATLAB version, this version is also installed with a standalone installer. The installer prompts for an installation directory and automatically installs Attune into that location. Attune can then be launched by selecting the Attune icon from the Start Menu.
This version requires that the MATLAB Compiler Runtime (MCR) be installed. The installer for these files is available from the ATA website (www.ata-e.com).