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 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 additional data sources are registered.

Multiple user accounts might share a username in different data sources. But some account parameters might differ. Manual editing is required in this situation. For example, assume that you have a user 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 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

When you register a data source that contains SNMP profile definitions, those profiles are automatically added 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 duplication of these parameters is detected, CA Performance Center retains the profile whose timestamp indicates the most recent modification.

If a duplicate Profile Name is synchronized but the User or Community String values do not match, CA Performance Center saves the new profile, appending a number to the name. For example, the first profile named Boston remains Boston. The second profile becomes Boston(1).