In the hosts element you list each host by a host ID, a host name, a port number, and (optionally) properties and directories.
The host syntax is as follows:
<host host-id="host1" host-name="localhost" port="8888"> <properties> <property name="department" value="engineering" /> <property name="department" value="prof services" /> <property name="enforceDiskQuota" /> </properties> </host>
In this example the port is the HTTP port through which the EAC Central Server communicates with its Agents. The optional use of host-id to alias host definitions is explained in the following section. The optional addition of properties and directories is described later in this document.
Related links
In each host definition, you can create a unique alias called host-id that may be used to refer to the specified host and port. (The host-name and port do not need to be unique.)
For example, say you defined host1 as follows:
<host host-id="host1" host-name="localhost" port="8888" />
Later, when defining components, you could simply refer to that host-id when specifying the host for a given component.
<dgidx name="dgidx-0" host-id="host1">
Aliasing hosts in this way has two benefits:
As part of host provisioning, you can also provision directories using a full path and a name.
For example, assuming a host has already been provisioned as defined above, you could add the following element:
<host > ... <directories> <directory dir-id="input"> <path>C:\staging_app\working\input</path> </directory> </directories> </host>
