If you re-configure a WebSphere Agent so that APMUI will display the server's alias name instead of the complete name, you may see that the alias name is not displayed. What has been observed, is that the order that you restart the agent and the server after reconfiguration affects what is displayed in APMUI.
1. After re-configuration, WAS server is restarted then the WAS agent is.
2. After re-configuration, WAS agent is restarted, then the WAS server is.
The new agent name takes effect when the WAS server is restarted.
When WAS agent is started, it launches a standalone process and trying to collect data without the data collector. It is called DC-less mode. This mode is to provide resource monitoring function before the data collector works(the data collector works after WAS restart). The DC-less process stops collecting data once it detects the data collector working.
In the second case, the DC-les process was started during agent restart and before WAS server restarted. it still uses the old agent name to collect data. After WAS
is restarted, the data collector starts to use the new agent name. But the DC-less process does not recognize the data collector as it is using different agent name. Then both the data collector and DC-less process collects data and sends to the server.
Once the WAS agent is restarted again after WAS server restart, the DC-less process will now use the new agent name, detects the data collector and stops collecting data. And after several minutes, the new name will displayed on APMUI.