Editing the license file

The initial license file is created during the (manual) install of the SLM Server.

Some of the data fields in the License file have an <editState> attribute that can adopt the these values:

Active
Add
Change
Delete

The active fields must contain the values that are valid in the current configuration. The fields that are labeled as add, change, or delete contain modifications that Infor Validation must approve before the modifications are implemented. To achieve implementation, you must submit a new activation key that is generated by Infor Validation to the master SLM server.

The first element in the License file is the <common> element. That element contains general information, such as the activation key, customer data, host data, and several options. In addition to the options, all of this data is mandatory.

A <common> element example:

<common>
  <activation key="" frozen="No"/>

<!-- the frozen attribute is not yet used -->

  <customer
    name="Customer name"
    code=""	     	# leave empty for now, provided by Infor
    number=""		# leave empty for now, provided by Infor
    editState="add"
    />
  <option
    HAS="No" 			# High availaibility support
    confirmTime="900" # leave the default
 clusterName=”SLMCluster” # any logical name you like
 clusterId=”<number>”    # this is a unique cluster id, 
									DO NOT CHANGE!
 clientUpdate=”Yes” 		#clients automatically sync’d
    editState="add"
    />

  <host
    name="blue"	# DNS name of the SLM Server
    id="59145922" 	# slmid of that server	
    port="6005"		# port it’s listening on
    editState="add"
    />  
<host		# a maximum of 4 SLM Servers in one cluster
    name="red"
    id="185574564"
    port="6007"
    editState="add"
    />
</common>

Because the fields are all new and must all receive the property editState="add".

The file must contain the license data of all the Infor products you can use. Dependent on the license agreement, you must specify these elements:

User license
Concurrent license
Server/Instance license

For the user license and the server license, you must indicate the number of licenses for each product.

A <userLicense> element example:

<userLicense>
  <product
    id="6017"
    name="OpenWorld Studio">
    <license
      lightUsers="0"
      heavyUsers="4"
      startDate="2004-03-01"
      endDate="2005-02-27"
      editState="add"
      />
    </product>
</userLicense>

Finally, each license file must contain a version number for the license deal.

<license layout="3" version="1">
   …
</license>

This version number is used to keep track of all the changes on the license file, and is additionally used as an implicit locking mechanism. Each time a data file is saved to the server, the version number is incremented. The server is locked for all files with a version number that differs from the current version number plus one.

Note: Because of this locking mechanism, there must be one single point of maintenance. If more than one person modifies the license data from various points, and if one person submits changes to the server, the server locks everyone except the person who made the modification.

If the license file is complete, you must submit the file to the server. If the server accepts the file, the file is stored on the server in the directory SLMHOME/license/<version>/<server port>/license.xml.

Submit the license file to the SLM server. Run this command in which LicenseFile.xml is the name of your license file:

SlmCmd -newlic YourOwnEditedLicenseFile.xml

Note: If you change in the XML files on the server the values of the active fields by hand, the activation key is no longer valid. The SLM engine becomes unavailable. If you adjust the files with the SLM Management UI, you can reach the active fields. The properties you modify receive the Change, Add, or Delete status. These changes do not become active until a new activation key is submitted.

The content of the XML files is case sensitive. Notice that the mandatory activation key field and the mandatory customer fields are left open, because the values are yet unknown. You will receive them with your final activation key from Infor Validation.