HOWTO: How to colorize code in your joomla articles with geshi

To insert code samples into your articles in joomla, you use the pre tag like this:

<pre xml:lang="xxx"> your code goes here </pre>

You can use any of the following languages for colorizing your code in articles.

recital, abap, dos, lotusscript, rails, actionscript3, dot, lscript, reg, actionscript, d, lua, robots, ada, eiffel, m68k, ruby, apache, email, make, sas, applescript, fortran, matlab, scala, apt_sources, freebasic, mirc, scheme, asm, genero, mpasm, scilab, asp, gettext, mxml, sdlbasic, autoit, glsl, mysql, smalltalk, avisynth, gml, nsis, smarty, bash, gnuplot, objc, sql, basic4gl, groovy,

ocaml-brieftcl, bf, haskell, ocaml, teraterm, blitzbasic, hq9plus, oobas, text, bnf, html4strict, oracle11, thinbasic, boo, idl, oracle8, tsql, caddcl, index.html, pascal, typoscript, cadlisp, ini, perl, vbnet, cfdg, inno, per, vb, cfm, intercal, php-brief, verilog, cil, io, php, vhdl, c_mac, java5, pic16, vim, cobol, java, pixelbender, visualfoxpro, c, javascript, plsql, visualprolog, cpp, kixtart, povray, whitespace, cpp-qt, klonec, powershell, winbatch, csharp, klonecpp, progress, xml, css, latex, prolog, xorg_conf, delphi, lisp, providex, xpp, diff, lolcode, python, z80, div, lotusformulas, qbasic

Published in Blogs

HOWTO: Installing 64bit Recital on Linux

For Recital to run correctly on 64bit Linux you require the ia32 shared libraries.

The 64bit port of Recital requires these libraries to allow access to 32bit Xbase and C-ISAM data files which are 32bit.

If you do not have these libraries installed you will either get a "can't find db.exe" or an "error loading shared libraries" when trying to run or license Recital.

Installing the ia32 shared libraries

Redhat EL 5 / Centos 5 / Fedora 10

Insert the Red Hat Enterprise Linux 5 Supplementary CD, which contains the ia32el package.
After the system has mounted the CD, change to the directory containing the Supplementary packages. For example:

cd /media/cdrom/Supplementary/
Install the ia32el package:

rpm -Uvh ia32el-<version>.ia64.rpm

Alternatively: Note you must have the required repo's enabled.

 yum install ia32el

Ubuntu / Debian

sudo apt-get install ia32-libs

Published in Blogs

HOWTO: setup in memory file system for temporary files

All temporary files created by Recital are stored in the directory specified by the environment variable DB_TMPDIR.

In order to have these files stored in memory first create a temporary directory

mkdir /opt/recital/tmp

Then mount the directory with the tmpfs command

mount -t tmpfs -o size=1g recitaltmpfs /usr/recital/tmp

Then change the DB_TMPDIR variable in the recital.conf to point to the newly created temporary directory.

Published in Blogs

Compatibility Dialog won't go away

TIP
The Compatibility Dialog settings are written to the compat.db file in <path>/conf - please ensure that the user setting the compatibility settings has write access to this file and directory. Once these settings are written, the dialog will not be displayed unless SET COMPATIBLE is issued.

Published in Blogs

Tagged under

TECHTIP

HOWTO: Configure Samba for Recital and FoxPro

Recital's version of Samba allows application data to be shared and locked correctly across these systems, allowing a truly integrated heterogeneous data environment. For example Recital applications running on a UNIX/Linux server can read and update FoxPro databases residing on a Microsoft Windows NT server through the use of Samba.

You can view the modified changes by downloading the following files and patching these into your current Samba installation.

open.c (file opening and share modes)

version.h (versioning information)

The variable CPPFLAGS in the file Makefile will require the define -DRECITAL added to it.

In order to make the locking compatible between UNIX/Linux and Windows the following environment variable must be placed in the profile.db for Unix/Linux Developer and in profile.uas for the Universal Application Server:

DB_SAMBA=YES ;export DB_SAMBA

The following settings need to be added to the smb.conf file to ensure that file names are always converted to lower case:

preserve case = no 
default case = lower 
mangle case = yes

The following settings need to be added to the smb.conf file for locking to operate correctly:

oplocks = False 
share modes = no

Published in Blogs

Using the Recital ECHO command

