Server workflows for HP Matrix Operating Environment

33
Note: ESA logs are enabled by default; no specific settings are required. The log file is located at: C:\Program
Files\HP\Virtual Server Environment\logs\esa.log.
 ESA not calling OO
A call from ESA to an OO workflow can fail for following reasons:
o HP SIM service is not running or not responding
o OO RSCentral service is not running or not responding
o OO RSJRAS service is not running or not responding
o ESA (esa.properties) is not configured properly
To correct the problem, follow the steps below:
o Start/Restart the following services:
 HP SIM
 RSCentral
 RSJRAS
o Check and ensure that the correct values for ESA configuration in the esa.properties file are set for
following parameters:
 esa.oo.admin.username
 esa.oo.admin.password
 esa.oo.host
 esa.oo.port
 esa.oo.service.ws.path
o Check and ensure that the correct path is configured in the esa.properties file for the workflow
being invoked,
 OO Callback to ESA is failing
OO callback to ESA can fail for the following reasons:
o Wrong configuration for esa.oo.server.replytoURI property in esa.properties file
o Wrong configuration for jetty.host parameter in jetty.xml file.
o Invalid XML response from workflow execution
o LSA service is not responding or not running
o ESA service is not responding or not running
To correct the problem, follow the steps below:
o Ensure that the esa.oo.server.replytoURI property has the correct value to locate ESA service
o In the case of a remote standalone OO server, check and ensure that the jetty.xml file has been
configured with the proper IP address or has no default value set for the jetty.host parameter
o Check the OO Central report for any erroneous steps performed by the workflow during execution
 Ensure the Workflow response includes a valid XML string and is compatible to the XSD
defined for server services
o Start/Restart LSA and/or ESA service
 OO not able to connect to server’s remote management interface
During workflow execution, some of the operations try to connect to the remote server management interfaces
(iLO2). These operations can fail for following reasons:
o The remote server management interface is not accessible due to network issues
o Connection timeout due to slow network speed
o Wrong IP address configuration in the uuidHostMapper.xml file
o Authentication failures due to invalid username/password
o The service (ssh) being invoked is disabled or running with non-default port on the remote server
management interface
To correct the problem, follow the steps below: