54788  9999 /apps/aise01t/cis5.8/integrator/bin/hciengine -S he00387 -p icm_prod_ih
110872 10048 /apps/aise01t/cis6.1/integrator/bin/hciengine -S he00387 -p icm_prod_ih

I get the same results you did with RHEL 5.8 with Cloverleaf 5.8 and 6.1.
problem solved.

I tried the %r option and this also produced inconsistent results.

Code:
[5.8] aise01t> hcitcl
hcitcl>puts "[clock format [clock seconds] -format {%a %x %X}]"
Fri 10/30/2015 09:13:31 AM
hcitcl>puts "[clock format [clock seconds] -format {%a…Read more

Thanks for the replies.

Quote:
Check that your locale did not change

The 6.1 release was installed sometime ago and I am not aware of any changes to locale settimgs.

The details above were completed by setting root (5.8/6.1), executing hcitcl and then the clock command.

Quote:
… changing it to %r gives lower case am/pm

I’ll…Read more

If we have been requested to do this, we set up a non-production Cloverleaf site to connect to the new application.  The production messages are sourced from daily cycled SMAT files and are either sent in batches (using the standard file load), or sent at an approriate time, based on the messages MSH timestamp.

This provides the…Read more

We are on linux (migrated from AIX) and work on the server.

We login to the server with our own account and use ‘sudo’ to change user to the code owner (hci) or runtime owner (hcimgr).
i.e.
 sudo su – hci
or
 sudo su – hcimgr

We ensure that our local accounts are in the same *nix group as the ‘hci*’ accounts.

We also use Cloverleaf for non patient related interfaces, including one keeping the timesheet program up-to-date with new incident cases.

Our set up is publish and subscribe, where each Cloverleaf site is dedicated to an application (PAS, LIS, RIS …) and the Cloverleaf (internal to the server) threads complete the subscribe.

We’ve been using web services in Cloverleaf since 2008.
In our case many of the interfaces could have been created by extending HL7 and been a lot simpler, but the architects insisted on web services.

Some of the outbound methods we use could not be completed in the previous Cloverleaf IHB and we have used the TclCurl code for…Read more

David Barr wrote:

So you’re saying that the globals are only to pass data between TPS procs that are all on the inbound TPS stack? I was more worried about using the global variables to pass data from the inbound TPS to pre-xlate or OB TPS.

Typically the global variables are within the module to store data for later use or used in another…Read more

David Barr wrote:
I don’t think storing message data in global variables is a good idea. What happens if your engine process is stopped with messages that have already been through inbound TPS but are still in the recovery DB?

I store that kind of stuff in message metadata.

Hi David.

Cloverleaf keeps track of the module stack and the…Read more

I haven’t received an update … but I have attached a sample of a Proof Of Concept translation.
The namespace setup

We perform most of our translations in TCL. Previously management have blocked our request to share our code.  I’ve tried again and have a meeting later this week to discuss.

Essentially, we treat a message as string, split into segments and only parse the segments if a translation for the segments exists.

We are on *ix and generally run one script that loops through the Cloverleaf sites and then calls a second script to perform  the action.

When the second script has completed its work, the envieronment is dropped until the next call.  The second script can also be called from  the command line.

eg
cycleAllLog.sh…Read more

I’ve not attempted what you are trying achieve, but it may be worh investigating.

Note that this will only work in the ACK message is of type data.

We use this routing method frequenty. Our ‘generic’ routing TCL code is:
proc gen_code_trx_id {aMsgId} {
 
               #
               # The Application is in the message user data set in the xlate function
               #
       set myTrxId [msgmetaget $aMsgId USERDATA]

       return $myTrxId
}

You will need to ensure that the…Read more

We store NetConfig files in CVS with the site appended
eg
NetConfig_top_prod_rp
NetConfig_top_prod_fh

We have previously compared performance of TCL code with and without table lookups and found little extra cost.

We have now moved a lot of tables to CSV files. This enables an application support group to ‘own’ the table (spreadsheet, XLS format) and we just ‘save as CSV’ and migrate.

If you do use this, be very careful as the…Read more

Jeff W Dinsmore wrote:

Richard -> What do you mean when you say:

Quote:
We plan to create a database with an appropriate structure to load the SMAT files

Does that mean you’re planning to dump the whole SMAT, indexing, messages and all, into a DB?

Apologies for a poorly written response, we plan on cleaning up the SMAT file…Read more

We store all inbound untranslated messages in SMAT files and have housekeeping tasks that cycle the SMAT files daily, adding a YYYYMMDDHHMM timestamp and copy them to a ‘year’ repository. The SMAT files are deleted from the Cloverleaf site after a couple of months.

We also have a maintenance menu that allows cycling of the SMAT files.…Read more

How huge is huge?

There is an internal timeout and if you are validating the message before ACKing this could be an issue.

We have had 10mb files and  I’m pretty sure a 30mb file, although this was in error!

We have used the DustMote web server for displaying text documents and this can probably be modified to suit.
It’s written in TCL

Our master site provides the

Just to add our experience.

We have not used throttling in production as we prefer manual throttling if connected applications have ‘gone ferral’. I believe normal Cloverleaf configuration will attempt to ’empty’ a thread before moving on. This can result in an inbound thread processing all messages before routing.

