Skip navigation

This Question is Answered (go to answer)

2 "helpful" answers available (2 pts)
9,647 Views 15 Replies Last post: Jan 13, 2009 6:48 PM by hkwathome RSS 1 2 Previous Next
hkwathome Valued Contributor 77 posts since
Dec 3, 2008
Currently Being Moderated

Jan 5, 2009 11:24 PM

Installing Openvista Server

I am working on FEDORA Linux system and has installed GT.M

 

and has downloaded Openvista Server  , unzipped globals & routines to say g & r directory respectivly

 

ref this document :- http://medsphere.org/docs/DOC-1322 ,

which seems to be part of full Installation Document for OpenVista Server

 

Looking for Openvista Installation instructions

 

where can i find Deployment / Installation Instructions for Openvista Server

 

Regards

hkw

Jonathan Tai Medspherian 320 posts since
Jul 24, 2008
Currently Being Moderated
1. Jan 6, 2009 10:19 AM in response to: hkwathome
Re: Installing Openvista Server

We don't really have special instructions for installing OpenVista server - it works like any other VistA distribution.  Since you're using GT.M and already have it installed, you just need to set up your GT.M global directory file, create your empty database files, then mupip load the globals provided in our distribution.  From there, you should be able to run mumps -dir to get a programmer prompt.  Of course, be sure to set your GT.M environmental variables to point at your global directory file and your routines directory.  You shouldn't need to run ZTMGRSET or initialize FileMan or anything like that if you're running on GT.M.  Like other VistA distributions, you'll need to set up xinetd before you can connect with OpenVista CIS or CPRS.

 

If you're stuck at a particular step, please feel free to ask, or check out the OpenVista Appliance which has everything set up already.

Jonathan Tai Medspherian 320 posts since
Jul 24, 2008
Currently Being Moderated
2. Jan 6, 2009 10:29 AM in response to: hkwathome
Re: Installing Openvista Server

hkwathome wrote:

 

ref this document :- http://medsphere.org/docs/DOC-1322 ,

which seems to be part of full Installation Document for OpenVista Server

 

That document is a proposal for standardizing the directory names and installation locations for OpenVista and is not meant to be an install guide.  The idea is that if we can all agree on where OpenVista should be installed, in the future we could create packages (e.g., RPMs and .debs) and tools to make OpenVista installation simpler.  At the moment, OpenVista installations are a manual process.

Pete Johanson Medspherian 48 posts since
Aug 6, 2008
Currently Being Moderated
4. Jan 7, 2009 8:51 AM in response to: hkwathome
Re: Installing Openvista Server

