|
Windows: Upgrading Vitalware 1.4 to 2.0 |
|
|
Vitalware 2.0 Install/Upgrade Notes
|
Introduction
The upgrade from Vitalware Version 1.4 to 2.0.01 involves a number of steps. Please follow the instructions below carefully. You cannot skip any steps under any circumstances. Before proceeding with the update please ensure that a complete backup of the KE Vitalware server exists and is restorable.
There are four main components that require upgrading:
- Texpress (the database engine)
- TexAPI (web services)
- Vitalware Server (the application)
- Vitalware Client (the client)
The notes below detail how to upgrade all systems. Check the Releases table for Client specific notes. Upgrading comprises the following steps:
In the notes below client refers to the name of the client directory for the current installation. The term ~vw is used to refer to the user vw's home directory. This is normally /dev/fs/C/home/vw.
Requirements
Stopping Vitalware services
- Log in as local user vw.
- Start a Korn Shell with Start>Programs>Windows Services for UNIX>Korn Shell.
A command window will appear.
- Log in as vw
- Enter client client
- Enter vwload stop
Installing Texpress
Installing Texpress 8.1 is only required for the first client upgraded to Vitalware 2.0. Once Texpress 8.1 has been installed this section may be skipped for subsequent upgrades.
- Enter cd ~vw/texpress
- Enter mkdir -p texpress/8.1.xxx/install where xxx is the version of Texpress being installed.
- Enter cd 8.1.xxx/install
- Obtain the appropriate Texpress version for your Unix machine via the KE Texpress hyperlink above. Save the release in ~vw/texpress/8.1.xxx/install calling it texpress.sh.
- Enter sh texpress.sh
The Texpress release will be extracted.
- Enter . ./.profile
- Enter bin/texinstall ~vw/texpress/8.1.xxx (expand the ~vw)
The Texpress installation script will commence.
- Enter cd ~vw/texpress/8.1.xxx
- Enter . ./.profile
- Enter texbldperms
- Enter bin/texlicinfo. Obtain your Texpress licence code and place it in a file called .licence.
- Enter bin/texlicset < .licence to install the licence.
- Enter \rm -fr install
- Enter cd ~vw/texpress
- Enter In -s 8.1.xxx 8.1
Upgrading TexAPI
Installing TexAPI is only required for the first client upgraded to Vitalware 2.0. Once TexAPI has been installed this section may be skipped for subsequent upgrades.
- Enter cd ~vw/texpress
- Enter mkdir 3.1.xxx where xxx is the version of TexAPI being installed.
- Obtain the appropriateTexAPI version for your Windows 2000/XP/2003 running Microsoft Services for Unix machine via the KE TexAPI hyperlink above.
Save the release in ~vw/texpress calling it texapi.sh.
- Enter sh texapi.sh -i ~vw/texpress/3.1.xxx (expand the ~vw).
- Enter \rm -f texapi
- Enter ln -s 3.1.xxx texapi
- Enter rm -f texapi.sh
Upgrading Vitalware Server
- Enter cd ~vw/client
- Enter mkdir install
- Enter cd install
- Obtain the appropriate Vitalware version via the KE Vitalware Server hyperlink above.
Save the release in ~vw/client/install calling it vw.sh.
- Enter sh vw.sh. The Vitalware release will be extracted.
- Enter . ./.profile
- Enter bin/vwinstall client. The Vitalware installation script will commence.
- Enter cd ~vw/client
- Enter cp .profile.parent ../.profile
- Enter . ../.profile
- Enter client client
- Enter vwreindex -p eregistry
- Enter vwload stop
- Enter vwbldlinks
- Enter \rm -fr install
In order to allow easier upgrades of Texpress (without having to update the etc/opts file) all Texpress options are now set in the client specific .profile-local file. When upgrading from Vitalware 1.4 to Vitalware 2.0 you will have to add all Texpress options from the Texpress 8.0 installation. In particular the dateorder, dateformat, timeformat, latitudeformat, longitudeformat, tmppath and loadmemory settings should be noted. Please see Texpress options for a list of acceptable values.
- Enter vi .profile-local and add the Texpress options to the file. An example file is:
TEXPRESSOPTS="${TEXPRESSOPTS} dateorder=mdy dateformat='dd MMM yyyy'" export TEXPRESSOPTS
- Enter client client
- Any other client specific setting can be set at this time (e.g. shell specific settings, etc.).
Now that the client is installed the upgrade process can take place. The steps below may take some time to complete on large data sets.
- The client will now be upgraded to Vitalware 2.0. If you are upgrading from a version prior to Vitalware 1.4.07 you must run the upgrade scripts sequentially for all versions after the old version before running the Vitalware 2.0 upgrade.
- Enter vwsecurity
- Enter upgrade-2-0-01
- Enter upgrade-2-0-01.security (may take some time)
- This next step must, without exception, reindex every table. A reindex is required even if the table does not contain any records. Also if any table contains a data/tablename/vwoptions file which has the line:
REINDEX=no then you must temporarily set the value to yes or comment out that line prior to running the vwreindex command. Enter vwreindex -f -p (may take some time)
- Enter upgrade-2-0-01.tabs
The script upgrade-2-0-01.security sets the default record level security values. The default settings allow Everyone to Display, Edit and Delete records, subject to normal operational privileges. Some institutions may want to alter the default security upgrade to take advantage of their security model. If the default security upgrade is not required, custom built upgrade scripts must be produced to set the base security values. The upgrade-3-1-01.security script removes all history records from the upgraded tables. Standard KE Vitalware installations do not use the Texpress history facility so upgrading is safe. If an institution does use the history facility (TT & QLD?) another update mechanism is required (eg. global edits from within the Vitalware client).
The script upgrade-2-0-01.tabs adds the Security tab immediately prior to the Admin tab. If the Security tab is to be hidden from users, the appropriate tab switching entries must be modified after performing the upgrade.
Starting Vitalware services
- Enter vwload start
- Enter exit to close the command window.
- Log out.
Upgrading Vitalware Client
When upgrading to Vitalware 2.0 the Windows client must be installed on all client machines. To upgrade the Vitalware Client follow the Installing Vitalware Client notes.
Introduction
|
|
Last Updated on Monday, 15 March 2010 20:57 |