WebSphere Discovery Issues – Clusters and EAR Classification

[bertrand06]

Hello everyone,

I’m reaching out for help regarding the WebSphere discovery that I’ve just implemented. I’m currently encountering a few difficulties and would appreciate any guidance on the following points:

1. WebSphere Clusters: I’ve successfully discovered the WebSphere server clones, but I’m unable to identify the clusters that support them. Is this a mistake on my part, or is there a specific configuration required to also discover the clusters?

2. EAR Classification: I noticed there is a cmdb_ci_app_server_ws_ear class in the CMDB, but the discovery classifies the EARs under the cmdb_ci_web_application table. Could someone explain why this different classification occurs?

Thank you in advance for your feedback and assistance!

Best regards,

[mike533mike]

For WebSphere Clusters, the discovery process may not automatically identify clusters unless explicitly configured. Ensure your discovery patterns include cluster-specific attributes and that the clusters are properly defined in WebSphere. You may need to adjust the discovery settings or scripts to capture cluster information.

Regarding EAR classification, the discrepancy occurs because discovery tools often classify EAR files based on their deployment context. If an EAR is deployed as a web application. Review your discovery patterns and classification rules to ensure they align with your intended CMDB structure.

[bertrand06]

Hello,

Thank you for your response. After verification, unless I am mistaken, I do not see any cluster-specific attributes in the discovery model. I was surprised not to have this information, even though the clones are correctly detected.

Regarding our WebSphere configuration, the clusters are visible, and everything is properly configured. If you have any insights to help me retrieve this information, I would appreciate it. Apologies for my lack of knowledge on certain aspects—I do not yet have the necessary experience.

As for the EAR files, since Discovery initially detects the WebSphere infrastructure, I expected a classification in the dedicated table. After checking the suggested relationships, there is no "Contains IBM WebSphere AS" relationship. This could be the cause.