- 23 Apr 2024
- 2 Minutes to read
- Print
- DarkLight
- PDF
Mapping Configurations
- Updated on 23 Apr 2024
- 2 Minutes to read
- Print
- DarkLight
- PDF
This section helps the user to define the Threshold and Endpoint Configurations for monitoring.
Threshold Configuration
This setting allows the user to define the default configuration values for threshold monitoring.
The error and warning threshold limit for the Disk, System Resources, BHM and Service instance monitoring can be set here, the user can alter these limits based on the business usage. These threshold values will automatically get reflected in the following monitoring sections.
- BizTalk/SQL Server Disk usage monitoring (Default Warning count 20, Error count 40)
- BizTalk/SQL Server System resource monitoring (Default Warning count 20, Error count 40)
- By default, the maximum polling frequency is set to 15 seconds per minute, but you have the option to adjust it to a maximum of 30 seconds per minute.
- BHM monitoring (Default Warning count 20, Error count 40)
- Service Instance (Default Warning count 10, Error count 20)
This configuration will save time if you have multiple servers, as the values you define here will be reflected across all the server mapping.
Endpoint Configurations
This setting will automatically update the endpoint URLs from BizTalk Server if there is any change.
If any folder location or queues are configured for monitoring, BizTalk360 actually monitors the reachability of the endpoint URLs for FTP/SFTP/FILE and IBM MQ. If that URL is modified in BizTalk Server then BizTalk360 won't be able to monitor it further, the monitor status will be set to orphaned. To handle this situation, enable the endpoint configuration, which will automatically update the Endpoint URLs if they change and continue to monitor without any interruption.
Restart Host Instance
The automatic restart configuration is designed to initiate a restart of host instances if there is a threshold violation in the monitoring of File, FTP, or SFTP.
To update the automatic restart settings for a specific host instance, simply click on the respective host instance listed .
- The "Number of retries" parameter indicates the number of retry attempts that will be made if a host instance restart fails.
- The "Retry interval" refers to the time duration between each retry attempt.
- Enabling the "Reset on new issues" option will reset the retry count to 0 whenever new issues occur, ensuring a fresh restart attempt.
After successfully setting up this, users are permitted to enable the automatic restart option in the file location threshold monitoring configuration. This can be done through the following path: Monitoring -> Manage Mapping -> File Location.
The "Restarted History" section displays a log of host instance restart occurrences, including the status (success or failure), timestamp, and the number of retry attempts made.
Certificates
This settings enables the BizTalk and IIS servers for certificate Monitoring.
- All the available BizTalk and IIS server in the environment will be listed here.
- To configure certificate monitoring configuration, simply click on the respective server .
- Enable the monitoring toggle .
- Select the certificate stores for monitoring and click on save. You can monitor only the certificates which are available in the chosen store.
After successfully setting up this, users are permitted to map the certificates for monitoring . This can be done through the following path: Monitoring -> Manage Mapping -> BizTalk Server(or)IIS Server.