What are the effects of removing Java_home on a client machine?
search cancel

What are the effects of removing Java_home on a client machine?


Article ID: 39466


Updated On:


CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) Workload Automation Agent



What are the effects of removing JAVA_HOME on a client machine?


We're running Autosys R11.3.5 = Incremental 3 with Sybase 15.7 at the back end. During the installation, the package that is pushed out on application team servers is a combination of the R11.3.5 agent and the client. The JAVA_HOME variable is set to $AUTOROOT/JRE_WA/1.6.0_33. This preset value of JAVA_HOME is causing a number of app team java jobs to fail. To prevent this we're planning to remove JAVA_HOME export statement from the $AUTOUSER/autosys.sh.<hostname> and /opt/CA/WorkloadAutomationAE/SystemAgent/WA_AGENT/profiles/WAAE.txt / $AUTOSERV.txt in our agent packages. Kindly let us know whether removal of JAVA_HOME variable from these files would affect the agent functioning or client utilities in any manner?


Autosys Version: 11.3.5 and 11.3.6

OS: UNIX and Windows


The client utilities will not get affected even if we remove the JAVA_HOME path from $AUTOUSER/autosys.sh.<hostname>. By default, the JAVA_HOME value is not set in /opt/CA/WorkloadAutomationAE/SystemAgent/WA_AGENT/profiles/WAAE.txt or $AUTOSERV.txt files. $AUTOSERV.txt specify the $EWAGLOBALPROFILE environment variable to mention the path to a file or script that defines global variables.

JAVA_HOME location for windows machine is “C:\Program Files (x86)\CA\WA Agent R11.3.4\jre” (agent installation location\jre). 

Important Note:

We strongly recommend to take a backup of the file before removing the file as this is also a configuration file.


Release: ATSYHA99000-11.3.6-Workload Automation AE-High Availability Option