Ovrimos is very easy to install and does not require much disk space. Depending on the operating system, the total space required is between 3 to 4 MBytes of disk space.
The product comes in a zipped or tarred file (depending on the operating system). Since installation for all Unix-Linux systems requires similar steps, while installation in Win 32 requires different procedures, we describe the Win 32 installation separately and all Unix system installations together.

For both system platforms, it is necessary for TCP/IP to have been installed prior to running the Server. Installation, of course, may proceed and be completed even if the TCP/IP was not installed at this point. FreeBSD Unix users may have to rebuild their system kernel in order to install System V IPC before running the database. See Appendix - FreeBSD Unix for details.

Files and Data
The product kernel, together with the on-line manual is found in www.ovrimos.com.
Demo scripts and data files are provided separately. A readme file with instructions about script running is included.
Some general purpose information (readme files etc.) may also be found in the site.

Attention! Previous version owners! (Owners of Altera SQL Server)
Owners of Altera SQL Server version 2.0 must make some steps before and after Ovrimos version 2.5 installation if they wish to retain and reuse their Altera databases under Ovrimos. They must not proceed to installation before reading Appendix 6 - Previous version owners, which describes in detail the steps to be taken by both Win 32 and Unix system users.

Installation in Win 32 (x86 and Alpha)

The entire product comes in one zipped file. There is a x86 release, called x86.zip and an Alpha release, called alpha.zip  Installation steps go as follows:

• Users are advised to make a temporary directory where they will copy (or download) the appropriate zipped file.
• Unzip the contents with an uncompressing program (such as winzip or pkunzip)
• Run setup. The setup.exe is one self-extracting program, written with Install Wizard.

The above caption shows an example path, called datatools, where a tempodir is created. The zipped file was originally copied and unzipped there. Execution of the setup.exe file will start the installation.

The installation program is written with the InstallShieldWizard to provide uninstall facilities, therefore the usual screens of InstallShieldWizard appear at this point.

Caption Install-2 shows the first dialog box for the installation of Ovrimos.

The installation program will use C:\Ovrimos as a default path to copy files and create subdirectories. The user may modify that default path through the Browse... button.

The next screen, prompts the user for the Application Folder and assumes Ovrimos as a default folder name. The folder name may also be modified.
After obtaining this initial information, the installation program begins extracting files and creating directories. By default, a test database, called testbase is also created. This database is to be used for running some simple scripts and examples. Initially it is devoid of data files. Only example scripts and programs may be found under its root subdirectory.

Installation completion - x86 architecture
When copying and file generation is finished, a folder containing various elements of Ovrimos will appear on screen.

Ovrimos Folder
Caption Install-3 shows the Ovrimos Folder for Windows NT

 

The installation will be complete when the Database Manager will be installed. The user needs only click on the Install DBManager icon in Ovrimos Folder. As mentioned already in Working Environment, the database manager runs in Windows NT as a service. From this point on, the Database Manager service will be started automatically every time the NT starts running.

The folder elements will be described later in this section since they are of interest to both x86 and Alpha architecture computer owners.

Installation Completion - Alpha architecture
In Alpha architecture the Ovrimos Folder is not generated automatically. One more step is required for completing the installation.
The user must go to a subdirectory named bin, which was created during installation under the application root directory (i.e. if the default directory C:\Ovrimos was used, then it is C:\Ovrimos\bin) and run a batch file, called runme.bat. This batch file will install the Database Manager and generate the Ovrimos Folder. (See caption 3-3). From this point on, there is no difference between the x86 and the Alpha release for Win 32.

Brief description of the Ovrimos Folder elements

Help files
The first page (the index) of this manual.

Install DBManager
Installs the database manager as a service and starts this service. The database manager remains running as a service as long as the computer is on. Users need only connect to the DBManager HTTP Port. The services for testbase database are also installed at this point.

Readme File
A few on-line instructions as a simplified user's guide.

