This one is still baffling me. The error while service mapping:
The system failed to create an inclusion connection from the CI (type: cmdb_ci_app_server_websphere). There is a containment rule for this CI type and a pattern which is associated with the contained item, but no inclusion connection created.
There is a containment rule, yes. Is this saying that, it expects cmdb_ci_app_server_websphere to contain one of the recommendations?
Each of the IBM Websphere app servers 'points' at dozens of Websphere Servers hosted on dozens of virtual servers. Each of the Websphere Servers contain dozens of Websphere EAR deployments. It all seems pretty complete to me.
I could follow the instructions in Service Mapping Discovery failed to create an inclusion connection from the CI (type: cmdb_ci_app_se...
That tells you to put an entry in an "ecc_agent_property" to make the errors go away. We don't have the property "map_accuracy_errors_ci_types_to_exclude" set up yet.
I suppose that is an option but it seems like I am missing a fundamental understanding of Websphere components. The patterns seems to discover quite a bit. I DO eventually get to an EAR file, one of the contained suggestions it is expecting.
I suppose what I am looking for out of this question. Where can I learn more about what a Websphere service map is SUPPOSED to look like AND why does mine deviate? I suppose it would be nice to know if it is common practice just to create the entry in "map_accuracy_errors_ci_types_to_exclude" and silence the error messages.
