Financial Services Accelerator 6.6: Spring Error - Failed to load audit configuration.

[former_member608948]

Followed the below page for installation. Even though the page belongs to 6.6 it asks to download 6.5! https://help.hybris.com/6.6.0/hcd/8ad8692c86691014ba22a7a121019ccd.html#loio8ad8692c86691014ba22a7a1...

I downloaded the following to install Financial Service Accelerator 6.6:
1. HYBRISCOMM6600P_6-70003031
2. YFINANCEPACKAGE00_0-70003065

Extracted them to: C:\DEV\y66_financial

Executed : install.bat -r financial
Result: BUILD SUCCESSFUL

Executed: install.bat -r financial initialize
Result: BUILD FAILED

LOG: Tried attaching complete log but it doesn't allow. Says: File format not permitted (Seriously! a .txt file is not permitted!)

      [java] ERROR [main] [AuditEnablementService] Failed to load audit configuration. Following properties are not lowercase: audit.InsuranceQuote.enabled,audit.FSIncidentType.enabled,audit.InsurancePolicy.enabled,audit.InsuredObjectItem.enabled,audit.InsuredObject.enabled,audit.FSClaim.enabled,audit.Coverage.enabled,audit.YFormData.enabled
      [java] WARN  [main] [CloseAwareApplicationContext] Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'defaultAuditViewService' defined in class path resource [core-spring.xml]: Cannot resolve reference to bean 'auditEventProvider' while setting bean property 'auditEventProvider'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'defaultAuditEventProvider' defined in class path resource [core-spring.xml]: Cannot resolve reference to bean 'auditingEnablementService' while setting bean property 'auditEnablementService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'auditingEnablementService': Invocation of init method failed; nested exception is de.hybris.platform.persistence.audit.internal.AuditConfigurationException: Failed to load audit configuration. Following properties are not lowercase: audit.InsuranceQuote.enabled,audit.FSIncidentType.enabled,audit.InsurancePolicy.enabled,audit.InsuredObjectItem.enabled,audit.InsuredObject.enabled,audit.FSClaim.enabled,audit.Coverage.enabled,audit.YFormData.enabled
      [java] WARN  [main] [CloseAwareApplicationContext] Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'defaultAuditViewService' defined in class path resource [core-spring.xml]: Cannot resolve reference to bean 'auditEventProvider' while setting bean property 'auditEventProvider'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'defaultAuditEventProvider' defined in class path resource [core-spring.xml]: Cannot resolve reference to bean 'auditingEnablementService' while setting bean property 'auditEnablementService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'auditingEnablementService': Invocation of init method failed; nested exception is de.hybris.platform.persistence.audit.internal.AuditConfigurationException: Failed to load audit configuration. Following properties are not lowercase: audit.InsuranceQuote.enabled,audit.FSIncidentType.enabled,audit.InsurancePolicy.enabled,audit.InsuredObjectItem.enabled,audit.InsuredObject.enabled,audit.FSClaim.enabled,audit.Coverage.enabled,audit.YFormData.enabled
      [java] ERROR [main] [HybrisContextFactory] Error initializing global application context!
      [java] org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'defaultAuditViewService' defined in class path resource [core-spring.xml]: Cannot resolve reference to bean 'auditEventProvider' while setting bean property 'auditEventProvider'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'defaultAuditEventProvider' defined in class path resource [core-spring.xml]: Cannot resolve reference to bean 'auditingEnablementService' while setting bean property 'auditEnablementService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'auditingEnablementService': Invocation of init method failed; nested exception is de.hybris.platform.persistence.audit.internal.AuditConfigurationException: Failed to load audit configuration. Following properties are not lowercase: audit.InsuranceQuote.enabled,audit.FSIncidentType.enabled,audit.InsurancePolicy.enabled,audit.InsuredObjectItem.enabled,audit.InsuredObject.enabled,audit.FSClaim.enabled,audit.Coverage.enabled,audit.YFormData.enabled

[Former Member]

Hi ,

Please try reaching out to this link for download of FSA 6.6

Currently, FSA is not listed in the 6.7 Commerce because it is still in development. Commerce was released couple of months ago, but FSA is yet to come on 15th of August. We are working on making this announcement on release dates more transparent in the future.

Feel free to reach out to us for any further questions.

Kind regards,

Rastko

[former_member608948]

Thanks for this information.

We are looking forward to 6.7 release. We are quite impressed by the recent features from 6.4 till 6.6 in FSA. And also the release videos by you is really good! :-)

[former_member608948]

I have a feedback. I was searching for FSA documentation for days on Help. As by default the website takes you to 6.7, I was searching and navigating all over the documentation but couldn't find anything. At the end I went back to Wiki to refer the old docs. After a few days I discovered the documentations in 6.4 - 6.6 while preparing an upgrade assessment. It will be really great if we can have just one page in the Release Notes of 6.7 about FSA, just saying to refer the previous versions. I got the same feedback from some other consultants as well.

Thanks and regards Vivek

[Former Member]

Hi Vivek,

Thanks for the kind words. We always strive to provide the best experience for our customers. Both through the features developed, as well as for the information provided and documentation needed.

It is also a great thing that you stressed out the trouble you have with accessing the documentation. Our Technical Writer is actually working on it and I expect that the announcement appears with next documentation publication (happens bi-weekly). The trouble is that regarding this we have to align with all other industry accelerators, but the process is ongoing.

Thanks once again!

[Former Member]

Hi , I do not find YFINANCEPACKAGE00_0-70003065 (or similar) under the link you posted. Can you confirm that it is not downloadable anymore?

I noticed that the financial services accelerator is not listed in commerce 6.7 as an external accelerator. Does someone know more about the whereabouts? I would still be interested in the 6.6 financial services accelerator.

Thanks Nils

[former_member446394]

Hi Vivek,

In order to fix this error, you should edit the project.properties file from financialstore extension, and change the itemtypes to lowercase, so instead of:

 audit.InsuranceQuote.enabled=true
 audit.FSIncidentType.enabled=true
 audit.InsurancePolicy.enabled=true
 audit.InsuredObjectItem.enabled=true
 audit.InsuredObject.enabled=true
 audit.FSClaim.enabled=true
 audit.Coverage.enabled=true
 audit.YFormData.enabled=true

You should have this:

  audit.insurancequote.enabled=true
  audit.fsincidenttype.enabled=true
  audit.insurancepolicy.enabled=true
  audit.insuredobjectitem.enabled=true
  audit.insuredobject.enabled=true
  audit.fsclaim.enabled=true
  audit.coverage.enabled=true
  audit.yformdata.enabled=true

Kind regards, Ksenija

[former_member608948]

Hi @Ksenija Zivkovic ,

Thanks for your response.

Yes this will fix the problem. But we don't want to do the same in the production envt when we go live. Adding in the local.properties is not replacing them in the context.

As of now I am able to start the server but it should be fixed as part of the accelerator. I wonder if the right guys know about it and we can get it fixed in the next patch.

Thanks and regards

Vivek