XCOM for Linux 12.0 Docker RHEL 9.x installation and patch LU11905

Products

• XCOM Data Transport
• XCOM Data Transport - Linux PC

Issue/Introduction

Moving XCOM Docker container from Host OS CentOS 7.x to Host OS Red Hat Enterprise Linux (RHEL) 9.x.

RHEL 9.x does not have xinetd so tried to install into the container the RHEL 9.x systemd patch r12.0.23114 (LU11905) i.e. XCLX86_XCOMPATCH_r12023114_64.bin
However this error occurs:

Either CA XCOM Data Transport r12.0 SP00 64bit not found or XCOM_HOME is not set correctly. You must have CA XCOM Data Transport r12.0 SP00 64bit installed and XCOM_HOME Environment Variable set to CA XCOM Data Transport installed directory to apply maintenance. Installer will now exit.

Environment variables (from the docker container):
XCOM_HOME=/opt/CA/XCOM
XCOM_JAVA_HOME=/opt/java/openjdk
XCOM_JDBC_DIR=/opt/CA/XCOM/jdbclib

# xcomqm -r
CA XCOM Data Transport r12.0 22042 SP00 64bit (for <no SNA support>)

Why does the installer not find the installation path/XCOM_HOME variable?

Does the patch need to be applied to the container because RHEL 9.x does not have xinetd?

Environment

XCOM for Linux 12.0 Docker installation.
Red Hat Linux Enterprise (RHEL) 9.x

Resolution

The xinetd should still be available within the XCOM Docker container even though the host OS RHEL 9.x does not have it i.e. the RHEL 9.x patch r12.0.23114 patch (LU11905) is not required.

At this time there is no published maintenance for XCOM Docker containers and the standard XCOM maintenance/patch .bin files cannot be installed in a Docker container which is why an error was encountered trying to do so.

Additional Information

1. After starting the container xcomd and xinetd should be automatically started as per doc page Configure XCOM Docker Containers.
   Therefore xinetd should be visible as a running process and listed as the process for the XCOM listening ports 8044-8047. To verify start a bash shell in the container and run the relevant commands.
   
   # docker exec -it xcomdocker-caxcom-1 bash
[root@deb552536d35 XCOM]#
   
   Run the ps command e.g.
   [root@deb552536d35 XCOM]# ps -efw
UID          PID    PPID  C STIME TTY          TIME CMD
root           1       0  0 04:51 ?        00:00:00 /bin/bash bin/start.sh
root          95       0  0 04:52 pts/0    00:00:00 bash
root         189       1  0 04:56 ?        00:00:00 /usr/sbin/xinetd -stayalive -pidfile /var/run/xinetd.pid
root         195       1  0 04:56 ?        00:00:00 /opt/CA/XCOM/sbin/xcomd -d9
root         618      95  0 05:09 pts/0    00:00:00 ps -efw

Run the netstat command e.g.
   [root@deb552536d35 XCOM]# netstat -nap | grep 804
tcp        0      0 0.0.0.0:8045            0.0.0.0:*               LISTEN      189/xinetd
tcp        0      0 0.0.0.0:8044            0.0.0.0:*               LISTEN      189/xinetd
tcp6       0      0 :::8047                 :::*                    LISTEN      189/xinetd
tcp6       0      0 :::8046                 :::*                    LISTEN      189/xinetd

   
   NOTE: On RHEL 9.x It has been observed that after the container is started there may be a delay of several minutes in the start of the xcomd and xinetd processes or if the xinetd process is immediately visible a delay in the 804* LISTEN ports being listed. This is currently being investigated by XCOM Engineering.
   
   
   
2. XCOM Data Transport for UNIX/Linux 12.0 > Installing > Install Using Docker