Server workflows for HP Matrix Operating Environment

30
After performing the above steps, the Get Server Info operation can be invoked from ESA by providing the new
server’s UUID in the serverContextList parameter. The returned server details for the new UUID will contain the new
server data along with the last known (if not most recent) power status data.
Server Power ON operation
To perform the Power ON operation on the new server, the following changes should be made to the current
implementation:
A new subflow should be created with the logic to execute the Power ON operation on the remote management
interface.
Modify “PowerOn” subflow to add the newly created subflow.
The IP address of the remote management interface should be added into uuidHostMapper.xml file.
The following steps explain how to support the Power ON operation on a new server:
Implement the logic to execute Power ON operation on the remote management interface into a new subflow.
o Make sure the new subflow will receive all the necessary input parameters:
IP Address of the remote management interface
If necessary, add login (username/password) credentials into OO System Accounts
Power ON command to execute on remote management interface
Any other parameters to fulfill the flow logic
o Capture the results
Command output in case of success
Error message in case of failure
After the newly created subflow has been successfully tested, modify the PowerOn subflow to call it upon
matching the server model string.
o Add a String comparator to compare server model of the new server
o Add the newly created subflow as a step operation. This subflow will be called upon successfully matching
the server model string from the new string comparator
Provide all necessary inputs to the newly added subflow operation
Define the following result field parameters to hold the result of the subflow
CmdOutput: To capture the command output if the subflow executes successfully
ErrMsg: To capture failure message if the subflow execution failed
o The successful transition of the new subflow should return success from PowerOn subflow
o The failure transition of the new subflow should return failure from PowerOn subflow
Note that the main flow (Server Power ON) will also update the serverInfo.xml file with powerOn status set to false
upon successful execution. Thus, even if the server does not support an explicit power status command, the power
status is set based on any power operations performed through the OO workflows.
After performing the steps outlined above, the Server Power ON operation can be invoked from ESA by providing the
new server’s UUID and server model in the serverContext parameter. A successful execution will turn on the server if it
is turned off.
Server Power OFF operation
To perform Power OFF operation on the new server, following changes should be made to the current
implementation:
Create a new subflow with the logic to execute the Power OFF operation using the server’s remote management
interface
Modify the “PowerOff” subflow to add the newly created subflow
Make sure that the IP address of the server’s remote management interface is added into uuidHostMapper.xml file.