Recital on UNIX Installation

From Recital Documentation Wiki
Revision as of 13:02, 4 October 2010 by Yvonnemilne (Talk | contribs)

Jump to: navigation, search

Overview

Recital products for UNIX (except SCO OpenServer) are distributed as a binary executable which contains all the products and allows any one or more of them to be installed. Recital products for SCO OpenServer are distributed as individual tar archives.

Recital

A complete database with an integrated 4GL scripting language for developing and deploying high performance character mode database applications. Used extensively in banking, logistics, POS and other systems that require quick response times.

Recital Server

A cross-platform SQL database and application server.

Recital Web

A server-side scripting language, integrated database and application server for creating dynamic Web pages

Downloads

Recital products for UNIX are available for the following platforms:


Recital for UNIX product codes
Operating System Product code
HP PA-RISC HP-UX 10.20 and above Product Code 20
Sun SPARC Solaris 8 and above Product Code 36
SCO OpenServerr 5.0.5 and above Product Code 47
Sun Intel Solaris 10 and above Product Code 52
IBM AIX 4.3 and above Product Code 54
HP Intel Itanium HP-UX 11.23 and above Product Code 61


Downloads are available from the Downloads area of http://www.recitalsoftware.com.

For details of purchasing Recital licenses, please contact Recital Sales mailto:sales@recitalsoftware.com or visit our online store at http://www.recitalsoftware.com. For evaluation licenses, please contact Recital Support mailto:support@recitalsoftware.com

Graphical Installation

Note: The installation must be run as root.

  1. Download the distribution file into a temporary directory
  2. Check that the distribution file has the execute permission set
  3. Run the distribution file
  4. Follow the on screen instructions:
    1. License agreement
    2. Select components
    3. Installation directory and shortcuts
    4. Linking to /usr/bin
    5. ODBC Installation type (Recital Server / Recital Client Drivers)
    6. Java Virtual Machine selection (Recital Server / Recital Client Drivers)
    7. TomCat Installation type (Recital Server / Recital Client Drivers)
    8. Apache Firecat Plugin Installation (Recital Web)
    9. Install license file

Text Installation

Note: The installation must be run as root.

  1. Download the distribution file into a temporary directory
  2. Check that the distribution file has the execute permission set
  3. Run the distribution file
  4. Follow the on screen instructions:
    1. License agreement
    2. Select components
    3. Installation directory and shortcuts
    4. Linking to /usr/bin
    5. ODBC Installation type (Recital Server / Recital Client Drivers)
    6. Java Virtual Machine selection (Recital Server / Recital Client Drivers)
    7. TomCat Installation type (Recital Server / Recital Client Drivers)
    8. Apache Firecat Plugin Installation (Recital Web)
    9. Install license file

Tar Installation

Note: The installation must be run as root.

  1. Create a directory on your system called recital-x.x where x.x is the Recital version number, by convention this is created in /usr.
    # cd /usr
    # mkdir recital-x.x
  2. Download the tar file into this directory
  3. Change to the directory
    # cd /usr/recital-x.x
  4. Extract the files from the downloaded tar archive
    # tar xf tarfile
  5. Run the extracted setup script for the product
    Recital:
    # ./setup/setupRTD.sh /usr/recital-x.x
    Recital Server:
    # ./setup/setupRDS.sh /usr/recital-x.x
    Recital Web:
    # ./setup/setupRWD.sh /usr/recital-x.x
    Recital Client Drivers:
    # ./setup/setupRCD.sh /usr/recital-x.x


Uninstall

Note: The uninstaller must be run as root.

To uninstall Recital products for UNIX, run the uninstall script in your chosen installation directory.

Running Recital

Recital can be accessed from the graphical environment using its desktop shortcut, or from a terminal or console using the following commands from the Operating System command prompt.

db [-p <license text file>] | [-r] | [-w] [-f]

Starts Recital in development mode. In development mode, the command window or prompt and the development tools are accessible. Development mode access requires a valid development license.


Option Description
–p Loads the information from a license text file into the Product Registration Screen, and then allows the license to be saved before starting.
–r Displays the Product Registration Screen, allowing license details to be added or amended before starting.
–w Start without the default windows active. The default windows are defined in the main config.db. The windows can also be disabled using the CLEAR WINDOWS command.
–f Start in Fox compatibility mode. The following are active: SET COMPATIBLE TO FOXPRO and SET FILETYPE TO FOXPRO. This can also be achieved using the fox script instead of the db script.
dbdemo

Starts Recital in Assistant mode in the demo directory.

dbl -i <input file> -o <output file> -x <first procedure> -m <message file>

Calls the Recital/Linker to link program source. Please see the Recital/Linker documentation for full details.

dbrt <compiled program>

or

db -x <compiled program>

Runs the specified <compiled program> in runtime mode. In runtime mode the development tools are not accessible and all source must be compiled. For more information on compiling, please see the COMPILE command. Runtime mode access requires a valid runtime license. The following alternative syntax can also be used:

dbstop <pid>

Cleanly stops the Recital process identified by the process identification number in <pid>.

dbusers –c | -l | -r

Creates, resets or lists the users file or files. Please see the Users Files documentation for full details.


Exiting Recital

Type QUIT at the command prompt to exit Recital.


Managing the Recital Server

The Recital Server can be managed using the uas script.

Note: uas must be run as root.

Starting the Recital Server:

# uas start

Restarting the Recital Server:

# uas restart

Stopping the Recital Server:

# uas stop

Is the Recital Server Running?:

# uas status