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/
n5https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/DAV/data/turtle/general/
n2http://data.openlinksw.com/oplweb/faq/UDA/WhatDoUsersNeedToDoToConfigureTheirMulti-TierDriversAnswer#
n4https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/data/turtle/general/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
xsdhhttp://www.w3.org/2001/XMLSchema#

Statements

Subject Item
n2:this
wdrs:describedby
n4:uda-faq.ttl n5:uda-faq.ttl
rdf:type
schema:Answer
schema:answerExplanation
Unix users need to insure that openlink.sh (Bourne/Bash) or openlink.csh (C) is executed in the appropriate shell. These shell scripts set environment variables that pertain to ODBC. They appear in both client and server components installations. Unix users need to run set or env to insure that the environment variables (ODBCINI, ODBCINSTINI, etc.) are actually set. All users need to insure that the appropriate [Environment] section of the ~/openlink/bin/oplrqb.ini file contains the correct environment variables. All users should uncomment and set the PortHigh parameter that appears in the [Protocol TCP] section of the ~/openlink/bin/oplrqb.ini file. PortHigh should equal PortLow + the number of concurrent connections alloted by the license + a few extra ports. All users need to start the Request Broker. The Request Broker is the oplrqb executable that appears in the /bin sub-directory of Multi-Tier server components installation.