OpenVistA Medsphere Installation and Setup Problems
Jawad Shafiq
Ben Mehling
Has anyone downloaded the Medsphere server and Client installations from sf.net and set it up correctly. If yes, is CIS working ??
I suppose you mean _besides_ Medsphere, right? :-)
I did explain all the steps in another thread on this group and ben Mehling did reply once.
According to the last email I saw, I thought it was determined you were using the "old style" RPC broker setting. Did you switch to the "new style" broker then? I do apologize we don't have much documentation available at this time, but we'll add things as we can.
We injected some of our own code and replaced Medsphere Connection class code with our own. It was sucessfull. we got the first screen, patient list, all the 'patient selection' filters are wroking, and one can see Alerts at the 'patient selection screen' too.
I'm afraid I don't understand -- you "injected some of your own code and replaced Medsphere Connection class"? What does that mean? Where was the change made? In the Server or in CIS product? What was changed?
But after selecting a patient, the 'cover sheet' screen is displayed and program hangs for like infinite time. After running CIS in debug mode, it seems like it is fetching data from the server and it is taking ages.
OpenVista Server:
- What operating system?
- What DB server are you running? Cache? GT.M?
- The broker is running as "new style" now? What port?
- What WebDAV service are you running -- on the same server?
OpenVista CIS:
- What operating system?
- If windows, .NET or Mono? Latest GTK library?
A hang like you describe has not been reported to us before. Honestly, it sounds like OpenVista Server is running fine. Are you able to connect w/ a CPRS v26 client to the broker okay? Any hangs in CPRS v26? What did you replace the "Medsphere Connection Class" with -- could that be the problem? Is the server publicly accessible -- can we try to connect to it from our offices?
Ben, could you please help me out here. i want to make a connection to the OpenVista sevrer using your (medsphere's) Connection classes. At server side, TaskManager is running and a RPClistner port is also open.
I'm happy to help, but we need much more in terms of specific details -- your emails don't give me a lot to work with.
- Ben
Jawad Shafiq
- WinXP box
- Mumps subsystem/DB server is Cache 5.2
- New Style broker running at 9250
- WebDAV ?? what for??
- WinXP box with GTK runtime....same machine as OpenVistA server
- Latest GTK library
"We did a little more digging and it seems that the during DataConnection.StartSession() function. the server does not return "accept" the tcpclient.readbyte() returns -1 and so the session is not started. We noticed that the RPC protocol useed in the DataConnection class is a little different i.e. sending [XWB] in the header.we have developed an inhouse RPCcomm connector in c# where we use a slightly different version we send {XWB} in the message header. we repleaced the DataConnection class with our RPCComm class and the CIS connected to the server successfully"
Ben Mehling
On 3/7/07, Jawad Shafiq <jawad....@gmail.com > wrote:
OpenVistA server:
- WebDAV ?? what for??
OpenVistA CIS:
- WinXP box with GTK runtime....same machine as OpenVistA server
- Latest GTK library
Regarding Code injection/replacement ..we didnt change the CIS code or anbything on the server side...but we did make some changes to Bridge code....i guess you missed the last thread..let me paste it here ...again
I saw the email -- I just think you're twiddling a lot of knobs at once. If you change out too many variables at once, debugging becomes difficult.
Yes, i was/am using both old and new style broker and tested both type of brokers. none of them worked.Yes, i am able to connect CPRS 26 to the server and all the tabs are working fine. i can browse through all tabs and perform diffrent actions.
So my guess is the Server is setup fine, except that you should definitely have the broker in 'new style' mode.
But with CIS, if we use Medspher's Bridge code , we get an error "session rejected by server" and if we use the modified version of bridge(with our code injected), we get an infinite hang on 'cover sheet' tab of CIS.
I don't think that we'll be able to debug a configuration we don't know. I suggest you get the setup working out of the box before modifying the communication protocols. I believe it was stated earlier that the differences in RPC traffic was the broker settings (and that's why you were seeing the "[]" versus "{}").
We'll help where we can, but helping to debug software you've written and included in our Bridge is extremely difficult.
Thanks, Ben
Edmond Cissé
I am facing the same problem Jawad reported i.e I'm prompted with the
"session rejected by the server"
error dialog box when attempting to connect using MedSphere CIS. I
work with the solutions out of the box from Medpshere distrib. (no
source code changes).
FYI : I setup a VistA server from CacheVADemo9-26-06 package and use
CPRSChartVer68 which connects and work fine.
My working environment :
OpenVista Server:
- Windows XP Pro SP2
- Cache 5.2
- Localhost/Port 9220 (I checked in the TaskMgr that Bridge is
running)
OpenVista CIS:
- Windows XP Pro SP2(running on the server)
- .NET Framwork 1.1
Do not hesitate if you need any test to be performed or additional
information I could provide to fix the problem.
Regards.
--
Edmond Cissé.
> rejected by server"
On Mar 7, 10:45 pm, "Ben Mehling" <ben.mehl...@medsphere.com> wrote:
> On 3/7/07, Jawad Shafiq <jawad.sha...@gmail.com> wrote:
>
> > OpenVistA server:
>
> > - *WebDAV ?? what for??*
>
> > Image server -- that's how the client uploads/displays images. This is
>
> probably not what's causing your issue, so we'll have to come back to this
> later.
>
> OpenVistA CIS:
>
>
>
> > - WinXP box with GTK runtime....same machine as OpenVistA server
> > - Latest GTK library
Ben Mehling
FYI : I setup a VistA server from CacheVADemo9-26-06 package and use
CPRSChartVer68 which connects and work fine.
Hrrrm. The VA Demo Cache package? I'm not sure that we've tested recently against a stock FOIA VistA server setup. While the changes we've made to the OpenVista Server are modest, I do believe we require them for CIS to work. I can try to test the CIS against a stock FOIA VistA server and see what the results are... thanks for giving this a try, but I'm not surprised there are connection issues w/ the VA's version of the server.
Do not hesitate if you need any test to be performed or additional
information I could provide to fix the problem.
- Ben
Greg Woodhouse
On Mar 10, 9:06 am, "Ben Mehling" <ben.mehl...@medsphere.com> wrote:
>
> Thanks... let's see if we can get this working w/ some minor adjustments to
> the VA Server config.
>
> - Ben
Did you say that the basic difference is that you had added some new
RPCs to CIS? I don't know how RPCs work in CIS, but the bsic process
of creating RPCs in VistA is a bit convoluted (in my opinion), but
relatively straightforward. Fist of all, you need a routine and entry
point where the first parameter (passed by reference) is used for the
return value. The input parameters (the remaining ones) are passed by
value. Next, an entry is created in the REMOTE PROCEDURE file with the
desired RPC name (which should be namespaced) and the entry point.
Now, that much is intuitive enough, but you then create an entry in
the OPTION file of type RPC pointing to the RPC. To give a use access
to the RPC, you need to place the corresponding option(s) on a menu,
and give that menu to the user as a secondary menu.
Perhaps this is all the same in CIS, and if so, I apologize for the
duplication. To add new RPCs to VistA, I'd recommed creating a KIDS
containing all of the above components and then making it into a
VistA patch. Obviously, you still need to assign the menus. his is
usually done manually, but could conceivably done as a post-install,
though I think system managers would not generally support this
procedure.