Unmapped Application Artifacts
The Unmapped Application Artifacts option is used to manage artifacts that are not mapped to any of the BizTalk360 Alarms for monitoring.
The Unmapped artifacts status is shown on the Home Page of BizTalk360. The status is considered healthy when all the application artifacts in an environment are mapped to an alarm. It will list the artifacts that are left unmapped for monitoring. By clicking on the link Unmapped Application Artifacts, the user can view the list of unmapped artifacts in an environment.
To look into the unmapped artifacts within the environment, follow the below steps:
- Log in to the BizTalk360 application.
- Select the environment for which you want to map the artifacts.
- Select Monitoring and expand Manage Mapping
- Select Application and click the Unmapped Application artifacts tab. This will list all the application artifacts that are currently unmapped for monitoring.
- The Unmapped Monitoring state is the default state for application artifacts. You can set the expected state as start/stop, enable/disable, and start monitoring the artifacts. Use the Do Not Monitor state if you don't want to monitor a particular artifact. In such cases, such artifacts will not be listed in the Unmapped Application Artifacts list.
- Select the artifact and click on Configure Mapping, here you can set the expected state of the unmapped artifact.
- By selecting the alarm, you can map the artifacts to any other available alarms in the environment.
- By enabling the auto-correct, you can set the retry count and reset interval for the mapped artifacts.
AutoCorrect Not Configured Artifacts
This section displays all the mapped artifacts. Here, you can select individual artifacts to set their auto-correct state or choose all artifacts at once to apply auto-correct settings in a single action