Looking for help?
< All Topics

LeanCOST installation (MsSQL database)

This guide describes both server-side and client-side installation for LeanCOST with database on MsSQL. It applies for LeanCOST EVO 1.0.0 or higher. For previous versions, please contact the Hyperlean support team at support@hyperlean.eu.

1. Introduction

To install LeanCOST you need to download some files from a few links: you shall check that each “.zip” file you download does not have a security block and, if it does, disable it, by applying the following procedure:

  1. Right-click on the downloaded “.zip” file
  2. Select “Properties” in the context menu

If the “.zip” file is blocked, there will be an “Unblock” option in the “General” tab. In this case:

  1. Press “Unblock” or flag “Unblock”.
  2. Press “Ok” to save the changes.

2. Server-side configuration

Server-side, there are three main topics to highlight:

  • License installation
  • Materials and data sharing among LeanCOST users
  • Set up the MsSQL database

The shared folder can be created in the same server where LeanCOST license is installed or in a different one.

2.1 License installation

First, you need to install the license manager driver by following next procedure:

  • Download “LicenseDriverInstallation_8.41.zip” from Dropbox.
  • Unzip the downloaded file. The folder “LicenseDriverInstallation_8.41”, obtained from the unzip, contains the following 4 files:
  • Run as administrator the file “InstallLicenseDriver.bat” (right-click on it, then “Run as administrator”) to install the license manager driver.
  • Check if the service Sentinel LDK License Manager is running, otherwise start it. Look for “Services” on Windows search bar to check if it’s running.

Open the “LicenseDriverInstallation_8.41” folder and:

  1. Double-click on “RUS_GEWKM.exe” to run it
  2. In the “Collect status information” tab
  3. Select “Installation of new protection key”
  4. Click on “Collect information” button

Save the related “C2V” file (fingerprint) with the name of your server.

Send the fingerprint file by email to support@hyperlean.eu.

NOTE: “C2V” files do not contain private customer information. They contain information about the license terms and data stored in deployed Sentinel protection keys. For further information, please visit the provider’s webpage.

Hyperlean will send you a “V2C” file that will activate the license.
To apply the file, run the “RUS_GEWKM.exe” then:

  • Select the “Apply License File” tab
  • Click the three points button to upload the “V2C” file received by Hyperlean
  • Click on “Open” to open it
  • Click on “Apply Update” to activate the license

Open an internet browser and browse to http://localhost:1947/int/devices.html to check if the license was installed. If it was installed correctly, you’ll see a row like the one on next picture.

2.2 Creation of a shared folder with LeanCOST material

Create a shared folder called “LeanCOST” where all LeanCOST users must have read permissions. Inside “LeanCOST” create the following subfolders:

  •  “Installer”: copy here the installation package and the registry file “AddRegistryKeys_64bit.reg”
  • “Documentation”: save here the guides sent by Hyperlean

2.3 Database creation

In this chapter we describe how to create a LeanCOST database on your SQL server.

Preliminary steps

Before you create the database, you must:

  • Select or create an instance on the MsSQL server database where to upload LeanCOST database.
  • Recover the port used for the remote connection to MsSQL server (by default it’s 1433).
  • Create a specific user with the role of db_owner of the LeanCOST database. We suggest you name the user as “leanuser”. It is not necessary that this user has ”System Administrator” rights.

Database creation

The first step to do is to restore a “.bak” file received from Hyperlean to create the “LeanCOSTDB” database.

Log-in the instance where the “LeanCOSTDB” database will be stored and right click on the “Databases” node, then select “Restore Database…” in the context menu.

The “Restore Database” window wil open: here follow the steps shown in the next picture.

Once pressed “OK” at step 6 of the previous image, the path of the file “LeanCOSTDB.bak” to restore will appear in the “Select backup devides” window: here press “OK” to go on with the restoration.

After having pressed “OK” you’ll be redirected to the “Restore database” window.
If you want to change the path where the data and log files will be savedelect “Files” in the left menu, check “Relocate all files to folder” and type the desired path in the “Data file folder” and “Log file folder” textboxes.
Make sure the paths are correct in the “Restore As” column.

Now, select “Options” in left menu and select “Overwrite the existing database (WITH REPLACE)” option and, finally, press “OK” button to start the restoration.

Once the restoration procedure has been completed, you’ll recieve this message meaning that the database was created.

The “LeanCOSTDB” will be listed under the “Databases” node.

Set the “db_owner” user

