AOPD service fails to start and below traces are logged:
===
09 Jun 2023 19:10:02,234  INFO [Member1] [com.tibco.fom.bootstrap.AOPDWebInitializer] [cxfServletRegistration] - [ThreadID:60] cxfServletRegistration INVOKED 
09 Jun 2023 19:10:02,255 ERROR [] [org.springframework.boot.context.embedded.tomcat.TomcatStarter] [] - Error starting Tomcat context. Exception: org.springframework.beans.factory.UnsatisfiedDependencyException. Message: Error creating bean with name 'springSecurityFilter1Registeration' defined in com.tibco.fom.bootstrap.AOPDWebInitializer: Unsatisfied dependency expressed through method 'springSecurityFilter1Registeration' parameter 0; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'org.springframework.security.web.FilterChainProxy' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {} 
09 Jun 2023 19:10:02,475 ERROR [] [org.springframework.boot.diagnostics.LoggingFailureAnalysisReporter] [] - 

***************************
APPLICATION FAILED TO START
***************************

Description:

Parameter 0 of method springSecurityFilter1Registeration in com.tibco.fom.bootstrap.AOPDWebInitializer required a bean of type 'org.springframework.security.web.FilterChainProxy' that could not be found.


Action:

Consider defining a bean of type 'org.springframework.security.web.FilterChainProxy' in your configuration.

===
See attached aopd-local.log file for more details.  

This issue is due to misconfiguration. It occurs when trying to start AOPD as a separate microservice and setting the property "com.tibco.fom.aopd.deployMode"  to "AOPD_colocated" in $OM_HOME/roles/aopd/standalone/config/profiles.properties file. To solve this issue, set this property to "AOPD_standalone" and restart AOPD service.