I recently inherited a WFM upgrade request. The initial install was done by someone else, several years ago, with 8.1.0 components.
I did a manual upgrade of all the components to the latest 8.1.2 hotfixes. I also upgraded Tomcat and the JDK, and tuned Tomcat and WFMWeb as suggested in the latest "how to".
However, I've ended up with two issues:
1. WFM Daemon cannot be started via SCI. The service on the host goes into a "starting" state, but fails once the startup timeout expires, and goes into a "stopping" state in Windows service manager. When the service shows "stopping", all WFM components in SCI goes Unknown until the service stops. No logs files are produced.
Starting the Daemon on the service works, but produces no logs.
Starting the Daemon via startserver.bat works, and produces logs. It's also the only scenario where WFM Daemon shows "Started' in SCI.
My suspicion is that I need to upgrade LCA, but perhaps someone else has encountered this issue?
2. I only have access to the solution via VPN, and cannot access the WFMWeb url from anywhere other than IE8 on the Win2003 WFM host. I've opened around 20 WFM sessions, and requested various schedules and performance stats each time. The login page pops up immediately, as does the authentication into WFM. But there's around 60 seconds in WFM Supervisor while "checking availability of java environment"is displayed. Once that's out of the way, the performance is excellent, with no delay between page changes.
The delay was not there before the upgrade :|
