search cancel

sdk install does not create java64 directory

book

Article ID: 216837

calendar_today

Updated On:

Products

CA Single Sign On Agents (SiteMinder) SITEMINDER

Issue/Introduction

After installing ca-sdk-12.8-sp04-linux-x86-64.bin on Red Hat Enterprise Linux release 8.3 (Ootpa),

the install completes but does not create the java64 directory (no 64 bit jars).  All the other directories are created.

Environment

Release : 12.8.03

Component : SITEMINDER -WEB AGENT FOR APACHE

Cause

Out of box SDK installation folders:

drwxrwxr-x  2 root root  4096 Sep 16  2020 bin32
drwxrwxr-x  2 root root  4096 Sep 16  2020 bin64
-rwxrwxr-x  1 root root    69 Sep 16  2020 ca-sdk-uninstall.sh
drwxrwxr-x  2 root root  4096 Sep 16  2020 etpki-install32
drwxrwxr-x  2 root root  4096 Sep 16  2020 etpki-install-64
drwxrwxr-x  2 root root  4096 Sep 16  2020 include
drwxrwxr-x  3 root root  4096 Sep 16  2020 install_config_info
drwxrwxr-x  6 root root  4096 Sep 16  2020 install_config_jre
drwxrwxr-x  2 root root  4096 Sep 16  2020 java
-rwxrwxr-x  1 root root 67067 Apr 26  2017 license.txt
drwxrwxr-x  2 root root  4096 Sep 16  2020 properties
-rwxrwxr-x  1 root root   155 Apr 26  2017 readme.txt
drwxrwxr-x  2 root root  4096 Sep 16  2020 resources
drwxrwxr-x  4 root root  4096 Sep 16  2020 samples32
drwxrwxr-x 20 root root  4096 Sep 16  2020 samples64

Siteminder has removed folder java64 since 12.7 releases.

Resolution

Product is working as designed. Java bytecode is java bytecode, it doesn't matter whether it was built with a 32-bit or 64-bit JDK. Only native code matters for bitness.

Siteminder has removed folder java64 since 12.7 releases.

Additional Information

Usage of bin64, java64 and samples64 folders for Older version SDK.

https://knowledge.broadcom.com/external/article?articleId=38002