v11.3

Prev Next

Release Date:31st January 2025

New features

Active MQ Monitoring

  • State Monitoring: Monitor the queue states by setting the expected state (Resume , Pause) and enable auto-correct to resolve state violations.

  • Threshold Rule: Configure threshold rules to track Active MQ queue message counts and performance metrics, ensuring operational consistency. Get real-time notifications for any threshold violations.

Automated Tasks - Predefined Templates

Predefined templates provide a quick-start guide with pre-configured settings and structures tailored for common use cases. Use these templates to automate tasks such as Artifact Shutdown for Maintenance, Resume Artifacts After Maintenance, Reverse Actions, Reverse Workflow, and Clean Up Excess Storage.

EDI AS2/MDN Transactions monitoring

Enable notifications for processed and failed EDI messages, with an option to attach the corresponding MDN/997 transactions.

Enhancements

EDI Administration

  • Improved User Experience in Manage Agreement Validation:

    • Highlight validation errors directly on form fields to reduce navigation efforts.

    • Provide detailed error messages with actionable suggestions for resolution.

  • Enable direct creation of EDI Parties & Profiles from the tree view by right-clicking on relevant nodes.

Monitoring

  • IBM MQ Channel Monitoring

    • Retrieve IBM MQ monitoring configuration from the Client Channel Definition File.

    • Determine the channel state as "Started" when the channel is Running or Inactive.

    • Display the queue type (Local or Remote) in IBM Queue monitoring.

  • SQL Server Always On Monitoring:  Detects the primary and secondary server names, when SQL Servers are set up with Always On Availability.  

  • Process monitoring:  Added an option to mark the monitoring status as healthy if any one of the ports meets the expected count.

  • Clone Schedule Configuration: Create the Data monitoring schedules with the existing configuration with the clone option.

  • Unmapped Artifacts Mapping: Configure unmapped artifacts for monitoring and set auto-correction actions directly from the Unmapped Artifacts section.

  • Monitoring service performance Optimization

    • Optimized performance when the application attempts to collect data from an unavailable server.

    • Ensured the Monitoring Service continues to monitor even after detecting orphaned artifacts

Analytics

  • Added widgets to display daily completed transaction details per application.

  • Users can configure the aggregation and plot frequency, based on which the data will be displayed on the analytics widget.

  • Enhanced the performance of data collection for BizTalk Table Size and Database Disk Usage metrics.

Reporting

  • Reporting email: Users can personalize the subject line of reporting emails

  • Custom SQL Reporting has been enhanced to support multiple SQL queries in a single report.

General

  • License Activation: Improved the license deactivation flow by providing the option to remove the license when it is already deactivated.

  • Landing Page: Set the user-preferred feature as the landing page, such as the Application Dashboard.

  • Import/Export Improvements:  Indicate the orphaned ports ,queues and endpoints which are associated in monitoring mapping.

  • BizTalk360 Accessibility: Improved the accessibility challenges, providing more details;

    • Indicate the information when user is not created for BizTalk360 Service Account

    • Provide information about BizTalk/BizTalk360 databases are not reachable.

Bug fixes

Below issues are addressed in this version

Administration

  • Extended the maximum column width in Message Box, Tracking, ESB, and EDI Queries to improve content visibility.

  • Resolved the application count mismatch issue in IIS Server App Pool Details.

    Monitoring

  • Handled timeout exceptions for large datasets in the b360_alert_NotifiedResults table with an effective data purging mechanism.

  • Implemented server availability checks to skip monitoring with an orphaned warning state if the server is unreachable.

  • Fixed the regional date-time format conversion issue in the Next Run Time of the Auto-Restart Monitoring Service.

  • Removed the default alarm mapping configuration when the corresponding orphaned application is deleted from BizTalk360.

  • Resolved an issue where Message Box Data Monitoring notifications failed when the error description contained the character ‘’, causing a hexadecimal value 0x1A error.

  • Fixed the “Value cannot be null. Parameter name: source” exception in Service Instance Monitoring.

  • Addressed an issue in Azure Queues and Topics Monitoring, where mapping a queue with the same name across different resource groups resulted in incorrect mappings.

Reporting

  • Fixed an issue where Analytics reports were not generated when configured for the Analytics Dashboard with the MessageBox Database Top Tables Reserved widget.