Set-up after Installation

Once you have installed Reality, you must carry out some or all of the following, depending on your installation:

1. Install the latest Reality updates. See Installing Updates.

2. See Setting up a firewall.

3. Create one or more databases. See Creating a database.

4. Configure your databases. See Configuring a database.

5. Configure any Resilience features that you intend using. See Configuring resilience features.

Setting up a firewall

If you have installed Reality on any recent version of Windows (that is, on Windows Server 2003 SP1 or later), you must enable incoming connections through the Windows firewall by running the batch file realmanDirectory\15.1\bin\sup\firewall.bat - you can find the location of the realman directory by using the Defaults option in the netadmin host utility - see Specifying Defaults.

By default, firewall.bat enables the following connections from the servers subnet:

• Incoming connections to Reality (telnet, ODBC/JDBC, JReal, RealWeb, Remote File Access).

• Connections from GUI admin clients (port 2002).

• Reality remote administration (for tlmenu) or GUI admin (port 445).

• Reality remote administration and mini web server for on-line documentation.

• Failsafe link.

• Clean log transfer during database recovery from tlmenu.

• Reality Remote Tape server.

If you do not need to use all the above, or access is required from other subnets, you can edit firewall.bat and edit or comment out the appropriate lines. Alternatively, you can configure the Windows Firewall using the Windows Control Panel.

Creating a database

Before you can start using Reality you must create at least one database. Different types of database are available (refer to Types of Database) - this section shows you how to create a partition database using files on a single disk partition so that you can start using Reality. You can create this type of database at any convenient location in the Windows file system.

To create a Reality database, start a Windows command prompt, change to the drive and folder that will hold the database and then run the mkdbase command. For a database on a single file system, include the -S option to specify the size of the database:

mkdbase -S size -N databaseName

Where size is the size of the database in Mbytes (M suffix) or Gigabytes (G suffix). For example:

mkdbase -S 100M -N pdbase

creates a 100Mbyte database called pdbase.

Before other users can use your database, you must do the following:

• Use the netadmin utility to set the default database - see Specifying Defaults.
• Use the unlockdbase utility to unlock the database.

The database owner

When you create a new database, a Reality user-id with SYSMAN privileges is created for the database owner (the Windows user who created it). The owner of the database can log on even when the database is locked, without specifying a user-id. If you need to administer the database, you should log on as the database owner.

To start Reality and log on as the database owner, use the realitycommand, specifying the database required. For example, to log on to the database dbase0, enter:

reality dbase0

Configuring a database

The Reality system can be configured to suit particular user requirements by using the configuration parameters listed in the section Reality Configuration on the Host. The parameters required must be defined in the Windows file drive:\usr\realman\15.1\files\config if they are applicable to all new databases. To change the settings for a particular database, edit the appropriate config file (DatabasePath\configs\config) once you have created the database. Missing parameters are given their default values.

Tape configuration

If your system has one or more tape drives, you must set the following parameters.

Parameter	Default Value	Purpose
TapeNum	2	TapeNum defines the number of tape drives on the database, named Tape1, Tape2, etc.
TapeDevTypen	3	TapeDevType1, TapeDevType2, etc. define the type of tape drive for TAPE1, TAPE2, etc, respectively. The types currently supported are: 2   8mm (Exabyte) cartridge 3   ¼ inch (QIC) cartridge 5   4mm (DAT) cartridge 8   remote tape 9   tape image
TapeDevSizen		TapeDevSize1, TapeDevSize2, etc defines the tape capacity size of the tape used in dbsave. Still relevant with virtual tape drives.
Tapen	As defined in the supplied config file	Associates a tape number with a Windows device name.
CompressTapeImage	0	Specifies the default compression level (0 to 9) for tape images created from this database. 0 is no compression (fastest); 9 is maximum compression (slowest). Recommended level: 2.

The Tapen entries define the default devices for tape attachments without density specifications. For example, the TCL command T-ATT 2 will use Tape2. Additional entries in the form Tapen:density can be used to define different devices. For example, the command T-ATT 1 DEN = 6250 would require an entry Tape1:6250 = \\.\TAPE0.

Reality counts tape drives from 1, whereas Windows counts tape drives from 0. Tape1 is therefore normally set to \\.\TAPE0. Appending the letter 'c' to the Windows device (for example, \\.\TAPE0c) will enable hardware compression if available.

How to configure tape devices is described in greater detail in the User's Reference: Administration.

Configuring resilience features

To enable resilience features to be used, you must create a Rawlog file. It is recommended that you use a separate disk for the logs (Rawlog and the cleanlogs).

1. Make a logs folder:

   C:\> mkdir Drive:\clogs	(where Drive is the logs drive)

2. Log on to Windows as the database owner and from the Command Prompt, run:

   C:\> mklog -rtos100 Drive:\clogs\RawLog (where Drive is the logs drive)

   This will create a 100Mb Rawlog.

3. Stop and start the central daemon using:

   C:\> realserv -e

   C:\> realserv -s

   Note

   This will log off all users from all databases.

4. Use tlmenu from the command prompt to setup the database for Transaction Logging or Failsafe (refer to the Resilience section of the on-line documentation for details).

5. Set up the accounts and files for transaction handling by running TL-SET-LOG-STATUS from TCL

6. Transaction Logging can now be started.