Previous Topic: How Configuration Data from Data Sources Is HandledNext Topic: View a List of Data Sources


Redundant Definitions in Data Sources

During registration, CA Performance Center imports user accounts and other configuration parameters from the data sources. Conflicts or duplicates are handled using the processes that are outlined in the following sections.

Redundant User Accounts

A user can have two different accounts with the same name in different data source products. The resulting user account retains the password of the first account that is synchronized. The unique role rights and permissions from the second or third account are added to the account as you register more data sources.

Multiple user accounts sometimes share a username in different data sources. Some account parameters differ. Manual editing is required in this situation. For example, assume that a user that is named Robert in CA Network Flow Analysis, and a different user, also named Robert, in CA Application Delivery Analysis. In this case, CA Performance Center creates one account that is named Robert. The role rights and permissions from both data sources are merged into the new account. To preserve the distinct role rights of the two accounts, create an account with a unique username.

Redundant SNMP Profiles

Registering a data source that contains SNMP profile definitions automatically adds the profiles to CA Performance Center. The profiles are distributed to the other registered data sources during the next synchronization.

When a data source is added, CA Performance Center minimizes duplication of SNMP profiles by comparing the following values to existing profiles:

If CA Performance Center detects duplicate parameters, CA Performance Center retains the most recent profile, as indicated by the timestamp.

CA Performance Center saves and appends a number to any duplicate Profile Name that is synchronized, but where the Community String values do not match. CA Performance Center the saves the new profile. For example, the first profile that is named Boston remains Boston. The second profile becomes Boston(1).