Recital 10 introduced the ECHO command. This command operates in the same way as the PHP ECHO command. It does not append a newline to the output but rather operates in the same way as the existing ?? command in Recital. The string being output can contain C-style string escapes \n \t or \r (newline, tab and carriage return respectively) e.g.

echo "Hello world\n"

Published in Blogs

Working with server-side JDBC data sources

In this article Barry Mavin, CEO and Chief Software Architect for Recital, details on how to use the Client Drivers provided with the Recital Database Server to work with local or remote server-side JDBC data sources.

Overview

The Recital Universal .NET Data Provider provides connectivity to the Recital Database Server running on any supported platform (Windows, Linux, Unix, OpenVMS) using the RecitalConnection object.

The Recital Universal JDBC Driver provides the same functionality for java applications.

The Recital Universal ODBC Driver provides the same functionality for applications that use ODBC.

Each of the above Client Drivers use a connection string to describe connections parameters.

The basic format of a connection string consists of a series of keyword/value pairs separated by semicolons. The equals sign (=) connects each keyword and its value.

The following table lists the valid names for keyword/values.

Name	Default	Description
Data Source -or- Server -or-Nodename		The name or network address of the instance of the Recital Database Server which to connect to.
Directory		The target directory on the remote server where data to be accessed resides. This is ignored when a Database is specified.
Encrypt -or- Encryption	false	When true, DES3 encryption is used for all data sent between the client and server.
Initial Catalog -or- Database		The name of the database on the remote server.
Password -or- Pwd		The password used to authenticate access to the remote server.
User ID		The user name used to authenticate access to the remote server.
Connection Pooling -or- Pool	false	Enable connection pooling to the server. This provides for one connection to be shared.
Logging	false	Provides for the ability to log all server requests for debugging purposes
Rowid	true	When Rowid is true (the default) a column will be post-fixed to each SELECT query that is a unique row identifier. This is used to provide optimised UPDATE and DELETE operations. If you use the RecitalSqlGrid, RecitalSqlForm, or RecitalSqlGridForm components then this column is not visible but is used to handle updates to the underlying data source.
Logfile		The name of the logfile for logging
Gateway		Opens an SQL gateway(Connection) to a foreign SQL data source on the remote server. Using Gateways, you can transparently access the following local or remote data sources: Recital Oracle ODBC (Server-side ODBC data sources) JDBC (Server-side JDBC data sources) ADO (Use this to connect to SQL Server and other Native Windows OLEDB data sources) MySQL PostgreSQL The gateway can be specified in several formats: servertype@nodename:username/password-database e.g. oracle@nodename:username/password-database mysql@nodename:username/password-database postgresql@nodename:username/password-database -or- odbc:odbc_data_source_name_on_server oledb:oledb_connection_string_on_server jdbc:jdbc_driver_path_on_server;jdbc:Recital:args

To connect to a server-side JDBC data source, you ue the gateway=value key/value pair in the following way.

gateway=jdbc:jdbc_driver_path_on_server;jdbc:Recital:args

You can find examples of connection strings for most ODBC and OLE DB data sources by clicking here.

Example in C# using the Recital Universal .NET Data Provider:

////////////////////////////////////////////////////////////////////////
// include the references below
using System.Data;
using Recital.Data;

