- 22 Apr 2024
- 2 Minutes to read
- Print
- DarkLight
- PDF
Orphaned artifacts
- Updated on 22 Apr 2024
- 2 Minutes to read
- Print
- DarkLight
- PDF
Monitoring orphaned artifacts can result in discrepancies, leading to errors or exceptions in alerts and dashboards. The consolidated view of orphaned artifacts is available in the monitoring section, facilitating easy management of mappings.
The consolidated view of all the orphaned artifacts are listed in this section Monitoring->Manage Mapping->Orphaned Artifacts. The orphaned details are listed along with the details Monitor Category, Monitor Group, Artifact Type, Artifact Name ,Mapped Alarms
- Monitor Category: It represents the feature that comes under the manage mapping sections like Applications, Azure Services, BizTalk, BizTalk environment, File locations, Queues, SQL Server, SQL Server instances, IIS, Server Availability.
- Monitor Group: It represents the details as below,
- Name of the application under applications,
- Subscription name under Azure Services.
- BizTalk server name under BizTalk.
- BizTalk environment under BizTalk environment.
- File locations under File locations.
- Queues under Queues.
- SQL server name under SQL Server
- name of the instance under the SQL server instance.
- name of the IIS server under IIS
- name of the server under server availability.
- Artifact type: This column shows the details as,
- Type of artifact like Orchestration, Receive locations, send port, Send port group under application.
- Artifact like Azure logic app, Queues, Topics, API apps under Azure Services.
- Artifact like Disk, NT services under BizTalk server.
- Artifact like Host instances, Host throttling, BizTalk Health Monitor, EDI Agreements, Database size.
- Artifact like File, FTP, SFTP.
- Artifact like IBM MQ, MSMQ.
- Artifact like Disk, NT services.
- Artifact like SQL jobs under SQL server instance.
- Artifact like App pools, Website.
- Artifact Name: This column shows the details as,
- "All mapped artifacts" when the application itself becomes Orphaned.
- Name of the Orchestration, Receive locations, send port, Send port groupunder applications.
- name of the Azure logic app, Queues, Topics, API apps under Azure Services.
- name of the Disk, NT services under BizTalk server.
- name of the Host instances, Host throttling, BizTalk Health Monitor, EDI Agreements, Database size under BizTalk environments.
- name of the port under File, FTP, SFTP.
- name of the MSMQ and port in IBM MQ
- name of the Disk, NT services under SQL server.
- name of the SQL jobs.
- name of the app pool and website.
- Mapped alarms: The alarm names associated to the orphaned artifacts will be shown.
Also, you can route to the respective page by clicking "View Mapping" option on the respective orphaned artifact .
Remove Orphaned
The removal of orphaned artifacts in BizTalk360 is essential for maintaining system health and ensuring accurate monitoring .To remove orphaned artifacts from this consolidated view, select the items you wish to remove and then click on the "Remove Orphaned" option to remove orphaned artifacts mapping. This action will clear all mappings, preventing any false notifications.
Removing these artifacts ensures that monitoring and alerting systems provide accurate information, allowing for timely identification and resolution of genuine issues.