Configure a License Server Manager

To configure a license server manager, perform the following steps:

  1. From the Monitor Web GUI, go the Control Center tab and select the Setup option.
  2. Click on Initialize Repository.
  3. Go to the Server & File Control option.
  4. Choose the License server tag you wish to configure or edit.
    The configuration will display.

    Figure 1. License Files and Commands
  5. You can edit the following parameters:
    This shows the host on which the license server instance is running. This is normally one or a triad. Multiple hosts should be separated by a space.
    This is the directory that the license server instance will be started in. This is normally a single directory, but could be a list of directories if HOSTS refer to a triad, and the directory is different on each of the different hosts. If the HOSTS line shows more than one host, then the first directory is used for the first host, the second for the second host and so on. If there are fewer directories than hosts, then the last directory is used for each host in excess to the number of directories.
    The default location for LicenseManager job logs is the directory specified by the DIR setting. If another location is desired, specify the absolute path with the LOGDIR setting.
    This is the command to start the license daemon. This command will be executed in the directory specified. This field can be empty if the start capability is unwanted.
    This is the command to stop the license daemon; this command will also be executed in the directory specified. This field can be empty if the stop capability is unwanted.
    This command forces a reread of the license file. This field can be empty if the reread capability is unwanted.
    This is a list of files in to the directory “DIR.” Normally, this is the license file and the options file, but the list may also include other files. Monitor can fetch and deploy these files. The field can be empty if the file fetching and publication capabilities are unwanted.
    The user that owns the license daemon. Ideally, this should be the same user as the owner of Monitor, but in many cases, this must be a different user. This user exists in the remote system(s) specified in the HOSTS line. If left empty, it is assumed that the owner is the same as the owner of Monitor.
    This shows the users of Monitor that have authorization to perform license management tasks. If empty, it assumes that the only manager is the owner of Monitor.
    This is a comment field for communication of status between team members.
    This is a flag to enable Monitor to manage the license daemon or file. The default is disabled, and the flag is set to 0. To enable, set the flag to 1.
    Note: The Control Center will try to fill in reasonable defaults for tags that are already being monitored by using Monitor's tracked data.
  6. Once you’ve configured the tag appropriately, click Save.
    This saves the configuration and creates the jobs for managing the license daemons and fetching and deploying jobs for each managed file specified in the configuration.