////////////////////////////////////////////////////////////////////////
// The following code example creates an instance of a DataAdapter that 
// uses a Connection to the Recital Database Server, and a gateway to
// Recital Southwind database. It then populates a DataTable 
// in a DataSet with the list of customers via the JDBC driver. 
// The SQL statement and Connection arguments passed to the DataAdapter 
// constructor are used to create the SelectCommand property of the
// DataAdapter.
public DataSet SelectCustomers()
{
	string gateway = "jdbc:/usr/java/lib/RecitalJDBC/Recital/sql/RecitalDriver;"+
			"jdbc:Recital:Data Source=localhost;database=southwind";       
	RecitalConnection swindConn = new
			RecitalConnection("Data Source=localhost;gateway=\""+gateway+"\");
	RecitalCommand selectCMD = new
			RecitalCommand("SELECT CustomerID, CompanyName FROM Customers", swindConn);
	selectCMD.CommandTimeout = 30;
	RecitalDataAdapter custDA = new RecitalDataAdapter();    
	custDA.SelectCommand = selectCMD;    
	swindConn.Open();    
	DataSet custDS = new DataSet();
	custDA.Fill(custDS, "Customers");    
	swindConn.Close();
	return custDS;
}

Example in Java using the Recital Universal JDBC Driver:

////////////////////////////////////////////////////////////////////////
// standard imports required by the JDBC driver
import java.sql.*;
import java.io.*;
import java.net.URL;
import java.math.BigDecimal;
import Recital.sql.*;

////////////////////////////////////////////////////////////////////////
// The following code example creates a Connection to the Recital 
// Database Server, and a gateway to the Recital Southwind database. 
// It then retrieves all the customers via the JDBC driver.
public void SelectCustomers()
{
    // setup the Connection URL for JDBC
    String gateway = "jdbc:/usr/java/lib/RecitalJDBC/Recital/sql/RecitalDriver;"+
			"jdbc:Recital:Data Source=localhost;database=southwind";       
    String url = "jdbc:Recital:Data Source=localhost;gateway=\""+gateway+"\";

    // load the Recital Universal JDBC Driver
    new RecitalDriver();

    // create the connection
    Connection con = DriverManager.getConnection(url);

    // create the statement
    Statement stmt = con.createStatement();

    // perform the SQL query
    ResultSet rs = stmt.executeQuery("SELECT CustomerID, CompanyName FROM Customers");

    // fetch the data
    while (rs.next()) 
    {
        String CompanyID = rs.getString("CustomerID");
        String CompanyName = rs.getString("CompanyName");
        // do something with the data...
    }
    
    // Release the statement
    stmt.close();

    // Disconnect from the server
    con.close();
}

Published in Blogs

Recital tuning guide - Part 1

Recital is a rich and versatile product with many ways to do the same thing. Developers usually write code in the way that they are accustomed to without paying much attention to how this will perform in a multi-user environment with large amounts of users and transactions. The best way to optimize Recital applications is to use the built-in tuning capabilities introduced in Recital 10.

Published in Blogs

The Recital Solution for Universal Data Integration

In this article Barry Mavin, CEO and Chief Software Architect for Recital provides details on how the Recital Database Server can be used to provide a solution for Universal Data Integration.

Overview

The Recital Database Server handles universal cross-platform data access to a wide range of data sources. The database server natively handles full remote SQL data access to Recital, Visual FoxPro, FoxPro, FoxBASE, Clipper and older dBase data. Using Bridges, it handles full remote SQL data access to C-ISAM and OpenVMS RMS. Using gateway connections, it handles full remote SQL data access to Oracle, MySQL, PostgreSQL, SQL Server, server-side ODBC, server-side JDBC and server-side OLE DB data sources. With its ability to access data using server-side ODBC, JDBC and OLE DB drivers from clients on all supported operating systems (Windows, Linux, Unix, OpenVMS), the Recital Database Server is an ideal Data Integration Solution for applications of all sizes and complexity.

Universal Data Integration Solutions

There are several ways in which data may be accessed by the Database Server.

Table 1:

Client Universal Data Access solutions for accessing local or remote data.

Client	Solution
Recital	Use remote gateway connections
Visual FoxPro	Use the Universal ODBC Driver
Java (all platforms)	Use the Universal JDBC Driver
.NET Framework	Use the Universal .NET Data Provider
Microsoft Office	Use the Universal ODBC Driver
Windows Mobile	Use the Universal Compact Framework .NET Data Provider
PHP on Linux	Use the Universal ODBC Driver for Linux
Mono on Linux	Use the Universal .NET Data Provider
Others	If the data source you want to access is not in the list above, then you can use a remote ODBC, JDBC or OLE DB gateway. You can find examples of connection strings for most ODBC and OLE DB data sources by clicking here.

Table 2:

Windows Server Universal Data Access solutions accessible from any remote client running on Windows, Linux, Unix or OpenVMS:

Data Source	Solution
Recital	Native support (See table 1)
Visual FoxPro	Native support (See table 1)
FoxPro	Native support (See table 1)
FoxBASE	Native support (See table 1)
Clipper	Native support (See table 1)
dBase	Native support (See table 1)
C-ISAM	Use a bridge (See table 1)
Access	Use a gateway connection gateway="oledb:Provider=Microsoft.Jet.OLEDB.4.0;Data Source=\somepath\mydb.mdb;User Id=admin;Password=;"
Exchange	Use a gateway connection gateway="oledb:Provider=ExOLEDB.DataSource;Data Source=http://servername/publicstore"
Excel	Use a gateway connection gateway="oledb:Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\MyExcel.xls;"
Oracle	Use a gateway connection gateway="oledb:Provider=msdaora;Data Source=TheOracleDB;User Id=xxxxx;Password=xxxxx;"
SQL Server	Use a gateway connection gateway="oledb:Provider=sqloledb;Data Source=Aron1;Initial Catalog=pubs;User Id=sa;Password=asdasd;"
MySQL	Use a gateway connection gateway="oledb:Provider=MySQLProv;Data Source=mydb;User Id=xxxxx;Password=xxxxx;"
IBM DB2	Use a gateway connection gateway="oledb:Provider=DB2OLEDB;Network Transport Library=TCPIP;Network Address=XXX.XXX.XXX.XXX;Initial Catalog=MyCtlg;Package Collection=MyPkgCol;Default Schema=Schema;User ID=MyUser;Password=MyPW"
Sybase ASA	Use a gateway connection gateway="oledb:Provider=ASAProv;Data source=myASA"
Sybase ASE	Use a gateway connection gateway="oledb:Provider=Sybase.ASEOLEDBProvider;Srvr=myASEserver,5000;Catalog=myDBname;User Id=username;Password=password"
IBM Informix	Use a gateway connection gateway="oledb:Provider=Ifxoledbc.2;password=myPw;User ID=myUser;Data Source=dbName@serverName;Persist Security Info=true"
Ingres	Use a gateway connection gateway="odbc:dsn=data_source_name"
Firebird	Use a gateway connection gateway="odbc:dsn=data_source_name"
IBM AS400 iSeries	Use a gateway connection gateway="oledb:PROVIDER=IBMDA400; DATA SOURCE=MY_SYSTEM_NAME;USER ID=myUserName;PASSWORD=myPwd"
Interbase	Use a gateway connection gateway="oledb:provider=sibprovider;location=localhost:;data source=c:\databases\gdbs\mygdb.gdb;user id=xxxxx;password=xxxxx"
Others	If the data source you want to access is not in the list above, then you can use server-side ODBC, JDBC or OLE DB. You can find examples of connection strings for most ODBC and OLE DB data sources by clicking here. Full details on using server-side JDBC drivers can be found here. Full details on using server-side ODBC drivers can be found here. Full details on using server-side OLE DB drivers can be found here.

Table 3:

Linux and Unix Server Universal Data Access solutions accessible from any remote client running on Windows, Linux, Unix or OpenVMS:

Data Source	Solution
Recital	Native support (See table 1)
Visual FoxPro	Native support (See table 1)
FoxPro	Native support (See table 1)
FoxBASE	Native support (See table 1)
Clipper	Native support (See table 1)
dBase	Native support (See table 1)
C-ISAM	Use a bridge (See table 1)
Oracle	Use a gateway connection gateway="oracle:Connection_String"
MySQL	Use a gateway connection gateway="mysql:Connection_String"
IBM DB2	Use a gateway connection gateway="db2:Connection_String"
PostgreSQL	Use a gateway connection gateway="postgres:Connection_String"
Others	If the data source you want to access is not in the list above, then you can use a server-side JDBC driver. Full details on using server-side JDBC drivers can be found here.

Table 4:

OpenVMS Server Universal Data Access solutions accessible from any remote client running on Windows, Linux, Unix or OpenVMS:

Data Source	Solution
Recital	Native support (See table 1)
Visual FoxPro	Native support (See table 1)
FoxPro	Native support (See table 1)
FoxBASE	Native support (See table 1)
Clipper	Native support (See table 1)
dBase	Native support (See table 1)
RMS	Use a bridge (See table 1)
Others	If the data source you want to access is not in the list above, then you can use a server-side JDBC driver.

Supported Data Sources

Native Data Access

The Recital Database Server has native built-in support for the following data sources:

Recital
Visual FoxPro
FoxPro
FoxBASE
Clipper
dBase

You can setup tables to work with using the Database Administration Tool in Recital Enterprise Studio.

Bridges

Using Bridges, you can access the following data sources as if they were standard Recital/FoxPro tables:

CISAM
OpenVMS RMS

You can setup bridges using the Database Administration Tool in Recital Enterprise Studio.

Gateways/Connections

Using Gateways, you can transparently access the following local or remote data sources:

Recital
Oracle
ODBC (Server-side ODBC data sources)
JDBC (Server-side JDBC data sources)
OLEDB Use this to connect to SQL Server and other Windows OLE DB data sources)
MySQL
PostgreSQL