Remove DBManager
Stops the Database Manager and uninstalls the service. It does not remove the database manager file. It is necessary to remove the database manager as a service before uninstalling (or removing, renaming etc. the dbman program). The services for testbase database are also removed at this point.

SQL Client for testbase
Starts a DOS Client window for the existing database testbase. Ovrimos must be up and running for any connection to be accepted.

Please note that under WinNT 3.51 the installation fails to put the SQL Client arguments in the properties. Please go to the properties window for this icon (select it and go to File|Properties or press Alt+Enter) and add by hand after the executable name: "localhost testbase admin pegasus".

Start
This icon will call the browser for an HTTP connection to the database manager. Since the database manager is already installed and runs as a service, the Start icon is merely a shortcut for calling the browser and connecting to localhost:9000, which is the database manager default port. See also Parameters.
For more about starting and stopping the database server, see the Database Manager.

Uninstaller
The InstallWizard's uninstaller. The uninstall program will remove all files and directories that belong to Ovrimos, as well as the Registry entries that refer to the server. The registry entries for testbase are also removed. The uninstaller does not remove the database files and registry entries that belong to other databases, since this may not be the user's intention (i.e. the user does not wish to remove previously created databases in case of an upgrade). Users wishing to totally remove the databases and registry entries from their system, need do so, either through the database manager before uninstalling, or manually afterwards.

All directories created and files copied during installation are described in the Parameters: Files chapter of this manual.

Note: Static IP Address
The user's computer must have a static IP address. This is an issue for non-networked computers only. If users only use TCP/IP with dial-up connection, they need to define a static IP address. This is done by

• Start|Settings|Control Panel|Network|Protocols|TCP/IP Protocol|Properties|IP Address (Win NT)

If the host computer name is not known, then the user may run Network from the Windows Control Panel and click on the Identification tab. The first information field is the computer name.

NT users must make sure that \WINNT\System32 is in their path.

Installation in Unix

• The user must decide on the directory that will become the applicaton root. Before that he/she must make sure that the appropriate rights to create directories are granted.
• In the application root directory, the appropriate .tar file will be copied, e.g. for Solaris Sparc systems it will be solaris\sparc.tar.
• The file must be untarred by the tar program.
• The script dbman.ini.create, which is copied into the application root directory, must be run. This will create the database manager initialization file and the testbase initialization file.

During installation a test database, called testbase is also created. This database is to be used for running some simple scripts and examples. Initially it is devoid of data files. Only example scripts and programs may be found under its root subdirectory.

Registration and Licensing

Users do not register during installation. They may register as soon as they connect to the database manager program for the first time. See, The Database Manager for Licensing Information.

After Installation: First Run - Filling in the test database

As mentioned already, the Database Manager is the service/program that must be started before working on any database.
Users of Windows NT will have to install the Database Manager as a service (as described in Installation completion - x86 and Installation completion - Alpha above). Thus, in Windows NT the Database Manager is installed once and remains active thereafter.
Users of U*ix-Linux systems will have to run the dbman executable file, which remains running until explicitly stopped.
Next step is connecting to the Database Manager. Users may start any browser and type the URL address <host>:9000, where <host> is a host computer name (or address) and 9000 is the DBMANPORT. See also Parameters and the Database Manager.

In the beginning only the empty database testbase exists.
The database testbase, which is created during installation, may be filled with test data to allow users a quick start. Script and data files may be found in directory demos of the product site. To fill in the test database, the user will have to run the application program sqlapp4 from the directory where the data reside.
The user must start the database testbase. Then, assuming that no modifications of the initial parameters has been made, he/she must go to the directory containing the script and data and type:
  <full-path-name>\sqlapp4 <server>|localhost #3000 admin pegasus insert (Win 32) or
  <full-path-name>/sqlapp4 <server>|localhost 3000 admin pegasus insert (Unix).
 The application program sqlapp4 is described in detail in Application Interface - sqlapp4. Instructions are also written in the readme file under the directory demos. 
 
 
 

Previous Chapter: Working Environment

Next Chapter: Parameters-Database Functional Aspects