[Marc Pleijers]

Hi all,

Infor has done research on this issue together with Redhat.

In RHEL 7 and 8 there was a bug in the TCPIP stack that was fixed in RHEL9 and now the TCIP stack is completely according to the specifications.

This fix adds the PSH flags in HL7 messages of a certain minimum size, when Cloverleaf sends them to Sectra and other systems. This is exactly according to the TCPIP specifications.

For HL7 messages the MLP protocol is used on top of the TCPIP protocol. Receiving system Sectra should  buffer the message until  according to MLP protocol 1c0d (File separator/Carriage Return)  is received. They should not start processing once they get a PSH flag inside the message body.

Conclusion is that this is not a Redhat 9 /Cloverleaf 2022.09 issue but is an MLP implementation problem at the receiving Sectra System. Sectra has been informed about this.

Kind regards,

Marc Pleijers

 

• This reply was modified 3 months, 3 weeks ago by Marc Pleijers.

Marc Pleijers
Senior Integration Consultant
Enovation BV
The Netherlands

[Marc Pleijers]

Hi Todd

Thanks for the response.

That was just the hint I needed.

I’m already checking it using the CloverleafJavaUpocAPI documentation that is part of the documentation delivered with Cloverleaf.

Kind regards,

Marc

Marc Pleijers
Senior Integration Consultant
Enovation BV
The Netherlands

[Marc Pleijers]

we decided not to use SMAT first of all for the disk space, 10-15 million messages a day uses quite some space.

And the hospital also stated that they don’t need those messages in SMAT archives in Cloverleaf anyway.

Marc Pleijers
Senior Integration Consultant
Enovation BV
The Netherlands

[Marc Pleijers]

We have connected multiple Capsule Tech Datacaptors with Epic for several hospitals.

We use a seperate site for it without SMAT.

Largest configuration is one hospital with more than 200 Datacaptors sending data every 2-3 seconds in HL7 ORU messages. And that results in 10-15 million messages a day. Cloverleaf has no problem with it.

Marc Pleijers
Senior Integration Consultant
Enovation BV
The Netherlands

[Marc Pleijers]

Hi Rudy

Like Jim mentioned the add-on is called Secure Messenger and as far as I know you have to pay for this add-on.

We are reseller in The Netherlands for Cloverleaf and our customers have to pay for this add-on.

In the process printout but also in your license file you will see these add-on modules when you have Secure Messenger:

– cl-aom-ssl

– cl-aom-sftp

– cl-aom-ftps

Often this add-on is bought by customers because they want to use FTPS or SFTP, but you can also do SSL over TCP/IP with this add-on module.

The CAA-WS add-on is for Web Service interfaces and has SSL included, but when you have CAA-WS you still need Secure Messenger if you want to do FTPS, SFTP or SSL over TCP/IP.

Kind regards

Marc Pleijers

Marc Pleijers
Senior Integration Consultant
Enovation BV
The Netherlands

[Marc Pleijers]

Hi,

See attached tcl file with example of lsearch.

It is made to run stand-alone without the need of any example message.

You can run it inside the tcl interpreter (hcitcl ) using source example_lsearch.tcl

kind regards Marc

Marc Pleijers
Senior Integration Consultant
Enovation BV
The Netherlands

[Marc Pleijers]

Hi Gene,

The problem you report sounds familiar. We had the same issue over here.

The server you mount to is probably a windows server.

The problem is caused by the way you have created the mount.

The correct way to create a mount is:

mount -t cifs -o user=me,pass=secret,nounix,noserverino //server/share /mount

Especially the two parameters nounix and noserverino are important and will fix the problem.

The fault: Cannot stat : Value too large for defined data type

is caused by the missing parameter noserverino

This parameter deals with inodes. An inode is a way to store files on a disk. the name comes from index-node. Large files are divided and stored in small pieces called sectors. Administration is necessary to know which sector is belongs to which file.

When you mount to a system that uses a 64 bit OS that system returns a 64 bit inode ID to Cloverleaf as a reference to the file. Cloverleaf however is still 32 bit. Cloverleaf tries to store that 64 bit reference in a 32 bit buffer which does not fit and results in an Value too large for this data type error.

With the option noserverino you state that you don’t want to use the inode ID of the server when dealing with the mount. Then Cloverleaf will have no problem.

