This HTML5 document contains 4 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
wdrshttp://www.w3.org/2007/05/powder-s#
schemahttp://schema.org/
n4https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/DAV/data/turtle/general/
n6https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/data/turtle/general/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n2http://data.openlinksw.com/oplweb/faq/UDA/WhatIsZeroConfigAnswer#
xsdhhttp://www.w3.org/2001/XMLSchema#

Statements

Subject Item
n2:this
wdrs:describedby
n4:uda-faq.ttl n6:uda-faq.ttl
rdf:type
schema:Answer
schema:answerExplanation
OpenLink's ZeroConfig functionality allows the OpenLink administrator to define sets of database connection parameters using the Administrative Assistant. For instance, the OpenLink Administrator may hard-code the Request Broker host and port, database name, database username, and database password in a ZeroConfig Data Source. Existing ZeroConfig Data Sources are broadcast over the corporate network. End users may create Data Source Names from scratch. Alternatively, users may select a convenient ZeroConfig Data Source Name. Use of ZeroConfig Data Sources allow novice or non-privileged users to connect to the database using an immediate and reliable set of connection parameters.