Server workflows for HP Matrix Operating Environment

31
The following steps explain how to support the Power OFF operation on a new server:
Implement the logic to execute a Power OFF operation on the server’s remote management interface into a new
subflow.
 Make sure the new subflow will receive all the necessary input parameters:
o IP Address of the remote management interface
o If necessary, add login (username/password) credentials into OO System Accounts
o Power OFF command to execute on remote management interface
o Any other parameters to fulfill the flow logic
 Make sure that the logic/command will turn off the system after successful execution.
 Capture the results
o Command output in case of success
o Error message in case of failure
 Once the newly created subflow has been tested successfully, modify the PowerOff 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 PowerOff subflow.
o The failure transition of the new subflow should return failure from PowerOff subflow.
Note that the main flow (Server Power OFF) 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 above steps, the Server Power OFF 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.
Testing and troubleshooting
This section provides information about testing changes made to the server OO workflows.
Testing can be done at various levels. The workflow writer may test the data collection and transformation aspects
independently from Matrix OE and OO. The workflow writer may then proceed to edit the workflows, adding their
specific subflows and contents. From that point, testing may be done within OO Studio. Finally, once testing within
OO is successful, the workflow writer will perform end-to-end testing,
Testing a workflow or subflow
During the implementation of a flow (main or subflow) on OO Studio, OO Studio keeps checking for the errors. Once
the developer successfully implements the execution logic into the flow, the behavior of the flow can be tested on the
Studio using “Debug flow” tool, by providing appropriate parameters during execution.
The following steps explain how to debug a flow:
 Double click on the flow name in the explorer window to open the flow
 Click on the “Debug flow” icon on the tool bar