# Agidxs

An Agidx component is defined. An indexing cluster is used to simplify common operations across multiple Agidxs. The indexing cluster is described in the previous Dgidx section.

In addition to standard Agidx configuration settings and process arguments, the Deployment Template uses several configurable properties and custom directories during processing.

- `numLogBackups` - Number of log directory backups to store.
- `numIndexbackups` - Number of index backups to store.
- `incomingPreviousOutputHost` - Host to which source data files are extracted.
- `incomingPreviousOutputDir` - Directory to which source data files are extracted.
- `skipTestingForFilesDuringCleanup` - Used for directory-cleaning operations. If set to "true", will skip the directory-contents test and instead proceed directly to cleaning the directory. The default behavior is to test the directory contents and skip cleanup if the directory is not empty.
- The properties documented in the "Fault tolerance and polling interval properties" topic.

In addition to standard Agidx configuration and process arguments, Agidx processes add a custom property used to define which Agidx processes run in parallel with each other when they belong to an indexing cluster.

`agidxGroup` - Indicates the Agidx's membership in an Agidx group. When the run method on an indexing cluster is executed, Agidx processes within the same Agidx group are run in parallel. Agidx group values are arbitrary strings. The indexing cluster iterates through the groups in alphabetical order, though non-standard characters may result in groups being updated in an unexpected order.