So I uninstalled iManager completely from one of my fully patched 24.3 servers, and reinstalled it through yast. iManager works after the installation, but has no plugins installed (in Yast, the famous "installing imanager plugins" didn't appear either).

Trying to add or update *any* plugin results in the same as in every other server I tried: Absolutely *nothing*, except a (IMHO fake) display in iManager itself that it is installing the plugins, which never moves forward.

Watching the tomcat logs, in fact it doesn't seem to be doing anythign at all.

To which java version does JAVA_HOME in /etc/opt/novell/tomcat/conf/novell-tomcat.conf point ?

iManager only works correctly with jre-1.8.0-ibm, the openjdk java did not allow installation of plugins. That problem should have been addressed by the latest updates to OES, but maybe it did the opposite to iManager.

Openjdk. Seems to be the same on all current servers, no matter their history. Totally fresh installed or dozens of version upgrades.

Changing it to java-1.8.0-ibm-1.8.0 (and of course restarting tomcat) does not make any difference though. In the sense that the tomcat process still runs in openjdk, as that is the link /usr/lib/java points at. The setting in the conf file seems to be entirely pointless.

But of course I can find a way to run tomcat in the IBM java.

You are correct I see this at my servers, too.

But for the ibm-java to work you have to set JAVA_HOME to "/usr/lib64/jvm/java-1.8.0-ibm-1.8.0/jre" I just found out after looking in older catalina logs, which show this path. After changing to this path, the catalina log now shows the Java vendor "IBM".

Right. With the JAVA_HOME set this way, it runs in the IBM Java.
Nonetheless, this does not change the core problem. No way to install or update plugins, same symptoms as with openjdk.

Right. With the JAVA_HOME set this way, it runs in the IBM Java.
Nonetheless, this does not change the core problem. No way to install or update plugins, same symptoms as with openjdk.