java version on windows machines
search cancel

java version on windows machines

book

Article ID: 230559

calendar_today

Updated On:

Products

CA Workload Automation AE - System Agent (AutoSys)

Issue/Introduction

Why a symbol link, pointing to a jre, is required in the agent directory?

https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/workload-automation-system-agent/12-0/installing-and-upgrading/replace-the-jre-installed-by-the-agent-without-upgrading-the-agent.html

The symbol links are automatically created when the agent is installed/upgraded, but our windows team would like to find out if there is a way to just use the system version of java without having to mess around with symbol links.

Environment

Release : 12.0

Component : Workload Automation System Agent

Resolution

In the Agent parameter file, agentparm.txt, there is a parameter, oscomponent.javapath, that specifies the full path to the directory where Java resides.

Below is an example:

# Java parameters
oscomponent.javapath=C:/Program Files/CA/WorkloadAutomationAE/SystemAgent/WA_AGENT/jre/bin

In this case, the Java resides under the <Agent>/jre directory.

If you're not using the Java that resides under <Agent>/jre directory, you can create a software link <Agent>/jre that points to the actual location of the JRE that you installed.  In this case, you do not need to update the oscomponent.javapath parameter setting.

Alternatively, if you're not using the jre soft link, you can specify the full path of Java via the oscomponent.javapath parameter.  Each time the location of your Java is changed, you need to update your parameter in agentparm.txt.  To make any change in agentparm.txt effective, you will need to restart the Agent service as well.