i
This document refers to an older version. GeneXus 16 is our latest version; check the latest one here.

How to configure GXflow running in Linux using licenses from a Windows server

Official Content
This documentation is valid for:

Note: See HowTo: Configuring Protection for GXflow Installed on Linux, AIX and OS400 if the licenses need to be installed on the same server as the application.

To configure a GXflow Application running in Linux to use the protection system from a Windows server, follow these steps:

Step 1 – Install GeneXus Protection Server

Install the latest GeneXus Protection Server version on a Windows Server. This server will centralize GeneXus licenses products.

Step 2 – Configure the GeneXus License Manager

Download the files from here.
On the Linux server where the application is running install the GeneXus License Manager. You need to unzip the LinuxCSProt.zip file (located in Packages\Gxpm\Protection\Linux under GeneXus installation folder) into a directory, for example, gxprot. The License Manager must be configured via command line options; check Annex I for further detail on License Manager Options. The location for the Protection server is stored in a file called protect.properties (same as Protect.ini in Windows environments); which is used by the Web application and License Manager to locate the Protection Server.

To set the Protection Server location, execute the following:

java -Dgxprotect.dir=/gxprot/license –jar licmgr.jar -s server.host=localhost user.domain=localhost user.id=test user.pwd=test123

where:

  • -Dgxprotect.dir: System Property to set the path where the protect.properties file will be generated.
  • server.host: IP or hostname where the GeneXus Protection server is executing.
  • user.domain: Windows domain to be used to authenticate with.
  • user.id: User to be used to authenticate with.
  • user.pwd: Password to be used to authenticate with.

You don't need to set all properties at once; you can execute the same command several times with different parameters. The specified user to access the server must have security permissions to access the server via DCOM.

Step 3 – Configure the application to use the Windows Protection Server

For the application to use the Protection Server, you need to place the JAR files contained in the LinuxCSProt.zip file in the webapp lib folder. Besides, you need to add an environment entry in the web.xml file to set the directory where the protect.properties is located.

For example:

<env-entry>
<env-entry-name>gxprotect.dir</env-entry-name>
<env-entry-value>GXProt</env-entry-value>
<env-entry-type>java.lang.String</env-entry-type>
</env-entry>

where:

  • env-entry-name: the value must be gxprotect.dir
  • env-entry-value: absolute path where the protect.properties is located; it must match the GeneXus License Manager location.
  • env-entry-type: the value is always java.lang.String

Annex I – License Manager Options

Whenever you run the License Manager you must reference a System Property as a parameter, for example:

java –Dgxprotect.dir=”gxprot” –jar licmgr.jar

It is recommended to explicitly set the directory that will be used to save the properties file. When using the license manager it is advisable to use a system property "gxprotect.dir". License Manager available options are:

protGXflowRemotaWindows