Shared Components java version - can we delete older 32 bit jre after upgrading to r12

Products

• Autosys Workload Automation

Issue/Introduction

Is the JAVA under /opt/CA/SharedComponents/JRE/1.5.0_11  still in use after upgrade to version 12.0?

We are receiving several critical vulnerabilities on this version and need to upgrade or removed the java in this location.

Environment

Release : 12.0

Component : WORKLOAD CONTROL CENTER

Resolution

AutoSys and WCC R12 are 64 bit applications.  Any JRE(s) the products would be using as of R12 would need to be 64 bit.  If you have a 32 bit jre left over after upgrading to R12 it should no longer be needed if you are at R12.

Details from a fresh r12.0 install that was then upgraded to sp1:
 
# /opt/CA/SharedComponents/EmbeddedEntitlementsManager/jre/bin/java -version
openjdk version "1.8.0_242"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_242-b08)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.242-b08, mixed mode)

# /opt/CA/WorkloadAutomationAE/jre/bin/java -version
openjdk version "1.8.0_252"
OpenJDK Runtime Environment (build 1.8.0_252-b09)
Eclipse OpenJ9 VM (build openj9-0.20.0, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20200416_608 (JIT enabled, AOT enabled)
OpenJ9   - 05fa2d361
OMR      - d4365f371
JCL      - cfa47e66cd5 based on jdk8u252-b09)

And the following links 
/opt/CA/WorkloadAutomationAE/wcc/jre
/opt/CA/WorkloadAutomationAE/SystemAgent/WA_AGENT/jre
that point to the 
/opt/CA/WorkloadAutomationAE/jre

Before removing any older 32 bit JRE check that you have no environment variables pointing to that old JRE.
Check files such as the $AUTOUSER/autosys.sh.* files and startup scripts /etc/init.d and /etc/profile.CA

If you find nothing pointing to it then first try renaming the directory.
Then try normal operations such as starting and stopping the product, issuing commands, etc...
If all is well with the older JRE renamed then remove it.