Page History

...

Requirements for setting up Custom Applications

To use Custom ApplicationApplications, you must:

• Install License Statistics Agent and connect it to the License Statistics server.
• Add one or more Agent groups, if none have yet been added. (Agent groups can also be added on the fly when configuring the application for monitoring.)
• Configure the applications to be monitored, as described in this section.
  Currently, each

...

Adding applications for Application Monitoring

Configuring Custom Application monitoring

You After you have connected License Statistics Agent to the License Statistics server and added one or more Agent groups, you can configure applications to be monitored , as described below. You can add an "Application" License Server type or using the  Application Monitoring Administration option. by:

• Adding a "Custom Application" license server

or

• Using the "Custom Applications" option from the Administration menu.

The following sections describe each method.

Add an "Application" License Server type

Anchor
lic_server_option lic_server_option

Add a "Custom Application" license server

One method for adding a custom application to monitor is by adding a license server, as described below.  

1. Select License Servers from the Administration section in the left navigation pane.
2. From the General tab, click the Add button located at the bottom left of the License Servers grid. A Create License Server dialog opens to allow you to configure the new license server. 
3. Enter a name for the license server.Go to Administration -> License Servers -> General tab -> Add button.
   Image Removed
   The license server is enabled by default. You can toggle this option on and off as needed.
4. From the License Manager Type drop-down list, choose "Custom Application."
   
   Image Added
   
   
5. Fill in the license server settings as needed and toggle the Enable option on/off in the same manner as for other license server types. See Adding and editing license servers for complete information about license server configuration.
6. After you have completed all required fields for the license server, click Click Next to proceed to the End User Custom Application Monitoring tab. 
7. The Enable End User Custom Application Monitoringoption is checked toggled on by default. You can toggle this option on and off as neededThis option must be toggled on in order to configure Custom Application monitoring.
8. From the Application drop-down list: 
   Select an existing application to monitor:
   Image Removed
   Or:
   
   1. 1. If the application you want to monitor already exists, select the application. In this case, no further configuration is needed, and you can skip to step 11.
         Or
         
      2. If the application does not already exist, create a new Custom Application on the fly by typing the name of the new application you want to monitor and then clicking on the name. (The application name is denoted with "(Create new)" when the name you type does not already exist, as illustrated below.)
         
         Image Added
         
         
   Type the name of a new application to monitor:
   Image Removed
   2. If you are adding a new application (step 8b):
   3. 1. Complete the basic configuration
      for the application
      1. information, including the name that you want to use for the application in reports; the executable name
      ,
      1. ; and an optional description
      , and
      1. . (See How the executable name is used for additional information regarding how executable names are used for Custom Application monitoring.)
      2. Select which Agent groups will be monitoring the application
      . 
      Image Removed
      1. .
         Or
      2. If the Agent group does not already exist, create a new Agent group on the fly by typing the desired name in the Agent Groups drop-down list area and then clicking on the name. (The group name is denoted with "(Create new)" when the name you type does not already exist.)
         
         Image Added
         
         
   4. Click Save to close the configuration dialog, and then click Save and Close to add the new License Server license server and return to the License Servers page.
   5. You In the General tab of the License Servers page, you will now see under the General tab that that the license server with the new application has been added for monitoring. In our illustration, we've configured Application Monitoring to gather usage details about the "notepad app"application being monitored by Agents that belong to the groups "Test Group" and "Test Group 2."
      Image Removed
      

   Add an application directly from Administration options  

   You can add an application to be monitored directly from the Administration options.

   1. 
      
      Image Added
      
      
   2. Optionally, you can set up License Harvesting for the application.

   Anchor
   custom_app_option custom_app_option

   Use the Custom Applications option from the Administration menu  

   As an alternative to adding a license server as described above, you can use the Administration menu's Custom Applications option to configure a new Custom Application for monitoring, as described below.

   1. Select Custom Applications Select Application Monitoring under the Administration section in the left pane.
   2. Click Add. The Add Custom Application form opens.
      
      Image Added
      
      
   3. Fill in the Name and Executable Name fields.  (See How the executable name is used for additional information regarding how executable names are used for Custom Application monitoring.
      Image Removed)
   4. Select which Agent groups will be monitoring the application
      Or
      Create a new Agent group on the fly by typing the desired name in the Agent Groups drop-down list area and then clicking on the name. (The group name is denoted with "(Create new)" when the name you type does not already exist.)
      
   5. Click Next to proceed to the Monitoring tab.
   6. Toggle on Enable Monitoring. (If Enable Monitoring is not toggled on, the rest of the tab will be blank.)
      
      Image Added
      
      
   7. Click the Add button in the lower left of the License Servers grid.
   8. Fill in the form Click Next to add the new License Server license server that will be used by the applicationCustom Application. (Note: The License Manager Type is already automatically set to "Custom Application" and cannot be changed.)
      
      Image Added
      
      
   9. Click Save to save the new Custom Application ."
      Image Removedlicense server. You will see that the license server has been added to the License Servers grid in the Monitoring tab.
      
      Image Added
      
      
   10. Click Next to proceed to the License Harvesting tab, and optionally, set up set up License Harvesting for the application.
   11. Click Save to save the configuration and return to the Applications page. You will see that the new application has been created and is included in the Applications grid.
       
       Image Added

   Anchor
   executable executable

   How the executable name is used

   The executable name provided during Custom Application setup (described in the instructions above) is used on the host to detect whether the application is running. The executable name is processed differently, depending on what you enter in this field during Custom Application setup, as detailed below.

   • The executable name is not case-sensitive. For example, "NOTEPAD.exe" is processed the same as "notepad.exe".
   • When you provide the full executable name, the name will match only that specific executable. For example, if you enter the executable name "notepad.exe," it will only match Microsoft Notepad instances and will not match Notepad++ instances, as illustrated below.
     
     

   Image Added

   
   

   • When you provide a partial executable name, it will match any executable name that contains those characters; for example, "app" will match "some_app1.exe," "some_app2.exe," etc. Additionally, note that: 
     • The applications must have the same vendor; otherwise, monitoring will fail, because License Statistics does not support multiple vendors for a single application
     • To monitor multiple processes that have different vendors, you must add each process as an individual custom application with a separate license server 
   • When you provide a full path for the executable name, it will match only the instances in the explicitly specified path. For example, you can specify the full path "C:\Windows\System32\notepad.

   ...

   • exe" as the executable name to specifically monitor only the Microsoft Notepad applications found under that path, as illustrated below.
     
     Image Added