Exports entitlements from an AppClarity 5.2 database into a TSV file, which can then be reviewed and imported into AppClarity 7.1. You only require access to the AppClarity 5.2 database, you do not require a full installation of AppClarity 5.2. The TSV export file contains all the exported entitlements. Below is a summary of the process which is shown in the picture opposite:

  1. Set permissions on the AppClarity 5.2 database
  2. Set permissions on the export folder
  3. Configure the AppClarity v5.2 connector

After export, you should review the TSV file you will need to use the Entitlement .tsv connector to import them into AppClarity 7.1. See  Entitlement import files reference page regarding structure and content of TSV files.

If you are migrating from AppClarity 5.2 please contact 1E for help, with using this process and reviewing the contents of your TSV file before importing into AppClarity 7.1.


The AppClarity 5.2 connector is a preview for a forthcoming feature that will enable the migration of entitlements from AppClarity 5.2 so that they can be imported into AppClarity 7.1 . We recommend that this feature is not used in a production environment and evaluated only in a lab environment.

The following limitations apply:

  • Only license and maintenance entitlement types are exported from AppClarity 5.2
  • Linked entitlements only support a single license with associated maintenance entitlements. For example, License1 is associated with Maintenance1, Maintenance2, Maintenance3 etc.
  • Files attached to contracts in AppClarity 5.2 are not exported or imported.
  • Management groups must exist in Tachyon if they are referenced in any entitlements in AppClarity 5.2. Please refer to Tachyon 5.1 - Management groups page.
  • Bundled entitlements are not supported for extended cases and may result in incorrect linking or export results. For example, when a single license is associated with multiple contracts or when a single maintenance is associated with multiple licenses and many more such cases.
  • There are some input value restrictions in AppClarity 7.1  that are not in AppClarity 5.2. For example, contract number is allowed as alphanumeric in AppClarity 5.2, but must be a number only in AppClarity 7.1 . Issues should be highlighted as caveats during import, most of which you can resolve by editing any problematic entitlement.
  • Metric Type and Metric Name in AppClarity 5.2 do not map directly to Metric Type and Metric Other in AppClarity 7.1 . Therefore, you will see Invalid Metric Other caveat for every entitlement you import, unless the original Metric Type is Other. For Metric Type of Device, which is most common, you can publish directly without any concern. For remaining metric types, you can review before import, or correct after import.

Set permissions on the AppClarity 5.2 database

The connector requires an SQL login to exist in the AppClarity 5.2 database, with explicit Execute permissions to the stored procedure dbo.APSP_ExportEntitlement

This can be granted in any of the following ways:

  • If the connector is using Trusted Connection, the SQL login is the SLA Integrate Services Agent account which is normally Network Service
  • If the connector is not using Trusted Connection, then you can use any SQL login on the AppClarity database and grant it the above rights, and use this login as User ID and password in the AppClarity 5.2 connector.

Set permissions on the export folder

The connector requires a folder location that must be file share, or a folder on the Tachyon server, to which the SLA Integrate Services Agent account has write access to.

The folder location can be a folder on the Tachyon server, or a remote share, provided write access is given to the  SLA Integrate Services Agent account which is normally Network Service.

On this page:


Configure the AppClarity v5.2 connector

  1. Navigate to Settings→Configuration→Connectors.
  2. Click the Add button.

  3. In the Add Connector popup select the required Connector type from the list of connector types.

  4. Once you've made a selection the Add connector popup will show fields appropriate to the selected Connector type.
  5. Enter Connector name.

  6. In Name, enter a logical name for this connector, for example AppClarity 5.2 production

    You should use a naming convention for connector names:

    <connector type> <scope> <RCR>

    Scope describes where data is coming from or what it's being used for. For example Demo, Test, Lab, Q2 Audit.

  7. In SQL Server, enter the name of the SQL Server instance where the AppClarity 5.2 database is hosted. If it is a named instance, append it to the server name, for example Server_Name\Instance.
  8. In Database, enter the name of the AppClarity 5.2 database, this is usually AppClarity.
  9. If you are using Windows Authentication to authenticate with the SQL Server instance:
    1. Check Trusted Connection
    2. You do not need to populate the User Id and Password fields.
  10. If you are using a SQL Login to authenticate with the SQL Server instance:
    1. Uncheck Trusted Connection
    2. In User Id, enter the name for the SQL login you want to use to connect to the database.
    3. In Password, enter the password for this login.
  11. In Folder Location, enter the location for where your exported TSV file will be written.

  12. Click Save.

Test will confirm whether the SLA Integrate Services Agent account, or specified SQL Login, can connect to the specified database instance.

It does not test the following.

It is only when you attempt to use the connector (create new action Sync Data) that you will experience an issue if these points are not addressed. Then you will find the export TSV file is not created, and not see any error or warning.

Additionally, Test does not test if the stored procedure has been hotfixed.

AppClarity v5.2 connector

Execute Sync Action - AppClarity 5.2

When a new connector is saved a new action is defined in Tachyon. This new action will have a name of the form: Sync Data - Connector name, for example Sync Action - AppClarity 5.2 production.

  1. Click the Execute button - th ebutton is at the top right of the 
  2. In the Execute action popup subsequently displayed, use the Repository menu to select the inventory repository you want to populate. 
  3. Once the repository has been selected you can then select the action to run. In the case of inventory repositories the actions will be restricted to inventory related actions. For a connector you will be looking for an action with the form Sync Data - <connector name>.
  4. For inventory syncs you have the option to check the Clean Sync checkbox.