Remote Data Object functions

Recital 10 includes a complete and robust set of data source independent functions for accession MySQL, Oracle, DB2 and Postgres. This article explains how to use them.

Client Data Access drivers

Included with the Recital Database Server are three Client drivers. These Client drivers can access any data sources supported by the Recital Database Server. They are not restricted to accessing only Recital data. They can be used to access server-side ODBC, JDBC and OLE DB data sources also.

Recital Universal .NET Data Provider

Use this client driver when building .NET applications with Visual Studio .NET. A data provider in the .NET Framework serves as a bridge between an application and a data source. A data provider is used to retrieve data from a data source and to reconcile changes to that data back to the data source.

Key features of the Recital Universal .NET Data Provider:

Fully Internet enabled
The Recital Universal .NET Data Provider works across the internet providing access to a wide range of data sources located on remote servers running Windows, Linux, Unix and OpenVMS.
SQL Server compatible
The Recital Universal .NET Data Provider is plug compatible with the .NET Framework SQL Server Data Provider.
Cross-platform Data Integration
Using the Recital Universal .NET Data Provider, you can connect to remote Windows, Linux, Unix or OpenVMS servers and access any data source supported by the Recital Database Server.
Managed code
The Recital Universal .NET Data Adaptor written in C# is 100% .NET Framework managed code.
Runs on Windows Mobile
The Recital Universal .NET Data Adaptor runs under the .NET Compact Framework on Windows Mobile.

