A single Java process hosts both:
- Oracle WebLogic Server
- Oracle Coherence (embedded)
WebLogic CI gets created in cmdb_ci_app_server_weblogic .
i created pattern extension to create oracle coherence in generic table.
Current Behavior
When the hosting Java/WebLogic process is stopped:
- The WebLogic CI is correctly marked as Absent.
- The Oracle Coherence Generic Application CI remains Installed/Operational and is not marked Absent.
When the process is started again and Discovery is rerun:
- The WebLogic CI returns to Installed status as expected.
- The Coherence CI is rediscovered and updated (Last Discovered timestamp changes), but since it never became Absent, it remains Installed throughout the process.
Is there any additional configuration, relationship, attribute, process linkage, correlation field, classifier, or lifecycle mechanism required for a custom Generic Application CI (cmdb_ci_appl_generic) created from a pattern extension to participate in the same absence/lifecycle handling as the parent WebLogic CI?
Specifically, what determines whether a Generic Application CI is marked Absent when the backing discovery process is no longer present?
Any guidance on recommended modeling or lifecycle best practices for custom application CIs created through pattern extensions would be appreciated.
Thank you.
