Customer observed that their EEM server.log has not received any updates since it was started.
EEM server.log may not have any info if the logging levels the server.xml is set to, has not generated any content
Release : 11.3.6
EEM's server.log may not get additional entries if the set log levels have not generated any content. EEM's audit.log is a better one to look at in this case, as all EEM operations get logged there. Some times there maybe a few seconds delay in seeing updates to this file, but EEM constantly writes to this file (as long as users/applications are using EEM).
In case of Autosys/WCC, if they are configured to connect to multiple EEM servers for High Availability, then we need to check which EEM's 5250 port the application is currently connecting to:
netstat -an|grep 5250
tcp 0 0 10.0.0.1:56728 10.0.0.2:5250 ESTABLISHED
The above shows that the current server (IP: 10.0.0.1) is connected to EEM server (10.0.0.2 on port 5250 ). This way we can identify which EEM server, the Autosys server currently connecting to.