What we are doing is using BladeLogic (TrueSight Server Automation... I think that's the new name) to stop the agent, erase those folder contents, and provide new archives straight from Oracle. This has been working great in our environment.
Hi Josh, thank you for your reply. Customer asking like the below.
Please remove the following Java 1.6 binaries from the list of Non-Production RHEL7 Servers below:
Please let us know if we delete the JRE folder in Linux servers, is there any interrupt to monitoring that client RHEL servers?
It depends on what you are monitoring. Many customers don't just use OS KM, but also application specific KM. Oracle, Log, Scripting, so on. Many if not all of these require Java to be installed either in the patrol folder or in the system path.
Let me also add one more note to this...
If you create a package in TSPS that requires java and you do not include java from the repository, the package will fail to install on the operating system. I found that out the hard way.
What I wanted to do was do a clean install of agent and KMs and THEN add a fresh version of java on top from oracle, but the installer seems to look for certain java files to be included in install files path.
is there any interrupt to monitoring that client RHEL servers if you remove those java binaries under $PATROL_HOME?
-> It depends if there is a KM loaded and using this java binary. Not all the KMs require java, so once you know the KMs loaded on the Agent you will have to check the km documentation whether a java is required for this KM.
For instance the Oracle KM version 9.7 requires java binary, but this one can be installed anywhere on the system, but you can change the java path used by the KM by using pconfig variable /OraNetConfig.javaHome and use for instance the binary installed under /usr/bin/
PATROL for Web Services KM also requires, see as well