Print

File naming conventions

The following file naming convention provides you with a convenient way of interpreting the file names of AE Services deliverable. This naming convention is not a formal standard, it is simply a guideline for reading file names.

<api>- <type>- <target>- <version> - <build>.<suffix>

Where:

Name Description
<api>- Refers to the name of the API. For example, tsapi or cvlan
<type>- Refers to the type of deliverable. Can be client-, sdk- or client-sdk (for ISOs).
<target> Refers to the name of the operating system.
<version> Refers to the software version.
- <build> Refers to the software build number, preceded by a dash.
noteNote

This number changes frequently. It is often represented in this document by x instead of an actual build number.

.<suffix> Refers to the file or package type.

Examples

noteNote

The numbers following the build version are subject to change. For example, the numbers following tsapi-client-win32-7.x.x- are subject to change.

The table applies the naming convention to the AE Services deliverables.

Table 1. AE Services TSAPI and CVLAN software deliverables -- file names
<api>- <type>- <target>- <version> -<build> .<suffix>
tsapi- client- linux- 7.1.2 -170 .bin
tsapi- client- win32- 7.1.2 -170 .zip
tsapi- sdk- linux- 7.1.2 -170 .bin
tsapi- sdk- win32- 7.1.2 -170 .zip
cvlan- client- linux- 7.1.2 -70 .bin
cvlan- client- win32- 7.1.2 -70 .zip
noteNote

Build numbers change frequently. These numbers are provided as examples only.