Every VistA variant has its strengths and weaknesses. One of OpenVistA's is its straightforward and open source [[http://medsphere.org/community/project/gtm/blog/2010/01/13/install-openvista-in-about-10-minutes-updated|install procedure]]: * apt-get the OpenVistA environment and download the zip with OpenVistA's globals and routines * command-line utilities that create directories, compile code and setup instances. * the only annoying thing is that you have to manually reset the value of ''box pair'' in ''TaskMan Site Parameters". then you just do "/etc/init.d/openvista start " and all is well. WorldVistA's procedure is much more trying but thankfully you can make WorldVistA run in the OpenVistA environment: * download the zip with WorldVistA's globals and routines * create a new VistA instance with the OpenVistA's command line utility, ovinstance add, but instead of pointing to OpenVistA's globals and routines, point to WorldVistA's. There's one gotcha: WorldVistA ships globals in a .dat, OpenVistA uses (the more portable?) .zwr format. * again you need to manually reset "box pair" * BUT you also have to '''manually''' delete the contents of the Taskman global! * AND WorldVistA doesn't use MSC's add-on to GT.M to make its sockets behave like Cache's and so you must configure and start xinetd to run the RPC Broker with this done, you type the (incongruous) "/etc/init.d/openvista start worldvista" and an instance of WorldVistA called worldvista comes to life. I presume but haven't yet tested that FOIA would run in MSC's environment in the same way. I think that there should be one environment on Linux+GT.M for all VistAs in preparation for the setup of one unified VistA. I can't see a need for difference in something this rudimentary. Nor do I think it should be an involved process. My vote is that OpenVistA's setup forms the basis of a (converged) "installation and management environment" but perhaps others know of better setups than MSC's?