Operating Environment Software Owner's manual

<nicID>nic0</nicID>
<macAddress>00:1E:0B:CC:61:B0</macAddress>
<ipAddress xsi:nil=”true”/>
<networkInterfaceName>vlan84-dhcp-pxe-sa</networkInterfaceName>
<pxeEnabled>true</pxeEnabled>
</networkInterfaces>
</networkInterfaceList>
<storageInterfaceList/>
<serverModel>ProLiant DL380 G5</serverModel>
<osType>Windows</osType>
<memoryMB>32000</memoryMB>
<coreCount>4</coreCount>
<cpuFrequencyMHz>3000</cpuFrequencyMHz>
<cpuCount>2</cpuCount>
<cpuFamily>x86_64</cpuFamily>
<powerOn>true</powerOn>
<extendedAttributes xsi:nil=”true”/>
</ooServers>
The following screen shot from OO Studio shows the reference workflow which reads and processes
the “serverInfo.xml” file:
For each server in the “inventoryList.xml” file, the “Get Server Info” workflow is invoked. In brief,
the workflow extracts the detailed server definition from “serverInfo.xml”, and then uses the server’s
management processor to determine the current power state. The server management processor
operations are invoked through additional workflows. The persisted power state is updated if required
and the resulting server record is returned as an XML document to the ESA web service. The ESA web
service processes the returned XML document and hands it back to the Logical Server Management
that functions as the upper level inventory manager. The logical server software layer then updates the
persisted inventory record for the server thereby enabling Insight Orchestration to include the server as
a part of its inventory. As the servers are processed, they become visible in Insight Orchestration’s
“Servers” interface.
30 Configuration