A meshed federation is similar to a hierarchical federation in that it may have tiers. The primary difference is in the configuration of the connections between the servers. A meshed federation can allow any CA User Activity Reporting Module server in the network to query, and report on, the data in all of the other CA User Activity Reporting Module servers. The capabilities for reporting depend on the relationships you create between the servers.
For example, in a meshed federation, the servers may interconnect only within a vertical branch. This means all CA User Activity Reporting Module servers in that branch would have access to all other CA User Activity Reporting Module servers in the same branch. This is in direct contrast to a CA User Activity Reporting Module server in a hierarchical federation, which can produce reports only on the servers beneath it in the hierarchy.
In a ring or star formation, every CA User Activity Reporting Module server is configured to be a child of all of the other servers. When you request report data from any one CA User Activity Reporting Module server, you see the data for all CA User Activity Reporting Module servers in the network.
The meshed federation allocates two or more CA User Activity Reporting Module servers as primary and uses servers in federation without respect to their placement in the network. The servers configured as children are also configured to view the children in the same or other branches as federated to them. For example, if you had two CA User Activity Reporting Module servers, A and B, you could create a meshed federation by making B a child of A, and A a child of B. This is the expected configuration when you are using two or more management servers.
|
Copyright © 2013 CA.
All rights reserved.
|
|