After manually configuring the ARD Hub 3.5 version on the Windows Server, the ARD application fails to start when the *.war files are deployed by Tomcat.
The following error is seen in the apigw.log, but a similar error should be present in all the .ard/log files.
Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
2024-12-10 10:43:20.423 ERROR [apigw,,] 8504 --- [Catalina-utility-2] o.s.b.d.LoggingFailureAnalysisReporter :
***************************
APPLICATION FAILED TO START
***************************
Description:
Failed to bind properties under 'zuul.routes.ims.url' to java.lang.String:
Property: zuul.routes.ims.url
Value: "${api.routes.ims.url}"
Origin: class path resource [application.yml] - 8:18
Reason: java.lang.IllegalArgumentException: Could not resolve placeholder 'iam.scheme' in value "${iam.scheme}://${apigw.host}:${apigw.port}"
Action:
Update your application's configuration
ARD Hub 3.5
When deploying the ard *.war files, Tomcat is unable to resolve the 'iam.scheme' variable in the .ard/conf/settings.properties file.
This was caused by a bad copy of the settings.properties file, which was missing the iam.scheme property.
If Tomcat is not configured for SSL:
If Tomcat is configured to use SSL:
Restart Tomcat, or redeploy the ard *.war files, and check the ./ard/log files to ensure each started cleanly.