Difference between revisions of "Migrating a VistA/GT.M installation from one platform to another"
From VistApedia
| Line 5: | Line 5: | ||
# [http://xinetd.org xinetd] is assumed to control th | # [http://xinetd.org xinetd] is assumed to control th | ||
# It is assumed that the GT.M versions use the same database format. | # It is assumed that the GT.M versions use the same database format. | ||
| − | # The VistA environments to be copied must be identified, along with the hierarchical structure, e.g. | + | # The VistA environments to be copied must be identified, along with the hierarchical structure (see [[Link title]]), e.g. |
#* /usr/local/FOIAVistA20061230 | #* /usr/local/FOIAVistA20061230 | ||
#** /var/FOIAVistAprod | #** /var/FOIAVistAprod | ||
Revision as of 14:32, 26 July 2007
These are instructions for copying a GT.M SemiVivA installation from one platform to another. For this discussion, the platforms are assumed to be of different endian-ness, e.g., x86 GNU/Linux and Sun SPARC Solaris).
Notes
- Existing SemiVivA scripts use the bash shell, and assume that it is located at /bin/bash. Modify the location if bash is located elsewhere. Edit the scripts as needed to use other shells.
- xinetd is assumed to control th
- It is assumed that the GT.M versions use the same database format.
- The VistA environments to be copied must be identified, along with the hierarchical structure (see Link title), e.g.
- /usr/local/FOIAVistA20061230
- /var/FOIAVistAprod
- /usr/local/WorldVistAEHRvTEST20070616
- /home/vista/myWorldVistAEHR
- /home/bhaskar/WorldVistAEHRdev
- /home/vista/myWorldVistAEHR
- /usr/local/FOIAVistA20061230
Steps
- Obtain and install GT.M for the new platform in a sub-directory of /usr/local, e.g., in /usr/local/gtm_V5.2-001.
