WAAE commands/CLIs return the following error:
Please check atleast one of the following conditions are met.
*) Set CAPKIHOME environment variable.
*) Pass valid second parameter to etpki_lib_init function. Ex: if the second parameter is /a/b/c/[lib]cryptocme2.[dll][so][sl], it is assumed that /a/b/c has all the required CAPKI shared libraries
CAUAJM_E_00224 The CAPKI library experienced an internal error and may not have initialized properly.
CAUAJM_E_10029 Communication attempt with the CA WAAE Application Server has failed! [<AutoServer>:<AutoServerPort>]
CAUAJM_E_10221 Exhausted list of available Application Server(s). Failing request.
CAUAJM_E_50033 Error initializing tx subsystem: CAUAJM_E_10062 Failed to get initial configuration from CA WAAE Application Server(s).
Example:
Check the $CASHCOMP and $CAPKIHOME variables and set them to the correct value. Ensure the CASHCOMP variable is set to correct path in the following profile files:
CASHCOMP is an abbrev. for CA Shared Components and represents the absolute path of SharedComponents directory which by default is /opt/CA/SharedComponents.
The following command returns the installation path of SharedComponents:
lsm -q CACommonComponents -l | grep INSTALLATION_PATH | cut -d":" -f2
Example:
CAPKIHOME is not set by default and is not always required to be. However, if set to an incorrect value, WAAE commands will fail with the following errors:Could not open CAPKI shared library, errno is 0, errmsg is <$CAPKIHOME>/Linux/x86/32/lib/libcapki.so: cannot open shared object file: No such file or directory.
CAUAJM_E_00224 The CAPKI library experienced an internal error and may not have initialized properly.
CAPKIHOME may optionally be set to $CASHCOMP/CAPKI