Server workflows for HP Matrix Operating Environment

Locations of XSD and WSDL files

Once ESA is installed as part of Matrix OE, the WSDL is available at

http://localhost:52000/esa/services/serverservice?wsdl.

The XSD file (esa-server-model-1.0.xsd) can be found at C:\Program Files\HP\Virtual Server

Environment\esa\etc\xsd\esa-server-model-1.0.xsd.

Supporting servers not using Virtual Connect

The Matrix OE solution provides support for a range of servers, including blades using Virtual Connect, blades not

using Virtual Connect, and rack-mount HP servers. The support for Integrity servers not using Virtual Connect is

included beginning in the Insight Dynamics 6.2 release. Information regarding Virtual Connect blades can be

gathered automatically. Control operations can be performed through Virtual Connect, or for customers using

infrastructure orchestrationin Matrix OE via OO workflows (using the HP iLO2 interface for HP servers not using

Virtual Connect). The following sections describe how to take advantage of the range of server support in Matrix OE,

and customize it as appropriate for your environment. The Matrix OE solution includes integrated support for:

 HP server blades with Virtual Connect

 HP server blades not using Virtual Connect using iLO2 or later

 HP Rack-mount servers using iLO2 or later

The XML files used to supply information about non-Virtual Connect servers can be customized for a specific customer

environment (e.g., describing the HP blades and HP rack-mount servers not using Virtual Connect).

The ESA server OO workflows support:

 Discovery of HP servers not using Virtual Connect

 Retrieving details of HP servers not using Virtual Connect

 Powering ON the HP servers not using Virtual Connect (via iLO)

 Powering OFF the HP servers not using Virtual Connect (via iLO)

The interaction happens as follows:

1. The Matrix OE logical server management layer requests an update of its catalog through ESA, which invokes

the OO GetInventory workflow. This returns the basic server data which is loaded into the inventory of servers.

2. The logical server management layer requests more information on each of the servers, using ESA to invoke the

GetServerInfo workflow. This returns the more detailed server information (including LAN and SAN connectivity).

3. When Matrix OE needs to power on a server, it performs the operation through Virtual Connect, or uses ESA to

call the OO Server Power ON workflow which in turn uses the server’s remote management interface (iLO2) to

power on the specific server.

4. When Matrix OE needs to power off a server, it performs the operation through Virtual Connect, or uses ESA to

call the OO Server Power OFF workflow which in turn uses the server’s remote management interface (iLO2) to

power off the specific server.

Deployment and configuration of server OO workflows

The four server OO workflows (i.e. GetInventory, GetServerInfo, PowerON, and PowerOFF) are deployed as part of

the Matrix OE installation. Three XML files (described in subsequent sections) need to be modified to supply

appropriate information about the iLO2 servers not using Virtual Connect. If Virtual Connect is being used, the servers

will be automatically discovered and information gathered, so no XML file adjustments are required. The following

operations configure the OO workflows.

In OO Studio, configure the following System Account.