pure::variants Quick Installation Guide
Version 1.9
pure::variants Installation
There are three alternative ways to install pure::variants. The first alternative is recommended for
all Microsoft Windows users who want to set up pure::variants as an stand-alone application. If
pure::variants shall be integrated into an existing Eclipse based tool chain or the operating system
platform is Linux or Mac OS X, the second and third alternative provide instructions for those
scenarios.
In case of very strict firewalls or no network access on the installation machine choose either the
first or the third alternative. Both allow downloading the installation packages and install it on a
different computer.
The installation procedures are described below. Once the initial installation has finished,
installation of a license is required to use pure::variants. See following section for more information
on license installation. In case of problems contact pure::variants Support using the e-mail address
[email protected] .
1. Install with Windows Installer (Windows Only)
The Windows Installer can be downloaded from the pure::variants product web page. Go to
http://www.pure-systems.com/pvde-update. The product download pages are protected by a
password. You need to login by using the e-mail address and the registration number from the
license file.
Download the installer package and start the installation by double click the executable and follow
the steps of the wizard. The installer will set up a fresh eclipse with pure::variants and
documentation. All pure::variants extensions available for the account are automatically included in
the Windows Installer download. However, some may not be enabled by default in Installer. Make
sure to select the desired extensions during the installation process. Later updates to the extension
selection can be done either by reinstalling pure::variants or by following the alternatives two or
three of this Quick Installation Guide.
The installer provides the following command line options:
Option
Description
/S
Run in silent mode
/ALL
Select all packages for installation
/32
Force 32bit installation also on 64bit operation system
/NODOTNET
Do not install the .NET 4 Framework
/NOINTCOMP Do not install the integration components for Java & .NET
/JAVA
Location of Java executable
/JAVA=”C:\Program Files\Java\jre6\bin\java.exe”
/D
Set installation directory
/D=C:\pure-variants
Must be the last parameter used in the command line and must not contain any
quotes, even if the path contains spaces
A video showing the installation process can be found at the pure-systems web site.
2. Install into Eclipse by using the Remote Update Site
Start the Eclipse application you want to install pure::variants in.
To install pure::variants with the Eclipse Update Manager open the menu “Help -> Install New
Software”. Add a new remote update site by pressing the “Add” button. Into the upcoming dialog
enter the following data:
Name: pure::variants Update Site
Location: http://www.pure-systems.com/pvde-update
and press “OK”. Enter the e-mail address and registration number from the license into the login
dialog. In the next step select the features to install. Please restart Eclipse after finishing the
installation.
3. Install into Eclipse from Archived Update Site
Alternatively it is possible to download archived update site files containing the current
pure::variants version. To install from an archived update site, simply download the updates site(s)
from http://www.pure-systems.com/pvde-update. Now follow the instructions given above for the
second alternative with the exception to use “Archive...” button instead of entering the location of
the update site. Select the downloaded zip file in the file selection dialog.
Installing the License
License File Installation
A valid license file is always required in order to use pure::variants. If pure::variants is started and
no license is present, then the user is prompted to supply a license. Select the “Yes” button and use
the file dialog to specify the license file delivered with pure::variants. The specified license will be
stored in the current workspace.
If you are using multiple workspaces, then the license file has to be installed in each of them.
If you have purchased a network floating license secured by an USB dongle, you can either plug it
directly into the machine running pure::variants or setup a network license server as described
below. If you have purchased multiple license stored on one USB dongle, setting up a network
license server is required to use more than one purchased license.
License Service Installation
If your installation is for use with a network floating license, a License Server running the license
service has to be setup before pure::variants can be used on multiple machines. The License Server
can be installed on any compatible machine on the network. It does require a pure::variants
installation on this machine.
Make sure that the client machines running pure::variants can reach the License Server using the
UDP port 22350.
If the client machines running pure::variants do not automatically detect the running License Server,
follow the described steps with exception of step 2 also on the client machines.
Step 1: (All) Install the CodeMeter Runtime
For the installation you will need administrator privileges.
Download the CodeMeter installer from
http://www.pure-systems.com/downloads/CodeMeterRuntime_6.10a.exe.
Start the installation by double click the “CodeMeterRuntime_6.10a.exe”. Follow the steps of the
wizard.
After the successful installation the CodeMeter icon is visible in the task bar.
Step 2: (License Server only) Enable Network License Service
The network service can be enabled with the Web Administration Interface. Right click the
CodeMeter task bar icon and select “WebAdmin”. Go to the “Configuration” tab and choose the
page “Network”. Enable the “Run Network Server” check mark.
After applying these changes restart the service.
Ensure that the Windows firewall does not block connections to UDP port 22350 from your
network to the machine running the CodeMeter license service.
Make sure that the USB dongle is plugged into the License Server at all times.
Step 3: (pure::variants Clients only) Add Server to Search List on Client
If the License server is still not automatically detected, you will need to add the CodeMeter server
to the “Server Search List” on clients if they are located into different networks. Please install the
CodeMeter Runtime also to the client machine and run the WebAdmin configuration tool. Go to the
“Configuration” tab and choose the “Network” page. Press the add button and enter the CodeMeter
servers DNS name or the IP address into the search list.
License Updates
Depending on the kind off license update you will have to update the license file stored in
pure::variants workspaces and/or the license information stored in the USB dongle.
Updating the License File
If pure::variants is not explicitly asking for a new license, the update can be forced by starting
pure::variants and opening “Window->Preferences”. Select “Variant Management->pure::variants
License” and install license using the provided “Install” button.
Updating the License Information on USB Dongle
Step 1: Create CodeMeter Context File
This step is optional and is only to be executed if requested by a pure-systems representative.
Access to a CodeMeter Context File specific to the individual USB dongle is required to provide
updates to the installed licenses.
To create a context file press the right mouse button on the Desktop and select “New -> WIBU
Control File” from the menu.
In the upcoming window select “CmStick Remote Programming Context File”, press “Create” and
“Ok”.
After successful operation the content of the stick is saved into the “MyCmStick.WibuRaC” file
which is located on the Desktop. This file has to be sent to pure-systems prior to the update.
Step 2: Installing a Remote Update File
The remote update file with updated license information is installed by double clicking on the file
with the stick inserted in the same machine. The license service must be running during update.