UseBindIpForConnect parameter requires Java 19 or later in CA Automic Workload Automation

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

The configuration file (.ini) for Java-based OS agents contains the parameter UseBindIpForConnect, with comments stating it requires a Java version higher than 19. However, the product Compatibility Matrix indicates that JDK 17 is the supported version.

• Users are unable to utilize the UseBindIpForConnect feature while running on the officially certified JDK 17.
• Confusion regarding the discrepancy between the .ini file documentation and the official compatibility matrix.

Environment

• Product: CA Automic Workload Automation
• Component: Automation Engine / Java OS Agents
• Platform: Windows, Unix
• Feature: UseBindIpForConnect (used for bindaddr attribute in file transfers and JCP connections)

Cause

The UseBindIpForConnect parameter specifically relies on Java network modules and bind interface features that were only introduced in Java version 19 and later. These modules are not present in JDK 17.

Resolution

Feature Requirement: To use the UseBindIpForConnect parameter, the agent must be running on Java 19 or higher.

Current Certification: The current general certification for Java agents remains JDK 17. Use of this specific parameter requires an uncertified (higher) Java version.

Future Support: Broadcom Engineering is currently in the process of certifying Java v21 and later.

Documentation Update: Once the certification for Java 21+ is finalized, the official compatibility matrix will be updated to reflect support for these newer versions, aligning it with the requirements of this parameter.