The application
configuration file
<app dir>/config/script/AppConfig.xml and its
associated files define the hosts, components, and scripts that make up an EAC
application and that orchestrate updates by executing the defined components.
The Deployment Template provides a single
AppConfig.xml file that contains pointers to other
files that define distinct parts of an application, separate scripts from
component provisioning, and are used for other purposes. The full set of
application configuration files are as follows:
AssemblerConfig.xml- Specifies the application server cluster that allows for quick updating of all Assemblers.AuthoringDgraphCluster.xml- Specifies the Dgraphs used in the authoring environment and a script that pushes configuration from Workbench to each Dgraph in the authoring cluster.DataIngest.xml- Specifies data processing scripts, including the baseline update script, partial update script, and the components to perform data processing such as CAS or Forge and Dgidx.DgraphDefaults.xml- Specifies default values that are inherited by all Dgraph components. These values include host IDs, data processing paths, and Dgraph flags.InitialSetup.xml- Specifies scripts to perform initial setup tasks.LiveAppServerCluster.xml- Specifies your application server clusters, the servers within each cluster, and the applications running on a given Assember.LiveDgraphCluster.xml- Specifies the Dgraphs used in the live environment and a script that pushes configuration from Workbench to each Dgraph in the live cluster.ReportGeneration.xml- Specifies the hosts used for logging and report generations, and several scripts that produce log files at different time intervals.UsageCollectionConfig.xml- Specifies the Dgraph clusters and application server clusters from which usage is collected.WorkbenchConfig.xml- Specifies the Endeca Configuration Repository component and a script that promotes content from the authoring environment to the live environment.
In addition to these files, any number of
--app-config arguments may be specified to the
Controller class in the EAC development toolkit. All of the objects in the
files will be read and processed and scripts can refer to components, hosts, or
other scripts defined in other files.
