Business Service discovery fails with error "Host XXXXX ignored since it is not in operational status"

Issue

Business Service discovery fails with error: Host XXXXX ignored since it is not in operational status as illustrated below:

Solution

When running a discovery of the Business Service, the engine expects that the operational status of the target CI be operational. If another operational status is set, then this issue can occur. For example, if Business Service is run against the target CI below, it fails because its operational status is DR Standby:

To change this behavior and add some other valid operational statuses for the Business Service discovery, add the sa.active_operational_status property into the System properties (sys_properties) table and fill in a comma separated list of values considered valid for service mapping discovery.