Running Client GUI on Citrx

[lisa sater]

Hello,  We are struggling with getting a quick way to run the QDX GUI’s remotely.  Using VPN and running the client on your lap/desktop at home is extremely slow.  So we are trying to run them via Citrx.  Has anyone else had success with QDX and Citrx?  OR any other methods?  

Lisa

Topic

[Terry Kellum]

You could use Citrix, but why use a steamshovel to fill a thimble.

Check out Ultra@VNC.  We use this package for all of our remote control needs.  Using this software, I can control my own workstation over the VPN, and perform functions locally from a remote location.

http://ultravnc.sourceforge.net/

[Rick Martin]

I know this is an older post I’m replying to, but is anyone using the Cloverleaf client on Citrix?

We have a need for multiple (more than the 2 we get with Windows Server) remote developers to be developing using the Cloverleaf client and we’re having the known problem with the Testing Tool not working across the VPN.  I’ve got our network folks trying to figure out what’s wrong, but I’m looking for alternatives.

[Michael Hertel]

There is a known issue with the testing tool working across a VPN connection. Do a search here for more info, don’t have the network folks chase this for too long.

[Rick Martin]

Yep, I’ve read those posts.  They seem to alude to some type of network filtering.  We’ve gathered a network trace from the server and client.  When on the LAN we can see the communication going back and forth, but when on the VPN, we see the request go out, but nothing come back.

On LAN:

Request goes from port 4202 (probably dynamic) to 1052

Response comes back from 1389 to 4203 (probably dynamic)

On VPN:

Request goes from port 4985 (probably dynamic) to 1052

No response come back

The use of ports 1052 and 1389 seems strange to me.

[Keith McLeod]

I currently use the Client for 5.3 and 5.4 using Citrix over SSL.  This provides me access from nearly everywhere there is an internet connection.  I was hesitant at first, but support multiple servers remotely and it is used by multiple staff.  I had this configuration for nearly 4 years and feel that it has been successful.

[James Cobane]

We simply run the testing tools via command line over the VPN; just set up the test criteria in the Tester GUI, then copy the command from the GUI and paste it at the command prompt to run.  You can redirect the output to a file or to the ‘less’ or ‘pg’ command for viewing.

Jim Cobane

Henry Ford Health

[Rick Martin]

Still no luck getting the testing tool to run over the VPN.

I can copy the hcixlttest command from the testing tool window, but what command line are you talking about pasting it into?

If I paste it into a Windows Command Prompt window, I get an error that tcl83.dll is missing – this is a client-only install.

[Russ Ross]

I beleive he is talking about pasting the command into the command window on the cloverleaf server and not in a DOS window on the client.

In my case that means I open up an xterm on my AIX server and create a ksh script like the one I worked on this morning as follows called test_name.ksh:

Code:

#!/usr/bin/ksh

hcixlttest -d 2 -f nl parse_hl7_v23_name.xlt /quovadx/qdx5.2/integrator/test_russ/data/testdata1.hl7

I do a quick chmod 775 on test_name.ksh and run it over and over as needed.

FYI – fortunately we run all the cloverleaf components that I know of just fine over our Nortel VPN, including the tester; however, we do not use Citrix that I know of when doing this.

Personally I find using the tester via command line to be more useful for doing repeated testing.

Plus it is handy for repeating the same test(s) when migrating to production without having to do much work.

Russ Ross
RussRoss318@gmail.com

[James Cobane]

Yes, when I stated the ‘command line’, I was referring to a shell session open on the server (i.e. a telnet, or XWindows session).  If you press the ‘Shell Window’ button of the ‘Runtime’ Panel of the IDE, this is one method of getting you into a command window.

Jim Cobane

Henry Ford Health

[Rick Martin]

Our environment is Windows Server at the server end and Windows XP at the client end.  Since Windows Server limits you to 2 adminitrative logons to remote desktop, that is the problem I’m trying to solve – having the developers run the client on their desktop/laptop while VPN’ed in to the network.

[Author]

Replies