6. RESULTADOS DEL TRABAJO
6.1 ANÁLISIS DE LA PRIMERA CATEGORÍA: TRATAMIENTO DE LA
Licensing configurations
In a typical AE Services configuration, a standard license file is installed on each AE Services server, and the licenses in that license file are acquired through a local WebLM server running on the AE Services server (or running on Cdom for the AE Services on System Platform server). However, the following configurations are also possible:
• Multiple AE Services may be configured to acquire their feature licenses from a single WebLM server where a standard license file is installed. In this configuration, feature licenses can “float” from one AE Services server to another as they are needed.
• With enterprise-wide licensing, an enterprise license file is installed on a master WebLM server. Feature licenses can be allocated from the enterprise license file to multiple AE
Services servers. The local WebLM server acquires the feature licenses from the AE Services servers. If any of the feature licenses from the enterprise license are not allocated to the individual AE Services servers, these licenses can also float among the AE Services servers.
Note:
For AE Services, the use of floating licenses is not recommended. If you are using floating licenses, adjust your WebLM configuration appropriately.
Note:
For more discussion on licensing configurations, see Enterprise Wide Licensing for the Avaya Application Enablement Services.
Reserving unified desktop licenses
Unified desktop licenses are type of licenses used by TSAPI - typically for Microsoft Office
Communicator (MOC) or IBM Sametime users. These users connect to AE Services via DMCC, but their licenses are controlled by TSAPI. Thus, like the TSAPI basic user licenses mentioned in the previous section, accessing the WebLM server for each license request can have a noticeable effect on performance. For example, if your LCS, OCS, Lync, or IBM Sametime server initiate monitors for hundred MOC or for hundred IBM Sametime users, the TSAPI Service will normally acquire a license from the WebLM server, for each of these users, one at a time. You can reduce the time by reserving unified desktop licenses. When you reserve unified desktop licenses, the TSAPI Service acquires all of the reserved licenses at startup time by making a single request to the WebLM
server. If more than the reserved amount of unified desktop licenses are used at any given time, TSAPI will acquire the extra licenses from the WebLM server, one at a time.
About this task
After installing or upgrading to AE Services 6.3 or later, perform this procedure to: • Ensure the TSAPI Service starts successfully after a system reboot.
• Optimize the performance of the TSAPI Service.
Procedure
1. Using a web browser, log into the AE Services Management Console.
2. From the AE Services Management Console main menu, select Licensing > WebLM Server Access. A new browser window appears displaying the Web License Manager
page.
3. Using the Web License Manager page, log into WebLM.
4. Click Application_Enablement to view the AE Services licensed features. 5. Note the number of Unified Desktop users that are licensed
(VALUE_AES_AEC_UNIFIED_CC_DESKTOP). 6. Log out of WebLM.
7. From the AE Services Management Console main menu, select Licensing > Reserved Licenses. The Reserved Licenses page appears.
8. In the Reserved Unified Desktop Licenses box, enter the number of Unified Desktop users that are licensed. This is the value you noted in Step 5.
9. Click Apply Changes.
10. On the Apply Changes to Reserved Licenses page, click Apply.
11. From the AE Services Management Console main menu, select Maintenance > Service Controller.
12. On the Service Controller page, select the TSAPI Service check box. 13. Click Restart Service.
14. On the Restart Service page, click Restart.
Reserving TSAPI user licenses
About this task
After installing or upgrading to AE Services 6.3 or later, perform this procedure to • ensure the TSAPI Service starts successfully after a system reboot
• optimize the performance of the TSAPI Service
The TSAPI Service acquires its licenses from the WebLM server. Depending on the nature of your TSAPI applications and the number of extensions under TSAPI control, accessing the WebLM server for each license request can have a noticeable effect on the performance of your application. For example, if your TSAPI application initiates monitors for several hundred extensions during its initialization, the TSAPI Service will normally acquire a license from the WebLM server for each of these extensions one at a time. You can reduce the time that it takes your TSAPI application to initialize by reserving TSAPI licenses. When you reserve TSAPI licenses, the TSAPI Service acquires all of the reserved licenses at startup time by making a single request to the WebLM server. If more than the reserved amount of TSAPI licenses are used at any given time, then TSAPI will acquire the extra licenses from the WebLM server one at a time.
Procedure
1. Using a web browser, log into the AE Services Management Console.
2. From the AE Services Management Console main menu, select Licensing > WebLM Server Access.
A new browser window appears displaying the Web License Manager page. 3. Using the Web License Manager window, log into WebLM.
4. Click Application_Enablement to view the AE Services licensed features. 5. Note the number of TSAPI simultaneous users that are licensed
(VALUE_AES_TSAPI_USERS). 6. Log out of WebLM.
7. From the AE Services Management Console main menu, select Licensing > Reserved Licenses.
The Reserved Licenses page appears.
8. In the Reserved TSAPI Basic User Licenses box, enter the number of TSAPI simultaneous users that are licensed. This is the value you noted in Step 5 of this procedure.
9. Click Apply Changes.
10. On the Apply Changes to Reserved Licenses page, click Apply.
11. From the AE Services Management Console main menu, select Maintenance > Service Controller.
12. On the Service Controller page, enable (check) the TSAPI Service check box. 13. Click Restart Service.
14. On the Restart Service page, click Restart.
Reserving DMCC licenses
About this task
After installing or upgrading to AE Services 6.3 or later, perform this procedure to • ensure the DMCC Service starts successfully after a system reboot
• optimize the use of the DMCC licenses
Like the TSAPI Service, the DMCC License Service acquires its licenses from the WebLM server. DMCC licenses are used to register a DMCC endpoint (station) with Avaya Communication
Manager for first-party call control. A DMCC license is required for each endpoint that is registered through DMCC.
Depending on the nature of your DMCC application and the number of endpoints it registers via DMCC, accessing the WebLM server for each license request can have a noticeable effect on the performance of your application. For example, if your DMCC application registers one or more endpoints for each of several hundred telephone extensions, the DMCC License Service will normally acquire a license from the WebLM server for each of these endpoints. Each license request to the WebLM server will be completed one license at a time.
You can reduce the time it takes your DMCC application to register these endpoints by reserving DMCC licenses. When you reserve DMCC licenses, the DMCC License Service acquires several licenses at the time of the first registration by making a single request to the WebLM server. One license will be allocated immediately for the initial registration, while the rest of the licenses will be held in reserve for future registrations. If more licenses than the specified reserve amount are required (that is, there are more concurrently registered endpoints than reserved licenses), then another increment of DMCC licenses (equal to the reserve amount) will be acquired from the
WebLM server. License acquisition is performed in increments of the specified reserve amount up to the maximum number available on the WebLM server. Similarly, as endpoints are unregistered, the freed licenses will be released back to the WebLM server in similar increments (equal to the reserve amount). Note that when the last endpoint is unregistered, all of the remaining reserved DMCC licenses will be released back to the WebLM server.
Procedure
1. Estimate the maximum number of endpoints that will be registered via DMCC. If you are sure this is a firm limit, you can use this number as the value for the Reserved DMCC Licenses in the following steps. If this is not a firm limit, it may be wiser for you to use a smaller value for the Reserved DMCC Licenses in the following steps. DMCC will acquire and release
licenses from the WebLM server in increments (chunks) equal to this reserve value.
For example, if you estimate the maximum number of registered endpoints to be 1000, then you can perform one of the following actions:
• Specify 1000 as the value for the Reserved DMCC Licenses. In this case, 1000 DMCC licenses will be acquired from the WebLM server on registration of the first endpoint. Note that no licenses will be released back to the WebLM server until the last endpoint is unregistered.
• Specify a smaller number (for example, 50) as the value. In this case, only 50 licenses will be acquired on registration of the first endpoint, another 50 licenses will be acquired on registration of the 51st concurrently-registered endpoint, etc. Note also that, in this case,
as endpoints unregister and no longer need the DMCC licenses, the DMCC licenses will be released back to the WebLM server in chunks of 50 (for this example).
2. Using a web browser, log into the AE Services Management Console.
3. From the AE Services Management Console main menu, select Licensing > Reserved Licenses.
The Reserved Licenses page appears.
4. In the Reserved DMCC Licenses box, enter the value you estimated in Step 1 of this procedure.
5. Click Apply Changes.
6. On the Apply Changes to Reserved Licenses page, click Apply.