Promoting the Content in Endeca

There are two types of promoting the Content to ATG Application

1)Directly updating the IFCR

For this type 1 comment the Following Lines in 

C:\Endeca\Apps\ATGen\config\script\WorkbenchConfig.xml, and Uncomment the Blue one. 

<script id="PromoteAuthoringToLive">

  <log-dir>./logs/provisioned_scripts</log-dir>

  <provisioned-script-command>./control/promote_content.bat</provisioned-script-command>

  <bean-shell-script>

  <![CDATA[

  // Exports a snapshot of the current dgraph config for the Live

  // dgraph cluster. Writes the config into a single zip file.

  // The zip is written to the local config directory for the live

  // dgraph cluster. A key file is stored along with the zip.

  // This key file keeps the latest version of the zip file.

  //IFCR.exportConfigSnapshot(LiveDgraphCluster);

  // IFCR exportApplication

  // Used to export a particular node to disk. This on disk format will represent

  // all nodes as JSON files. Can be used to update the Assembler.

  // Note that these updates are "Application Specific". You can only export nodes

  // that represent content and configuration relevant to this Application.

  //IFCR.exportApplication();

  // Applies the latest config of each dgraph in the Live Dgraph cluster

  // using the zip file written in a previous step.

  // The LiveDgraphCluster is the name of a defined dgraph-cluster

  // in the application config. If the name of the cluster is

  // different or there are multiple clusters, You will need to add

  // a line for each cluster defined.

  //LiveDgraphCluster.applyConfigSnapshot();

  // AssemblerUpdate updateAssemblers

  // Updates all the assemblers configured for your deployment template application.

  // The AssemblerUpdate component can take a list of Assembler Clusters which it

  // should work against, and will build URLs and POST requests accordingly for each

  // in order to update them with the contents of the given directory.

  //AssemblerUpdate.();

 

  // To promote using a direct connection, as in prior versions (3.X) of Tools

  // and Frameworks, comment out the prior lines and uncomment the following line.

  IFCR.promoteFromAuthoringToLive();

  ]]>

  </bean-shell-script>

  </script>

After changing this, when you do the promotecontent, then it directly updates the IFCR.

2)Updating the File Store Factory

The ATG-Endeca integration includes the /atg/endeca/assembler/cartridge/manager/DefaultFileStoreFactory component.ExtendedFileStoreFactory has a configurationPath property for specifying the directory to retrieve the promoted content from.

updating the FileStore Factory has the Following approaches

1)Single MDEX

If your environment includes a single MDEX engine (for example, if all indexed content is in one language, or content is in multiple languages but all languages are indexed in the same MDEX), you can enable file-based content promotion by performing the following steps:

1.Set the storeFactory property of the /atg/endeca/assembler/cartridge/manager/DefaultWorkbenchContentSource component to theDefaultFileStoreFactory component:

storeFactory=\

/atg/endeca/assembler/cartridge/manager/DefaultFileStoreFactory

2.Set the storeFactory property of the /atg/endeca/assembler/admin/EndecaAdministrationService component to theDefaultFileStoreFactory component:

storeFactory=\
/atg/endeca/assembler/cartridge/manager/DefaultFileStoreFactory

3.Set the configurationPath property of the /atg/endeca/assembler/cartridge/manager/DefaultFileStoreFactory to the file-system pathname of the directory to retrieve promoted content from. For example:

configurationPath=\
ToolsAndFrameworks/11.0.0/server/workspace/state/repository/ATG

Once this configurations are done, then Do the Promote Content . You can able to see the promoted content in the ATG App.

For Information on Updating the Multiple Estore Instances, Refer Cluster Setup for updating the Estore Instances.