Adding a custom configuration

In addition to using the provided user configuration file, you can create a custom plug-in configuration.
Note: Custom configurations collect the static data from end user machines, such as emulator installations and their resource files, but do not collect data from emulator processes.
  1. In the HAA portal , click User Configuration from the side panel.
  2. Select User configuration from the drop-down list.
  3. At the bottom of the user configuration file, under pluginFamilies, add the custom product entry. For example:
    ,
        {
          "generic": {
            "vendorName": "MyVendor",
            "productName": "BlueZone"
          }
        }
    Note: productName must be unique.
  4. Click SAVE. A message appears telling you that the custom emulator has been created and that you should now complete its plug-in definitions.
    When you click SAVE, a new default plug-in configuration is created on the server side:
    {
      "family": {
        "generic": {
          "vendorName": "MyVendor",
          "productName": "BlueZone"
        }
      },
      "pluginDefinition": {
        "productFilters": [
        ],
        "extensions": [
        ],
        "processes": [
        ]
      }
    }
  5. Click OK.
  6. In the new configuration file, complete the product filters and the extensions that the product should collect. For example:
    {
      "family": {
        "generic": {
          "vendorName": "MyVendor",
          "productName": "BlueZone"
        }
      },
      "pluginDefinition": {
        "productFilters": [
              {
                "vendorNameRegEx": [
                  "(?i)(Rocket)"
                ],
                "productNameRegEx": [
                  "(?i)(.*)?BlueZone!(.*)?"
                ],
                "versionRegEx": [],
                "addon": false
              }
        ],
        "extensions": [
          {
            "ext": "vb2",
            "resourceType": "MACRO",
            "trueVerifier": {}
          }
        ],
        "processes": [
        ]
      }
    }
  7. Click SAVE.

    The new configuration is propagated to end users at the time specified in the Service configuration file in MessagesUploaderTaskConfiguration cronSchedulerExpression.