Modify the /atg/endeca/assembler/AssemblerApplicationConfiguration component in the local server configuration. Set the useFileStoreFactory property to true to automatically create a corresponding FileStoreFactory for each EAC application and set a reference to that FileStoreFactory on the application’s WorkbenchContentSource:

useFileStoreFactory=true

The AssemblerApplicationConfiguration component has a prototypeFileStoreFactory property that points to the /atg/endeca/assembler/cartridge/manager/PrototypeFileStoreFactory component. (The PrototypeFileStoreFactory component’s $basedOn property is set to the DefaultFileStoreFactory component described in the Single-MDEX Environment section.) The FileStoreFactory instances are created from the PrototypeFileStoreFactory component.

Set the assemblerContentBaseDirectory property of the AssemblerApplicationConfiguration component to the file-system pathname of the directory to retrieve promoted content from. For example:

assemblerContentBaseDirectory=\
   ToolsAndFrameworks/version/server/workspace/state/repository

For each FileStoreFactory created, the corresponding EAC application name is appended to the assemblerContentBaseDirectory value to set the FileStoreFactory component’s configurationPath property. For example, if assemblerContentBaseDirectory is set as shown above, the configurationPath property for an application named ATGes would be ToolsAndFrameworks/version/server/workspace/state/repository/ATGes.

Modify the /atg/endeca/assembler/admin/EndecaAdministrationService component in the local server configuration. Set the $class property to atg.endeca.assembler.MultiAppAdministrationService:

$class=atg.endeca.assembler.MultiAppAdministrationService

The MultiAppAdministrationService class is able to handle updates to multiple store factory instances.

Set the storeFactory property of the EndecaAdministrationService component to null:

storeFactory^=/Constants.NULL