ATS Licensing

The ATS Licensing Server is a plugin for ATS Security and Configuration Manager which administrates the licenses for ATS software applications, including ATS CM4D (both desktop and web applications). Application servers and other CM4D systems can then connect to the Licensing Server, either locally or over a Network.

Supporting Windows Services:

• ATS Licensing Server
• ATS Licensing WCF Host Communicator
• ATS Protection Plus Processor

For information on installing and running the ATS Licensing Server, please refer to the documentation installed with the ATS Licensing Server or visit ATS-HELP.com.

Version Compatibility

License Types

There are two types of licenses that are used with the ATS Licensing Server:

• Named Lease: A license that is assigned to a specific machine and is reserved for use by that computer only. CM4D Server installations must use a Named Lease.
• Concurrent: A license that has a set number of connections that can be made by client machines throughout a network. These licenses are checked out at run-time, and if a license is not available, the module will not run.

Connect to a License Server

You can obtain a license from an ATS License Server Service, either on a local machine or a Network server, two different ways. Choose one of the following methods:

• During installation - Enter the name of the ATS License Server in the field.
  
• After installation - To change the license server, edit the server name in the file ATSLicensingServer.Client.dll.config, located in the CM4D Installation folder (note the yellow highlighted lines in the example below). The Licensing Client config file should only be edited by the Network Administrator.

<setting name="EndpointAddress" serializeAs="String">
        <value>net.tcp://licenseservername:8001/ATSLicensingServer/</value>
</setting>

Configuring Licensing Clients

While the licensing client config file can use the default settings, there are options available for advanced configuration. For more details, refer to the topic Configuring Licensing Clients.

Backup License Server

Up to two additional license servers can be set up to be used as backup license servers in case the primary license server becomes unavailable. To assign backup servers, copy the address string (net.tcp://licenseservername:8001/ATSLicensingServer/) between the <value> attributes for the BackupEndpointAddress and BackupEndpointAddress2. Set each Backup Endpoint to each alternate license server name.

<setting name="EndpointAddress" serializeAs="String">         <value>net.tcp://licenseservername:8001/ATSLicensingServer/</value>       </setting>

<setting name="BackupEndpointAddress" serializeAs="String">         <value >CopyStringHere</value>       </setting>

<setting name="BackupEndpointAddress2" serializeAs="String">         <value >CopyStringHere</value>       </setting>

Each alternate license server will need to be configured by importing licenses and assigning Machine IDs for Named Leases.

ATS Licensing FIPS Compliance

For FIPS complicance, an additional setting must be configured for the ATS Licensing WCF Host Communicator service used by ATS Licensing Server when running CM4D.

The WCF Communicator service configuration file is typically installed parallel to the ATS Licensing Server. Default path:Default path: .\Applied Tech Systems\ATS Licensing WCF Communicator

Edit the LicenseServiceHost.exe.config file and set the following for the LicenseService Properties Settings:

• Setting Name: "DisableHash"
• Value: True

License Files

Unless you are using Concurrent licenses, Named Leases need to be assigned to the Modules and Features that CM4D will be using. Refer to the following list to determine which type of license should be used with which Module or Feature:

1. Modules - The modules are the main applications of ATS CM4D.
   1. CM4D Classic - Can use either Named or Concurrent licenses. This license is not consumed by the CM4D Scheduler clients.
   2. CM4D Interactive - Can use either Named or Concurrent licenses.
   3. CM4D Workcell - Can use either Named or Concurrent licenses.
   4. DataSmith - Can use either Named or Concurrent licenses.
   5. Server - Must be a Named license. Required for CM4D Scheduler, DataSmith Batch, and EventSmith Services. If you are running this license, you also need to have the Enterprise Module Option.
   6. Upload Portal - User licenses (assigned to a user login rather than a machine ID), either Named or Concurrent.
   7. Peruse - Concurrent User licenses (assigned to a user login rather than a machine ID).
2. Features - The module option requires Concurrent licenses, which are checked at runtime and then released.
   1. Beta - Allows you to run Beta (test) versions of the software. [Obsolete]
   2. Authentication - Allows you to create user groups and enforce user privileges within a Site database, using Site Manager to manage the levels of access of your Network users.
   3. API - Allows you to use the internal CM4D API functions.
   4. Enterprise - Allows you to run an Server Installation and all modules related to that install type.

Named Leases

If you are using Named Leases, you will need to assign Named Leases to license files in the ATS Licensing Server Manager. You can do this in two ways:

• Approve Named Requests - As a machine requires a license, it will send a request to the ATS Licensing Server. A License Manager can then simply go to the Named Requests dialog and either Approve the Request or Remove that request. If Approved, the machine that requested the license will be assigned a Named license permanently (or until it is removed by the License manager).
• Assign Named Leases - A License manager can manually assign Named Leases by entering the Machine ID's for each license. Run the Machine Identifier on the Client (the computer running CM4D) to obtain your Machine ID, then enter that ID in the Named Leases dialog for the license. That Named license will be assigned to that Machine permanently (or until it is removed by the License manager).

Can we improve this topic?