Wiki source code of ACMP Lizenzen
Last modified by Sabrina V. on 2026/07/22 12:24
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{aagon.priorisierung}} | ||
| 2 | 40 | ||
| 3 | {{/aagon.priorisierung}} | ||
| 4 | |||
| 5 | {{aagon.floatingbox/}} | ||
| 6 | |||
| 7 | = Notes on ACMP Licensing Starting with ACMP Version 6.6 = | ||
| 8 | |||
| 9 | {{aagon.versionierungsbox}} | ||
| 10 | If you have already entered the Server license key in version 6.5.7, you do not need to take any further action. | ||
| 11 | {{/aagon.versionierungsbox}} | ||
| 12 | |||
| 13 | Due to a general transition of Aagon’s licensing model to ACMP online licensing via a license server, you will need a server license key. This key is entered in advance in the ACMP Console and then retrieves all of the customer’s license information from the license server - that is, how many licenses have been purchased for which solutions. With online licensing, the customer’s license information will be automatically downloaded and updated in the future. | ||
| 14 | |||
| 15 | This means: Each customer receives **a single** **32-digit Server license key**, which must be entered **once** and is valid **only** for that customer. | ||
| 16 | |||
| 17 | You will automatically receive the license key from Aagon, which is valid from the date of issuance and has no expiration date. | ||
| 18 | |||
| 19 | {{aagon.infobox}} | ||
| 20 | Please note that it is impossible to perform the installation of ACMP version 6.6.0 without the key! If you have not received a server license key, please contact your representative at Aagon to ensure that you can continue using ACMP in the long term. | ||
| 21 | {{/aagon.infobox}} | ||
| 22 | |||
| 23 | As soon as you receive an email from Aagon containing the server license key, you should take the following steps: | ||
| 24 | |||
| 25 | (% style="width:1293.48px" %) | ||
| 26 | |(% style="width:596px" %)The ACMP Server must allow access to the following license servers:|(% style="width:695px" %)((( | ||
| 27 | [[https:~~/~~/acmplicense.aagon.com/>>https://acmplicense.aagon.com/]] or [[https:~~/~~/aesblicense.aagon.com>>url:https://aesblicense.aagon.com/]] | ||
| 28 | |||
| 29 | Port: 443 | ||
| 30 | ))) | ||
| 31 | |(% style="width:596px" %)At least one ACMP Console must allow access to the following update servers:|(% style="width:695px" %)((( | ||
| 32 | [[https:~~/~~/acmpupdate.aagon.com/>>https://acmpupdate.aagon.com/]] or [[https:~~/~~/aesbupdate.aagon.com/>>https://aesbupdate.aagon.com/]] | ||
| 33 | |||
| 34 | Port: 443 | ||
| 35 | ))) | ||
| 36 | |||
| 37 | {{box}} | ||
| 38 | Also check the [[required URLs>>doc:ACMP.610.ACMP installieren.Checkliste zur Installation.WebHome||anchor="HRequiredURLs"]] to make sure you have already marked them as trusted and approved them. | ||
| 39 | {{/box}} | ||
| 40 | |||
| 41 | To import the Server license key, follow these steps: | ||
| 42 | |||
| 43 | == Step 1: Update ACMP to version 6.6 or perform a fresh installation == | ||
| 44 | |||
| 45 | {{aagon.infobox}} | ||
| 46 | This step is performed when you want to upgrade from ACMP version 6.5.7 to 6.6 or perform a complete reinstallation of ACMP. | ||
| 47 | {{/aagon.infobox}} | ||
| 48 | |||
| 49 | First, you must update your console to version 6.6.0 via //System //>//[[ ACMP Update>>doc:ACMP.610.ACMP-Solutions.System.ACMP Update.WebHome]]// or, if you are installing ACMP for the first time, perform the [[initial installation of the acmp console>>doc:ACMP.610.Arbeiten mit der ACMP Console.WebHome]]. | ||
| 50 | |||
| 51 | |||
| 52 | == Step 2: Enter the server license key == | ||
| 53 | |||
| 54 | A window will open where you can enter the server license key. | ||
| 55 | |||
| 56 | {{figure}} | ||
| 57 | [[image:66_ACMP Lizenzen_Login_902.png||data-xwiki-image-style-alignment="center" height="461" width="631"]] | ||
| 58 | |||
| 59 | {{figureCaption}} | ||
| 60 | Enter the Server license key or offline Server license file | ||
| 61 | {{/figureCaption}} | ||
| 62 | {{/figure}} | ||
| 63 | |||
| 64 | Enter the server license key from the email you received under //Enter Server License Key//. | ||
| 65 | |||
| 66 | In the rare case that you are using an offline environment, you will also receive an offline file in ZIP format that can be imported. | ||
| 67 | |||
| 68 | {{aagon.infobox}} | ||
| 69 | Please note that we do not automatically send you the offline file; you must actively request it from your Aagon contact person! | ||
| 70 | {{/aagon.infobox}} | ||
| 71 | |||
| 72 | To do this, enable the radio button //Select Offline Server License File// and click the icon [[image:https://doc.aagon.com/bin/download/ACMP/66/ACMP-Solutions/System/ACMP%20Lizenzen/WebHome/image-20240314150648-1.png?width=27&height=27&rev=1.2||alt="image-20240314150648-1.png" height="27" width="27"]]. Then import the file //LicencePackage.zip//. | ||
| 73 | |||
| 74 | {{aagon.infobox}} | ||
| 75 | Please note that this option is not recommended and should only be used as an exception, since it requires you to manually import current license information on a regular basis. This is the only way to ensure that your licenses remain valid. | ||
| 76 | {{/aagon.infobox}} | ||
| 77 | |||
| 78 | Under //Configure Proxy//, you can choose whether to use the system's default proxy settings, a manual proxy configuration, or proxy authentication. | ||
| 79 | |||
| 80 | Then click //OK.// | ||
| 81 | |||
| 82 | You can now use the ACMP Console. | ||
| 83 | |||
| 84 | |||
| 85 | = Overview of ACMP Licenses = | ||
| 86 | |||
| 87 | The ACMP Licenses plugin provides an overview of all licenses for the individual solutions that you have purchased for ACMP. | ||
| 88 | |||
| 89 | {{figure}} | ||
| 90 | [[image:68_ACMP Lizenzen Plugin_1595.png||alt="Plugin Übersicht.PNG" data-xwiki-image-style-alignment="center"]] | ||
| 91 | |||
| 92 | {{figureCaption}} | ||
| 93 | ACMP Licensing Plugin | ||
| 94 | {{/figureCaption}} | ||
| 95 | {{/figure}} | ||
| 96 | |||
| 97 | In addition to the solutions you use in ACMP, you’ll see information about the number of licenses purchased for each solution, license usage, and license types: | ||
| 98 | |||
| 99 | The license types are categorized as //Licensed//, //Unlicensed//, and //Evaluation// - that is, EVAL licenses or trial licenses. | ||
| 100 | |||
| 101 | When you click on a solution in the list view, a detailed view of the solution and its current licensing status opens in the right half of the workspace. | ||
| 102 | |||
| 103 | {{figure}} | ||
| 104 | [[image:Lizenzdetails.PNG||data-xwiki-image-style-alignment="center" height="277" width="424"]] | ||
| 105 | |||
| 106 | {{figureCaption}} | ||
| 107 | Licensing the ACMP Helpdesk solution in the Details View | ||
| 108 | {{/figureCaption}} | ||
| 109 | {{/figure}} | ||
| 110 | |||
| 111 | The following information is submitted for licensing purposes: | ||
| 112 | |||
| 113 | |(% style="width:160px" %)**Name**|(% style="width:1857px" %)The name of the license is displayed. | ||
| 114 | |(% style="width:160px" %)**Status**|(% style="width:1857px" %)((( | ||
| 115 | The status indicates the condition of the licenses, which you can accept after the license server has verified them. This determines whether and how you can continue working with the licenses. | ||
| 116 | |||
| 117 | **Active** | ||
| 118 | |||
| 119 | The license is active and in use. | ||
| 120 | |||
| 121 | {{aagon.infobox}} | ||
| 122 | EVAL licenses are always active. | ||
| 123 | {{/aagon.infobox}} | ||
| 124 | |||
| 125 | **Expired** | ||
| 126 | |||
| 127 | The license expiration date has passed. The license can no longer be used. | ||
| 128 | |||
| 129 | **Pending** | ||
| 130 | |||
| 131 | The license start date has not yet been reached. The license cannot yet be used. | ||
| 132 | |||
| 133 | **Threshold Exceeded** | ||
| 134 | |||
| 135 | The response threshold has been exceeded. | ||
| 136 | |||
| 137 | This may be due to the following reasons: | ||
| 138 | |||
| 139 | 1. The ACMP Server was unable to reach the license server for too long (approx. 30 days). | ||
| 140 | 1. No new offline server license file has been imported for too long (approx. 180 days). | ||
| 141 | |||
| 142 | The license was not validated and can therefore no longer be used. | ||
| 143 | |||
| 144 | **Error** | ||
| 145 | |||
| 146 | An error occurred during license validation. | ||
| 147 | |||
| 148 | This may be due to the following reasons: | ||
| 149 | |||
| 150 | 1. A solution with multiple licenses has different license metrics. It would be correct and error-free if it had only one license metric. | ||
| 151 | 1. The finish date of the license precedes the start date. | ||
| 152 | |||
| 153 | The licenses cannot be used. | ||
| 154 | ))) | ||
| 155 | |(% style="width:160px" %)**Number of Licenses**|(% style="width:1857px" %)The “Number of Licenses” field indicates the total number of licenses purchased. | ||
| 156 | |**Metric**|((( | ||
| 157 | The licensing metric specifies how ACMP counts individual licenses and their usage. | ||
| 158 | |||
| 159 | |||
| 160 | **Floating** | ||
| 161 | |||
| 162 | * Each license is associated with a client. | ||
| 163 | * Each client counted consumes one license point. | ||
| 164 | * If a client is deleted, the license point becomes available again and can be used for another client. | ||
| 165 | |||
| 166 | **Node-Locked** | ||
| 167 | |||
| 168 | * Licenses are available as client licenses. | ||
| 169 | * However, licenses are not automatically assigned to clients. | ||
| 170 | * The mapping of a Node-Locked license point to a client occurs through actions that the user performs with the client. | ||
| 171 | * The triggering action can be freely defined for each solution. | ||
| 172 | * Once a Node-Locked license point is mapped to a client, that license point is used and can no longer be released. | ||
| 173 | |||
| 174 | {{aagon.infobox}} | ||
| 175 | Please note that deleting the client from ACMP after the fact will not release the license! | ||
| 176 | {{/aagon.infobox}} | ||
| 177 | |||
| 178 | **Per Asset** | ||
| 179 | |||
| 180 | * Each license is associated with an asset. | ||
| 181 | * Each asset consumes one license point. | ||
| 182 | * If an asset is deleted, the license point is released and can be used for another asset. | ||
| 183 | ))) | ||
| 184 | |**Licensing Model**|((( | ||
| 185 | The licensing model specifies how long a license remains valid. | ||
| 186 | |||
| 187 | **Perpetual** | ||
| 188 | |||
| 189 | * The license is purchased. | ||
| 190 | * The right to use the software never expires. | ||
| 191 | * Updates and Support must be purchased separately on an annual basis. | ||
| 192 | |||
| 193 | **Subscription** | ||
| 194 | |||
| 195 | * The license is rented. | ||
| 196 | * The right to use the software expires as soon as the subscription ends. | ||
| 197 | * Updates and Support are included in this licensing model. | ||
| 198 | |||
| 199 | **Evaluation** | ||
| 200 | |||
| 201 | * EVAL licenses are trial licenses for prospective customers. | ||
| 202 | * These licenses are automatically included with new installations. | ||
| 203 | * EVAL licenses have a fixed number of license points. | ||
| 204 | * Depending on the solution, additional technical license restrictions may apply. | ||
| 205 | ))) | ||
| 206 | |**Start date**|This entry displays the start date of the licensing period for this solution and its licenses. | ||
| 207 | The licenses may have different runtimes. | ||
| 208 | |((( | ||
| 209 | **Finish Date / Updates and Support Until** | ||
| 210 | )))|((( | ||
| 211 | This field indicates the end date of the license term for these licenses. | ||
| 212 | |||
| 213 | **Finish Date** | ||
| 214 | |||
| 215 | * The “Finish Date” field applies to subscription licenses. | ||
| 216 | * If an infinity symbol ∞ appears there, it means that the license agreement has not been terminated. | ||
| 217 | |||
| 218 | **Updates and Support Through** | ||
| 219 | |||
| 220 | * The “Updates and Support Through” field is only available for the //Perpetual// license model. | ||
| 221 | ))) | ||
| 222 | |||
| 223 | = Refresh License Information = | ||
| 224 | |||
| 225 | If, for example, new licenses for ACMP have been purchased and this status change needs to be updated immediately, you can queue the //Update Server License// server job. | ||
| 226 | |||
| 227 | To do this, click [[image:image-20240320163900-1.png||height="26" width="24"]]//Refresh License Information// on the ribbon bar. | ||
| 228 | |||
| 229 | {{aagon.infobox}} | ||
| 230 | As a rule, newly imported licenses are updated daily by default using the //Update Server License// server job as part of the scheduled server jobs. The start condition can be changed under //System// > //Settings// > //ACMP Server// > //Update Server License//. | ||
| 231 | {{/aagon.infobox}} | ||
| 232 | |||
| 233 | | ||
| 234 | |||
| 235 | = Enter Server License Key = | ||
| 236 | |||
| 237 | Generally speaking, the need to re-import a server license key will rarely arise as long as you are working in a normal ACMP environment. | ||
| 238 | |||
| 239 | However, if you are working in an offline environment, you must manually import your offline file on a regular basis. | ||
| 240 | |||
| 241 | For both scenarios, proceed as follows: | ||
| 242 | |||
| 243 | ~1. Under //System//, navigate to //ACMP Licenses//. | ||
| 244 | |||
| 245 | 2. Click [[image:https://doc.aagon.com/bin/download/ACMP/66/ACMP-Solutions/System/ACMP%20Lizenzen/WebHome/image-20240320164121-2.png?width=35&height=34&rev=1.1||alt="image-20240320164121-2.png" height="25" width="26"]]//Enter Server License Key// on the ribbon bar. A window will open: | ||
| 246 | |||
| 247 | {{figure}} | ||
| 248 | {{figureCaption}} | ||
| 249 | |||
| 250 | |||
| 251 | |||
| 252 | |||
| 253 | [[image:66_ACMP Lizenzen_Server-Lizenzschlüssel updaten Login_902.png||data-xwiki-image-style-alignment="center" height="501" width="686"]] | ||
| 254 | |||
| 255 | Importing the Server license key or the offline Server license file | ||
| 256 | |||
| 257 | |||
| 258 | |||
| 259 | {{/figureCaption}} | ||
| 260 | {{/figure}} | ||
| 261 | |||
| 262 | 3. Enter the server license key from the email you received under //Enter Server License Key//. | ||
| 263 | |||
| 264 | 4. If you are using an offline environment, you will also receive an offline file in ZIP format that can be imported. To do this, enable the radio button //Select Offline Server License File// and click the icon [[image:https://doc.aagon.com/bin/download/ACMP/66/ACMP-Solutions/System/ACMP%20Lizenzen/WebHome/image-20240314150648-1.png?width=27&height=27&rev=1.2||alt="image-20240314150648-1.png" height="27" width="27"]]. | ||
| 265 | |||
| 266 | {{aagon.infobox}} | ||
| 267 | Please note that we do not automatically send you the offline file; you must actively request it from your Aagon contact person! | ||
| 268 | {{/aagon.infobox}} | ||
| 269 | |||
| 270 | 5. Then import the //LicencePackage.zip// file. | ||
| 271 | |||
| 272 | 6. Next, click [[image:https://doc.aagon.com/bin/download/ACMP/66/ACMP-Solutions/System/ACMP%20Lizenzen/WebHome/image-20240320164121-5.png?width=36&height=32&rev=1.1||alt="image-20240320164121-5.png" height="20" width="23"]]//Refresh //on the ribbon bar. | ||
| 273 | |||
| 274 | Your new server license key has now been imported, and the license information has been updated. |

