Understanding HP SIM's Federated Search Architecture

3
Figure 1: This is an example of a distributed Federated CMS setup in a large enterprise company where each
CMS manages the maximum HP recommended number of servers. In this example, the federated search would
return 20,000 servers in addition to other systems, such as iLO management processors and switches.
HP SIM
Houston
5000
Servers
5000
Servers
New York
5000
Servers
HP SIM
HP SIM
HP SIM
(main CMS)
5000
Servers
London
Hong Kong
HTTPS
SOAP
protocol
HTTPS
SOAP
protocol
HTTPS
SOAP
protocol
Implementing a Federated Search
To maximize security, carefully plan the authorization of the role-based accounts that configure the
Federated CMS and perform searches. Configuring a Federated CMS is easy and secure.
Setting up role-based authorization
The user account of the person who configures the federation of CMSes must be a full rights user with
authorization to configure the main and remote CMSes. The user account of the persons who perform
searches must have authorization on the main and remote CMSes to query the remote CMSes they
will search.
By default, the main CMS uses your main CMS user account when making requests to the remote
CMSes.