[William Grow]

Saw this post. For business reasons beyond my control, I am using the 5.3 revision of the cloverleaf integration engine. Per the documentation this revision specifically states that when using java that you should use the jdk.1.3. I checked the version using the java -version command and found that the build was listed as 1.3.1_09-b03.  Current revision of the microsoft sql server driver for jdbc require a higher revision of the jre. That being said the jtds driver can work with the older revision of java in the case that you are stuck with an older jre.

BTW nice proc.

[William Grow]

The advanced scheduling worked great in 5.3 for this problem. I did note that the thread would automatically look for a file whenever it was bounced. Also, the specified ftp directory needs to be relative to the ftp ftp server root of the user that is logging in to the system.  Another problem I noted was that the thread would go into an error state if it tried to parse a completely empty directory. To resove that problem I placed some dummy files in the directory and added a tps directory parse script to ignore the dummy files.

[William Grow]

Hi,

 I wanted to ask a question about your post. When you say that you park your cloverleaf application and logging on the SAN, do you mean that the full cloverleaf installation is on the SAN?

[William Grow]

Hi,

I had an interface similar to the one that you describe with the exception that it was for a state ED monitoring agency. Essentially, I created an xlate that contained logic to suppress messages if the transaction didn’t meet certain criteria (such as having an ED admit source). The outbound  communications thread used the file protocol and wrote all transactions to a specific file in the exec directory of the process that the thread belonged to.  A route was set up using the xlate to route the transactions to the outbound file protocol thread. I then used a second thread that used the UPOC protocol with advanced sceduling. The UPOC thread executed a script that made some non HL7 standard modifications to file containing the batch of messages. It also added a batch header segment, and a batch trailer segment and then used the tcl FTP package to ftp the file to the sending system. I favored the approach of using the advanced sceduling feature of the UPOC protocol over cron so that the process would be documented via the netconfig as opposed to being less obvious by being part of a cron job.

[William Grow]

Has the supported platform list for QDX5.3 and 5.4 changed

[William Grow]

Has the supported platform list for QDX5.3 and 5.4 changed

[William Grow]

I guess the subject heading says it all.   I spoke to someone about advanced security…they made it out to be more trouble than it was worth. What I am curious to determine is if there is anyone out there with advanced security up and running and how difficult it was to implement. Additionally, can it serve the role of a tool to be able to audit changes made to files.  

Also, how did you get around the application user default useranme and password ie. u=hci p=******  To me it seems that if you implement advanced security you have to lock them out of the command prompt.

[William Grow]

Hi, in reading the installation documentation for 5.4, i thought it stated that to upgrade to 5.4, the site had to be at a minimum of 3.8.1p. However, from your post it seems like you were able to go directly from 3.5.5 to 5.4. Is this correct? If so how did you accomplish.

[William Grow]

Thanks to both of you.  I sent the vendor an email and they are going to load a code patch. Having never had to write the code for an outbound or inbound interface, I don’t know how this can be missed by the engineers.

[William Grow]

John, what is the referrence to a qdx site documentation tool. I haven’t heard of this before?

[William Grow]

Jim,

 Two of my company’s senior integrators will be present. Marcelo Trujilo and Kevan Riley.  I couldn’t make it this time.  Is it a bad idea to link directories from one site to another active site?

[William Grow]

One thing that I didn’t mention was that this xlate is the largest xlate that I have ever seen in my life in the sense that both the xlate is extremely long and the xlt tclprocs called are also long with a lot of logic. I am adding to that additional information that wildcard routes are being used to route ADT through this one xlate for about 8 facilities.   The decision to handle the routes this way was an administrative decision. Would that have anything to do with this because there isn’t anything using port 127.

[William Grow]

Charlie,

 Thanks for replying.  This was a mistake someone here in the office made when setting up the outbound thread.

[William Grow]

I just finished setting up an inbound ftp thread using advanced scheduling. There were a couple of surprises for me. One was that I needed to use a tps directory parse script to parse out subdirectories from the inbound list of files to grab. Without the directory parse script the engine tries to grab everything including subdirectories. When it can’t grab the subdirectory (not a file) it tosses an error in the process log file.  The second is that despite the advanced scheduling if I bounce the process the ftp thread on startup goes to the server and looks for a file to grab.  The thread is very stable.  A third surprise is a temp log file that the ftp fileset protocol places in the process directory.  The file is read/write/execute locked so it was causing backups to fail until the backup was changed to exclude this file. Other than this I like the thread it is reliable and it allows me to create the same smat files that my other threads are creating.  I even changed the standard directory parse script to add entries into the process log file to indicate what files were found in the directory and which files it would try to parse for messages adding the date time to these messages.

[William Grow]

Thanks a-lot. I didn’t think that anyone was going to reply to this post. The parse script location mention helped out a lot.

[Author]

Replies