So you have to remove the mount completely and create it again with the above mentioned parameters. Don’t forget to correct etc/fstab as well.

More info you will find here:  http://linux.die.net/man/8/mount.cifs

Kind regards,

Marc Pleijers

VANAD Enovation

The Netherlands

Marc Pleijers
Senior Integration Consultant
Enovation BV
The Netherlands

[Marc Pleijers]

Hi all,

Regarding the post on using a temp variable (e.g. @var) as a basis for an iteration, I can inform you about the following:

According to the documentation you should be able to use a temp variable as a basis for an iteration.

However we tried this and it did not work.

We registered a call for this in InforXtreme Case number: 8849524

Infor replied that this is a bug and it is planned to be solved in Cloverleaf 6.2

AR number for 6.2: AR12925

Kind Regards,

Marc Pleijers

Marc Pleijers
Senior Integration Consultant
Enovation BV
The Netherlands

[Marc Pleijers]

Hi All,

Sorry for my late response.

I was busy teaching Cloverleaf Level 2 at one of our customers in Cambridge (UK) and had limited Internet access.

It was provided to us as a hotfix to solve some problems.

I could not find it InforXtreme either.

Kind regards

Marc

Marc Pleijers
Senior Integration Consultant
Enovation BV
The Netherlands

[Marc Pleijers]

Hi,

Windows Server 2012 R2 is already supported with Cloverleaf 6.1.0.2.

We already install Cloverleaf 6.1.0.2 on Windows 2012 R2 platforms at our customer sites.

See attached document on pag 81.

Kind Regards,

Marc Pleijers
Senior Integration Consultant
Enovation BV
The Netherlands

[Marc Pleijers]

Hi,

We are reseller for Cloverleaf in The Netherlands.

When we request a license for either a new customer or when an existing customer upgrades to a new release, we will receive an email from LicenseKey.Care-Lwason@infor.com as a reply.

That email has another email as attachment. The attached email has license.dat (the requested license ) as attachment and the mail body contains the installation instructions for the license.

So this sender address is actually being used for serious cloverleaf business.

We don’t classify it as spam.

Kind Regards,

Marc Pleijers

Product Manager/ Senior Integration Consultant/ Cloverleaf Trainer

ENOVATION BV (member of the VANAD GROUP)

The Netherlands

Marc Pleijers
Senior Integration Consultant
Enovation BV
The Netherlands

[Marc Pleijers]

Hi All,

You can also use the following construction (suppose doing a trick with OBX):

# create list of all OBX positions

set OBXlocationList [lsearch -all -regexp $segments {^OBX}]

# create a list of all the OBX content

set OBXcontentList [lsearch -all -inline -regexp $segments {^OBX}]

#now you can loop through both lists at the same time without problems

# both list have the same length

foreach loc $OBXlocationList cont $OBXcontentList {

   #   in your loop the segment location is available in $loc

   #   in your loop the segment content is available in $cont

   #   so you don’t need a lindex anymore in your loop

   echo $loc

   echo $cont

  }

Best regards

Marc

Marc Pleijers
Senior Integration Consultant
Enovation BV
The Netherlands

[Marc Pleijers]

Hi Matthew

You should protcol fileset local and use the following piece of TCL in your script to correctly set the metadata.

assuming that your new filename is in variable $newfilename

  # set the filename

           set driverctl “{FILESET {{OBFILE $newfilename}}}”

           msgmetaset $mh DRIVERCTL $driverctl

regards,

Marc[/code]

Marc Pleijers
Senior Integration Consultant
Enovation BV
The Netherlands

[Marc Pleijers]

Hi,

According to infor

   * Revision patch 6.0.1 for Cloverleaf 6.0

   * Revision patch 5.8.7 for Cloverleaf 5.8

are both expected to become available in July.

Beta test for 6.0.1 has just been started.

regards,

Marc

Marc Pleijers
Senior Integration Consultant
Enovation BV
The Netherlands

[Marc Pleijers]

Have a look on http://www.sqlite.org/

There is also a chapter on their website about the TCL interface.

That’s the interface you need within Cloverleaf.

Building your SQLite Database file is possible with free SQLite

Marc Pleijers
Senior Integration Consultant
Enovation BV
The Netherlands

[Author]

Replies