Tuesday, March 15, 2016

Endeca 11.2 - Publish Deployment Failed : File Store

Behavior:-  Find out solution below if you find any errors in Oracle Endeca Tools and Framework 11.2 Error : Deployment failed : Fil... thumbnail 1 summary

Behavior:- 

Find out solution below if you find any errors in Oracle Endeca Tools and Framework 11.2

Error : Deployment failed : File Store
Detailed Status : [ Export : Success ] ; [ Store update : failure ]
Export Details : [ Exported generation : generation_2015-12-15T13-25-56Z_1450166156077.zip ]
Error Details : [ Cause : No store available to deploy ] ; [ Suggested fix : Start the application specific file store(s) ]
Tools : Imported Editor Configuration, Experience Manager, Automatic Phrasing, Keyword Redirects, Imported Cartridge Templates, Thesaurus, User SegmentsUsers : admin
Deployment ID [PUBSERV5] - Please see log for additional information.


Solution :- 

By default, the Experience Manager expects to have a running Authoring Assembler configured to receive and apply the Generational Store updates.In an Oracle Commerce Platform with Oracle Commerce Guided Search deployment, this Authoring Assembler lives in the Publishing Server, and is configured during the deployment of the publishing server (BCC, etc.) components.If the Publishing Server is not deployed, there will be no Authoring Assembler active in the application environment for Experience Manager to contact.

1. Install Publishing server or try to make store instance as publishing server to verify. Following property should be available

 - Verify that the previewEnabled property on the /atg/endeca/assembler/cartridge/manager/AssemblerSettings/ component is set to 'true'.
 - Verify that the authoring property on the /atg/endeca/assembler/cartridge/manager/DefaultWorkbenchContentSoub. Verify that the authoring property on the /atg/endeca/assembler/cartridge/manager/DefaultWorkbenchContentSource/ component is set to 'true'.

2.  Edit /atg/endeca/assembler/cartridge/manager/DefaultFileStoreFactory component and update configurationPath.
Path should be - > <<Install_PATH>>/ToolsAndFrameworks/11.2.0/server/workspace/state/generation_data/<<App_name>>

3. Restart instance.


4. try changing content from Endeca experience manager. 


Find out screenshot below after doing all the above steps.




Click here to get more topics related to Endeca basics?

It's your Turn
Was this post help you to resolve the issue that you are looking for? Any other issues that you might have and need a solution?

Provide your feedback in the comment section below.

4 comments

  1. Hi Ajay ,

    I am facing the same issue with discover application do you have an idea how to fix this in discover application .

    ReplyDelete
  2. Hi Ajay,

    Iam facing similar issue in case of forge base application. How can i resolve this error?

    ReplyDelete
    Replies
    1. Hi Rakesh,

      It does not matter if its Forge based or CAS based. Did you try the solution listed above? are you using ATG or any assembler service?

      Thanks,
      Ajay Agrawal

      Delete
  3. Hi Ajay,

    Followed the above mentioned steps to configure store instance as the preview server. However the instance is not up. All Endeca driven pages are empty. I am able to see in the logs that the generation zip file being read successfully and the store getting updated and the authoring assembler successfully started. But No response from Endeca when accessed any of the Endeca driven pages. Is there any other configuration that needs to be configured so that the instance will be up and running as a preview server (by pointing to the authoring MDEX export dir)?

    Thanks in Advance.

    ReplyDelete

Text Widget