Shell environment not set correctly in jobs on non-privileged Java Unix Agent

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

Agent Unix Java 24.x in a non privileged mode (agent started as username and launching jobs as username) does not load the full environment of the user (/etc/profile + $HOME/.profile) when launching a JOBS.

As a result, environment variables that are defined in these files /etc/profile (and subprofile files like the ones for CAPKI) and $HOME/.profile or $HOME/bash_profile or $HOME/.bashrc among others, depending on the shell, are not loaded when we launch a job with the option "login shell with profile loaded" (-bash,-sh, -ksh, -csh).

Environment

Agent Unix Java 21.x and 24.x

Cause

DE181699

Resolution

Workaround:

Start the agent in privileged mode or add the required environment variables to one of the different unix headers or an include to be executed before the jobs

Solution:

Update to a fix version listed below or a newer version if available.

Fix version:
Component(s): Agent Unix Java

Automation.Engine 24.4.x - yet to be planned