# Specifying a CAS Server host

The `host` element defines the specifics of the machine on which the CAS crawls are deployed. The `host` configuration is the same for crawls that write output to a Record Store instance and crawls that write to a record output file.

The `hostName` is set automatically when you run the deployment script. You therefore do not typically have to change the hostname unless you decide to start using a CAS Server on another machine.

Note: The Deployment Template checks the host and port definition in AppConfig.xml, NameCasCrawlConfig.xml, and fetchCasCrawlDataConfig.xml. If host or port information conflicts in any of these three files, errors will occur. Either make sure the host and port configuration is same in the three files, or comment out host and port configuration in both NameCasCrawlConfig.xml and fetchCasCrawlDataConfig.xml and put the configuration in AppConfig.xml.

To specify a CAS Server host:

1. Open the AppConfig.xml file in a text editor.
2. Locate the `Servers/hosts` section and do the following:
   - Add a `host` element and specify an `id` attribute for the machine running the CAS Server.
   - Specify a `hostname` attribute for the machine name running the EAC Agent.
   - Specify a `port` attribute specifies the port on which the EAC Agent is listening. This is the Endeca HTTP Service port on that server (`8888` in the example).
   For example:

       <!—
       ########################################################################
       # CAS servers/hosts
       -->
       <host id="CASHost" hostName="WEB009.mycompany.com" port="8888" />