Troubleshooting guide for DB2 monitoring in ManageEngine Applications Manager.
Applications Manager connects to DB2 over SSL when SSL is enabled in the monitor credentials. It uses its own truststore, apm.keystore, located at:
<AppManager_Home>/working/Cert/apm.keystoreImport certificates through the Applications Manager certificate screen. Use Trust certificates to import a certificate and List certificates to verify the certificates already present. Accepted formats are .crt, .cer, .pfx, .der, .jks, .keystore and .truststore.
SSL_SVCENAME, normally a different port from plain SVCENAME. Run:db2 get dbm cfg | grep -i svcenameDB2COMM must include SSL:db2set -all | grep -i DB2COMMTCPIP only, set DB2COMM=TCPIP,SSL and restart the instance using db2stop and db2start.What it means: Applications Manager reached the DB2 server and started an SSL handshake, but does not trust the certificate presented by the server.
If intermediate CAs are present, import the intermediate and root certificates too. Every link in the chain must be trusted.
For detailed import instructions, refer to How to import certificates for monitoring DB2 Server with SSL authentication.
What it means: Applications Manager could not open its own truststore. The file may be damaged, unreadable by Java, or have a password that no longer matches the password maintained by the product. This can happen if the file was copied manually, restored from backup or replaced outside the product.
apm.keystore by copying a file over it. Always import certificates through Applications Manager.What it means: The connection did not reach the certificate stage. Applications Manager could not reach the port or reached a port that is not serving SSL.
db2 get dbm cfg | grep -i ssl_svcenameSVCENAME port.DB2COMM includes SSL:db2set -all | grep -i DB2COMMdb2stop and db2start.SSL_SVR_KEYDB and SSL_SVR_STASH are configured in db2 get dbm cfg.telnet <db2-host> <ssl-port>What it means: Both sides began SSL negotiation, but the server closed the connection during the handshake. The TLS versions or cipher suites may not overlap. Applications Manager runs on Java 17, which does not support TLS 1.0 or TLS 1.1.
db2 get dbm cfg | grep -i ssl_versions
db2 get dbm cfg | grep -i ssl_cipherspecsSSL_VERSIONS is set to TLSV1 or TLSV11, configure TLS 1.2:db2 update dbm cfg using SSL_VERSIONS TLSV12
db2stop
db2startSSL_CIPHERSPECS contains only older cipher suites, clear the setting to use the DB2 default set:db2 update dbm cfg using SSL_CIPHERSPECS NULL
db2stop
db2startCertificate host name: Applications Manager connects with host name validation turned off. The certificate CN or SAN does not have to match the host name or IP entered in the monitor. If an error mentions a host name mismatch, it originates elsewhere.
Client certificates: Applications Manager does not present a client certificate to DB2. A DB2 instance configured to require client authentication will reject the connection.
Collect the following before contacting support:
db2 get dbm cfg, especially SVCENAME, SSL_SVCENAME, SSL_VERSIONS, SSL_CIPHERSPECS, SSL_SVR_KEYDB and SSL_SVR_STASH.db2set -all.<AppManager_Home>/logs/AMErrorLog*.txt and stdout.txt covering the time the monitor was added.