AutoSys AIX Install Java Error (InvocationTargetException) from Corrupt ISO

Products

• Autosys Workload Automation

Issue/Introduction

You encounter an InvocationTargetException error during the installation of AutoSys Workload Automation (WLA) on an AIX system. Specifically, after you choose to use the Java Virtual Machine (JVM) installed with this application, the installer fails with an InvocationTargetException and exits. The underlying cause for this failure is a java.lang.NoClassDefFoundError for org.apache.commons.lang.StringUtils, as detailed in the stack trace. This prevents the installation from proceeding to the component selection screen.

Environment

Product: AutoSys Workload Automation

Operating System: AIX 7.3 TL1 SP2 (7300-01-02-2320)

Cause

This error indicates that the ISO installation file is corrupted or incomplete. The java.lang.NoClassDefFoundError: org.apache.commons.lang.StringUtils occurs because critical components, such as specific Java libraries required by the installer, are missing or damaged due to this file corruption. File corruption can happen during the download from the Broadcom Support Portal or during its transfer to the AIX server, resulting in an incorrect MD5 checksum.

Resolution

To resolve the InvocationTargetException during AutoSys Workload Automation installation on AIX, you must ensure the integrity of the ISO installation file. It is possible for the MD5 checksum of the install.bin file is okay/matches a non-corrupt file while the ISO file was corrupt. This scenario could lead to these types of problems - which is why it's necessary to validate the MD5 of the ISO as soon as it's downloaded.

1. Re-download the ISO file: Obtain a fresh copy of the ISO file from the official Broadcom Support Portal.
2. Verify MD5 Checksum: Before attempting installation or transferring the file to the AIX server, verify the MD5 checksum of the newly downloaded ISO file.
   • Compare the checksum to the official MD5 value provided on the Broadcom Support Portal for ISO.
   • On your AIX system, use the csum command to calculate the MD5 checksum of the file:
     bash csum -h MD5 <ISO Filename>
3. Ensure Integrity During Transfer: If you are transferring the ISO file to the AIX server, ensure the transfer method preserves file integrity. Verify the MD5 checksum of the file after it has been transferred to the AIX server to confirm it matches the source.
4. Re-attempt Installation: Once you confirm that the ISO file's MD5 checksum matches the expected value, proceed with the AutoSys Workload Automation installation. The Java InvocationTargetException with NoClassDefFoundError should no longer occur.