# Activating Features on Selected Clients

The module activation override configuration enables the activation of features on specific clients.

  1. In the module activation configuration file, add an override subobject after the value. The override node changes the active/inactive values written in the main node or submodule node depending on the architecture, operating system, or host.

    It has seven child options:

    Child Options Description
    type Accepts list as value
    arch The architecture of the client machine where the feature will be activated if set to true and deactivated if set to false
    os The operating system of the client machine where the feature will be activated if set to true and deactivated if set to false
    host The hostname of the client machine where the feature will be activated if set to true and deactivated if set to false
    exclude-arch The architecture of the client machine that will not be included in feature activation
    exclude-os The operating system of the client machine that will not be included in feature activation
    exclude-host The hostname of the client machine that will not be included in feature activation
    Module Activation Override Child Options

    The arch, os, and host follow this format:

    <arch|os|host> : <value> : <true|false>
    Example
    override
    {
        type=list
        os:.*:true
        arch:.*:false
        host:mnl.*:false
    }
    

    If the machine's os, host, or arch matches the specified regex pattern, then the active value of the main node will be set to the value configured on this override node.

    If the child options have different Boolean values, the last one to match the regex will be the active value. In the example above, the os has a regex pattern of .* and its value is set to true, while the host has pattern of mnl.* and a value of false, then the active value will still be false if the hostname starts with mnl.

    The exclude-arch, exclude-os, and exclude-host follow this format:

    <exclude-arch|exclude-os|exclude-host> : <value>
    Example
    override
    {   
        type=list
        exclude-os:win.*
        exclude-arch:.*64.*
        exclude-host:(?i)mnl.*
    }
    

    If the machine's exclude-os, exclude-host, or exclude-arch matches the specified regex pattern, then the active value of the main node will be excluded.

    For example, you want to activate DSLS Autoconfigurator on all hostnames starting with mnl, except on RHEL machines and mnl1555win:

    license_analyzer.conf
    31| dsls
    32| {
    33|     display=DSLS
    34|     description=Job for autoconfigurating DSLS License Servers.
    35|     active
    36|     {
    37|         type=bool
    38|         value=true
    39|         override
    40|         {
    41|             type=list
    42|             host:(?i)mnl.*:true     
    43|             exclude-os:rhel.*
    44|             exclude-host:mnl1555win
    45|         }
    46|     }         
    

    Another example, you want to activate FreezeMonitor on all machines with Windows 64-bit operating systems:

    license_optimizer.conf
    12|  standalone
    13|	 {
    14|		display=Optimizer Agent
    15|		description=Job to log, suspend, or terminate idle application
    16|		active
    17|		{
    18|			type=bool
    19|			value=true
    20|         override
    21|         {
    22|             type=list
    23|             os:win.*:true 
    24|             arch:64-bit:true
    25|         }
    26|		}
  2. Save the changes in the module activation configuration file.

  3. To immediately reflect the changes on the client machine, delete the dist-config folder and dist-config.[platform].tar.gz file in the temp directory, which is by default in C:\Program Files\OpeniT\Core\Log\temp. Then, follow the instructions in the Manual File Distribution to a Client section.

  1. In the module activation configuration file, add an override subobject after the value. The override node changes the active/inactive values written in the main node or submodule node depending on the architecture, operating system, or host.

    It has seven child options:

    Child Options Description
    type Accepts list as value
    arch The architecture of the client machine where the feature will be activated if set to true and deactivated if set to false
    os The operating system of the client machine where the feature will be activated if set to true and deactivated if set to false
    host The hostname of the client machine where the feature will be activated if set to true and deactivated if set to false
    exclude-arch The architecture of the client machine that will not be included in feature activation
    exclude-os The operating system of the client machine that will not be included in feature activation
    exclude-host The hostname of the client machine that will not be included in feature activation
    Module Activation Override Child Options

    The arch, os, and host follow this format:

    <arch|os|host> : <value> : <true|false>
    Example
    override
    {
        type=list
        os:.*:true
        arch:.*:false
        host:mnl.*:false
    }
    

    If the machine's os, host, or arch matches the specified regex pattern, then the active value of the main node will be set to the value configured on this override node.

    If the child options have different Boolean values, the last one to match the regex will be the active value. In the example above, the os has a regex pattern of .* and its value is set to true, while the host has pattern of mnl.* and a value of false, then the active value will still be false if the hostname starts with mnl.

    The exclude-arch, exclude-os, and exclude-host follow this format:

    <exclude-arch|exclude-os|exclude-host> : <value>
    Example
    override
    {   
        type=list
        exclude-os:win.*
        exclude-arch:.*64.*
        exclude-host:(?i)mnl.*
    }
    

    If the machine's exclude-os, exclude-host, or exclude-arch matches the specified regex pattern, then the active value of the main node will be excluded.

    For example, you want to activate DSLS Autoconfigurator on all hostnames starting with mnl, except on RHEL machines and mnl1555win:

    license_analyzer.conf
    31| dsls
    32| {
    33|     display=DSLS
    34|     description=Job for autoconfigurating DSLS License Servers.
    35|     active
    36|     {
    37|         type=bool
    38|         value=true
    39|         override
    40|         {
    41|             type=list
    42|             host:(?i)mnl.*:true     
    43|             exclude-os:rhel.*
    44|             exclude-host:mnl1555win
    45|         }
    46|     }         
    

    Another example, you want to activate FreezeMonitor on all machines with Windows 64-bit operating systems:

    license_optimizer.conf
    12|  standalone
    13|	 {
    14|		display=Optimizer Agent
    15|		description=Job to log, suspend, or terminate idle application
    16|		active
    17|		{
    18|			type=bool
    19|			value=true
    20|         override
    21|         {
    22|             type=list
    23|             os:win.*:true 
    24|             arch:64-bit:true
    25|         }
    26|		}
  2. Save the changes in the module activation configuration file.

  3. To immediately reflect the changes on the client machine, delete the dist-config folder and dist-config.[platform].tar.gz file in the temp directory, which is by default in /var/opt/openit/temp. Then, follow the instructions in the Manual File Distribution to a Client section.

We value your feedback!

Please take a few minutes to complete our survey and share your thoughts on your recent experience with our documentation.

Take survey

Close