BizTalk360 v9.1 Features

Clustered NT Service Monitoring

The clustered NT Services running in the BizTalk environment can be monitored by configuring the expected state as ‘At least One Active’. with this feature, the BizTalk360 monitoring service will ensure that the configured service is always up and running in any of the respective clustered nodes

Recurrence Scheduled Maintenance

Schedules can be configured to stop monitoring immediately or at a later point in time, based on the maintenance plan.

• One Time Execution – Stop the monitoring only once in a specific time period, for example the deployment of BizTalk applications, which has been planned only once in the future date, i.e on June 1st from 9 AM to 11 AM.
  
• Recurrence Execution – The schedule will be created once and can be executed multiple times based on the recurrence pattern daily, weekly, monthly, i.e daily 10-11 PM, alternate weekends, 4th Wednesday of every month, etc
  

Web Endpoint Monitoring

Monitoring Status Enabled/Disabled is introduced in Web Endpoint monitoring. This enables the user to define when BizTalk360 should start/stop monitoring the configured Web Endpoint.

Clone Alarm with Artifacts Mapping

The alarm configurations and the artifacts mapping can be cloned from one alarm to other, with the Clone alarm feature.

MSMQ Age Monitoring

This threshold parameter ‘Message Age’ is added to monitor and alert the oldest message in MSMQ, based on the configured message age units Days/hours/minutes.

Event Log Data collection optimization

To optimize the performance data collection, from this version on, we are providing an option to the user to select the event logs error levels(Information,Warning,Error,etc) This way, BizTalk360 will collect event log data for only the selected error levels.

View MDN message in EDI AS2

EDI AS2/MDN message content can be viewed as an encoded and wired format.