Server workflows for HP Matrix Operating Environment

34
o Ensure the network connectivity and accessibility of the remote server management interface
o Check and ensure the user credentials configured in the OO System Account is valid for the remote
server management interface (and appropriate use of the server UUID)
o Check and ensure that the service being invoked through the workflow is enabled and running on
the default port
 Unable to set/retrieve value from registry
The OO Workflows may fail with the error “Unable to set/retrieve value from registry” due to following reasons:
o In the case of a remote OO server, the server data files need to be copied to the OO server. The
location of these files must be configured in OO Studio in the Hpio_Install_Path system property. If
this configuration is missing, the OO workflow execution will fail with the exception set to “Unable
to set/retrieve value from registry.”
To fix this problem, follow the steps below:
o Configure the Hpio_Install_Path system property with the value set to the path for esa_extension
folder where server data files can be located. The remote OO server setup is outlined in the section
Configuring OO.
 GetInventory is failing
The Get Inventory workflow can fail for following reasons:
o The inventoryList.xml file is missing or not readable from the configured location:
C:\Program Files\HP\Matrix infrastructure orchestration\esa_extensions\server
To correct the problem, follow the steps below:
o Ensure that the inventoryList.xml file is available in the configured location:
C:\Program Files\HP\Matrix infrastructure orchestration\esa_extensions\server
o Check the OO Central reports or central_wrapper.log file for any fatal errors during execution of
the flow. In this case, ESA would have sent a “Timeout” response back to LSA.
 GetServerinfo is failing
The Get Server Info flow can fail for following reasons:
o Missing serverInfo.xml file from the configured location:
C:\Program Files\HP\Matrix infrastructure orchestration\esa_extensions\server
o Unsupported server model
o Invalid UUID
o Network issues while connecting to remote server management interface
o Wrong IP address configuration in the uuidHostMapper.xml file
o Invalid user credentials while connecting to the remote server management interface
o Fatal errors from OO Central and/or OO RSJRAS services
To correct the problem follow the steps below:
o Ensure serverInfo.xml file is available and readable from the configured location:
C:\Program Files\HP\Matrix infrastructure orchestration\esa_extensions\server
o Ensure a supported Server Model configured in the serverInfo.xml file and validate the server model
string contains the anticipated server type or name expected in the workflow
o Ensure a valid UUID is received as input parameter to the flow
o Ensure the UUID is configured in the uuidHostMapper.xml file
o Ensure the IP address is configured for the remote server management interface is valid for the
given UUID
o Ensure network connectivity and accessibility to the remote server, management interface
o Ensure valid user credentials are configured for the remote server management interface in the OO
System Accounts
o Check the OO Central reports or central_wrapper.log file for any fatal errors during execution of
the flow. In case of fatal errors in OO logs and/or Central reports, ESA would have sent a
“Timeout” response when invoked by Matrix OE.