After apply this solution but problem remain the same. I am very sure java 1.8 had installed and jre 1.8 exported into the path correctly. I even set it in sosite file per your suggestion but the problem remain the same.
Unfortunately, no respond from any broadcom staff. no KBA available. no solution.
Checking Java Version
No java version found
*****************************************************************************
err = 1
Error: A minimum of Java 8 is required for the Applications Manager install
Fatal Error occurred - check the log /opt/appworx/install/aw_install.log
jvm_bits not defined, set to 32 ==================
Requested processes "all" not running
stopso done
Installation exited with errors
*******************************************************************************
*******************************************************************************
done.
Original Message:
Sent: 06-03-2019 12:01 PM
From: Jason Eckelstafer
Subject: Re: AM v9.3 startso problem
The other option is you can set it in your sosite file instead of the .profile. This will ensure it's executed prior to running startso.
Linux: JAVA_HOME=/apps/am/master/jre;export JAVA_HOME
Windows: SET PATH=D:\AM\Agent\jre\bin;%PATH%
Sorry, I can't find the actual KBA due to the forum migration.
Original Message:
Sent: 05-06-2019 04:10 PM
From: Mayfield
Subject: Re: AM v9.3 startso problem
Traced this to the Linux account's PATH. Not sure why, no changes have been made to the Linux user, nor to AppMan since upgrading to 9.3 a month ago, but it appears that the java home path (set in .profile) is not feeding into PATH at login like it normally does. After logging in I manually exported the java home path to PATH and that worked. We were able to start AppMan and are once again running. We continue to research why this is occurring. A second AppMan account on this very same server is fine. Gremlins.