Hi,
In my Linux server with appian 20.4 installed,
the following are the details in the "profile" file in /etc folder --export JAVA_HOME=/data-01/appian/203/appian/java ---- actually this path does not exist in the serverexport PATH=$JAVA_HOME/bin:$PATH:
But when I run the command
echo $JAVA_HOME, I find this --
/usr/lib/jvm/jdk1.8.0_191
I tried removing the java folder, in the above path(/usr/lib/jvm/jdk1.8.0_191) and stopping my Appian services, (firstly the Tomcat) but the jsp commands are unrecognisable. As soon as I restored the Java at the above path, everything resumed fine.
The JAVA_HOME in the profile file refers to a different path while the actual JAVA location used by my services seems to be different.
Can any one guide me to change the JAVA_HOME path?
Can I point my Appian services to use the the Java in this path (/data-01/appian/204/appian/java)? If so where should I set the path for my Appian services to point to this path?
Thanks,
Chetana
Discussion posts and replies are publicly visible
Based on what you posted, this should work - no? You also need to reload your shell for the change to take effect.
export JAVA_HOME=/data-01/appian/204/appian/java export PATH=$JAVA_HOME/bin:$PATH:
Try running the following after making the update to the file:
bash --login java -version
Hi Mathieu,
i have tried the above steps and restared my services and the envi is up and running.
During the tomcat restart , observed the follwing logs --
2022-04-04 08:24:03 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version: 3.10.0-1160.59.1.el7.x86_642022-04-04 08:24:03 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture: amd642022-04-04 08:24:03 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home: /usr/lib/jvm/jdk1.8.0_191/jre
Do you think I need to change the path elsewhere too?
Regards,
chetana
What do you get when you run
java -version
from the terminal?
Here is the response to your query
Looks good to me.
I would suggest you log a ticket with Appian support to investigate why Tomcat displayed that message in the logs.
ok sure Mathieu....
thanks for you help