ATS Licensing

Topic ContentsTopic Contents
    1. Version Compatibility
    2. License Types
    3. Connect to a License Server
    4. Configuring Licensing Clients
      1. Backup License Server
    5. License Files
    6. Named Leases

The ATS Licensing Server controls the licenses for ATS software applications, including ATS CM4D.

Clients can then connect to the Licensing Server, either locally or over a Network. For information on installing and running the ATS Licensing Server, please refer to the documentation installed with the ATS Licensing Server.

Version Compatibility

ATS CM4D

ATS Licensing

v20

2.0

v21-v22

2.1

v23-v25.0

3.0 or higher

v25.1 or higher

4.0 or higher

License Types

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

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:

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

The Licensing Client config file should only be edited by the Network Administrator.

Configuring Licensing Clients

While the licensing client config file can use the default settings, there are options available for advanced configuration.

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.

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 used 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.
  2. Features - The module option require Concurrent licenses, which are checked at runtime and then released.
    1. Beta - Allows you to run Beta (test) versions of the software. [deprecated as of v
    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. If you are running unmanaged databases (those without a Site), this option must not be in your licensing management console.
    3. API - Allows you to use the internal CM4D API functions.
    4. Server - 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:

Can we improve this topic?