Corolar Release 6.12.0302.1 SP3

Description

Corolar Service Pack 3 is an update to Corolar which provides feature enhancements based on detailed feedback from customers. This release includes significant performance enhancements for the Corolar Pipelines, correlation between HL7 messages and their ACKs, custom field searching for the Corolar Interface Monitor, and other Corolar Interface Monitor enhancements and bug fixes.

Affected Components

Corolar Installer

When the user clicks on “Cancel” while the installation is in progress (ie, when the installation progress bar is shown), the installation will complete successfully, but it will fail to backup the files for the original version.

Symptoms:

While inspecting the installation log file after installation completes, the line “failed to backup ” is shown.

Solution:

Make sure not to click on “Cancel” after installation process has begun. A solution will be provided in the next Corolar release.

Installer refuses to install if the installer has been run previously but cancelled due to files being locked.

Symptoms:

If a file is locked during installation, and the user cancels the installation, the next time user runs the installer, the installer will refuse to install stating certain Corolar component is not installed.

Cause:

Cancelling the installation causes the install to be left in an unknown state, resulting in subsequent install failure.

Solution:

Ensure none of the Corolar related files are opened and locked by any other applications before installing Service Pack 3. A solution will be provided in the next Corolar release.

Corolar Interface Monitor

  • Users in the Corolar Interface Monitor User list can now be enabled/disabled.
  • Purge intervals of interface logs can now be set at a per interface level.
  • The user can now search for logged messages by MSH-9.2.
  • Five additional “Dynamic search fields” have been added so that users can promote desired fields into the dynamic search fields, and search for messages using those fields.
    – Note: For one-way receive ports, the fields must be promoted in a component preceeding the Corolar tracking component.
  • When users search for messages for an interface, they can now see the associated Acknowledgement for the message by clicking on the “view ack” button. This is applicable only to 2-way send ports and 2-way receive ports.
    – Note: this feature is only applicable to messages that are processed after installation of Service Pack 3.
  • Users can now set the alert frequency for invalid messages to avoid multiple invalid message alerts within a short timeframe.

Corolar Alert Service

  • Users can now set the alert frequency for invalid messages to avoid multiple invalid message alerts in a short timeframe.

Corolar BizTalk Artifacts

  • Several Corolar Pipelines have been enhanced and optimized to provide superior performance.
  • The Corolar Pipelines have been enhanced to provide correlation of an HL7 message and its corresponding Acknowledgement.

Corolar Database

  • The Corolar Database has been updated to support the new features and functionalities described above.

Included Fixes

Installation of Corolar on a 32bit system requires a pre-installation procedure to create the 32bit registry entry.

Symptoms:

When the user attempts to install Corolar or its service packs on a 32bit Operating System, it fails, with an error saying “missing registry”.

Cause:

Corolar assumes the user is installing in a 64bit environment.

Solution:

Contact the Corolar Support team to obtain pre-installation instructions prior to installing Corolar Service Pack 3.

Corolar BizTalk Artifacts

Messages are not processed if the Corolar Tracking pipeline component cannot access the Corolar Interface Monitor Database.

Symptoms:

In the event the Corolar Interface Monitor Database is inaccessible by the BizTalk host instance (e.g. due to a network connection problem, database permission issues, or offline database) and “TraceEnabled” is set to “True” on the Corolar Pipeline’s tracking component, messages passing through the Corolar Pipeline will be held in an infinite loop until the Corolar Interface Monitor Database can be re-accessed.

Cause:

In order to prevent the loss of messages, the Corolar Pipeline waits for database connectivity, before allowing messages to pass through BizTalk.

Solution:

Apply 6.12.0302.1 Service Pack 3 to address this issue. With SP3 installed, in cases where the Corolar Monitor Database is inaccessible by the Corolar pipelines, the system behaviour will be as follows:

  • Messages will be passed through BizTalk to the downstream systems
  • An error will be raised and written to the Windows Event Log.
  • The original message and other relevant information will be written into a file (Note: The file path for this file can be selected during SP3 installation).

Corolar Interface Monitor, Corolar Database

The Corolar Interface Monitor dashboard is not synchronizing with BizTalk properly when interfaces are deleted and then re-created (by either importing bindings or manual creation) using the same name.

Symptoms:

When interfaces are being deployed via the Microsoft BizTalk deployment framework, the interfaces will become “out of sync” between BizTalk and the Corolar Monitor, causing the Health status to be updated incorrectly.

Cause:

BizTalk has an internal “Interface ID” that identifies an interface. However, when using the MS BizTalk Deployment framework, the interface is actually deleted and then recreated. This causes BizTalk to use a new interface ID for the “redeployed” interface.

Solution:

A Corolar SQL Job “Dapasoft_Corolar_Monitor_Rebind_Interfaces” is available on the SQL server where the Corolar Database is installed. Run this job manually everytime interfaces have been deployed using the BizTalk deployment framework, or whenever you delete an interface and re-import the bindings to recreate those interfaces.

Corolar Monitor Message View/Edit/Resubmit sometimes truncates the message

Symptoms:

Under certain situations, when viewing logged non-HL7 messages in the Message Management tab of the Corolar Interface Monitor, the message is partially truncated.

Cause:

The HTML page display reduces multiple spaces into one space which causes truncation of some parts of the message but does not affect the actual data of the logged message.

Solution:

Apply 6.12.0302.1 Service Pack 3 to address this issue

  • Note: If the message is very long, (with or without lots of white spaces), it may be wrapped by the system. For long single-line messages, use the horizontal scroll bar to view the entire message.

Symptoms:

Under certain situations, editing a message before resubmitting partially truncates the message.

Cause:

