Application is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ' databaseSchemaUpgrade ' defined in URL [jar:file:/C:/Program%20Files/Serena/common/tomcat/8.0/webapps/pulse/WEB-INF/lib/platform-dbschema-14.3.1-SNAPSHOT.jar!/META-INF/starlight/app-components.xml]:
Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name ' databaseSchemaUpgrade ' defined in URL [jar:file:/C:/Program%20Files/Micro%20Focus/common/tomcat/8.5/webapps/pulse/WEB-INF/lib/platform-dbschema-14.5.0-SNAPSHOT.jar!/META-INF/starlight/app-components.xml]:
Logging in gives error "The proxy server isn’t responding" and server.log gives "Error creating bean with name 'liquibase' defined in class path resource"
com.serena.solfwk.srp.service.LocalizationServiceImpl.localizationBean; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'localizationBean' defined in class path resource [srp-context.xml]: Invocation of init method failed; nested exception is java.lang.NullPointerException
When enabling the SSO (supplied with SBM) for Dimensions CM 12.1, there may be issues with the Build completing if “localhost” is used to define the default Dimensions CM URLs when the SSO URL is set the machine name .
nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'configuration' defined in class path resource
The problem is if you use the Mashup Event tab on a Nofication Definition. You can create a Notification definition for things like Item Add, Item Update etc and when you fill in the Mashup Event tab you can tell it the endpoint url and event name .
Cannot find class [com.microfocus.sbm.sso.idp.saml2sp.SBMSAML2SPConfigFilter] for bean with name 'sbmSAML2SPConfigFilter' defined in ServletContext resource [/WEB-INF/conf/saml2sp/securityContext.xml]; nested exception is java.lang.ClassNotFoundException: com.microfocus.sbm.sso.idp.saml2sp. SBMSAML2SPConfigFilter
If you edit any of the url's make sure to deploy all the applications that use that endpoint. If any of the RLM endpoints are pointing to the wrong server ( Most commonly a problem after promoting all your applications ) then you could run into a problem where the SSO token used in the various orchestrations is not valid if the endpoint is pointing to the wrong server. This seems like a random problem when this situation occurs because sometimes their are two endpoints defined with slightly different names but two different url's are used in the environment.
... the site contains Java Beans , then copy the Java Bean files to the ... ... It must be defined for each project ... ... and click its name to display the "Edit Metadata Definitions " dialog box ... ... add a metadata definition . ... from the Metadata name ... add another metadata definition . ... Choose "Preview URL " from the Metadata name ... , enter the URL for the ROOT ... ... part of the URL (such as ... Long Path Names ... (404) error may result when ... ... limit, the error will occur. ... , a "Directory browsing not allowed" error will occur ...
