Mapping Configurations

  • Updated on Mar 4, 2025
  • Published on Apr 23, 2024
  • 4 minute(s) read
Prev Next

This section helps the user to define the Threshold and Endpoint Configurations for monitoring.

Threshold

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

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.

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 .

  • Enable masking for Thumbprints- Enabling this option will hide the specific thumbprints of certificates, displaying them only as masked values in certificate listings and alerts.

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

When you disable the server for certificate monitoring , all the associated monitor mapping configuration will be removed .

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.


IBM MQ

In this section, the Queue Manager that hold queues mapped to BizTalk are listed along with their Name, Configured Server and Connection Name. By configuring the connection between BizTalk360 and the Queue Manager, you can monitor the available Queues, Channels and Listeners.

To configure Queue Manager, simply click on the respective Queue Manager and select Server connection or the Client connection in configuration blade.

Channel Type

-Client connection

  • In IBM MQ, a client connection allows applications on different machines to access queue managers on remote systems without requiring a full MQ installation on the client machine.

  • You can connect the queue manager with BizTalk360 using the authentication details alone as the other connection details will be fetched from the Client channel definition table that must be accessible by web and monitoring service installed server.

  • Note: Ensure the MQCHLLIB, MQCHLTAB environment variables are configured correctly to point to the CCDT file's location.

-Server connection

  • Connection Name - Update the Hostname or Ip address along with the port. e.g., Hostname (1414)

  • Channel Name -Enter the channel name used to communicate with the queue manager. This is a case sensitive.

  • Transport Type: Select the transport type, typically TCP used for IBM MQ communication.

Authentication Configuration:

  • You can update the service account credentials globally under Settings->System Settings->Service account and reuse it across the application.

  • Else, Enter the user ID and password that has permission to connect to the IBM MQ queue manager.

Login as respective user and execute below command to update object authorization of Queue Manager and its Queue


  • setmqaut -m <queueManagerName> -t queue -n <queueName> -g mqm +set

  • setmqaut -m <queueManagerName> -t queue -n <queueName> -g mqm +inq

Enable SSL (Optional)

  • Check the SSL option if (SSL) communication is required for connecting to the queue manager.

  • If SSL is enabled, you can optionally provide:

    • SSL Cipher Specification - Every MQ Channel definition includes the SSLCIPH attribute. The value is a string with a maximum length of 32 characters. SSL Cipher specification is optionally.

    • SSL Peer Name - Peer name specifies the SSL Peer Name used on the channel. The SSL Peer attribute is used to check the Distinguished Name (DN) of the certificate from the peer queue manager or client at the other end of an IBM® WebSphere® MQ channel.

click the Save button to create the connection between BizTalk360 and the IBM MQ Queue Manager. On successful connection, ' Is Configured' and 'Is Connected' column in the grid will turn green, which indicates active connection.