Deployment of Monitoring Service (MCR) through Command Line Interface (CLI) build fails due to certificate exception.
Article ID: KB0089886
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix Service Grid | - |
| TIBCO BPM Enterprise (formerly TIBCO ActiveMatrix BPM) | - |
| TIBCO ActiveMatrix BusinessWorks Service Engine | - |
Description
Description:
MCR Aggregator application deployment through Command Line Interface throws certificate exception.
Symptoms:
The CLI (Command Line Interface) build command (ant -f build.xml deploy-mcr) to deploy MCR fails with the following exception. The ActiveMatrix (AMX) Administrator is configured to have SSL enabled for the external HTTP connection.
Exception seen in the SystemNode.log.
**********************************
Caused by: java.security.cert.CertificateException: No name matching <HOST-NAME> found
at sun.security.util.HostnameChecker.matchDNS(Unknown Source)
at sun.security.util.HostnameChecker.match(Unknown Source)
**********************************
Cause:
The external keystore used for the external httpConnector is having the server identity "CN" not being resolved to the actual host name for AMX (ActiveMatrix) Administrator.
MCR Aggregator application deployment through Command Line Interface throws certificate exception.
Symptoms:
The CLI (Command Line Interface) build command (ant -f build.xml deploy-mcr) to deploy MCR fails with the following exception. The ActiveMatrix (AMX) Administrator is configured to have SSL enabled for the external HTTP connection.
Exception seen in the SystemNode.log.
**********************************
Caused by: java.security.cert.CertificateException: No name matching <HOST-NAME> found
at sun.security.util.HostnameChecker.matchDNS(Unknown Source)
at sun.security.util.HostnameChecker.match(Unknown Source)
**********************************
Cause:
The external keystore used for the external httpConnector is having the server identity "CN" not being resolved to the actual host name for AMX (ActiveMatrix) Administrator.
Issue/Introduction
Deployment of Monitoring Service (MCR) through Command Line Interface (CLI) build fails due to certificate exception.
Resolution
1). Generate a new keystore (for external httpConnector) with a server identity (CN) that matches with the
primary aAministrator actual host name.
2). Edit the HTTPConnector using the TIBCO Configuration Tool (TCT) wizard. Click on "Edit TIBCO ActiveMatrix Administrator Server Configuration" from the TCT wizard > Select the AMX Administrator > Select the "Edit HTTP Connection Settings" > For SSL settings, select the new keystore generated in the first step.
Note: You may also edit the external httpConnector settings from CLI using the sample scripts bootstrap-edit-build.xml, edit-httpconnector-data.xml provided under the <TIBCO-HOME>\administrator\<version>\scripts folder after making the necessary modifications based on your environment.
3). Apply the changes. It may take a few minutes to get the SystemNode started up completely. In the event you find any issues with login, restart SystemHost and try login again.
4). Perform the MCR build to deploy the Monitoring Service.
2). Edit the HTTPConnector using the TIBCO Configuration Tool (TCT) wizard. Click on "Edit TIBCO ActiveMatrix Administrator Server Configuration" from the TCT wizard > Select the AMX Administrator > Select the "Edit HTTP Connection Settings" > For SSL settings, select the new keystore generated in the first step.
Note: You may also edit the external httpConnector settings from CLI using the sample scripts bootstrap-edit-build.xml, edit-httpconnector-data.xml provided under the <TIBCO-HOME>\administrator\<version>\scripts folder after making the necessary modifications based on your environment.
3). Apply the changes. It may take a few minutes to get the SystemNode started up completely. In the event you find any issues with login, restart SystemHost and try login again.
4). Perform the MCR build to deploy the Monitoring Service.
Additional Information
Feedback
Yes
No
Powered by
