-
Title
Database agents in a FMS Federation Architecture -
Description
How does RMI work in a Foglight (FMS) Federation architecture?
What database agent pages and functions are not available in Federation?
Which DB metrics are not available in a Federator / Federated Master?
-
Cause
Federation is designed to give an over-whole look on the Agents running in the child FMS machines.
By design, there are no Agent objects running in Federation hence creating new Agents over * Federation* is not possible.
That also means that no topologies can be written to the FMS Federation in Real time, and Federation will show exiting topologies (data) gathered from the FMS child's Agents.Therefore, from the DB Agent perspective running over Federation, the Agent components with on-demand collections that are not expected to work (and hence align with Federation concept) are:
- Call-Back screens
- Global Administration
RMI calls are working, as RMI doesn't require Agent objects.
-
Resolution
There are no call-back screen in the Oracle, SQL Server, and DB2 cartridges. All of the screens except for the Global Administration panel should work with Federation.
The tasks listed below cannot be accomplished from the central Foglight Management Server (the federation master):- Creating agents
- Administering agents
- Viewing a monitored instance from the federation master which is defined under two or more federation child server.