Overriding user name mappings for the same client IP

NAM allows for mapping (inheriting) the monitored user's name between analyzers for a given client IP address. You can use this capability to provide user names for traffic data records that do not have an associated user name and to replace the user name reported by an analyzer of a lower priority with that of the user name reported by an analyzer of a higher priority.

Configuration

To configure the user name mappings in the NAM Server:

Open the Admin console.
There are two ways to open the Admin console. Use the way you prefer:

  • On the NAM Server main menu, select Tools ► Admin console, or
  • In your browser address line, enter:
    http://server_IP_address/DiagConsole
    where server_IP_address is the NAM Server IP address.

In the Configuration management column, click Advanced properties editor.

Use the right arrow to page through to the Advanced Properties Editor - Maps page.

In the Property name column, find MAP_CLASS_IPUserForce-map.

Tip

Paste that string into the search box at the top of the Advanced Properties Editor screen and you will see only matching rows.
MAP_CLASS_IPUserForce-map

In the Value column of MAP_CLASS_IPUserForce-map, paste the following value:
adlex.rtm.repository.ClientIPclientIPserverMap

This setting causes the report server to build a cache of user names and client IP addresses while traffic data is being read by the report server. For a given client IP, the cache stores the user name as it was reported for that session by the analyzer with highest observed priority. The order of priority of analyzers is as follows, starting with the highest priority:

SAP (highest priority)

Oracle Forms

HTTP

Exchange

Citrix

SMB (lowest priority)

Important

The result of setting this configuration property is that – as the report server reads and analyzes monitored traffic records for a given session – the observed user names may be overwritten by the values from the cache for that session.

The exact behavior depends on an additional configuration setting (MAP_IPUserForce-overwriteUserNames). However, regardless of that, if the observed values of user name is empty or is equal to the client IP address, it is overwritten by the values from the cache for that session.

In the Property name column, find MAP_IPUserForce-overwriteUserNames

In the Value column of MAP_IPUserForce-overwriteUserNames, select ON or OFF .

Important

If MAP_IPUserForce-overwriteUserNames is defined and set to ON, the observed user names are overwritten by the values from the cache for that session, if the values from cache originate from traffic records with a higher analyzer priority.

To prevent this mapping, set MAP_IPUserForce-overwriteUserNames to OFF or leave MAP_CLASS_IPUserForce-map undefined.

Click Save to save your changes.

What to do next

  • Restarting the report server is not required. User name mapping is applied to data that is processed after you have configured the inheritance option.
    Data that was already in the report server database before you configured the mapping options are not changed. If this does not meet your requirements, and you want to apply the above configuration changes to historical data, it is necessary to purge the database and restart data collection. Note, however, that the NAM Probe will then be able to supply only the last 7 days of historical data to the report server (this is the default setting, which you can change on the NAM Probe).
  • If you later decide to disable address masking, clear the MAP_CLASS_IPUserForce-map property value and click Save.
    The value of MAP_IPUserForce-overwriteUserNames is meaningless if MAP_CLASS_IPUserForce-map is not set to adlex.rtm.repository.ClientIPclientIPserverMap .