• |
10 ms or lower in most cases leads to optimal results. |
• |
10 ms to 100 ms might be acceptable, depending on the complexity and frequency of browser interface requests. |
• |
100 ms and higher is likely to result in significant slowness. |
The Federation Master uses the RMI 1099 port during the connection setup process. In the server.config file of each Federated Child, specify the server.federation.port property to identify this port number.
IMPORTANT: Starting in version 5.9.2, Foglight® for Java EE Technologies no longer supports Nexus Federation. Without Federation, all application servers that could possibly participate in servicing the same request (through RMI or other remote calls) should be connected to the same Nexus. |
The Federation Master is a Foglight® Management Server that has been configured to incorporate the data of federated instances. A Federation Master can not be utilized as any other Management Server (for example, no connected clients, agents, standard rule analysis).
When installing a Management Server, federation is by default disabled. When you install a Management Server, the server does not know if it is going to operate as a Federation Master or as a normal server. The server identifies this only on startup, by checking the server.federation variable in the server.config file. If this variable is set to TRUE, the server makes a number of changes that are necessary for it to run efficiently (given a certain load).
A Federation Master must always be started with server.federation variable set to TRUE. If a Federation Master starts up, even just one time, as a normal server, it makes modifications to the server that deplete its performance as Federation Master.
When upgrading a Federation Master, you must first verify that the server.federation variable was not changed to FALSE before you restart the server.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center