Licence Protector

Customize Configuration Files

Hide Navigation Pane

Customize Configuration Files

 Previous topic Next topic  

Customize Configuration Files

 Previous topic Next topic JavaScript is required for the print function Mail us feedback on this topic!  

The following configuration files have to be configured

 

•The web.config file
•The project.config file
•The log.config file
•One or more Project files
•One or more Automatic Licence Generator configuration files

 

The configuration for EasyGo is explained in the main documentation - Chapter Configuration of the Web Activation Server

 

Configuring Web.config

If you use the MSI installer, the configuration is done automatically and only necessary, if you want to manually change default settings.

 

This file resides in the root directory of the web application (e.g. c:\inetpub\wwwroot\lpweb\web.config)

 

The file has a lot of configuration options which should not be changed. This tutorial describes only options you could change.

 

You can

 

1.Define where the log-configuration can be found: Simply adapt the value of the key „logconfig“ to your Web Application path (e.g. c:\\inetpub\\wwwroot\\lpweb\\log). Note to use two backslashes in the path-value
 
2.Define where the configuration for the project files can be found: Simply adapt the value of the key „licprotectorwsconfig“ to your Web Application path (e.g. c:\\inetpub\\wwwroot\\lpweb). Note to use two backslashes in the path-value
 
3.The database connection string: Set the value of the key „db“ according to your database position.

 

•Set „user id“ to a user who has read and write access to your LPWAS database. The system administrator „sa“ is not a bad choice.
•Set „password“ to the password of the configured user.
•Set „data source“ to your SQL Server machine.
•Set „initial catalog“ to your LPWAS database-name. Normally that name is LPWeb.

 

A path can be specified to export data (exportpath), for reports (reportpath) and for the language file. These folders must exist and read and write permission is necessary.

 

Here is the configuration for our example. The Web Application is installed in c:\inetpub\wwwroot\lpweb, the database machine is „mysqlserver“, the database is named „LPWeb“ and the user „sa“ has the password „secret“:

 

<?xml version="1.0" encoding="utf-8" ?>

<configuration>

 

<appSettings>

         <add key="logconfig" value="C:\Inetpub\wwwroot\lpweb\log.config" />

         <add key="licprotectorwsconfig" value="C:\Inetpub\wwwroot\lpweb\project.config" />

         <add key="db" value="user id=lpweb;data source=PCname\mysqlserver;persist security info=False;initial catalog=lpweb;password=your password" />

         <add key="exportpath" value="C:\Inetpub\wwwroot\lpweb\export\"></add>

         <add key="reportpath" value="C:\Inetpub\wwwroot\lpweb\reports\"></add>

         <add key="languagefile" value="C:\Inetpub\wwwroot\lpweb\languages\languages.xml"></add>

         <add key="LPWebFrontend.net.registerserver.licenseProtector-ASP.Net-WebService" value="http://localhost/lpweb/lpws.asmx"/>

         <add key="loglevel" value="4"></add>
         <add key="WebServiceURL" value="http://localhost/lpweb/lpws.asmx"/>

 </appSettings>

 

 

<system.web>

…

 

 

Configuring LicProtectorws.config

 

 

This files replaces the formerly used project.config file in the main web folder, which is still supported for backward compatibility.

 

For each project you need a project config file in the folder \pconfig . It needs the extension .config.

 

Example

.\pconfig\easy-go.config

 

If you are using EasyGo, a sample  file can be found in the folder ..\EasyGo\Web Activation Server. Hosting customers should use the files from the folder ..\EasyGo\Web Activation Server\Files for Mirage Hosting

 

The file could look as follows. Find the detail description in the list of available parameters.

 

<Configuration>

   

<Project>

     <ProjectID>demo-easygo</ProjectID>

     <ProjectDescription>Easy Go application Version 1.3 </ProjectDescription>

      <IsSerial>QHD001</IsSerial>

     <CheckActivationKeys>yes</CheckActivationKeys>

     <StoreKey>yes</StoreKey>

     <NoOfAllowedKeyOccur>1</NoOfAllowedKeyOccur>

   

     <CheckEntries>yes</CheckEntries>

     <EntryRequired>no</EntryRequired>

     <NoOfAllowedEntryOccur>1</NoOfAllowedEntryOccur>

   

     <InstCodeType1>6</InstCodeType1>

     <InstCodeType2>1</InstCodeType2>

     <InstCodeType3>3</InstCodeType3>

 

     <AllowReactivation>Yes</AllowReactivation>

Use either

   < MinIdenticalInstcodes>3</MinIdenticalInstcodes>

or an individual definition

    <CheckInstCodeType1>1</CheckInstCodeType1>

     <CheckInstCodeType2>2</CheckInstCodeType2>

     <CheckInstCodeType3>3</CheckInstCodeType3>

     <CustomerInfoMapping>last</CustomerInfoMapping>

     <MultipleLVS>true</MultipleLVS>

     <LvsDefaultName>Default</LvsDefaultName>        

 

     <GeneratorPath>C:\Inetpub\wwwroot\lptest\lpweb\bin\alg</GeneratorPath>

     <GeneratorApp>AutoLicGenerator.exe</GeneratorApp>

     <GeneratorConfig>config-autogenerator-EasyGo.xml</GeneratorConfig>

    <TicketValidMinutes>1440</TicketValidMinutes>        

   

  </Project>

 

 

</Configuration>

 

 

 

 

You have to restart the Activation Server after making configuration changes.