Instead of filling the tables directly, it is also possible to hand over jobs via an XML file. The default location for XML files to be used by the initiator is the directory Configurator\Log\EAI_Jobs on the server, on which the Empirum Interface Service runs (normally, the Empirum server).

It is also possible to write several jobs into one XML file. The EAI ignores irrelevant jobs.

Two examples for how to structure the XML file:

<?xml version="1.0" encoding="utf-8" ?>
<EmpTransport Interface="EAI" Version="11.1">
<commands>
<ClientCreate ActionType="1" ActionCode="0" TargetObjectType="1">
<parameters>
<ClientConfig>
<ClientName>29A7F31C901234</ClientName>
<Workgroup>THDWKGR</Workgroup>
<MACAddress>000C29A7F31C</MACAddress>
<PXE>1</PXE>
<DHCP>1</DHCP>
<OperatingSystemType>WindowsWorkstation</OperatingSystemType>
<HardwareType>Desktop</HardwareType>
</ClientConfig>
</parameters>
</ClientCreate>
</commands>
</EmpTransport>

If more than one job has to be executed, these jobs are entered into the respective tables as new jobs, beginning on top. The current version does not provide information on the result of the job.

The version check="11.1" is not included any more in the current Empirum Interface Service version and can be ignored.

<?xml version="1.0" encoding="utf-8" ?>
<EmpTransport Interface="EAI" Version="11.1" >
<commands>
<ClientDelete ActionType="2" ActionCode="0" TargetObjectType="1">
<parameters>
<ClientConfig>
<ClientName>PC29CF9724</ClientName>
<Workgroup>Workgroup</Workgroup>
<MACAddress>000C29CF9724</MACAddress>
<PXE>1</PXE>
<DHCP>1</DHCP>
</ClientConfig>
</parameters>
</ClientDelete>
<ClientCreate ActionType="1" ActionCode="0" TargetObjectType="1">
<parameters>
<ClientConfig>
<ClientName>PC29CF9724</ClientName>
<Workgroup>Workgroup</Workgroup>
<MACAddress>000C29CF9724</MACAddress>
<PXE>1</PXE>
<DHCP>1</DHCP>
<OperatingSystemType>WindowsWorkstation</OperatingSystemType>
<HardwareType>Desktop</HardwareType>
</ClientConfig>
</parameters>
</ClientCreate>
<ClientMoveToGroup ActionType="5" ActionCode="10" TargetObjectType="1">
<parameters>
<GroupConfig>
<GroupID>87231ED5-127B-45E3-810F-C5C30F068280</GroupID>
</GroupConfig>
<ClientConfig>
<ClientName>PC29CF9724</ClientName>
<Workgroup>Workgroup</Workgroup>
<MACAddress>000C29CF9724</MACAddress>
<PXE>1</PXE>
<DHCP>1</DHCP>
</ClientConfig>
</parameters>
</ClientMoveToGroup>
<ClientActivateSW ActionType="5" ActionCode="20" TargetObjectType="1">
<parameters>
<GroupConfig>
<GroupID>87231ED5-127B-45E3-810F-C5C30F068280</GroupID>
</GroupConfig>
<ClientConfig>
<ClientName>PC29CF9724</ClientName>
<Workgroup>Workgroup</Workgroup>
<MACAddress>000C29CF9724</MACAddress>
<PXE>1</PXE>
<DHCP>1</DHCP>
</ClientConfig>
</parameters>
</ClientActivateSW>
<ClientSetVariable ActionType="5" ActionCode="2" TargetObjectType="1">
<parameters>
<ClientConfig>
<ClientName>PC29CF9724</ClientName>
<Workgroup>Workgroup</Workgroup>
<MACAddress>000C29CF9724</MACAddress>
<PXE>1</PXE>
<DHCP>1</DHCP>
</ClientConfig>
<VariablesConfig>
<VariableName>READYTOINSTALL_TEST</VariableName>
<VariableValue>1</VariableValue>
<VariableType>ComputerVariable</VariableType>
</VariablesConfig>
</parameters>
</ClientSetVariable>
</commands>
</EmpTransport>

The current self-provisioning feature uses this XML file (example 2) to delete or create systems, assign them to the correct configuration group and fill variables.