The message being viewed contains non-printable characters e.g. null characters (0x00), backspace (0x08), ESC (0x1B). When the message is displayed, it may look truncated or incorrect due to the non-printable characters. When the user tries to resubmit the message, the message may be resubmitted without the special characters.

Solution:

Apply 6.12.0302.1 Service Pack 3 to address this issue. A warning will be displayed by the Corolar Interface Monitor informing the user that the message contains non-printable characters and cannot be modified or edited. The user can still view the message, however, he/she will be warned that it may not be displayed correctly. The message can still be resubmitted without modifications.

Corolar Interface Monitor: In the Message Management tab, the scroll bar on the dialog box does not function correctly while viewing a message.

Symptoms:

In the Message Management tab, after searching for messages and clicking view, the user has to click on the textbox and use the down arrow key to scroll the message instead of using the scroll bar.

Cause:

A defect in the HTML Schema implementation causes the scroll bar to function incorrectly.

Solution:

Apply 6.12.0302.1 Service Pack 3 to address this issue.

Known Issues

Corolar Database

There is a limit of 20 characters for username.

Symptoms:

When trying to assign a domain user that has a user name longer than 20 characters, an error occurs.

Cause:

The Windows 7 and SQL 2005 maximum length limit for user name is 20, whereas the SQL 2008 maximum user name length is 25.

Solution:

Use a domain account that is 20 characters or less in the user name.

Corolar BizTalk Artifacts

When uninstalling Service Pack 3, some DLL’s are not rolled back under certain situations.

Symptoms:

When uninstalling Service Pack 3, the Dapasoft.Corolar.V2XPipelineComponents_2013.dll is not rolled back to the hotfix version when Service Pack 3 is uninstalled from Corolar RTM + Hotfixes.

Cause:

This usually occurs when either the host instance is not stopped before uninstalling or some other applications have a lock on the DLL.

Solution:

If the Dapasoft.Corolar.V2XPipelineComponents_2013.dll is not rolled back, it can be manually updated. To update the Dapasoft.Corolar.V2XPipelineComponents_2013.dll in GAC, copy and overwrite the DLL file from [Corolar Installation Folder]\Corolar 2 BizTalk\deploy\Dapasoft.Corolar.V2XPipelineComponents_2013.dll to [Windows]\Microsoft.NET\assembly\GAC_MSIL\Dapasoft.Corolar.V2XPipelineComponents_2013\[assembly version].

Invalid messages logged by the Corolar Tracking Component of the Batch Receive Pipeline (by setting TraceInvalidMessage to True and TraceEnabled to True) does not contain the correct MSH-9.2 value.

Symptoms:

The logged invalid messages contain the value “ALL BATCH” in MSH-9.2 instead of the original MSH-9.2 value.

Cause:

This is caused by a bug in the Batch Receive Post Processor that does not revert the trigger event to its original value.

Solution:

A solution will be provided in the next Corolar release.

Corolar Monitor Tool

When a user tries to create a new interface profile (for Role Based Access Control) in the Corolar Monitor tool, the user may encounter an error upon saving the profile under certain situations.Symptoms:

If there are more than 20 interfaces configured in Corolar Monitor, and the user tries to create a new interface profile (for Role Based Access Control), the user may encounter an error upon saving the profile.

The error message would look like:

The formatter threw an exception while trying to deserialize the message: There was an error while trying to deserialize parameter Dapasoft.Corolar.Monitor.UILayer.WebApp.Service:Params The maximum string content length quota (8192) has been exceeded while reading XML data.

Cause:

The web service used by the Corolar monitor user interface to communiate with the Corolar DB uses a default setting to that is too small. This setting is used to prevent certain Denial of Service attacks.

Solution:

Add a configuration setting in web.config.

Steps:

  • 1) Go to Internet Information Service Manager (IIS Manager)
  • 2) locate Corolar Monitor Tool web application
  • 3) Right click on it and click on “Explore”
  • 4) Locate the Web.config file and do a backup of the file or, alternatively, the Web.Config for Corolar Monitor is by default located in C:\Program Files (x86)\Dapasoft Inc\Corolar\MonitorToolApp
  • 5) Open the file in notepad or a text editor of your choice
  • 6) Locate the section that resembles below
    • a) <webHttpBinding>
    • b) <binding name=”Dapasoft.Corolar.Monitor.UILayer.WebApp.Service.EntitiesAspNetAjaxBinding” openTimeout=”00:09:00″ closeTimeout=”00:09:00″ sendTimeout=”00:09:00″ receiveTimeout=”00:10:00″ maxBufferPoolSize=”524288″ maxReceivedMessageSize=”5242880″>
    • c) <security mode=”TransportCredentialOnly”>
    • d) <transport clientCredentialType=”Windows” />
    • e) </ security>
    • f) </ binding>
    • g) </ webHttpBinding>Insert the following line after line b) but before line c):<readerQuotas maxStringContentLength=”5242880″ />
    • h) save and close the Web.Config file
    • i) the file should now look something like below:
      • <webHttpBinding>
      • <binding name=”Dapasoft.Corolar.Monitor.UILayer.WebApp.Service.EntitiesAspNetAjaxBinding” openTimeout=”00:09:00″ closeTimeout=”00:09:00″ sendTimeout=”00:09:00″ receiveTimeout=”00:10:00″ maxBufferPoolSize=”524288″ maxReceivedMessageSize=”5242880″>
      • <readerQuotas maxStringContentLength=”5242880″ />
      • <security mode=”TransportCredentialOnly”>
      • <transport clientCredentialType=”Windows” />
      • </security>
      • </binding>
      • </webHttpBinding>
    • j) The changes should take effect immediately without having to restart IIS