The CA APM 10.0 and 10.1 em-jetty-config.xml file has a new "certAlias" property but it is missing from the webview-jetty-config.xml file.

Document ID : KB000036085
Last Modified Date : 16/07/2018
Show Technical Document Details
Issue:

The APM 10.0 and 10.1 em-jetty-config.xml file has a new "certAlias" property to force the use of a keystore certificate alias which is different from the default alias of 'wily'? i.e. the default entry has:
<Set name="certAlias">wily</Set>
However the "certAlias" property is missing from the webview-jetty-config.xml file.

Environment:
APM 10.0, 10.1
Cause:
The "certAlias" property is also supported for the webview-jetty-config.xml file and it was an oversight that it is missing from that file.
Resolution:

Manually add the "certAlias" property to the webview-jetty-config.xml.

Additional Information:
1. This problem is fixed in APM 10.2 and later releases.

2. Also see related KB article:
"In APM 10.x what feature does new EM/WebView Jetty web server config SSL property "certAlias" provide and how can the keystore be updated with own Private Key/Certificate pair for that alias value."
https://comm.support.ca.com/kb/in-apm-10x-what-feature-does-new-emwebview-jetty-web-server-config-ssl-property-certalias-provide-and-how-can-the-keystore-be-updated-with-own-private-keycertificate-pair-for-that-alias-value/kb000036154

3. In CA APM versions 10.0->10.5 the default value is 'wily' i.e. <Set name="certAlias">wily</Set>​
In CA APM version 10.7 the default value is 'caapm' i.e. <Set name="certAlias">caapm</Set>​

4. It is only supported to have 1 "certAlias" property in either jetty web server config file. Multiple entries for that property will not cause an error on startup but only the value from the last "certAlias" property entry will be used.