To let LeanCOST open successfully with the MsSQL database, it is necessary to check that the user created for the LeanCOST database (usually named “leanuser”) is “db_owner” of the “LeanCOSTDB” database.

Open “Security” node in the SQL instance where the LeanCOST database is stored. Open the subnode named “Logins”: here there will be the user created for LeanCOST database (suggested name = “leanuser”).
Select the user created for LeanCOST database, right click on it and select “Properties” voice in the context menu.

The “Login Properties” window will appear: select “User Mapping” on the left.
Then, select “LeanCOSTDB” database under the “User mapped to this login” table. Finally, check that “db_owner” is flagged. If it is not, select it and press “OK”.

Crypt and configure the connection string “.reg” file

Crypting operations of the string to connect to “LeanCOSTDB” database in MsSQL can be done on MsSQL server or on a client machine.

It’s required to create a crypted string to connect the “LeanCOSTDB” database. To crypt the string, download the following files:

  • “AddRegistryKeys_64bit.reg” from here
  • “LeanCostVSFConfigurationManager_X.x.x.zip” from the link Hyperlean sent you

Unzip the “LeanCostVSFConfigurationManager_X.x.x.zip” file. It contains the files shown below:

Run the “LeanCostVirtualFileSystemConfigurationManager.exe” as administrator (right-click –> “Run as administrator”) .
The window shown in next picture will open.

Type in “ServerDataStorage” a string with the following syntax:
mssql;<DBServerName>\<InstanceName>;<Port>;<DBName>;<DBUserName>;<Password>;;;;
Where:

  • <DBServerName> SQL server name where the db is stored
  • <InstanceName> instance name where the db is stored
  • <Port> port number used to connect to MsSQL, usually 1433
  • <DBName> database name, usually “LeanCOSTDB”
  • <DBUserName> username of the db_owner, usually “leanuser”
  • <Password> db_owner user password

After you typed the string, write it to your System Registry by clicking on the “Write to registry” button. Then, flag “Crypt” to crypt the string and copy it.

Open the “AddRegistryKeys_64bit.reg” file and paste the crypted string as the value of the key “ServerDataStorage” and save.

Save the customized file and copy it in “LeanCOST_X.x.x_Installer” folder.

Now you can install LeanCOST on each client machine by following the procedure described on the next chapter.

3. Client-side installation

og in to a client with a user with administrator rights.
Go to the shared folder named “LeanCOST” (located on the server) and temporarily copy the installer package on your desktop.
At the end of the installation, whether successful, you can delete it.

3.1 Enable database connection

Select the “AddRegistryKeys_64bit.reg” file and right-click on it, then select “Open” or “Merge” – depending on your OS.

This image has an empty alt attribute; its file name is image-23.png

Press “Yes” then “Ok” in the two windows that will open.

This image has an empty alt attribute; its file name is image-24.png
This image has an empty alt attribute; its file name is image-25.png

Merging this file will add the database connection string to the system registry, allowing LeanCOST to connect to its database.

3.2 Installer package

Run “Setup.exe” to install LeanCOST (by double clicking with the mouse or from command line). The LeanCOST setup process will automatically start.

This image has an empty alt attribute; its file name is image-26.png

In every machine where LeanCOST is installed for the first time, some prerequisites will be automatically installed.
Click “Accept” to accept terms of the license agreement.

This image has an empty alt attribute; its file name is image-3.png

Click “Install” to start the installation of the necessary prerequisites.

This image has an empty alt attribute; its file name is image-4.png

The installation of the prerequisites is not always necessary: if a previous release of LeanCOST had been installed on that client, they will not be installed again.

After the installation of all prerequisites, the setup wizard of LeanCOST will start. Click “Next” in the welcome window.

This image has an empty alt attribute; its file name is image-27.png

Tick “I agree” to accept EULA then click “Next”.

This image has an empty alt attribute; its file name is image-28.png

Press “Next” until the end of the procedure.

This image has an empty alt attribute; its file name is image-29.png
This image has an empty alt attribute; its file name is image-30.png
This image has an empty alt attribute; its file name is image-18.png

Click “Close” to end the installation.

This image has an empty alt attribute; its file name is image-31.png

To run LeanCOST, double-click on the desktop icon.

This image has an empty alt attribute; its file name is image-11.png

Select language, type username and password and click “Ok”.
First login can be made with the user “manager” and no password.

This image has an empty alt attribute; its file name is image-12.png

Wait for the LeanCOST interface to open.

If you run into any problems, contact support@hyperlean.eu.

Table of Contents