Mapping Configurations
  • 23 Jan 2024
  • 2 Minutes to read
  • Dark
    Light
  • PDF

Mapping Configurations

  • Dark
    Light
  • PDF

Article Summary

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) 
  • 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. 

When the Host Instance has High Availability enabled, the restart will be initiated according to the priority that has been configured. In the scenario of a clustered Host Instance, the active instance will undergo a restart. 

 

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. 



Was this article helpful?

ESC

Eddy, a super-smart generative AI, opening up ways to have tailored queries and responses