Corolar Release 6.12.0302.1 SP2

Description

Corolar Service Pack 2 is an update to Corolar which provides feature enhancements based on detailed feedback from customers. This release includes Role Based Access Control and Auditing for the Corolar Interface Monitor, as well as additional operational reports for interfaces. The Service Pack also contains all previous hot fixes and bug fixes.

Affected Components

Corolar Interface Monitor

The Corolar Interface Monitor now has Role Based Access Control and Auditing.

  • Upon installation of Service Pack 2, the user will be prompted for a Corolar Interface Monitor Administrative account. You will now need to log in to the Corolar Interface Monitor. To log in for the first time, please use the Administrative account that was set up during the installation process.
  • The Corolar Monitor Administrator has full control of the Corolar Interface Monitor. Roles and additional users can be set up and there is now the ability to restrict certain users to certain sections of the Corolar Interface Monitor, as well as limiting the interfaces they can access.
  • Along with Role Based Access Control, Auditing is now part of the Corolar Interface Monitor. With Auditing enabled, the administrator can run reports and inspect the audit trail of user interaction with the Corolar Interface Monitor.

For more information, please see the Corolar Interface Monitor User Guide.

Additional Interface Reports are now available. In addition to the Detailed Interface Reports provided by Service Pack 1, Service Pack 2 now contains Summary Interface Reports as well. Users can access these reports via the ‘Interface Report’ tab, ‘Summary Interface Report” within the Corolar Interface Monitor.

Included Fixes

The Corolar Service Pack 2 release includes all features and bug fixes found in the following releases:

Corolar 6.12.0302.1 Service Pack 1

Corolar Interface Monitor

Not all alert schedules are displayed on the alert schedule dropdown list

Symptoms:

Alert Schedule only shows a maximum of 10 schedules even if there are more than 10.

Cause:

There was a bug limiting the dropdown list to show only 10 schedules

Solution:

Install 6.12.0302.1 Service Pack 2

Corolar2BizTalk Send PostProcessor

Invalid message errors are not always logged in Windows Event Log

Symptoms:

If the logpath for the Send PostProcessor is set to an invalid path, no error is logged in the Windows Event log and messages are not sent to the destination.

Cause:

The Send PostProcessor was unable to handle the situation when the invalid path cannot be created automatically.

Solution:

Install 6.12.0302.1 Service Pack 2. The message will now be able to be sent to the destination and path related errors will be logged to the Windows Event Log

Known Issues

Corolar Installer

Service Pack fails to uninstall properly

Symptoms:

GAC_MSIL folder dll files are not rolled back when service pack 1 is uninstalled after service pack 2 is uninstalled.

Cause:

Service Pack 1 is unable to check the file version of the assemblies

Solution:

Step 1: Stop all related BizTalk host instances to unlock the assemblies in the GAC
Step 2: Run the following command to uninstall Corolar BizTalk Assemblies from GAC “\Dapasoft Inc\Corolar\Corolar2BizTalk\deploy\Deployment\Framework\C2BDeploy.bat” uninstall
Step 3: Uninstall the Corolar SP1 to rollback to the previous version.

Service Pack fails to uninstall properly

Symptoms:

When both Service Pack 1 and Service Pack 2 are installed, and an attempt is made to uninstall Service Pack 1 without first uninstalling Service Pack 2 unexpected behaviour happens with Corolar.

Cause:

Currently there is no automated check on the uninstallation process that Service Pack 2 must be uninstalled first before Service Pack 1 can be uninstalled.

Solution:

Manually uninstall Service Pack 2 before uninstalling Service Pack 1.

Service Pack fails to install properly

Symptoms:

Service Pack 1 can be installed after Service Pack 2 is installed, causing unexpected behaviour with Corolar.

Cause:

Currently there is no automated check on the installation process that Service Pack 1 cannot be installed anymore after Service Pack 2 is installed.

Solution:

Do not attempt to install Service Pack 1 after installation of Service Pack 2.

Interface Reports are not reporting the correct values and the SQL server process is taking up a high % of CPU processing power

Symptoms:

There are some very specific (but rare) scenarios where the interface reports are not reporting the correct values and the SQL server process is using a significantly higher amount of CPU processing power than normal.

Cause:

During the configuration of Corolar Monitor, when an interface is added to be monitored, but logging is turned OFF, Corolar would not create a log table for the interface. When the background job for data collection for reports is run, however, it will try to look for the table that does not exist, causing the stored proc to go into an infinite loop, thus never updating the reports data, and causing CPU usage to go up. This problem would not surface if logging is enabled at any point (it will then create the log table), even if logging is disabled after being enabled before.

Solution:

As a workaround, simply turn on logging for the interface, and turn it back off, this will create the log table in Corolar Database, and the stored procedure will run normally without causing high CPU usage and the reports will be up to date.