Frontend Application Unavailable After Promoting Rules/Content
Last updated on JANUARY 05, 2017
Applies to:Oracle Commerce Guided Search / Oracle Commerce Experience Manager - Version 3.1.0 to 3.1.0 [Release 3.x]
Oracle Commerce Merchandising - Version 9.0 and later
Oracle Commerce Guided Search / Oracle Commerce Experience Manager - Version 3.1.1 to 3.1.1 [Release 3.x]
Information in this document applies to any platform.
After running the Deployment Template baseline_update.bat|sh (or the promote_content.bat|sh) script to promote rules/content to live production MDEX engines, the frontend application becomes unavailable, no content and rules are being rendered. There are no errors returned by baseline_update.bat|sh or promote_content.bat|sh, and there are no errors in the MDEX logs when launching the application.
While there are no exceptions reported by the Deployment Template scripts, the following behaviors indicate a problem in the publishing process:
1. The \Endeca\ToolsAndFrameworks\3.1.x\server\workspace\logs\ifcr.log shows the following ERROR during promotion:
2. The regular (orange) Endeca Reference Application shows no supplemental objects (it would normally display the list of rules/templates that are defined in the MDEX configuration).
3. There are rules in Experience Manager showing text similar to "Invalid Dval (4,294,967,266)" in the Location field of the rule.
4. Assembler applications may throw NullPointerExceptions or ArrayIndexOutOfBoundsExceptions due to missing content in the MDEX.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms