Values: No (default) or Yes
Description: Use the client node name that is taken from the LDAP connection object when recording node statistics. The default (No) behavior is to take the node name that is provided by the client application.
The Node statistic that is displayed on the Statistics tab of the Global User property page and other objects' property pages is not always updated when other statistics such as the date, time, userid, and username are. This behavior is a result of the way the Node name is determined. By default, the node name must be provided by client applications in their requests. If the clients fail to do so, or the client submits a high-level operation, such as Synchronize, that spawns child operations to carry out the individual object updates, the server has no Node value to use to update that statistic. To rectify this problem, use the Node Stats From Connection configuration parameter. Change it's setting from the default No to Yes to select the alternative Node statistic algorithm.
The alternate algorithm uses the Node information that is obtained from the LDAP connection, which identifies the host that was the immediate client sending the request. This is often the same as the originating client, but can be another system.
For example, requests that originates from the CA IdentityMinder Server would be recorded as originating from the computer where the CA IdentityMinder Server is running, not the computer where the administrator is running a web browser. Also, if the clients connect to a dXRouter process for a failover or load-balancing between replicated Provisioning Servers and have the dXRouter send the request to the Provisioning Server, you should not enable the Node Stats From Connection parameter. It will result in all Node statistics indicating the router system.
|
Copyright © 2013 CA.
All rights reserved.
|
|