During MPP installation, the installation script creates a symbolic link to this file, which Apache uses to access the certificate. If that symbolic file does not exist, a connection cannot be established between the MPP and the EPM. Therefore, you must also verify that the symbolic link exists on the MPP.
Compare the MPP certificate to the one on the EPM by entering the curl http://EPM-server/cert.pem command, where EPM-server is the domain name or IP address of the system where the primary EPM software is installed.
At the Linux command line prompt, enter the cat $AVAYA_MPP_HOME/web/ssl.crt/vpms.crt command.
ADDITIONAL INFORMATION:
The system should respond with a message similar to the following:
Change to the directory in which the SSL certificate from the EPM resides by entering the cd $AVAYA_MPP_HOME/web/ssl.crt/ command.
List all files in this directory by entering the ls -al command.
ADDITIONAL INFORMATION:
You should see a symbolic link to the vpms.crt file, similar to the following entry:
lrwxrwxrwx 1 ^sroot^root^ 8 Oct 7 18:21 36c998fa.0 -> vpms.crt
The "l" at the beginning and the"-> vpms.crt" text at the end indicate that the symbolic file has been created. In this example, the file is named36c998fa.0.
Note:
This file is created and named automatically by the installation script, using a hash security encryption scheme.
Did the system respond correctly to both these commands?
If yes, an SSL certificate is correctly installed on the MPP. No further action is required, unless you want to ensure that the certificate is valid. In that case, you can reinstall the certificate.
If no, the SSL certificate either is not installed or is invalid. Try reinstalling the certificate.