2. What is the recommended Mono site download for CIS Client Linux and Windows

    ( it seems Linux Mono version ha GTK#  with it )

http://www.mono-project.com/Main_Page

for Redhat:

"Binaries for this platform have been discontinued.

Builds may be available from unsupported downloads or we may be looking for a volunteer to maintain packages."

what is the recommended Mono download location for RedHat ?

 

On CentOS 5 or the latest RH release, Mono and Gtk# are already packaged. You should be able to install the required packages with the following:

 

sudo yum install mono-core mono-web gtk-sharp2

 

For CentOS 4 or older RH releases, you'll have to download the following packages from the Mono Project:

  • mono-core

  • mono-data

  • mono-data-sqlite

  • mono-web

  • mono-winforms

  • libgdiplus0

Now, use the following command to install the downloaded packages:

rpm -Uvh *.rpm

 

For Windows, you will just need the Microsoft .NET 1.1 Runtime installed (should be part of any Windows XP or newer install), and then use the latest Gtk# installer found on the Gtk# Installer page.

 

3. I think one has to install GTK# before installing Mono . What is the recommended sequence to setup CIS Client ?

 

For any Linux distribution, the suggested path is to install Mono, then Gtk# from packages provided by your distribution. Many distributions now include Gtk# pre-installed, which makes this easier.

 

For Windows, the suggested path is to install Microsoft .NET, then install Gtk# from our provided MSI installers.

 

Hope that helps,

 

-pete

Jonathan Tai Medspherian 320 posts since
Jul 24, 2008
Currently Being Moderated
5. Jan 7, 2009 10:29 AM in response to: hkwathome
Re: Installing Openvista Server

1. Are there any optimized KERNEL & TASKMAN Parameters for production setup and development setup ??

   Are there any recommended parameters for KERNEL , TASKMAN and

any other Basic setup files which directly impacts the performance of the OpenVista

is there any way to reset the Default installation for KERNEL & TASKMAN Files ?

Not that I know of personally, but my expertise in this area is quite limited.

 

4. Does OpenVista Support CPRS as well , is the installation instruction same as WorldVista ?

CPRS should run against OpenVista Server, but you must use OpenVista CIS (or modify CPRS) to take advantage of some enhancements in OpenVista Server such as patient photos, document imaging, growth charts, etc.  See OpenVista Server Release Notes for a more detailed list of enhancements.  There are also enhancements in CIS itself such as spell checking.

 

5. What are openVista Bridge & WebDav Downloads

Albert's blog post, Introducing OpenVista Bridge should cover the basics of what the Bridge is.  The WebDAV download contains the contents of the patient photo/document imaging WebDAV repository.

Jonathan Tai Medspherian 320 posts since
Jul 24, 2008
Currently Being Moderated
7. Jan 8, 2009 8:38 PM in response to: hkwathome
Re: Installing Openvista Server

The xinetd part of the setup is mandatory if you want to connect to OpenVista Server with CPRS or CIS, even if you only want to connect one instance locally.  You don't need to set up xinetd if you're only going to use OpenVista Server's text-based interface.  To set up xinetd, on Fedora you should be able to

 

sudo yum install xinetd

 

Once you have it installed xinetd, you need to configure it.  The easiest way to configure it is to create a text file named rpcbroker with the following contents in the /etc/xinetd.d directory:  (Note: I'm not 100% sure that the directory name is /etc/xinetd.d on Fedora - it is on Ubuntu.  If that directory doesn't exist on your system after installing xinetd, look around in /etc for a directory with a similar name.)

 

service rpcbroker
{
    disable     = no
    type        = UNLISTED
    id          = rpcbroker
    socket_type = stream
    protocol    = tcp
    port        = 9201
    user        = 1000
    wait        = no
    server      = /path/to/rpcbroker/script
}

 

Note that the contents of this file was taken from the OpenVista Appliance.  The default port for our release is 9201, but you can use whatever port you want.  Make sure you substitute the correct path for the server argument - it should be the path to the script that xinetd should run when it receives a connection on port 9201.  You need to create this script with contents similar to the following:

 

#!/bin/bash

export gtm_dist=/path/to/gtm/installation
export gtmgbldir=/path/to/global/directory.gld
export gtmroutines=/path/to/routines

$gtm_dist/mumps -run GTMLNX^XWBTCPM

 

Again, be sure to substitute the correct paths.

 

Once you have the two scripts in place, restart xinetd.

 

Assuming you get xinetd running...

 

The openvistacis-0.9.9.zip is not necessary unless you want to compile the code yourself.

 

You should unzip the bridge zip before the client zip, and it sounds like you have already done that.  If you're running the bridge on the same machine as OpenVista Server, you should run it with --vista-host=localhost and --vista-port 9201, where 9201 is the port you configured the OpenVista Server RPC broker to run on earlier.

 

Finally, you should unzip the client zip.  If you're running OpenVista CIS on the same machine as the bridge, you should enter "localhost" for the host and port 7979 for the port.  Port 7979 is the default port that the bridge listens on.  (Remember, CIS connects to the Bridge; the Bridge connects to the OpenVista Server RPC Broker.)  Use pu1234 for the Login ID and pu1234!! for the Password to log in as a physician; nu1234/nu1234!! to log in as a nurse.

 

You could technically run all three components on separate machines - OpenVista Server, OpenVista Bridge, and OpenVista CIS.  Typically, we run the Bridge on the same host as the Server, and CIS runs on separate end-user desktop machines.

Jonathan Tai Medspherian 320 posts since
Jul 24, 2008
Currently Being Moderated
10. Jan 12, 2009 9:05 AM in response to: hkwathome
Re: Installing Openvista Server

There are two ways to see if xinetd is listening properly.  First, you can use the netstat tool with the -a flag, which shows all listening ports.  I usually add the -p flag, which shows what process is listening on that port, and the -n flag, which shows everything numerically.  Note that you must run netstat as root to use the -p flag. 

 

On a typical system, you might get something like:

# netstat -apn | grep 9201
tcp        0      0 0.0.0.0:9201                0.0.0.0:*                   LISTEN      31741/xinetd       
tcp        0      0 192.168.1.72:9201           69.233.123.119:1418         ESTABLISHED 17255/bash         
tcp        0      0 192.168.1.72:9201           71.52.172.212:18742         ESTABLISHED 17189/bash         

 

The first line of output shows that a process called xinetd with process id 31741 is listening on port 9201. The other two lines indicate there are two established connections to that port.

 

If xinetd is not listening on the port, you want to check syslog to see why not.  Right after starting xinetd on a CentOS system you should see some log entries like this in /var/log/messages:

Jun  9 00:39:43 host xinetd[2259]: xinetd Version 2.3.14 started with libwrap loadavg labeled-networking options compiled in.
Jun  9 00:39:43 host xinetd[2259]: Started working: 1 available service


Also, one thing you may conside is moving the script that xinetd runs out of the /etc/xinetd.d directory - that directory is "special" and should only be used to hold xinetd configuration files.

Jonathan Tai Medspherian 320 posts since
Jul 24, 2008
Currently Being Moderated
12. Jan 12, 2009 10:50 PM in response to: hkwathome
Re: Installing Openvista Server

I'm going to guess that you don't have a user on your system with user id (uid) of 1000.  Run

id -u

 

to figure out the uid of your user on the machine, then edit the rpcbroker xinetd config file and replace 1000 with your uid.  Incoming connections will run as your uid - if this is not what you want, then look in /etc/passwd for the uid of the user you want incoming connections to run as.

Jonathan Tai Medspherian 320 posts since
Jul 24, 2008
Currently Being Moderated
14. Jan 13, 2009 10:18 AM in response to: hkwathome
Re: Installing Openvista Server

GT.M and the Bridge both create new files during normal operation, so if you invoke them as root, they may not run properly when running as a normal user later because the normal user won't be able to overwrite root's files.  I would recommend double-checking your permissions and not running any of these processes as root.

 

I think the problem with your export script is that you need quotes around the multiple paths, e.g.

jon@host:~$ export gtmroutines=/home/openvista/FOIA-JAN06/r /usr/local/gtm .
bash: export: `/usr/local/gtm': not a valid identifier
bash: export: `.': not a valid identifier
jon@host:~$ export gtmroutines="/home/openvista/FOIA-JAN06/r /usr/local/gtm ."
jon@host:~$

 

Also, from your path, it appears that you're trying to run OpenVista CIS against a FOIA version of VistA.  OpenVista CIS contains a few enhancements above and beyond FOIA VistA that require additional server-side components be present.  These server-side components are in OpenVista Server, but not in FOIA VistA.  So even if you get the Linux side of things installed and working, CIS will probably not allow you to fully log in because it will try to call certain RPCs that will be missing.

More Like This

  • Retrieving data ...

Bookmarked By (0)