Recital Universal JDBC Driver

The JDBC API is the industry standard for database-independent connectivity between the Java programming language and a wide range of databases. The JDBC API provides a call-level API for SQL-based database access. JDBC technology allows you to use the Java programming language to exploit "Write Once, Run Anywhere" capabilities for applications that require access to enterprise data.

Key features of the Recital Universal JDBC Driver:

Fully Internet enabled
The Recital Universal JDBC driver works across the internet providing access to a wide range of data sources located on remote servers running Windows, Linux, Unix and OpenVMS.
JDBC 3.0 API
The Recital Universal JDBC driver supports the JDBC 3.0 API.
Pure Java Type 3 Driver
The Recital Universal JDBC driver is a 100% pure Java Type 3 driver.
Full Access to Metadata
The JDBC API provides metadata access that enables the development of sophisticated applications that need to understand the underlying facilities and capabilities of a specific database connection.
Cross-platform Data Integration
Using the Recital Universal JDBC driver, you can connect to remote Windows, Linux, Unix or OpenVMS servers and access any data source supported by the Recital Database Server.
No Installation
A pure JDBC technology-based driver does not require special installation; it is automatically downloaded as part of the applet that makes the JDBC calls. The Recital Universal JDBC Driver is 100% java.

Recital Universal ODBC Driver

Connect to remote data from Microsoft Office or other applications that support ODBC data access. The Recital Universal ODBC Driver is also available for Linux and Unix.

Key features of the Recital Universal ODBC Driver:

Fully Internet enabled
The Recital Universal ODBC driver works across the internet providing access to a wide range of data sources located on remote servers running Windows, Linux, Unix and OpenVMS.
Works with Crystal Reports
The Recital Universal ODBC driver supports the SQL syntax generated by Crystal Reports.
Works with Microsoft Office
The Recital Universal ODBC driver works with Microsoft Office products.
Works with PHP on Linux
The Recital Universal ODBC driver is available for Linux and works with PHP.

Published in Blogs

HOWTO: Guide to Optimizing GlusterFS

There is a good article on the gluster website here which gives some good information regarding file system optimization suitable for a HA Recital cluster solution.

Published in Blogs

Login

Register

User Registration

* Required field
Name: *
Username: *
Password: *
Confirm Password: *
Email Address: *
Confirm email Address: *

or Cancel

Installing the ia32 shared libraries

Redhat EL 5 / Centos 5 / Fedora 10

Ubuntu / Debian

Overview

Example in C# using the Recital Universal .NET Data Provider:

Example in Java using the Recital Universal JDBC Driver:

Overview

Universal Data Integration Solutions

Table 1:

Table 2:

Table 3:

Table 4:

Supported Data Sources

Native Data Access

Bridges

Gateways/Connections

Client Data Access drivers

Recital Universal .NET Data Provider

Recital Universal JDBC Driver

Recital Universal ODBC Driver

More...

Company

Products

Account

Support

Services

Login

Register