If throttling is…Read more

Our setup has each developer logging as with their username and I have seen this when one user has selected the Cloverleaf site that belongs to another user.

This is an example of a PAS application site. The rcv and snd are for half-duplex communication and ‘out’ communicates to another Cloverleaf site.
Process              Connection                          State Proto Status…Read more

We store all files in CVS.

Add one extra thread that replaces the outbound thread. This new thread writes OB messages to a repository with date stamped files.  The thread also reads the repository and picks up files older than a…Read more

We use HTTP rather than HL7 to receive PDF documents, but the logic should be very similar.
The messages are parsed in the first Cloverleaf thread (from the IB) and the document is removed and stored using message unique identifiers.

When the message is to be sent outbound from Cloverleaf, the document is added back to the message.

The guys performing the…Read more

All is OK now and I have added quotes in my Makefile

ie
On Linux …
[5.8] he00387> mX “{fdw_xlate_top.tcl,icm_xlate_top.tcl}”
Arg >{{fdw_xlate_top.tcl,icm_xlate_top.tcl}}<
Cmd >glob -nocomplain -directory . {{fdw_xlate_top.tcl,icm_xlate_top.tcl}}<
Exe       >./fdw_xlate_top.tcl…Read more

I have not hacked mktclIndex!
On AIX it has worked for years – I think back to 3.3.0 – like this
  mktclindex {fdw_xlate_top.tcl,icm_xlate_top.tcl}

>Put some echo statements in there if you like
I did and found an inconsistency with the ‘glob’ function that I could work around in  mktclindex but not the auto_mktclindex.

This is a…Read more

This is what we use, with myObDir statically set in the code and the ‘my’ variables parsed from the message and the counter created if it doesn’t exist at thread startup.

set myObFile ${mySiteCode}_[CtrNextValue $myObSequence]_${myVisit}.xml

msgmetaset $aMsgId DRIVERCTL “{FILESET {{OBFILE $myObFile} {OBDIR $myObDir} {OBAPPEND 0}…Read more

Our resend code verifies that the HL7 ACK contains the Message Control Id from the sent message. We also have switches that kill a message after a few send attempts based on the ACK being AE or AR.

The unit

Thanks for the update.

This issue in this case appears to be that a state 14 is detected in a normally loaded environment, but not in a high loaded environment and as a result, with the many bounces of connections, message appear to have been ‘lost’ – they were sent, but the log files don’t indicate an ACK back before the connection…Read more

We have been using RCS and now CVS for many years, but we do work on the Cloverleaf server.   Not using any revision control can make bug tracking really hard.
We display the Modules revision and revision checks on thread startup
eg
12:40:23 pas_prod_ih_adt_in gen_code_printmsg:INFO : RCS Info $Id: gen_code_printmsg.tcl,v 1.1 2003/08/19…Read more

Cloverleaf has the ability to allow or not multiple connections (protocol properties multi-server) to a TCP server socket.
If you attempt a connection to a Cloverleaf site, both threads display ‘connect’ information ONLY if the socket is set to multi-server.

I have seen Vendor and ‘home grown’ server sockets created that use the…Read more

I found that many Microsoft generated schema definitions ‘failed’ a Cloverleaf validation and was fixed by ensuring that all the namespace aliases are included at the top level.

eg
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema” … xmlns:b=”http://ns./Schema/HCAL/Core/Base”  …

For Cloverleaf communication externally we use an ACK based comms.

I don’t have a fix, but I have had similar issue recently in development – self inflicted – where the only recovery was a DB cleanup.

Our ‘resend’ module is required in up to four different contexts, depending on configuration and I missed one.

We work with PDF documents, although ours are tiny!

When a document enters Cloverleaf, we strip it out of the message and replace it with a link.  When the document is sent out, we put it back in again.

This way, we don’t have documents being passed though the engine.

We have had 30mb documents sent to Cloverleaf – in error – so…Read more

Unless there is a server (AIX) issue or change, we don’t touch the engines.  If there is a thread disconnection, Ops (24×7) instructions are to bounce the thread as a simple start point.

We have around 75 production sites.

Just bumping this thread again as we had an issue last week where this setting was changed (its been the same for about 5 years!) and caused HUGE issue with performance!

We have 70+ production sites which normally take 11 minutes to start when started with locally wrapped start scripts.

We use external monitoring and I check the size of the error DB. If the size is greater that the ‘initialised file’ size, then we have an error.

A subsequent check is made on the lockmgr ‘pid’ file and an alert is raised ONLY if the db file is newer than the pid file.

i.e.
If a message is sent to the error database, an alert is raised.…Read more

We do this two ways.

If we have a tclproc that has already parsed the message, we use this proc to set message meta data to store routing information. The trx proc just returns the meta data.
e.g.
proc har_code_trx_id {aMsgId} {
       #
       # The Route is in the user data
       #
   set myTrxId [msgmetaget $aMsgId USERDATA]

 …Read more

We use a web service for documents – an architectural directive – but we parse out the document and store it out of Cloverleaf and then pick it up again on outbound.

We plan on using embedded documents for another project and again we plan to parse out the document and add on outbound delivery.