Corolar Release 7.1.0


The 7.1.0 release of Corolar includes all features from previous releases and hotfixes,as well as a number of enhancements to core Corolar components.

Affected Components

The affected components section describes the Corolar components for which this particular release applies.

Corolar Monitor

This release contains a number of new features for Corolar Monitor

  • Corolar can now correlate messages and their corresponding response (ACKs) for any type of messages. Previously, only HL7 v2.x was supported for message/ACKs correlation
  • Corolar can now correlate inbound messages with its corresponding outbound messages. This feature can be turned on in “Interface Settings” by clicking “YES” on “Enable Message Correlation” and accessed by going to Message Search and “View Correlated Messages”
  • Corolar Monitor “Settings” is now more granular, giving the user more control on permission settings for different roles. All security settings will be preserved when the user upgrades to 7.1.0
  • User Interface Enhancements
    • Interface Dashboard is now the default landing page when accessing the Corolar Monitor
    • User interface revamped by minimizing the number of scroll bars
    • There are now default values when creating new interfaces
    • Interfaces that have been previously configured will not be listed in the drop down list while configuring new interfaces
    • The interface name is now displayed while viewing message search results
    • The Corolar Interface Report is now presented in its own window, maximizing the use screen real estate
  • Exception/Fault Management Viewer
    • Integrated with the Corolar Interface Dashboard, users can click on the exception column on the dashboard for a specific interface and be brought to Exception Management viewer directly showing exceptions/faults for that interface
    • Users can also navigate to Exception Management directly from the Corolar Monitor Navigation bar
    • The Exception Management viewer allows the user to view and manage exceptions/faults
    • The viewer also captures Monitored events (e.g. Lack of messages and queue threshold exceeded)
    • Alerts can be set up for Exceptions/Faults based on severity level
    • Auditing is built-in with Exception Management

Corolar BizTalk Artifacts

  • Users can now reload messages that were stored in the file system, due to the Corolar DB being unavailable, into the Corolar DB
  • Exception/Fault Management
    • Pipeline Components, XML Schema and an API is provided to the user so custom exceptions/faults can be generated and published from BizTalk to the Corolar DB
    • Sample bindings are provided for the user to use as a template for setting up the send ports/receive ports required to enable Exception/Fault capturing and publishing
    • User documentation is available to guide the user to use the exception management artifacts

Corolar SDK

  • Included a component to guide the user on how to integrate Exception Management with maps

Known Issues

Corolar Monitor:

1. Under Audit Reports, clicking on the dropdown list sometimes does not work


When the user selects the filtering criteria for Audit reports, sometimes the dropdown list for some criteria would not show up when the user clicks on the down arrow


UI controls are not reset properly


Click on “View Report” to view a report, and the UI controls will be reset

2. Under Exception Management, the filtering sometimes show the same receive port name multiple times


If the user has configured multiple Receive Locations (that are under the same Receive Port) to be monitored in Corolar Monitor, under Exception Management Inbound Interface Filtering, the Receive Port name will show up multiple times instead of the individual Receive Location name


As of v7.1.0, Exceptions are always recorded under the port name. Even in cases where there are multiple receive locations for one receive port, and the receive locations are configured to be monitored under Corolar Monitor (and not receive port), the exceptions are still written at the receive port level. This potentially could cause the exception management page inbound port filtering to show the same receive port name multiple times


This issue will be fixed in the next Corolar Cumulative Update