Skip to main content

Mapping Generated User Names and Filtering by Application-Server Host

Usage events for some vendors result in a large number of randomly generated user names, where the user names contain appended characters and/or numbers. For example, if users access applications using a browser, the usage events are assigned randomly generated user names (user473796471_137, user1946733051_472, and so on). This causes issues because the generated user names do not appear in organizational structures, and the volume of the data impacts the organizational structure–import process.

To resolve this issue and prevent future report log–import issues, you must create an XML mapping file (vendorFeatureForRandomUser.xml) to map the randomly generated user names to fixed user names. In the XML file, you specify which vendor and feature-name combinations should map to a given user name. As a result of the mapping, you can report on consolidated usage.

In addition, you can filter which generated user names are consolidated, by the application-server host (the user host name in the usage event). That is, you can specify in another XML file, vendorHostForRandomUser.xml, which application-server–host names are relevant when mapping generated user names to a fixed user name.

The two XML files enable you to consolidate randomly generated user names on the basis of the following:

  • vendor + feature + application-server host

Mapping Generated User Names to Fixed User Names​

Map randomly generated user names to fixed names to allow for consolidated reporting.

To map generated user names to fixed user names:

  1. Create an XML file with the name vendorFeatureForRandomUser.xml. The XML file should have the same format as the following Example XML File: Mapping Generated User Names.
  2. Copy the file to the user data directory. By default, this directory is located at <fnmea_install_directory>``\data.

At the time of report-log import, FlexNet Manager for Engineering Applications checks the XML file for any changes. If there are changes to the file (if the file has been updated), FlexNet Manager for Engineering Applications will read the file for new mappings.

Example XML File: Mapping Generated User Names​

This file must be named vendorFeatureForRandomUser.xml.

<?xml version="1.0" encoding="UTF-8"?>
  <vendorDaemons>  
     <vendorDaemon name="acmeCo">    
         <feature name="designExec" newUserName="RollupUser1"/>    
         <feature name="projectAdmin" newUserName="RollupUser2"/>    
         <feature name="projectEdit" newUserName="RollupUser3"/>  
     </vendorDaemon>  
     <vendorDaemon name="sampleCo">    
         <feature name="drawSet" newUserName="RollupUser4"/>    
         <feature name="graphics" newUserName="RollupUser5"/>    
         <feature name="proDraw" newUserName="RollupUser6"/>    
         <feature name="proMap" newUserName="RollupUser11"/>    
         <feature name="workShop" newUserName="RollupUser12"/>  
     </vendorDaemon>
  </vendorDaemons>

Filtering the Mapping by Application-Server Host​

You can refine the user-name mapping by filtering the mapping by application-server host.

To filter mapping by application-server host:

  1. Create an XML file with the name vendorHostForRandomUser.xml. The XML file should have the same format as the following Example XML File: Filtering by Application-Server Host.
  2. Copy the file to the user data directory. By default, this directory is located at <fnmea_install_directory>``\data.

Example XML File: Filtering by Application-Server Host​

This file must be named vendorHostForRandomUser.xml.

<?xml version="1.0" encoding="UTF-8"?>
  <vendorDaemons>  
     <vendorDaemon name="acmeCo">    
         <feature name="designExec" newUserName="RollupUser1"/>    
         <feature name="projectAdmin" newUserName="RollupUser2"/>    
         <feature name="projectEdit" newUserName="RollupUser3"/>  
     </vendorDaemon>  
     <vendorDaemon name="sampleCo">    
         <feature name="drawSet" newUserName="RollupUser4"/>    
         <feature name="graphics" newUserName="RollupUser5"/>    
         <feature name="proDraw" newUserName="RollupUser6"/>    
         <feature name="proMap" newUserName="RollupUser11"/>    
         <feature name="workShop" newUserName="RollupUser12"/>  
     </vendorDaemon>
  </vendorDaemons>

In this case, the random user names generated by feature usage (as specified in the file vendorFeatureForRandomUser.xml) will be consolidated and mapped to a fixed user name only if the application-server host for the vendor daemon is specified in the file vendorHostForRandomUser.xml.