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
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.
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.
Thanks for your reply , my OpenVista Server is installed ( using "vistapedia installation instruction How to" as guidelinef) ,
but during
GTM>D Q^DI
Select option - enter or edit file entries
my Kernel parameters - i entered some values and similar - taskman site parameters
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 ?
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 ?
3. I think one has to install GTK# before installing Mono . What is the recommended sequence to setup CIS Client ?
4. Does OpenVista Support CPRS as well , is the installation instruction same as WorldVista ?
5. What are openVista Bridge & WebDav Downloads
pl. also review attached files
Regards
Hkw
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
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.
In order to Install Client side of OpenVista on the OpenVista server system itself
Following is done on Fedora 9 system with OpenVista Server already Installed
1. unzip <openvistacis-0.9.9.zip> in directory say openvistacis-0.9.9
2. unzip <openvistacis-0.9.9-bridge.zip> in directory say openvistacis-0.9.9-bridge
3. unzip <openvistacis-0.9.9-client.zip> indirectory say openvistacis-0.9.9-client
$cd openvistacis-0.9.9 --- directory
[openvista@localhost openvistacis-0.9.9]$ ./configure && make
./configure && make - command executed normally ( as per README from openvistacis-0.9.9 )
STEP for starting bridge
[Command format as per README from openvistacis-0.9.9
mono Bridge.exe --vista-host foo --vista-port 9999
Here vista-host is assumed : openvista and port # - 9999
[openvista@localhost ~]$ cd openvistacis-0.9.9-bridge
[openvista@localhost openvistacis-0.9.9-bridge]$ mono Bridge.exe --vista-host openvista --vista-port 9999
OpenVista® Bridge version 0.9.9-release-1.0-beta-1082 starting
Found addins:
- Medsphere.OpenVista.Remoting
- Medsphere.OpenVista.Vitals.Remoting, 0.9.9-release-1.0-beta-1082
- Medsphere.OpenVista.Vista.Remoting
- Medsphere.OpenVista.CIS.Remoting, 0.9.9-release-1.0-beta-1082
Ready for connections.
>> i am confused as what should be the hostname & the port -
STEP FOR STARTING CLIENT
[openvista@localhost ~]$ cd openvistacis-0.9.9-client
[openvista@localhost openvistacis-0.9.9-client]$ mono OpenVistaCIS.exe
the Screen has Username & Password with Hostname & port 7979
assuming admin , admin as username & password with local host
gives me bridge related errros
------
Test was done with the following scenario
1. xinetd is not installed as it was giving me installation error
( will the test be successful for just single client on the server machine or is it mandatory )
2. what should be the hostname & port for bridge command
3. what should be the userid , password , host as localhost ( will it work ) & port- 7979
4. any other configuration parameter or setting process required
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.
To install "xinetd" if working behind proxy server
if facing connection refusal problem & xinetd install problem
try
setup environment variable
ref
$export http_proxy=”http://<proxy-server-ip>:<port>”
also do
$yum install xinetd
using root user login ( not the sudo root password set up)
it works & installs xinetd
Ref previous installation instructions
1. openvista server , Bridge & CIS Client are on the same System
2. xinetd is installed
3. rpcbroker file is created in /etc/xinetd.d
4 script file is created in /etc/xinetd.d/medsphere as per ref in rpcbrokerfile
5 xinetd is started ,
openvista server is started ,
OpenVista Bridge is started
OpenVista CLient
is started as per sequence
6. OpenVista CLient gives me error in Bridge connecting to server
Error Message :
Bridge unable to connect to
OpenVistA server, incorrect host and/or port
is there anyway to know thru any log file / trace file why it is not able to connect Bridge with Server?
follwing are the configuration & execution steps
- where did i made any error in setup ?
=======
ENVIRONMENT VARIABLES
==========================
[root@localhost medsphere]# pwd
/etc/xinetd.d/medsphere
[root@localhost medsphere]# env
SSH_AGENT_PID=2828
HOSTNAME=localhost.localdomain
DESKTOP_STARTUP_ID=
TERM=xterm
SHELL=/bin/bash
XDG_SESSION_COOKIE=48efe52c7da33d69c2d52440495dc87d-1231746163.225233-1699256485
HISTSIZE=1000
GTK_RC_FILES=/etc/gtk/gtkrc:/home/openvista/.gtkrc-1.2-gnome2
WINDOWID=65021901
QTDIR=
QTINC=/include
GTK_MODULES=gnomebreakpad
USER=openvista
gcc=/usr/lib/ccache
LS_COLORS=no=00:fi=00:di=00;34:ln=00;36:pi=40;33:so=00;35:do=00;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=01;05;37;41:su=37;41:sg=30;43:tw=30;42:ow=34;42:st=37;44:ex=00;32:*.cmd=00;32:*.exe=00;32:*.com=00;32:*.btm=00;32:*.bat=00;32:*.sh=00;32:*.csh=00;32:*.tar=00;31:*.tgz=00;31:*.svgz=00;31:*.arj=00;31:*.taz=00;31:*.lzh=00;31:*.lzma=00;31:*.zip=00;31:*.z=00;31:*.Z=00;31:*.dz=00;31:*.gz=00;31:*.bz2=00;31:*.tbz2=00;31:*.bz=00;31:*.tz=00;31:*.deb=00;31:*.rpm=00;31:*.jar=00;31:*.rar=00;31:*.ace=00;31:*.zoo=00;31:*.cpio=00;31:*.7z=00;31:*.rz=00;31:*.jpg=00;35:*.jpeg=00;35:*.gif=00;35:*.bmp=00;35:*.pbm=00;35:*.pgm=00;35:*.ppm=00;35:*.tga=00;35:*.xbm=00;35:*.xpm=00;35:*.tif=00;35:*.tiff=00;35:*.png=00;35:*.mng=00;35:*.pcx=00;35:*.mov=00;35:*.mpg=00;35:*.mpeg=00;35:*.m2v=00;35:*.mkv=00;35:*.ogm=00;35:*.mp4=00;35:*.m4v=00;35:*.mp4v=00;35:*.vob=00;35:*.qt=00;35:*.nuv=00;35:*.wmv=00;35:*.asf=00;35:*.rm=00;35:*.rmvb=00;35:*.flc=00;35:*.avi=00;35:*.fli=00;35:*.gl=00;35:*.dl=00;35:*.xcf=00;35:*.xwd=00;35:*.yuv=00;35:*.svg=00;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:
CCACHE_DIR=/var/cache/ccache
SSH_AUTH_SOCK=/tmp/keyring-oFY6yl/ssh
GNOME_KEYRING_SOCKET=/tmp/keyring-oFY6yl/socket
gtmgbldir=/home/openvista/FOIA-JAN06/database
USERNAME=openvista
SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/2812,unix/unix:/tmp/.ICE-unix/2812
DESKTOP_SESSION=gnome
PATH=/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/gtm:/usr/lib/ccache:/home/openvista/bin
MAIL=/var/spool/mail/openvista
gtmroutines=/home/openvista/FOIA-JAN06/r /usr/local/gtm .
PWD=/etc/xinetd.d/medsphere
INPUTRC=/etc/inputrc
CCACHE_UMASK=002
GNOME_KEYRING_PID=2811
LANG=en_US.UTF-8
GDM_LANG=en_US.UTF-8
GDMSESSION=gnome
SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
HOME=/root
SHLVL=3
SDL_AUDIODRIVER=esd
GNOME_DESKTOP_SESSION_ID=Default
LOGNAME=openvista
CVS_RSH=ssh
QTLIB=/lib
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-4RAjn6drDI,guid=1725e85d3e30bce1de93611f496af474
gtm_dist=/usr/local/gtm
LESSOPEN=|/usr/bin/lesspipe.sh %s
DISPLAY=:0.0
G_BROKEN_FILENAMES=1
XAUTHORITY=/root/.xauth7kKlk2
COLORTERM=gnome-terminal
_=/usr/bin/env
OLDPWD=/etc/xinetd.d
[root@localhost medsphere]#
==========
Setting xinetd – rpcbroker & script files
[root@localhost xinetd.d]# pwd
/etc/xinetd.d
[root@localhost xinetd.d]# ls
chargen-dgram daytime-dgram discard-stream medsphere tcpmux-server
chargen-stream daytime-stream echo-dgram rpcbroker time-dgram
cvs discard-dgram echo-stream rsync time-stream
[root@localhost xinetd.d]# vi rpcbroker
contents of /etc/xinetd.d/rpcbroker file
==========================
service rpcbroker
{
disable = no
type = UNLISTED
id = rpcbroker
socket_type = stream
protocol = tcp
port = 9201
user = 1000
wait = no
server = /etc/xinetd.d/medsphere/script
}
==================
[root@localhost xinetd.d]# pwd
/etc/xinetd.d
[root@localhost xinetd.d]# pwd
/etc/xinetd.d
[root@localhost xinetd.d]# ls
chargen-dgram daytime-dgram discard-stream medsphere tcpmux-server
chargen-stream daytime-stream echo-dgram rpcbroker time-dgram
cvs discard-dgram echo-stream rsync time-stream
[root@localhost xinetd.d]# cd medsphere
[root@localhost medsphere]# ls
script.sh
[root@localhost medsphere]# vi script.sh
contents of /etc/xinetd.d/medsphere/script file
===================
#!/bin/bash
#export gtm_dist=/path/to/gtm/installation
export gtm_dist=/usr/local/gtm
#export gtmgbldir=/path/to/global/directory.gld
export gtmgbldir=/home/openvista/FOIA-JAN06/database
#export gtmroutines=/path/to/routines
export gtmroutines=/home/openvista/FOIA-JAN06/r /usr/local/gtm .
$gtm_dist/mumps -run GTMLNX^XWBTCPM
==========================
[root@localhost medsphere]# pwd
/etc/xinetd.d/medsphere
===============
EXECUTION STEPS
======
STARTING XINETD
================================
=====
step 1
starting xinetd
=====
[root@localhost medsphere]# cd /etc
[root@localhost etc]# cd init.d
[root@localhost init.d]# pwd
/etc/init.d
[root@localhost init.d]# ./xinetd start
Starting xinetd:
STARTING OPEN VISTA SERVER
$gtm
GTM> D ^XUP
===========================
STARTING BRIDGE :
======================
[openvista@localhost ~]$ cd openvistacis-0.9.9-bridge
[openvista@localhost openvistacis-0.9.9-bridge]$ ls
addins-0.9.9-release-1.0-beta-1082
Alerts.asmx
bin
Bridge.exe
Bridge.exe.mdb
CISUser.asmx
config.aspx
Consults.asmx
CoverList.asmx
CWAD.asmx
Documents.asmx
Encounter.asmx
GuiVitals.asmx
Imaging.asmx
Labs.asmx
Locations.asmx
login.aspx
Medications.asmx
Medsphere.OpenVista.CIS.Remoting.dll
Medsphere.OpenVista.CIS.Remoting.dll.mdb
Medsphere.OpenVista.CIS.Shared.dll
Medsphere.OpenVista.CIS.Shared.dll.mdb
Medsphere.OpenVista.Core.dll
Medsphere.OpenVista.Core.dll.mdb
Medsphere.OpenVista.Remoting.dll
Medsphere.OpenVista.Remoting.dll.mdb
Medsphere.OpenVista.Shared.dll
Medsphere.OpenVista.Shared.dll.mdb
Medsphere.OpenVista.Shared.Test.dll
Medsphere.OpenVista.Shared.Test.dll.mdb
Medsphere.OpenVista.Vista.Remoting.dll
Medsphere.OpenVista.Vista.Remoting.dll.mdb
Medsphere.OpenVista.Vitals.Remoting.dll
Medsphere.OpenVista.Vitals.Remoting.dll.mdb
Medsphere.OpenVista.Vitals.Shared.dll
Medsphere.OpenVista.Vitals.Shared.dll.mdb
Mono.Addins.dll
Mono.Security.dll
Orders.asmx
PatientCareEncounters.asmx
Patients.asmx
Print.asmx
Problems.asmx
Reminders.asmx
Reports.asmx
RpcProxy.asmx
Templates.asmx
version.aspx
Visits.asmx
VistaUser.asmx
Vitals.asmx
web.config
web.config.in
[openvista@localhost openvistacis-0.9.9-bridge]$ mono Bridge.exe --vista-host localhost --vista-port 9201
OpenVista® Bridge version 0.9.9-release-1.0-beta-1082 starting
Found addins:
- Medsphere.OpenVista.Remoting
- Medsphere.OpenVista.Vitals.Remoting, 0.9.9-release-1.0-beta-1082
- Medsphere.OpenVista.Vista.Remoting
- Medsphere.OpenVista.CIS.Remoting, 0.9.9-release-1.0-beta-1082
Ready for connections.
===================================================================
START CIS CLIENT
[openvista@localhost ~]$ cd openvistacis-0.9.9-client
[openvista@localhost openvistacis-0.9.9-client]$ mono OpenVistaCIS.exe
============
Error Message :
Bridge unable to connect to OpenVistA server, incorrect host and/or port
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.
Based on previous posts & analysis
following changes was done to rpcbroker file and the location of the script file
( script file moved to /etc/medspshere/script)
from the log file /var/log/messages - it was found that script file was not executing
because it was not having execute permission
RPCBROKER FILE
[root@localhost medsphere]# cd /etc/xinetd.d
[root@localhost xinetd.d]# pwd
/etc/xinetd.d
[root@localhost xinetd.d]# ls
chargen-dgram cvs daytime-stream discard-stream echo-stream rsync time-dgram
chargen-stream daytime-dgram discard-dgram echo-dgram rpcbroker tcpmux-server time-stream
[root@localhost xinetd.d]# cat rpcbroker
service rpcbroker
{
disable = no
type = UNLISTED
id = rpcbroker
socket_type = stream
protocol = tcp
port = 9201
user = 1000
wait = no
server = /etc/medsphere/script
}
[root@localhost xinetd.d]#
SCRIPT FILE
[root@localhost log]# cd /etc
[root@localhost etc]# cd medsphere
[root@localhost medsphere]# pwd
/etc/medsphere
[root@localhost medsphere]# ls
script
[root@localhost medsphere]# cat script
#!/bin/bash
#export gtm_dist=/path/to/gtm/installation
export gtm_dist=/usr/local/gtm
export gtm_dist_med=/home/openvista/FOIA-JAN06/r
#export gtmgbldir=/path/to/global/directory.gld
export gtmgbldir=/home/openvista/FOIA-JAN06/database
#export gtmroutines=/path/to/routines
export gtmroutines=/home/openvista/FOIA-JAN06/r /usr/local/gtm .
$gtm_dist_med/mumps -run GTMLNX^XWBTCPM
[root@localhost medsphere]#
execute permission is given as follows
[root@localhost medsphere]# ls -la
total 20
drwxr-xr-x 2 root root 4096 2009-01-13 11:24 .
drwxr-xr-x 113 root root 12288 2009-01-13 11:21 ..
-rwxr-xr-x 1 root root 380 2009-01-12 20:27 script
and also it was found that netstat command gives proper listener for port 9201
[root@localhost log]# netstat -apn | grep 9201
tcp 0 0 :::9201 :::* LISTEN 11411/xinetd
[root@localhost log]#
but now the client still gives new error with
"Unable to connect to VistA server" with STOP sign icon in the pop up message box
and the logfile /var/log/messages has the following messages
Jan 13 12:26:09 localhost xinetd[11411]: START: rpcbroker pid=11641 from=::ffff:127.0.0.1
Jan 13 12:26:09 localhost xinetd[11411]: EXIT: rpcbroker status=1 pid=11641 duration=0(sec)
Jan 13 12:26:25 localhost xinetd[11649]: getpwuid( 1000 ) (service=rpcbroker) failed: Success (errno = 0)
Jan 13 12:26:25 localhost xinetd[11411]: START: rpcbroker pid=11649 from=::ffff:127.0.0.1
Jan 13 12:26:25 localhost xinetd[11411]: EXIT: rpcbroker status=1 pid=11649 duration=0(sec)
how to resolve this cis popup error message
"Unable to connect to VistA server" , what is rpcbroker status=1 ?
is there any other instrumentation log file - to know more about the reason for "unable to connect"?
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.
As per rpcbroker user setting required , checked
id -u
and found user id as 503 for user - openvista and put that in rpcbroker file
but i am now getting different error ( message log given below ) from script file export gtmroutines command line
the messages are as below
1. i was not able to execute bridge from openvista login - so it was been executed with root login
2. Openvista has been started with root login , but my taskman shows not running
( earlier it was not running , i changed the box:volume pair - then it started running ,
now again it is not running despite giving restart command )
3.CIS client login as root & Openvista both give the same error for gtmroutines export line in script file
==
BRIDGE ( bridge requires root login , for openvista user gives error)
[openvista@localhost openvistacis-0.9.9-bridge]$ mono Bridge.exe --vista-host localhost --vista-port 9201
OpenVista® Bridge version 0.9.9-release-1.0-beta-1082 starting
Unhandled Exception: System.UnauthorizedAccessException: Access to the path "./bin/Bridge.exe" is denied.
at System.IO.File.Delete (System.String path) [0x00000]
at System.IO.Directory.RecursiveDelete (System.String path) [0x00000]
at System.IO.Directory.Delete (System.String path, Boolean recurse) [0x00000]
at Medsphere.OpenVista.Bridge.Driver.Main (System.String[] args) [0x00000]
[openvista@localhost openvistacis-0.9.9-bridge]$ su root
Password:
[root@localhost openvistacis-0.9.9-bridge]# ls -la bridge.exe
ls: cannot access bridge.exe: No such file or directory
[root@localhost openvistacis-0.9.9-bridge]# ls -la Bridge.exe
-rwxr-xr-x 1 openvista openvista 112128 2008-05-14 03:20 Bridge.exe
[root@localhost openvistacis-0.9.9-bridge]# mono Bridge.exe --vista-host localhost --vista-port 9201
OpenVista® Bridge version 0.9.9-release-1.0-beta-1082 starting
Found addins:
- Medsphere.OpenVista.Remoting
- Medsphere.OpenVista.Vitals.Remoting, 0.9.9-release-1.0-beta-1082
- Medsphere.OpenVista.Vista.Remoting
- Medsphere.OpenVista.CIS.Remoting, 0.9.9-release-1.0-beta-1082
Ready for connections.
===
CIS CLIENT ERROR LOG
[openvista@localhost openvistacis-0.9.9-client]$ mono OpenVistaCIS.exe
etc/medsphere/script: line 8: export: `/usr/loc
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke (System.Runtime.Remoting.Proxies.RealProxy rp, IMessage msg, System.Exception& exc, System.Object[]& out_args) [0x00000]
===
BRIDGE ERROR LOG
[openvista@localhost openvistacis-0.9.9-bridge]$ mono Bridge.exe --vista-host localhost --vista-port 9201
OpenVista® Bridge version 0.9.9-release-1.0-beta-1082 starting
Unhandled Exception: System.UnauthorizedAccessException: Access to the path "./bin/Bridge.exe" is denied.
at System.IO.File.Delete (System.String path) [0x00000]
at System.IO.Directory.RecursiveDelete (System.String path) [0x00000]
at System.IO.Directory.Delete (System.String path, Boolean recurse) [0x00000]
at Medsphere.OpenVista.Bridge.Driver.Main (System.String[] args) [0x00000]
[openvista@localhost openvistacis-0.9.9-bridge]$ su root
Password:
[root@localhost openvistacis-0.9.9-bridge]# ls -la bridge.exe
ls: cannot access bridge.exe: No such file or directory
[root@localhost openvistacis-0.9.9-bridge]# ls -la Bridge.exe
-rwxr-xr-x 1 openvista openvista 112128 2008-05-14 03:20 Bridge.exe
[root@localhost openvistacis-0.9.9-bridge]# mono Bridge.exe --vista-host localhost --vista-port 9201
OpenVista® Bridge version 0.9.9-release-1.0-beta-1082 starting
Found addins:
- Medsphere.OpenVista.Remoting
- Medsphere.OpenVista.Vitals.Remoting, 0.9.9-release-1.0-beta-1082
- Medsphere.OpenVista.Vista.Remoting
- Medsphere.OpenVista.CIS.Remoting, 0.9.9-release-1.0-beta-1082
Ready for connections.
Read failure
at System.Net.Sockets.NetworkStream.Read (System.Byte[] buffer, Int32 offset, Int32 size) [0x00000]
at Medsphere.OpenVista.Remoting.DataConnection.NetCall (System.String rpc, System.String packet, System.String& sec, System.String& app, System.Boolean& fatal) [0x00000]
RPC SECURITY ERROR:
etc/medsphere/script: line 8: export: `/usr/loc
===
rpcbroker uid set as userid for openvista
service rpcbroker
{
disable = no
type = UNLISTED
id = rpcbroker
socket_type = stream
protocol = tcp
port = 9201
user = 503
wait = no
server = /etc/medsphere/script
}
====
script file content – giving error line 8 (gtmroutines – export statement )
#!/bin/bash
#export gtm_dist=/path/to/gtm/installation
export gtm_dist=/usr/local/gtm
export gtm_dist_med=/home/openvista/FOIA-JAN06/r
#export gtmgbldir=/path/to/global/directory.gld
export gtmgbldir=/home/openvista/FOIA-JAN06/database
#export gtmroutines=/path/to/routines
export gtmroutines=/home/openvista/FOIA-JAN06/r /usr/local/gtm .
$gtm_dist_med/mumps -run GTMLNX^XWBTCPM
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.