JRE 1.5 to 1.8 u261 upgrade compatibility in CA Workload Automation AE environments

book

Article ID: 198644

calendar_today

Updated On:

Products

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

Issue/Introduction

The CA Workload Automation AE server has JRE 1.5 under the directory /opt/CA/SharedComponents/JRE. This document describes the impact of upgrading or removing the JRE from the location.

Current java release under "/opt/CA/SharedComponents/JRE"  -

-rwxr-xr-x 1 root root 65076 Jun  8  2010 /opt/CA/SharedComponents/JRE/1.5.0_11/bin/java
java version "1.5.0_11"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
Java HotSpot(TM) Server VM (build 1.5.0_11-b03, mixed mode)

Environment

Release : 11.3.6

Component : CA Workload Automation AE (AutoSys)

Resolution

The CA Common Components like CA-WV, CA-DIADNA, CA-diaukb, CA Event Manager would require the  JRE under  "/opt/CA/SharedComponents/JRE/1.5.0_11/" to be at the version shipped with the product due to code compatibility.

JRE from this location can be removed or upgrade if these components are not being used. Some of the other product component's startup scripts have the dependencies on one of these components though there is no functionality impact. Due to which, it is required to disable or unregister these components from command 'unisrvcntr'

For example, CA CCI does not have any relation with these components. However, the startup command like "unisrvcntr start CA-cci" would fail to start as the startup script has a dependency on CA-DIADNA. This can be avoided by deregistering the aforementioned components from unisrvcntr command. The CCI services would start fine afterwards.

The following syntax can be used to deregister services.

# unisrvcntr register -D <component_name>

Additional Information

It is suggested to remove JRE from the location in lower non-production environments prior to production.

Contact Broadcom technical support if unexpected behaviour is observed after the change.