Endpoint Protection

 View Only
  • 1.  How to install SEP using an alternative version of Java?

    Posted Aug 31, 2017 11:06 AM

    I'm pretty sure this is possible because I've heard it mentioned before.

    I would like to install SEP on redhat linux using a different version of Java than is currently installed. I wouldn't want to interfere with whatever the current java is doing, and would want SEP to use the newly installed java version and not touch the existing version.

    Is that install process documented somewhere?



  • 2.  RE: How to install SEP using an alternative version of Java?

    Posted Aug 31, 2017 11:11 AM

    Found this:

    http://www.symantec.com/docs/HOWTO36063



  • 3.  RE: How to install SEP using an alternative version of Java?

    Posted Aug 31, 2017 11:17 AM

    That looks perfect - thanks!



  • 4.  RE: How to install SEP using an alternative version of Java?

    Posted Aug 31, 2017 11:19 AM

    You're welcome.



  • 5.  RE: How to install SEP using an alternative version of Java?

    Posted Aug 31, 2017 02:11 PM

    One issue popped up - I removed the previous installation of SEP (./install -u), copied over the new version of jre files to /opt/Symantec, modified /etc/Symantec.conf to reflect the new location of JAVA_HOME, and ran the install.sh script again.

    After the install.sh script finished running, /etc/Symantec.conf had reverted back to the previous version of JAVA_HOME. It looks like SEP read the system default version of JAVA_HOME and overwrote /etc/Symantec.conf, or a pointer was kept from the previous install that was still pointing at the previous JAVA_HOME.

    Another anomaly I noticed was the the owner of /opt/Symantec/jre1.8.0_144 was 10:143 (not root:root) and all the files in it were owned by 10:143. I think that happened while running the install script because I would have noticed the weird ownership if it happened before hand.

    Any suggestions?



  • 6.  RE: How to install SEP using an alternative version of Java?

    Posted Aug 31, 2017 03:27 PM

    Actually, I think it was an ownership problem that I missed initially after un-tarring the gz file I got from Oracle. When I repeated my earlier steps, the gz file had root:root ownership, but the un-tarred files had the 10:143 ownership. I overlooked that in the subsequent steps. When the ownership was correctly set and the /install.sh -i was run again, the /etc/Symantec.conf kept the correct path to java