# Specifying a CAS Server as a custom component for record output files

The `custom-component` section defines the configuration properties of a specific CAS Server. This topic describes the configuration properties for a CAS crawl that writes output to a record output file.

Note: The configuration example below shows the CAS 3.0.x deployment template component name (i.e. the `class` attribute) rather than the CAS 2.2.x deployment template component.

To specify a CAS Server as a custom component for record output files:

Add custom-component with the following configuration:

- An `id` attribute that assigns a unique ID to a specific CAS Server.
- The `host-id` attribute points back to the id attribute of the `host` global configuration element.
- The `class` attribute specifies the class that implements the CAS deployment template component. If you are using CAS 2.2.x, specify `class="com.endeca.soleng.eac.toolkit.component.ContentAcquisitionServerComponent"`. If you are using CAS 3.0.x, specify `class="com.endeca.eac.toolkit.component.cas.ContentAcquisitionServerComponent"`.
- A `casHost` property to indicate the CAS Service which manages the file system and CMS crawls.
- A `casPort` property to indicate the port on which the CAS Service is listening. The port number must match the `com.endeca.cas.port` value that is used in the cas-server startup script. The cas-server startup configuration is in Endeca\CAS\workspace\conf\jetty.xml. Be sure to change the port number if it is not the same as the `com.endeca.cas.port` value.
- A `casCrawlFullOutputDestDir` property to indicate the destination directory to which the crawl output file will be copied after a baseline crawl. Note that this is not the directory to which the CAS crawl writes its output; that output directory is set as part of the crawl configuration.
- A `casCrawlIncrementalOutputDestDir` property to indicate the destination directory to which the crawl output file will be copied after an incremental crawl. As with the previous property, this is not the directory to which the CAS crawl writes its output. If you run incremental crawls, the default settings assume that the output format will be compressed binary files.
- A `casCrawlOutputDestHost` property to indicate the ID of the host on which the destination directories (specified by the previous two properties) reside.

For example:

    <!—
    ########################################################################
    # Content Acquisition System Server
    #
    -->
    <custom-component id="CAS" host-id="CASHost" class="com.endeca.eac.toolkit.component.cas.ContentAcquisitionServerComponent">
      <properties>
        <property name="casHost" value="WEB009.mycompany.com" />
        <property name="casPort" value="8500" />
        <property name="casCrawlFullOutputDestDir"
           value="./data/complete_cas_crawl_output/full" />
        <property name="casCrawlIncrementalOutputDestDir"
           value="./data/complete_cas_crawl_output/incremental" />
        <property name="casCrawlOutputDestHost" value="CASHost" />
      </properties>
    < /custom-component>