# Integrating and Running CAS Crawls

The Deployment Template provides support for running CAS crawls. This section describes the configuration changes necessary to integrate and run CAS crawls using the Deployment Template. You must upgrade the Deployment Template with the CAS WSDL client stub files for CAS integration to work. If you have not upgraded the Deployment Template, see the CAS Installation Guide before continuing with this chapter.

- About storage types for CAS crawls
  The Content Acquisition System can write output from a crawl to either a Record Store instance (the default) or to a record output file. The configuration of the Deployment Template varies depending on whether a crawl is configured to write output to a Record Store instance or configured to store crawl output in record output files. This topic describes the main differences between the storage types as they affect the operations of the Deployment Template.
- About Deployment Template files for both storage types
  This topic describes the files you modify in order to integrate and run CAS crawls as part of the Deployment Template.
- EAC Component API methods for CAS
  In your AppConfig.xml code, you can coordinate CAS crawls and baseline or partial updates using the methods available in `ContentAcquisitionServerComponent`.
- Integrating and running CAS crawls that write to Record Store instances
  This section describes the high-level steps for integrating and running a CAS crawl that writes output to a Record Store instance.
- Integrating and running CAS crawls that write to record output files
  This section describes the high-level steps for integrating and running a CAS crawl that writes output to a record output file.