var myHorizontalSlide;
  window.addEvent('domready', function() {
	var status = {
		'true': 'open',
		'false': 'close'
	};

	myHorizontalSlide = new Fx.Slide('driver_feature_description', {mode: 'horizontal'});

	$('driver_feature_description').style.display = "none";
	$('driver_anatomy').style.width = "677px";
	$('left_arrow').style.display = "none";
	myHorizontalSlide.hide();

	$('h_slidein').addEvent('click', function(e){
		$('driver_anatomy').style.width = "880px";
		//e.stop();
		$('driver_feature_description').style.display = "block";
	        $('left_arrow').style.display = "block";
	        $('right_arrow').style.display = "none";
		myHorizontalSlide.slideIn();
	});

	$('h_slideout').addEvent('click', function(e){
		//e.stop();
		$('driver_feature_description').style.display = "none";
		$('driver_anatomy').style.width = "677px";
	        $('left_arrow').style.display = "none";
	        $('right_arrow').style.display = "block";
		myHorizontalSlide.slideOut();
	});

	// When Horizontal Slide ends its transition, we check for its status
	myHorizontalSlide.addEvent('complete', function() {
		$('horizontal_status').set('html', status[myHorizontalSlide.open]);
	});
});

//<!-- Feature descriptions -->

  var feature_descs = {

standard_api_support:
  '<h1>Industry Standard API Support</h1>' +
  '<h2>JDBC, ADO.NET, ODBC, OLE-DB, XMLA</h2>' +
  '<p>' +
  'Consistent support for the major Data Access APIs, based on standards leadership, eliminates DB vendor lock-in.' +
  '</p>' +
  '<p>' +
  '<span class="fd_label">Blistering performance:</span><br/>Our drivers deliver data access performance levels across ODBC, JDBC, ADO.NET and OLE DB ' +
  "that don't compromise the viability of DBMS independent application development and deployment." +
  '</p>'
  ,

jdbc:
  '<h1>JDBC</h1>' +
  '<h2>Key Features</h2>' +
  '<p>' +
  '<span class="fd_label">Pure Java Drivers:</span><br/>' +
  'Our JDBC Drivers are 100% pure and run on any platform hosting a Java Virtual Machine (JRE).' +
  '</p><p>' +
  '<span class="fd_label">Miniature Driver Size:</span><br/>' +
  'Driver size is minimal with the smallest variant (Megathin) under 60K in size.' +
  '</p>' +
  '<h2>JDBC 3.0+ Enhancements</h2>' +
  '<p>' +
  '<span class="fd_label">Connection Pooling:</span><br/>' +
  'JDBC 3.0 standardizes connection pooling configuration properties thereby alleviating complexity ' +
  'from the myriad vendor-specific properties in JDBC 2.0. This enables higher interchangeability across JDBC Drivers for JDBC compliant application' +
  'and service developers. Additionally, the properties allow administrators to fine tune the connection pool to maximize the performance characteristics ' +
  'of the application or service. The following properties are implemented by our drivers: maxStatements, initialPoolSize, minPoolSize, maxPoolSize, maxIdleTime, and propertyCycle.' +
  '</p><p>' +
  '<span class="fd_label">Datatype Enhancements:</span><br/>' +
  'The DATALINK and BOOLEAN datatypes are additions to java.sql.Types. The DATALINK type provides access to external resources (URLs) from ' +
  'within a resultset using the new getURL() methods. While the BOOLEAN type is the logical equivalent of the BIT type with additional ' +
  'semantics, and is retrieved from a resultset using the getBoolean() method.' +
  '</p><p>' +
  '<span class="fd_label">Transaction Savepoints Support:</span><br/>' +
  'JDBC 3.0 provides the ability to have increased granularity over the control of database transactions. ' +
  'The new Savepoint interface allows you to partition a transaction into logical breakpoints, providing control over how much of the transaction gets rolled back.' +
  '</p><p>' +
  '<span class="fd_label">JDBC Metadata Enhancements:</span><br/>' +
  'The JDBC metadata APIs have been enhanced in JDBC 3.0, with the DatabaseMetaData interface now able to retrieve SQL type hierarchies. ' +
  'There is also a new ParameterMetaData interface to describe the types and properties of the parameters in PreparedStatement objects.' +
  '</p><p>' +
  '<span class="fd_label">Named Parameters in Callable Statements:</span><br/>' +
  "Prior to JDBC 3.0, the way to set a parameter in a SQL Stored Procedure was by specifying the parameter's index, not its name. " +
  "The CallableStatement interface has been enhanced in JDBC 3.0 so that you can now specify parameters by their names." +
  '</p><p>' +
  '<span class="fd_label">Resultset Holdability:</span><br/>' +
  'A holdable cursor, or result, is one that does not automatically close when the transaction that contains the cursor is committed. ' +
  'JDBC 3.0 adds support for specifying cursor holdability. To specify the holdability of your ResultSet, you must do so when preparing ' +
  'a statement using the createStatement(), prepareStatement(), or prepareCall() methods. The holdability may be one of the following constants: ' +
  'HOLD_CURSORS_OVER_COMMIT or CLOSE_CURSORS_AT_COMMIT.</p><p><em>Note: it is more efficient to close CURSOR at the end of transactions (after the COMMIT). ' +
  "JDBC doesn't specifiy a default HOLD_CURSOR behavour but for resource expediency we have chosen CLOSE_CURSORS_AT_COMMIT as the default.</em></p>" +
  '</p><p>' +
  '<span class="fd_label">Array Bound RowSets:</span><br/>' +
  'As part of the new RowSet class. It is now possible to bind data arrays to the columns of the OpenLink RowSet object, and retrieve the data directly ' +
  'into the arrays with a single invocation of the RowSet.next() method.' +
  '</p><p>' +
  '<span class="fd_label">Prepared Statement Pooling:</span><br/>' +
  'A prepared statement allows you to take a commonly used SQL statement and pre-compile it, thereby dramatically improving performance if the statement is executed multiple times. If your application has many queries that are reused with only parametric changes occuring, then it is beneficial to pool these statements and retain control over their life span. JDBC 3.0 delivers as solution to this need via Prepared Statement Pooling, which enables the life span of a prepared statement to be handled at the driver level thereby alleviating the JDBC application or service developer of this responsibility.' +
  '</p>'
  ,

ado_net:
  '<h1>ADO.NET</h1>' +
  '<p>' +
  '<span class="fd_label">Visual Studio and ASP.NET Compatibility:</span><br/>' +
  'OpenLink data providers integrate fully with Visual Studio and ASP.NET.' +
  '</p><p>' +
  '<span class="fd_label">Entity Framework Compatibility:</span><br/>' +
  "Support for Microsoft's Entity Framework and ADO.NET 3.5 is provided through OpenLink's ADO.NET Entity Framework Provider for Virtuoso." +
  '</p><p>' +
  'This Visual Studio 2008 compatible provider provides access to native Virtuoso data (SQL, XML, and RDF) in addition to any ' +
  'Virtuoso Linked Tables from external ODBC and JDBC accessible data sources.' +
  '</p><p>' +
  'Known-compatible external data sources include:<ul><li>Oracle (versions 7.x to 11.x)</li><li>Microsoft SQL Server (6.x to 2005)</li><li>IBM DB2</li><li>Sybase (4.2 to 12.x+)</li>' +
  '<li>IBM Informix (5.x to 11.x)</li><li>Ingres (6.4 to 9.x)</li><li>Progress (7.x to 10.x)</li><li>MySQL</li><li>PostgreSQL</li><li>Firebird</li></ul>' +
  '<a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VirtAdoNet35Provider">More Info</a>' +
  '</p>'
  ,

odbc:
  '<h1>ODBC</h1>' +
  '<p>' +
  '<span class="fd_label">ODBC 3.5 Compliance:</span><br/>' +
  'Enables broad compatibility between an extensive collection of older and newer ODBC applications across an array of platforms' +
  '</p><p>' +
  '<span class="fd_label">Cross Platform Support:</span><br/>' +
  'Enables the development of ODBC compliant applications and the utilization of ODBC drivers on non-Windows platforms such as: Linux (x86, PPC, Itanium, Opteron), Mac OS X, Mac OS Classic, FreeBSD, Solaris, AIX, HP-UX, HP True64 UNIX, IRIX, Altix, SCO UnixWare, and others.' +
  '</p><p>' +
  'ODBC support on non-Windows platforms is provided through the OpenLink-branded iODBC Driver Manager, <a href="http://www.iodbc.org">iODBC</a> being the acronym for Independent Open DataBase Connectivity, an Open Source platform-independent implementation of both the ODBC specifications.' +
  '</p>'
  ,

ole_db:
  '<h1>OLE-DB</h1>' +
  '<p>' +
  'The OpenLink OLE-DB to ODBC Provider is implemented as an OLE-DB to ODBC bridge, utilizing ODBC data sources for connectivity to databases.' +
  '</p><p>' +
  'The provider is bound to the ODBC Driver Manager enabling connectivity to any ODBC data source via an OpenLink ' +
  'Multi-Tier or Single-Tier driver or any third party ODBC driver.' +
  '</p><p><span class="fd_label">Microsoft SQL Linked Server (32 & 64 Bit) Compatible</span><br/>' +
  'UDA Release 6.2 includes a Microsoft SQL Server-compatible OLE DB provider which has been significantly enhanced ' +
  'to support SQL Server Linked Servers and add on services such as SQL Server Analysis Services and SQL Server Integration Services.' +
  '</p>'
  ,

xmla:
  '<h1>XMLA</h1>' +
  '<p>' +
  'XML for Analysis (XMLA) is the industry standard for data access in analytical systems such as OLAP and Data Mining.' +
  '</p><p>' +
  'The <a href="http://oat.openlinksw.com">OpenLink AJAX Toolkit</a> (OAT) includes an OpenLink XMLA Data Provider as part of the OpenLink AJAX DataBase Connectivity (ADBC) interface, ' +
  'a Generic Data Access API for Javascript that provides transparent access to SQL (via XMLA), RDF (via SPARQL), XML (via HTTP), Web Services ' +
  '(SOAP or REST variants over HTTP) and Free Text (via GData) data.' +
  '</p><p>' +
  'The OpenLink XMLA Data Provider includes binding layers to ADO.Net, OLEDB, ODBC & JDBC enabling transparent access to data stores accessible by any of these data access APIs. ' +
  'A lightweight standalone Web Server is also included for hosting the OAT and XMLA Provider applications or services. IIS can also be configured for hosting.' +
  '</p>'
  ,

advanced_api_functionality:
  '<h1>Advanced Data Access API Functionality</h1>' +
  '<h2>Build High Performance Applications Using Advanced API Features</h2>' +
  '<p>' +
  'Enables the development and utilization of DBMS application with DBMS independent granularity that extends to ' +
  'challenging areas such as scalar function calls, dates and timestamps manipulation, outer join handling, and SQL stored procedure invocation etc.' +
  '</p>'
  ,

multithreading:
  '<h1>Multithreading Support</h1>' +
  '<p>' +
  'Enables exploitation of scalability benefits arising from the use of multiple CPUs or clusters while developing or using DBMS independent applications' +
  '</p>'
  ,

unicode:
  '<h1>Unicode Support</h1>' +
  '<p>' +
  'Enables the development and deployment of internationalized applications that are independent of underlying database engine.' +
  '</p>'
  ,

distributed_transactions:
  '<h1>Distributed Transaction Processing</h1>' +
  '<h2>Two-Phase Commit Across ODBC, JDBC and ADO.NET</h2>' +
  '<p>' +
  'OpenLink Multi-Tier and Single-Tier drivers support distributed transactions using the Microsoft Distributed Transaction Co-ordinator (MS-DTC) ' +
  'or an XA-compliant transaction manager, such as Tuxedo. Distributed transactions are supported for Oracle, SQLServer, Sybase, Informix and Ingres. ' +
  'OpenLink JDBC drivers support distributed transactions using the Java Transaction API (JTA).' +
  '</p><p><a href="http://docs.openlinksw.com/mt/xamt.html">More Info</a>' +
  '</p>'
  ,

scrollable_cursors:
  '<h1>Scrollable Cursors</h1>' +
  '<h2>ODBC and JDBC Scrollable Cursor Support</h2>' +
  '<p>' +
  'Full support for ODBC and JDBC scrollable cursors provides applications with a flexible model for handling sensitivity to data changes.' +
  '</p>' +
  '<p>' +
  'Our ODBC drivers support the complete ODBC Scrollable Cursor Model covering scrollable cursor types: Forward-Only, Static, KeySet, Dynamic and Mixed.' +
  '</p>' +
  '<p>' +
  'JDBC scrollable cursors enable the development of JDBC-based DBMS independent applications that are capable of exploiting the ODBC style ' +
  '(Attached RowSet extension to JDBC by OpenLink) and JDBC style (Detached RowSet) scrollable cursor models from a single driver.' +
  'This approach provides the application developer with maximum flexibiity and control over the degree of database change sensitivity expressed by a JDBC based application.' +
  '</p>'
  ,

consistent_functionality:
  '<h1>Consistent Cross-Database Functionality</h1>' +
  '<h2>Improve Interoperability and Productivity through Uniformity</h2>' +
  '<p>DBMS support for the following functionality areas, and the manner in which each is exposed by the native DBMS API or SQL dialect, differs widely across database vendors:</p>' +
  '<ul><li>outer joins</li><li>scalar functions</li><li>stored procedures</li><li>CLOB and BLOB support</li><li>parameter binding</li><li>date and time literals</li></ul>' +
  "<p>The use of standard data access APIs coupled with OpenLink's industry leading driver implementations alleviates the problems caused by the non-uniformity of native DBMS APIs." +
  '</p>'
  ,

standard_or_native_sql:
  '<h1>API Standard or Native SQL</h1>' +
  '<p>' +
  'Applications can maximise their database independence by using the standard SQL defined by the data access API (e.g. ODBC SQL), ' +
  'but still revert to the native DBMS SQL dialect if necessary to exploit advanced proprietary database features.' +
  '</p>'
  ,

rich_uniform_meta_data:
  '<h1>Rich Uniform Meta Data</h1>' +
  '<p>' +
  'The meta-data interfaces of the industry-standard data access APIs reduce development costs by providing a consistent view of database metadata. ' +
  '</p><p>' +
  'OpenLink drivers provide rich meta-data, frequently synthesizing the required data when the base database meta-data or database API is not rich enough ' +
  'to furnish this information directly. This facility obviates the need for developers to craft often very complex queries to interrogate the database system tables directly.' +
  '</p><p>' +
  '<span class="fd_label">Enhanced ADO.NET Metadata:</span><br/>' +
  "A weakness of ADO.NET is the lack of a rigid metadata specification to which data providers must conform. " +
  "To enhance the metadata available from ADO.NET, OpenLink's ADO.NET providers expose all the schema information available from ODBC. " +
  '</p><p>' +
  "By exposing ODBC-like metadata through ADO.NET, the OpenLink providers plug a large gap in ADO.NET using a familiar and well established standard, " +
  "at the same time providing cross database uniformity across all the databases supported by OpenLink. " +
  '<a href="http://wikis.openlinksw.com/dataspace/owiki/wiki/UdaWikiWeb/UdaAdoNet2ProviderMetaDataExtensionsUserDocWP">More Info</a>' +
  '</p>'
  ,

uniform_error_handling:
  '<h1>Uniform Error Handling</h1>' +
  '<p>' +
  'The use of a standard data access API obviates the need for database-specific error handling in application code. ' +
  'OpenLink drivers map database native error codes to standard SQLSTATE values as defined by X/Open, across ODBC, JDBC and ADO.NET. ' +
  'The use of standard error codes streamlines application code, reduces coding effort and maximises application cross-database interoperability.' +
  '</p>'
  ,

missing_functionality_compensation:
  '<h1>Missing DB Functionality Compensation</h1>' +
  '<p>' +
  'Some of the more advanced features of the standard data access APIs demand functionality which many native DBMS APIs cannot provide directly. ' +
  '</p><p>' +
  'In such circumstances, OpenLink drivers compensate for the missing DBMS functionality by emulating it in the driver. ' +
  '</p><p>' +
  'Examples of this kind of compensation include scrollable cursor support, array parameter binding and array fetching, and scalar functions not supported natively.' +
  '</p>'
  ,

flexible_deployment_options:
  '<h1>Flexible Deployment Options</h1>' +
  '<h2>Maximum Incorporation, Minimum Disruption</h2>' +
  '<p>' +
  'OpenLink drivers are available in both Single-Tier and Multi-Tier formats to allow you to leverage any existing DBMS network software in your organisation. ' +
  "This flexibility reflects OpenLink's maxim of:</p>" +
  '<p><em>"Maximum technology incorporation with minimum disruption to your current computing infrastructure"</em>' +
  '</p>'
  ,

express_edition:
  '<h1>Express Edition (Single Tier)</h1>' +
  '<p>' +
  'An OpenLink Express Edition driver is a single component installed on the desktop or workstation machine only - there is no server-side administration. ' +
  'Once installed, it provides seamless connectivity to the database. ' +
  '</p><p>' +
  'Express Edition drivers interface to the wire-protocol of the underlying database. This is a client-only interface that communicates directly with the remote database server. ' +
  'These interfaces are typically unavailable to third-party developers. ' +
  "Express Edition drivers have been designed in harmony with Apple's Mac Universal Platform." +
  '</p><p><a href="http://uda.openlinksw.com/odbc/express/">More Info</a>' +
  '</p>'
  ,

lite_edition:
  '<h1>Lite Edition (Single Tier)</h1>' +
  '<p>' +
  '<span class="fd_label">Single Component Installation Process:</span><br/>' +
  'Lite Edition drivers utilise database-vendor-provided networking middleware products, ' +
  'such as Net8 and SQL*Net, Progress Client Networking, Informix Connect, Ingres Net, DB2 Connect etc.' +
  '</p><p>' +
  'In situations where DBMS vendor networking is already in place, Single-Tier Drivers provide ease of installation and configuration since ' +
  'you are only required to install a single client component that inherently depends on existing DBMS specific networking for remote data access.' +
  '<p/><p><a href="http://uda.openlinksw.com/odbc/st/">More Info</a>' +
  '</p>'
  ,

enterprise_edition:
  '<h1>Enterprise Edition (Multi Tier)</h1>' +
  '<h2>Database Independent Communications</h2>' +
  '<p>The Multi Tier Enterprise Edition features a high performance database-independent communications layer.' +
  '</p><p>' +
  'Multi Tier Enterprise Edition consists of three main types of component:' +
  '<ul><li>A <b>Generic Client</b>:<br/>A single driver (one per data access standard - ODBC, JDBC, OLE-DB etc) for connecting to a variety of data sources.</li>' +
  '<li>A <b>Request Broker</b>:<br/>Responsible for managing connections between Generic Clients and Server Agents. ' +
  'The Request Broker is completely configurable and its responses to incoming requests from Clients controlled by the <em>Sessions Rules Book</em>.</li>' +
  '<li><b>Server Agents</b>:<br/>One or more task specific applications launched by the Request Broker for Generic Clients to communicate with, and facilitate their needs.' +
  '<br/>Server agents are typically of two types:' +
  '<ul><li>Database Agents - One specific to each database: Oracle, Progress, Ingres, Postgres, SQL Server, etc...</li>' +
  '<li>ODBC-Bridge or JDBC-Bridge Agents - Special case Database Agents where another ODBC or JDBC data source is the target database.</li>' +
  '</ul></ul></p>' +
  '<h2>Benefits</h2>' +
  '<p>' +
  '<span class="fd_label">Powerful Access Policy Configuration:</span><br/>The Request Broker in combination with the Sessions Rules Book provides a powerful, centralized means of enforcing data access policies and data source aliasing.' +
  '</p><p>' +
  '<span class="fd_label">Generic Drivers:</span><br/>Install just one client component, as opposed to several, for your database independent applications.' +
  '</p><p>' +
  '<span class="fd_label">Network Ready:</span><br/>Enables usage of DBMS independent applications on any platform without installation of additional DBMS specific networking products.' +
  '</p>'
  ,

broad_os_support:
  '<h1>Broad (32 & 64 Bit) OS Support</h1>' +
  '<p>' +
  '32- and 64-bit components enable the development and utilization of 32- or 64-bit DBMS independent applications.' +
  '</p>'
  ,

windows:
  '<h1>Windows</h1>' +
  '<p>' +
  "OpenLink's product offering on Windows includes support for:" +
  '<ul><li>32 bit: Windows 98/NT/2000/XP/2003/Vista</li><li>64 bit: Windows XP/2003/Vista (Itanium)</li></ul>' +
  '<a href="http://download.openlinksw.com/download/product_matrix.vsp">More Info</a>' +
  '</p>'
  ,

unix:
  '<h1>UNIX</h1>' +
  '<p>' +
  "OpenLink's UDA product offering spans a broad range of UNIX variants, including:" +
  '<ul>' +
  '<li>Linux</li><li>HP-UX</li><li>Solaris</li><li>AIX</li><li>Tru64 UNIX</li><li>FreeBSD</li><li>UnixWare</li><li>SCO OpenServer</li><li>Dynix/PTX</li><li>Irix</li>' +
  '</ul>' +
  '<a href="http://download.openlinksw.com/download/product_matrix.vsp">More Info</a>' +
  '</p>'
  ,

mac_os_x:
  '<h1>Mac OS X</h1>' +
  '<p>' +
  'Our Mac OS X offering includes support in Mac OS X Universal binaries for PPC and Intel 32-bit mode on Tiger (10.4) and Leopard (10.5), plus Intel 64-bit mode on Leopard.' +
  '</p><p>' +
  '<a href="http://download.openlinksw.com/download/product_matrix.vsp">More Info</a>' +
  '</p>'
  ,

intelligent_networking:
  '<h1>Intelligent Networking</h1>' +
  '<p>' +
  'The UDA product suite uses intelligent networking to minimise driver and network configuration overhead, whilst maximising driver performance and wire security.' +
  '</p>'
  ,

zeroconfig_networking:
  '<h1>ZeroConfig Networking</h1>' +
  '<h2>Zero Configuration for ODBC DSNs (Multi Tier)</h2>' +
  '<p>' +
  'Provides a cross platform implementation of the Rendezvous service discovery protocol. This enables the configuration of ' +
  'ODBC Data Sources Names (DSNs) to be completely server based with no client side configuration whatsoever.' +
  '</p><p>' +
  'You simply pick a DSN configuration associated with your OpenLink Request Broker from a combo-box hosted list of OpenLink Services.' +
  '</p>'
  ,

network_aware_record_retrieval:
  '<h1>Network Aware Record Retrieval & Insertion</h1>' +
  '<p>' +
  'Enables the retrieval or insertion of multiple DBMS records in batches over the network with a minimal number of network hops. ' +
  '</p><p>' +
  'Record prefetching is fully configurable, with the number of records prefetched in a single call to the server set through a FetchBufferSize configuration parameter.' +
  '</p>'
  ,

secure_data_transmission:
  '<h1>Secure Data Transmission</h1>' +
  '<p>' +
  'Enables development and utilization of encrypted data transmission between DBMS independent applications and backend databases.' +
  '</p><p>' +
  'As of Version 5.2, OpenLink UDA drivers now come with optional support for using OpenSSL to encrypt the data layer between a generic client and the request broker / agent.' +
  '</p><p>' +
  '<span class="fd_label">SSL Implementation Features:</span><ul>' +
  '<li>Secures connections to both the broker and all database agents</li>' +
  '<li>Encryption is optional, although it can be made mandatory</li>' +
  '<li>The same connection endpoint endpoint (port) handles both encrypted and non-encrypted clients</li>' +
  '<li>Fully backward-compatible</li>' +
  '<li>Per-agent certificates</li>' +
  '<li>All changes are in the OpenLink communications layer - there is no need to change any of the database agents to cater for SSL.</li>' +
  '</ul>' +
  '</p>'
  ,

deferred_blob_fetching:
  '<h1>Deferred BLOB Fetching</h1>' +
  '<p>' +
  'The OpenLink generic multi-tier client features intelligent BLOB/CLOB data handling. ' +
  '</p><p>' +
  'For instance, the implementations of the ODBC functions SQLGetData and SQLPutData facilitate ' +
  'transferring BLOB parameter data in parts over the network between the client and database agent. ' +
  'Once transferred, the fragmented parameter data is reassembled during insertion.' +
  '</p><p>' +
  'Deferred fetching of BLOB data is supported, so BLOB data in a result set is only retrieved on-demand when actually accessed by the application.' +
  '</p>'
  ,

centralized_configuration:
  '<h1>Centralized Configuration & Management</h1>' +
  '<p>' +
  'Provides a single point of focus when administering the data sources that serve the data access standards compliant applications.' +
  '</p>'
  ,

distributed_licence_manager:
  '<h1>Distributed Licence Manager</h1>' +
  '<p>' +
  'Licence files can be shared and monitored across numerous machine installations without increased licence administration and tracking costs.' +
  '</p>'
  ,

rules_engine_based_security:
  '<h1>Rules Engine Based Security</h1>' +
  '<p>' +
  "Enables alignment and enforcement of company data access policies across multiple facets of an enterprise's IS infrastructure. " +
  'This includes any combination of users, user roles, applications, operating systems, databases, machine aliases, and networks.' +
  '</p>'
  ,

browser_based_admin:
  '<h1>Web Browser Based Admin Assistant</h1>' +
  '<h2>Easy Administration</h2>' +
  '<p>' +
  'OpenLink provides a user friendly utility, the OpenLink Admin Assistant, for configuring your database agents and administering the Sessions Rules Book. ' +
  'This powerful HTML based GUI, usable from any Web Browser, provides two approaches to configuring database agents using wizards or forms.' +
  '</p><p><a href="http://docs.openlinksw.com/mt/agentconfig.html">More Info</a>' +
  '</p>'
  ,

broad_database_support:
  '<h1>Broad Database Support</h1>' +
  '<p>' +
  'Enables DBMS independent application utilization and deployment across a wide array of industry leading DBMS engines that includes:<ul>' +
  '<li>Virtuoso</li><li>Oracle (7.x - 11.x)</li><li>SQL Server (6.x - 2008)</li><li>DB2 (6.x - 9.x)</li><li>Sybase (10.x - 15.x)</li>' +
  '<li>Progress (7.x - 10.x)</li><li>Ingres (6.4 - 9.x)</li><li>Informix (5.x - 11.x)</li>' +
  '</ul></p>'
  ,

database_coverage:
  '<h1>Unmatched Database Coverage & Data Integration Options</h1>' +
  '<p>' +
  'All the major enterprise databases are supported including:<br/>' +
  'Oracle, Microsoft SQL Server, DB2, SYBASE ASE, Informix, PROGRESS, CA-Ingres, MySQL, PostgreSQL and <a href="http://virtuoso.openlinksw.com">OpenLink Virtuoso</a>.' +
  '</p><p>' +
  'Other databases can be supported via our ODBC and JDBC bridge technologies, or via Virtuoso, our cross platform Universal Server ' +
  'for SQL, XML, RDF Data Management that also includes a powerful Virtual Database Engine, Web Services Deployment Platform, and Web Application Server.' +
  '</p>'
  ,

advanced_functionality_exposure:
  '<h1>Advanced Database Functionality Exposure</h1>' +
  '<p>' +
  'OpenLink drivers expose many advanced proprietary database features. Adherence to industry standard data access APIs need not imply a "lowest common denominator" approach.' +
  '</p><p>' +
  'Some of the supported advanced features are shown in the adjacent feature boxes. Because of space constraints, only feature boxes for Oracle and SQL Server are included, but our ' +
  'support for advanced database functionality extends to other databases also. For instance, our Progress (SQL-89) drivers support triggers, arrays and multiple databases.' +
  '</p>'
  ,

connection_pooling:
  '<h1>Connection Pooling (Oracle)</h1>' +
  '<p>' +
  'Oracle Connection Pooling gives you the ability to retain a pool of open connections to the database within the ODBC Driver, ' +
  'thereby avoiding costly connection establishment overhead for every connection from the client. Being implemented in the ' +
  'driver means you do not have to rely on the Driver Manager implementing connection pooling for you, and have finer control over how it behaves too.' +
  '</p><p>' +
  'Cross-client connection pooling by the OpenLink database agent may be preferable to client-side connection pooling by the Driver Manager in certain ' +
  'application domains and may offer better scalability. For instance, if the agent is used by an application server or web server.' +
  '</p><p>' + '<a href="http://docs.openlinksw.com/mt/oraconcpoolgeneric.html">More Info</a></p>'
  ,

taf_support:
  '<h1>RAC/TAF Support (Oracle)</h1>' +
  '<p>' +
  'Oracle Real Application Clustering (RAC) uses Transparent Application Failover (TAF), an Oracle facility which, if a connection to a database node fails, re-establishes it against an alternative node.' +
  '</p><p>' +
  'OpenLink Drivers for Oracle 10g and above support TAF event notifications to allow applications to respond to failovers.' +
  '</p>'
  ,

instant_client_support:
  '<h1>Instant Client Support (Oracle)</h1>' +
  '<p>' +
  'Instant Client is a small footprint Oracle client which allows you to run applications without installing the standard Oracle client.' +
  '</p><p>' +
  "Oracle's Instant Client can be used in OpenLink single-tier and multi-tier environments." +
  '</p>'
  ,

reference_cursors:
  '<h1>Reference Cursors (Oracle)</h1>' +
  '<p>' +
  'OpenLink Oracle drivers include support for OCI reference cursors in stored procedures.' +
  '</p>'
  ,

mars:
  '<h1>MARS (SQL Server)</h1>' +
  '<p>' +
  'Multiple Active Result Sets (MARS) is a SQL Server features introduced in SQL Server 2005 feature that allows a user to run more than one SQL batch on an open connection at the same time.' +
  '</p>'
  ,

single_sign_on:
  '<h1>Single Sign On (SQL Server)</h1>' +
  '<p>' +
  'Microsoft SQL Server Single Sign On and the Windows NTLMv2 authentication protocol are supported from Windows Lite and Multi-Tier clients.' +
  '</p>'
  ,

instance_auto_discovery:
  '<h1>Instance Auto Discovery (SQL Server)</h1>' +
  '<p>' +
  "OpenLink's SQL Server driver's configuration screens include a dynamic discovery feature to auto-discover SQL Server instances, simplifying configuration and administration of database connections." +
  '</p>'
  ,

database_mirroring:
  '<h1>Database Mirroring (SQL Server)</h1>' +
  '<p>' +
  'OpenLink SQL Server drivers are compatible with SQL Server database mirroring, allowing you to identify a failover server hosting a mirrored database as part of the driver configuration.' +
  '</p>'
  };

  //<!-- End: Feature descriptions -->

  function display_description(id)
  {
    var fdt = document.getElementById('feature_desc_text');
    fdt.innerHTML = feature_descs[id];
    $('h_slidein').fireEvent('click');
  }