Contact our corporate or local offices directly.
For organizations that require their Altium design software installations to remain offline – isolated from the internet – the convenience and flexibility of on-demand software licensing can be provided by a localized Altium Private License Service, rather than from the internet-based Altium Licensing Service.
The dedicated Private License Service (PLS), implemented on a PC connected to the company LAN/WAN, is set up by an administrator to acquire the company's Altium licenses and then serve these to Altium software installations as required.
In a similar arrangement to using a license from the Altium License Service portal, a seat (instance) of a PLS-hosted Altium license can be 'leased' by the software when it is in use, and then 'revoked' (returned to the available pool of licenses) when no longer required. With the Altium PLS, licenses can also be served on a Roaming basis, where the license seat is leased to the target machine for a specified time – this allows the Altium design software host PC, say a laptop, to 'roam' freely while isolated from the network.
A PLS offers the flexibility required by companies that host multiple Altium software installations, with the bonus that the license and seat usage can be configured, monitored and controlled from a centralized Altium Private License Service – which in turn is hosted on a local LAN/WAN that may be isolated from the internet.
Historically, the Altium Private License Service (PLS) has been available as a standalone application (legacy PLS v1.0) that is installed as a Windows service on the host machine. Supporting today's need for more sophisticated software license management, the current releases of on-site Altium Server products (such as Altium Concord Pro), offer an enhanced and simplified implementation of the PLS that is available as part of the server's installation. The Altium Concord Pro Private License Service supports several modes of operation, is configurable as a central or local License Service, and can serve both Altium design software and Altium Server licenses over the local network – plus much more.
If it's not already in place, the first step in using the server PLS is installing and licensing the Altium Concord Pro server.
Altium Concord Pro's functionality, including its Private License Service (PLS), becomes available when the server itself has been licensed by the addition of a suitable Altium Concord Pro License. To enable users to sign in to Concord Pro from Altium Designer and other Altium design software, a valid
Altium Concord Pro CAL license (Client Access License) is also required.
Altium servers provide a flexible self licensing method for adding or acquiring Altium licenses. This is available through the Licenses page (Admin » Licenses) of the Concord Pro server's browser interface, which provides the connection to the Altium Licensing portal () from where your company's Altium licenses can be locally acquired.
► See Altium Concord Pro Licensing for detailed information on acquiring and configuring licenses in Concord Pro.
In summary, Altium Concord Pro and its client connections can be licensed by:
alffiles from disk.
*.alflicense files in the root directory of the server installation (normally
C:\Program Files (x86)\Altium\Altium Concord Pro), which is the method used for past versions of Altium servers. The Concord Pro server will automatically import the license files when it restarts – a reboot may be required.
With Altium Concord Pro successfully licensed from the Cloud or existing license files, the Private License Service is ready to be configured to serve licenses over the local network. Additional Altium software licenses purchased by your company can be acquired through the server's License Manager page – Admin » Licenses.
To add a license to the server, such as an Altium Designer license, click the button and select from the cloud (or file) options as before. Note that licenses may be acquired in bulk or individually – use the checkboxes in the Add Licenses list to select which licenses Altium Concord Pro will acquire.
Newly acquired licenses are subsequently included in the server's Licenses list. Licenses are set to the 'All Users' group by default (unless that option has been unchecked), making them available to all registered server users. This can be confirmed from the License Edit page, which is accessed from the button associated with the license entry.
Once Altium Concord Pro has been installed and licensed (as above), licenses that are acquired can be made available on the host network by the server's Private License Service (PLS). To provide the maximum flexibility in how licenses are served to network-based clients (Altium software and other server installations), the PLS can be configured and used in different modes of operation, as summarized below:
► See the Server PLS mode comparison table for a practical summary of each mode.
As a reminder, before using the server's PLS in any of its modes Concord Pro needs to be configured to connect and sign in to the Altium License service portal, so that the licenses purchased by your organization may be acquired – the server can be offline once this is complete. Alternatively, all the required licenses could be acquired from the Altium Dashboard or via a separate Altium server that is connected to the internet, and then transferred to the local Concord Pro server as individual license files.
The acquired licenses, such as Altium Server and Connection (CAL) licenses or Altium design software licenses, can then be served over the local network by the PLS.
As implied by the name, the Concord Pro License Manager's No PLS mode is essentially the server in its standard configuration, where the PLS is not enabled.
As such it does not offer Altium licenses over the network, however licenses can still be acquired from the Altium License service portal. This function supports Concord Pro's capability of being 'self' licensed from acquired licenses or imported
alf license files, which exists alongside the legacy method of placing license files in the installation root folder.
To select this mode, check the No PLS option on the License Manager page in the server's browser interface – Admin » Settings – License manager.
The Automatically create assignment for All Users group option forces newly acquired licenses to be assigned to the default All Users group. How the licenses are assigned will affect their availability to user Roles when served over the network by the PLS, as outlined below.
In this server PLS configuration, licenses will be made available to Altium software and Server installations hosted on the network. Altium Concord Pro is licensed as normal, through acquired licenses or
alf license files.
To switch to this mode, select the Local PLS option on the License Manager page in the server's browser interface – Admin » Settings – License manager.
The PLS will expose licenses to Altium design software when the user signs in to Altium Concord Pro. Server Licenses will become available to other servers on the network when Concord Pro's PLS is in the 'No Authentication' security mode (see options below).
The Local PLS mode provides additional settings that determine which Users might be offered specific Altium software licenses (determined by User Roles), and how long a license will remain leased when not used.
The server PLS authentication mode can be set to 'Vault Session' or 'No Authentication' depending on how you would like to make licenses available to network clients (Altium software and servers). Use the License Manager Authentication Mode drop-down menu to make the selection.
The current client connection session is granted access to licenses – a Vault/Server Session is invoked by signing in to the Concord Pro server from Altium design software. This is the server's standard PLS mode, where license access is bound to a server Session. Select Team » Sessions from the main menu to view and manage the current connection sessions.
Any connection to the server PLS will be granted access to available licenses. This is a less restrictive mode that can be used for license access where Altium software users do not sign in to Concord Pro, or when the server is set up as a central Private License Service in a multiple server configuration.
server_name:user_name. The user will only have access to the licenses associated with that generated User Name – as determined by its subsequently assigned Role membership. This action can be disabled by unchecking the Automatic user creation option (see below).
When checked (default setting), Altium Concord Pro's PLS will automatically generate a user account that corresponds to the server sign-in account. So if a user signs in to, say, the
RND server using its registered
Dev5 User account, the PLS automatically creates a User named
Trevor LicenseServer (
Username server_name) – this is the 'active' Name that should be used for Role membership, and therefore to determine license distribution. See Automatic User sync functionality below for more information.
If the Automatic user creation option is unchecked, the server user account (
Trevor) will not be able to connect to the PLS (and therefore available licenses) unless the corresponding
Username server_name account already exists. In the majority of circumstances this option should be enabled. The exception might be where the server Administrator wishes to predetermine which Concord Pro user accounts may be used to connect to the server when in No Authentication mode.
In addition, Concord Pro's PLS will automatically generate a user account (set to the user's Windows Account Name) when a User connects through the Setup Private License Server feature in Altium design software, rather than signing in to Concord Pro – note that the generated user name is in a different format to that described immediately above. See Licensing without Server sign in below.
► See the Existing User section for a summary table of server User profile types.
The Seat return timeout interval option is included to force a leased license to expire after the Client (Altium design software) has not responded to the PLS for the specified number of hours.
The PLS regularly queries a Client over the network and expects a response, however the responses will not be returned if the Client's host PC has lapsed into Suspended or Hibernation mode, for example – or if the Client application has crashed or been forcibly closed. When Client responses have not been received for a longer period of time than the nominated timeout interval (4 hours, by default), the license seat leased by the Client will be revoked and returned to the pool of available seats for that license.
This option is effectively a timed, automated version of the manual License Release feature.
When this Local PLS option is checked (the default setting), newly acquired licenses will be assigned to the default All Users group. The served license will be accessible to all software users that connect to the server, regardless of the Role group a user is assigned to.
In Local PLS mode, licenses that have been configured and exposed by the Private License Service can be accessed by Altium software installations on the network, which act as clients to the PLS. To access an Altium software license provided by the Concord Pro server PLS, sign in from the Altium design software (such as Altium Designer) – the dialog associated checkbox can be used to automate the sign-in.
Once Altium design software is connected to the Concord Pro server and its PLS, the 'Available Licenses' area of the software's License Management page will be populated with the list of private licenses provided by the server's PLS connection, under the category Private Server – Connected to xxx, where 'xxx' indicates the name of the server that is offering the licenses from its PLS. Select the Licenses option from the User drop-down menu to access the License Management page.
To lease a license for the Altium software installation, such as the Altium Designer example shown here, select the desired license entry in the list and click the Use button. Note that a license hosted by the PLS may be set to Automatic Leasing mode, so that no user intervention is required in the client software, beyond signing in to the server.
The status of the selected license will then change to indicate that it is used by you – expand (►) the license entry to see its current users. Note that its Assigned Seat Count field will change to indicate that a seat of the license has been taken, and this is also reflected by an incremented User Count for that license entry in Altium Concord Pro (go to Admin » Licenses in the server's browser interface).
The status of the license is also visible in Concord Pro's browser interface on the License Manager page (Admin – Licenses). Expand the license entry () to see the current leasing details and, if required, to terminate the current user's leasing session by clicking the Release command.
► See the Server PLS mode comparison table for a relative summary of Local PLS mode.
Altium Concord Pro's External PLS configuration mode is intended for installations where multiple servers are present on the network and one is configured as a central (remote) Private License Service for all users. This type of installation is suited to a larger enterprise, where each company department (Engineering, Development, etc) might use multiple Altium software installations and a local department server for design data management purposes. Both the department design data servers and Altium software installations are licensed by a central Licensing Service such as the PLS in Altium Concord Pro, or an Altium Infrastructure Server, which is dedicated to that task.
In this arrangement the servers are configured as follows:
To switch the local server to External PLS mode, select the External PLS option on the License Manager page in Concord Pro's browser interface – Admin » Settings – License manager.
In this mode, the local Concord Pro server connects to and uses an external PLS (such a remote server PLS that has been set up as a Central Licensing Server) in place of its own PLS service. The network address of the Central License Server in the above image, and therefore the target for the external PLS connection, is
http://LicenseServer – this address is based on the
computer_name of the license server's host PC.
When an Altium software user signs in to the Local Server (now set up in External PLS mode), the remote server PLS service is 'redirected' through the local department server and will offer its licenses to Altium software. As usual, the user must use valid (local) credentials to sign in to the local server.
The External PLS options and settings are as shown below, and are typically used for a local/department server where both software and server licenses are managed by the PLS in a remote central licensing server.
The associated PLS url and PLS Port settings should match that of the external server configuration. The URL is the address (network name) of the remote PC that hosts the 'central' Server, as indicated by the host PC's 'Computer Name' entry under
Control Panel\System and Security\System. In recent Windows' versions, see Settings » System » About.
alflicense files that have been imported from disk or placed in the server's installation folder.
► See the Server PLS mode comparison table for a relative summary of External PLS mode.
The Automatically create assignment for All Users group option forces newly acquired licenses to be assigned to the default All Users role group. This option is disabled when the above Use local license manager for Vault licensing option is unchecked, since in that mode all licenses are sourced from the External PLS, such as the PLS in a remote server used as a Central Licensing Server.
As outlined above, to implement a centralized licensing system based on multiple Altium Servers, one server is configured as a Central PLS that serves licenses to Local (say, department) Servers and their assigned Users. The Central Licensing Server is set to Local PLS mode (and 'No Authentication'), and Local Servers are set to External PLS mode where their assigned PLS is the remote Central Licensing Server.
When Altium software users sign in to their Local Server, they have access to licenses that have been 'redirected' from the (external) Central Licensing Server PLS.
Part of the mechanism involved in granting a User's access to remote licenses via the Local Server is the creation of a 'synchronized' user name in the Central Licensing Server – the local User Name is synchronized to the Central Licensing Server. See Automatic user creation in No Authentication mode, above.
The created User profile in the Licensing Server has the composite User account name;
Username server_name, where
server_name refers to the network name of the user's Local (Department) Server, and
Username refers to the User Name used to sign in to that Local Server. The composite name refers to the user's 'local' account.
For example, if Altium Designer user
Harold signs in to his assigned Local Server (Company Server 2 hosted on the
Server4 machine), the PLS in the central server (License Server hosted on the
LicenseServer machine) will allow license access by creating a User entry named
Harold SERVER4. The First Name and Last Name of the new user profile will be
SERVER4, respectively (local Username and local Server) – the account's actual Username is
SERVER4:Harold. View the User account automatically created by the License Server in this example .
In this case, an Altium Designer license in the remote License Server will be shown as leased by the User Name
SERVER4:Harold – the synchronized
Harold user in the Local Server (Company Server 2 on
Server4). Even though the Altium Designer user is signed into the Local Server (Company Server 2), the software license is provided by the remote License Server PLS (via the local server).
User profiles that have been synchronized to a Central PLS server in a multi-server setup can be added to Roles, just as with any other Server set to Local PLS mode.
In the case of a server arrangement that consists of a central Licensing Server and distributed Local Servers (as detailed above), the duplicate (synced) Users in the Licensing Server can be added to Roles as needed. Therefore, when a User signs in to a Local Server, the licenses made available to the User (from the external Licensing Server PLS via the Local Server) will be determined by the Roles and License assignments configured for that synchronized User in the central Licensing Server.
In the above example, the synced User
Harold SERVER4 (the
Harold user synced from the Local Server) in the Licensing Server might be added to a 'QA' Role, which has a particular Altium software license assigned to it. When user
Harold signs in to his local server, the specified license will become available by virtue of the associated user Role and License assignment configuration in the external Licensing Server.
Generally, these user Role and License assignments would be implemented by the Licensing Server administrator, once a Local Server user has signed in for the first time (thereby instigating the User sync process).
► See License Role Assignments below for more information on working with Roles and License assignments.
For Altium software users who do not use the data management capabilities of Altium Concord Pro, and therefore do not sign in to the server, the design software can access licenses from the server's PLS using the software's internal PLS setup (as outlined below). For this approach, the Concord Pro server is set up as follows:
To access the Server-hosted licenses in Altium software (without sign-in), select Setup private license server on the License Management configuration page. Altium Designer is used here as an example. Select the License Management option from the Account drop-down menu to access the License Management page.
Enter the basic server details for the PLS in the Private License Server Setup dialog, and click OK. The server name will be the network (computer) name of the PC that is hosting the Concord Pro server, and the standard port is
9780 – use port
9785 to establish a secure
https connection. The other dialog settings, such as the Servers list options apply to the legacy PLS 1.0 type connection only.
Once connected to the PLS, the Available Licenses area of the License Management page (under the category Private Server – Connected to...) will be populated with a list of private licenses that you are able to use.
To lease a license for the Altium software installation, select the desired license entry and click the Use button. Alternatively, a license hosted by Altium Concord Pro may be set to Automatic Leasing mode, so that no user intervention is required in the Altium software, beyond activating the Private license server connection.
Once leased by the software, the status of the license will indicate that it is used by you – note that its Assigned Seat Count field will change to reflect that a seat of the license has been taken. On the server side, the license entry on the License Manager page (Admin » Licenses) will show that a seat has been taken by a User Name derived from the Altium Designer host PC – see the below section for more information.
When a user has connected to the Altium Concord Pro PLS from Altium software without signing in (as described above), a User profile is created in the server that matches the connecting Computer Name and its active Windows User Account Name – that is, the computer and Windows account that hosts the Altium design software.
For example, a user might be using a Windows account called
Design on a computer named
PC4. When the Altium software's Setup private license server option is used to access a license, the server PLS that hosts that license will create a user named
Design, with First/Last Name;
Again, this is the server User Name that may be added to Role(s), which in turn will determine which licenses are made available to the
Design account on
See below for the overall information on Roles and License assignments:
To control license availability for Altium software users, Altium Concord Pro's PLS can be configured to associate specific licenses with defined user Roles (groups of Users). In practice, when a user signs in to the server, the PLS will offer only those licenses that are assigned to Roles that have the user as a member.
Users and user Roles may be registered in Concord Pro already if it is currently in use for managing and storing Altium software design data. Licenses hosted by the server are assigned to 'All Users' by default, but can be reassigned to any available Role. Similarly, Users can be added to any available Role.
► See Managing Users for more detailed information about User Accounts in Altium Concord Pro.
Add the name of the new Role in the Add Role dialog, and include any Users you would like as Members of that Role. The New Members field will dynamically search for an existing User that matches the first letter(s) you have typed – select the full Member name to confirm your choice. Click the dialog's button to commit the changes.
► See Managing Users for more detailed information about Roles in Altium Concord Pro.
A Role may be added to an existing User by editing the entry's profile to include the desired Role. Click the User entry's icon to open the Edit User dialog, select from the available Roles(s) in the New Roles field and then save to commit the changes – as described in the Users section above.
Note that an existing User can be represented in a number of formats , depending on how it was added. The formats include standard
Username/Firstname/Lastname entries and entries that have been automatically generated by the PLS in response to incoming connections that do not instigate a server Session by sign-in.
|User||Username||First Name||Last Name||Account Creator||Circumstances|
|Harold Smith||Harold||Harold||Smith||Manually entered||A standard User account, added by a Server administrator.|
|Design PC4||Design||Design||PC4||Auto-generated||An Altium software user, working from the
In all cases, these User profiles can be made members of Roles by editing the user entry. Note that in a Central Licensing Server and multiple Local Servers arrangement (see External PLS mode), User Role membership is applied in the Central PLS, rather than at a Local Server level.
In a Central/Local multi-server setup, the User configuration process would be, typically:
In Local PLS mode, the Altium Concord Pro PLS can selectively offer Altium software licenses that have been assigned to a specific Role, which in turn, can be associated with a server User account. By default (unless otherwise specified), all licenses acquired by Concord Pro are assigned to the 'All Users' group, and therefore available to any User that connects to the PLS.
To view and edit the existing license Role assignments, go to Admin » Licenses in the server browser interface and select the Roles tab. Click on a Role name in the Roles column to see its User members, and on the right, view its assigned licenses.
The License type, the specific License and the proposed Role Assignment are all selectable from drop-down menus, which will be populated with a list of those currently available. In the below example image, 4 seats of a specific 20-seat license are being assigned to the 'Engineers' group Role.
The license assignment options include:
In the above license assignment scenario, 4 seats of the 20-seat Altium software license has been assigned to the 'Development' Role (and its single member,
Bruce), but is also available to all other users by virtue of its existing (default) 'All Users' Role assignment. Deleting the license's additional 'All Users' Role assignment will leave the license only assigned to the Development Role, rather than both – and thereby exclusively available to the Development group of Users.
To remove an existing license assignment, click the delete button () associated with its selected entry. A license assignment can also be edited via the button.
The License Manager page Roles tab provides an aggregate view of the current Roles, their constituent Users, and the Licenses assigned to each Role group. This versatile interface can be used in combination with how Users are grouped in Roles (configured under the main Users tab) for a flexible approach to allocating licenses and seats to Users.
The Private License Service (PLS) in Altium Concord Pro offers a range of administration features for managing license allocation and usage, including the ability to forcibly release a leased license and closely monitor how licenses are used.
For situations where a license has been in use by Altium software but not correctly released by the software, the PLS provides a means of terminating that lease and returning the seat to the pool of available license seats. This can occur when the PC has lapsed into standby while the Altium software is active, or through some form of software crash that has prevented a clean exit. In practice, that license seat is still registered as being in use and therefore denied to another user.
To locate the license of concern in this situation, go to the licenses list in the server's web interface by selecting Admin » Licenses. Within the list of licenses shown under the Licenses tab, the leasing information for each entry is available when a license entry is selected – use this approach to find the user that still retains the license seat.
The license leased to that user can be terminated, and the seat returned to the license pool, by clicking the Release link associated with the user entry and then confirming the action in the Release seat dialog. The Altium software will notify the user that the license has been forcibly released by an administrator.
Altium Concord Pro provides a range of license usage monitoring and reporting features that can be used to audit how Altium software licenses are used within an organization. This is useful for ensuring that the best use is being made of the available license seats, for anticipating future license requirements and to determine the usage of individual Users.
The server license usage features are accessed through the browser interface under the Reports tab on the License Manager page (Admin » Licenses). This offers an extensive range of reporting options that are accessed by specific tabs within the Reports view. Depending upon the type of information that's required for each report, the associated reporting filters can be applied to tailor the results to include specific Licenses, Roles, Users and time periods.
To filter the usage reporting results to show the activity of a particular license for example, begin typing a license name, select the license of interest from the Licenses drop-down menu and click . Additional licenses can be added as required. The filtering action of the selection remains in effect while each reporting style (Usage) tab is selected, allowing you to see usage reports that are constrained to that license.
The Reports page also offers the option to export the current report to disk in CSV format – compatible with Microsoft Excel and other spreadsheet applications – for administration and accounting purposes. Select the desired report results using the appropriate tab and filtering for your needs, click the button and nominate a location to save the file to disk.
If Altium software is not able to connect to the Concord Pro server PLS, or licenses that you have acquired and configured in the PLS are not appearing in the software's Available Licenses list, there may be system or software settings that are preventing access.
When troubleshooting any issues, consider the following:
9780by default when transferring licensing data on the network. Check that this port has been opened in the host PC's firewall during the server's installation.
Username server_nameUser account. Conversely, if you are connecting to the PLS using the 'Setup private license server' option in Altium design software, the Concord Pro server authentication must be set to 'No Authentication'.
The Concord Pro server PLS can be set to one of three distinct modes, each of which will suit particular licensing arrangements for Altium software and Altium Servers. The below table summarizes how the PLS manages and offers Altium licenses, when set to each PLS mode.
|No PLS mode||Local PLS mode||External PLS mode|
|Server license location:||Local||Local||Local or External|
|User authentication:||n/a||Vault Session||No Authentication||n/a|
|Altium Server licenses served to network:||No||No||Yes||Yes – Licenses sourced from external server PLS.|
|Altium software licenses served to network:||No||Yes||Yes||Yes – Licenses sourced from external server PLS.|
|Altium software license access using internal PLS setup:||No||No||Yes||No|
Contact our corporate or local offices directly.