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

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

Namespace Prefixes

PrefixIRI
n12https://www.openlinksw.com/about/id/entity/urn/howto:
n19http://data.openlinksw.com/oplweb/uda/howto/WindowsMulti-TierGenericODBCClientConfigurationGuideStep3#
n8http://data.openlinksw.com/oplweb/uda/howto/WindowsMulti-TierGenericODBCClientConfigurationGuideStep8#
n2http://data.openlinksw.com/oplweb/uda/howto/WindowsMulti-TierGenericODBCClientConfigurationGuide#
n20http://data.openlinksw.com/oplweb/uda/howto/WindowsSampleAppUsageC++DemoUsageGuide#
n15https://www.openlinksw.com/about/id/entity/urn/mdata:websites:google:uda:howto:
oplsofthttp://www.openlinksw.com/ontology/software#
wdrshttp://www.w3.org/2007/05/powder-s#
n4http://data.openlinksw.com/oplweb/uda/howto/WindowsMulti-TierGenericODBCClientConfigurationGuideStep5#
schemahttp://schema.org/
n11http://wikis.openlinksw.com/UdaWikiWeb/
n10https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/DAV/data/turtle/general/
n18http://data.openlinksw.com/oplweb/uda/howto/WindowsMulti-TierGenericODBCClientConfigurationGuideStep2#
n7https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/data/turtle/general/
n14http://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/data/turtle/general/
n17http://data.openlinksw.com/oplweb/opsys_family/Windows#
n23http://data.openlinksw.com/oplweb/uda/howto/WindowsMulti-TierGenericODBCClientConfigurationGuideStep7#
n13https://www.openlinksw.com/about/id/entity/urn/mdata:websites:google:
n24http://data.openlinksw.com/oplweb/uda/howto/WindowsMulti-TierGenericODBCClientConfigurationGuideStep4#
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n21http://data.openlinksw.com/oplweb/uda/howto/WindowsMulti-TierGenericODBCClientConfigurationGuideStep1#
n5http://data.openlinksw.com/oplweb/uda/howto/WindowsMulti-TierGenericODBCClientConfigurationGuideStep10#
xsdhhttp://www.w3.org/2001/XMLSchema#
n9http://data.openlinksw.com/oplweb/uda/howto/WindowsMulti-TierGenericODBCClientConfigurationGuideStep9#
n22http://data.openlinksw.com/oplweb/uda/howto/WindowsMulti-TierGenericODBCClientConfigurationGuideStep6#

Statements

Subject Item
n2:this
schema:description
Configuration of the Enterprise Edition (Multi-Tier) Generic Client ODBC Drivers, on Windows
wdrs:describedby
n7:uda-howtos.ttl n10:uda-howtos.ttl n12:island n7:uda-howtos-qa.ttl n13:seo n14:uda-howtos-seo.ttl n15:seo
schema:name
Configuration of the Enterprise Edition (Multi-Tier) Generic Client ODBC Drivers, on Windows
oplsoft:hasOperatingSystemFamily
n17:this
schema:category
Configuration Guide
schema:relatedLink
n11:InstallClientWIN32 n20:this
schema:text
<ol> <li>Launch the ODBC Administrator appropriate to the bitness (32-bit or 64-bit) of your client application and driver.</li> <li>Click the <strong>Add</strong> button that appears on the <strong>System DSN</strong> tab.</li> <li>Select the <strong>OpenLink Generic ODBC Driver</strong> from the list of available drivers.</li> <li>The first DSN configuration dialog takes these values: <ul> <li><strong>Name:</strong> A suitable name for your Data Source</li> <li><strong>Description:</strong> An optional description for your Data Source</li> <li><strong>Server:</strong> The host name or IP address of the machine containing your OpenLink Request Broker and the Broker's listen port. A colon separates the two. For example: <code>192.158.12.234:5000</code></li> </ul> </li> <li>Click <strong>Next</strong>.</li> <li>The second DSN configuration dialog takes these values: <ul> <li><strong>Domain:</strong> The value must match a <strong>[Domain Alias]</strong>, which is contained in the Server's Session Rules Book. This Alias typically represents the name and version of an OpenLink Agent. That agent version may differ from the DBMS version to which it connects. Note that advanced users may create custom domain names that follow their own desired conventions.</li> <li><strong>Database:</strong> Takes a database name or Oracle SID.</li> <li><strong>Options:</strong> This field passes parameters that enable users to connect to MySQL, PostgreSQL, SQLServer, and Sybase databases anywhere on the network. It also passes parameters that enable users to connect to any DBMS that does not reside on the same machine as the OpenLink Request Broker and Agent. <a href="http://wikis.openlinksw.com/UdaWikiWeb/MTServerConfigConnectOptions">Review Complete Settings and Usage for Connect Options</a>.</li> <li><strong>Secure Connection:</strong> If checked, the client sets up a secure connection to the Request Broker.</li> <li><strong>Connect now to verify that all settings are correct:</strong> Will attempt to connect to the database once you click Continue.</li> <li><strong>Login ID:</strong> A valid database UID.</li> <li><strong>Password:</strong> A valid database password.</li> <li><strong>XA Info:</strong> Refer to OpenLink's extensive Distributed Transaction Processing documentation for use of this field.</li> </ul> </li> <li>Click <strong>Next</strong>.</li> <li>The third tab contains settings that are not required for a basic connection: <ul> <li><strong>Read Only connection:</strong> Specifies whether the connection is "Read-only." Make sure the checkbox is unchecked to request a "Read/Write" connection.</li> <li><strong>Defer fetching of long data:</strong> Defers fetching of LONG (BINARY, BLOB, etc.) data unless explicitly requested in a query. This provides significant performance increases when fields in the query do not include LONG data fields.</li> <li><strong>Disable interactive login:</strong> Suppresses the ODBC "Username" and "Password" login dialog boxes when interacting with your ODBC DSN from within an ODBC-compliant application.</li> <li><strong>Multiple Active Statements Emulation:</strong> Enables the use of Multiple Active statements in an ODBC application even if the underlying database does not allow this, as it is emulated in the driver.</li> <li><strong>Row Buffer Size:</strong> Specifies the number of records to be transported over the network in a single network hop. Values can range from 1 to 99.</li> <li><strong>SQL_DBMS_NAME:</strong> Manually overrides the SQLGetInfo(SQL_DBMS_NAME) response returned by the driver. This is required for products like Microsoft InfoPath (for which the return value should be "SQL Server").</li> </ul> </li> <li>Click <strong>Next</strong>.</li> <li>Click on the 'Test Data Source' button to make a connection to the database to verify connectivity. A successful connection to the database has been made.</li> </ol> <ol> <li>Launch the ODBC Administrator appropriate to the bitness (32-bit or 64-bit) of your client application and driver.</li> <li>Click the <strong>Add</strong> button that appears on the <strong>System DSN</strong> tab.</li> <li>Select the <strong>OpenLink Generic ODBC Driver</strong> from the list of available drivers.</li> <li>The first DSN configuration dialog takes these values: <ul> <li><strong>Name:</strong> A suitable name for your Data Source</li> <li><strong>Description:</strong> An optional description for your Data Source</li> <li><strong>Server:</strong> The host name or IP address of the machine containing your OpenLink Request Broker and the Broker's listen port. A colon separates the two. For example: <code>192.158.12.234:5000</code></li> </ul> </li> <li>Click <strong>Next</strong>.</li> <li>The second DSN configuration dialog takes these values: <ul> <li><strong>Domain:</strong> The value must match a <strong>[Domain Alias]</strong>, which is contained in the Server's Session Rules Book. This Alias typically represents the name and version of an OpenLink Agent. That agent version may differ from the DBMS version to which it connects. Note that advanced users may create custom domain names that follow their own desired conventions.</li> <li><strong>Database:</strong> Takes a database name or Oracle SID.</li> <li><strong>Options:</strong> This field passes parameters that enable users to connect to MySQL, PostgreSQL, SQLServer, and Sybase databases anywhere on the network. It also passes parameters that enable users to connect to any DBMS that does not reside on the same machine as the OpenLink Request Broker and Agent. <a href="http://wikis.openlinksw.com/UdaWikiWeb/MTServerConfigConnectOptions">Review Complete Settings and Usage for Connect Options</a>.</li> <li><strong>Secure Connection:</strong> If checked, the client sets up a secure connection to the Request Broker.</li> <li><strong>Connect now to verify that all settings are correct:</strong> Will attempt to connect to the database once you click Continue.</li> <li><strong>Login ID:</strong> A valid database UID.</li> <li><strong>Password:</strong> A valid database password.</li> <li><strong>XA Info:</strong> Refer to OpenLink's extensive Distributed Transaction Processing documentation for use of this field.</li> </ul> </li> <li>Click <strong>Next</strong>.</li> <li>The third tab contains settings that are not required for a basic connection: <ul> <li><strong>Read Only connection:</strong> Specifies whether the connection is "Read-only." Make sure the checkbox is unchecked to request a "Read/Write" connection.</li> <li><strong>Defer fetching of long data:</strong> Defers fetching of LONG (BINARY, BLOB, etc.) data unless explicitly requested in a query. This provides significant performance increases when fields in the query do not include LONG data fields.</li> <li><strong>Disable interactive login:</strong> Suppresses the ODBC "Username" and "Password" login dialog boxes when interacting with your ODBC DSN from within an ODBC-compliant application.</li> <li><strong>Multiple Active Statements Emulation:</strong> Enables the use of Multiple Active statements in an ODBC application even if the underlying database does not allow this, as it is emulated in the driver.</li> <li><strong>Row Buffer Size:</strong> Specifies the number of records to be transported over the network in a single network hop. Values can range from 1 to 99.</li> <li><strong>SQL_DBMS_NAME:</strong> Manually overrides the SQLGetInfo(SQL_DBMS_NAME) response returned by the driver. This is required for products like Microsoft InfoPath (for which the return value should be "SQL Server").</li> </ul> </li> <li>Click <strong>Next</strong>.</li> <li>Click on the 'Test Data Source' button to make a connection to the database to verify connectivity. A successful connection to the database has been made.</li> </ol> <ol> <li>Launch the ODBC Administrator appropriate to the bitness (32-bit or 64-bit) of your client application and driver.</li> <li>Click the <strong>Add</strong> button that appears on the <strong>System DSN</strong> tab.</li> <li>Select the <strong>OpenLink Generic ODBC Driver</strong> from the list of available drivers.</li> <li>The first DSN configuration dialog takes these values: <ul> <li><strong>Name:</strong> A suitable name for your Data Source</li> <li><strong>Description:</strong> An optional description for your Data Source</li> <li><strong>Server:</strong> The host name or IP address of the machine containing your OpenLink Request Broker and the Broker's listen port. A colon separates the two. For example: <code>192.158.12.234:5000</code></li> </ul> </li> <li>Click <strong>Next</strong>.</li> <li>The second DSN configuration dialog takes these values: <ul> <li><strong>Domain:</strong> The value must match a <strong>[Domain Alias]</strong>, which is contained in the Server's Session Rules Book. This Alias typically represents the name and version of an OpenLink Agent. That agent version may differ from the DBMS version to which it connects. Note that advanced users may create custom domain names that follow their own desired conventions.</li> <li><strong>Database:</strong> Takes a database name or Oracle SID.</li> <li><strong>Options:</strong> This field passes parameters that enable users to connect to MySQL, PostgreSQL, SQLServer, and Sybase databases anywhere on the network. It also passes parameters that enable users to connect to any DBMS that does not reside on the same machine as the OpenLink Request Broker and Agent. Review Complete Settings and Usage for Connect Options.</li> <li><strong>Secure Connection:</strong> If checked, the client sets up a secure connection to the Request Broker.</li> <li><strong>Connect now to verify that all settings are correct:</strong> Will attempt to connect to the database once you click Continue.</li> <li><strong>Login ID:</strong> A valid database UID.</li> <li><strong>Password:</strong> A valid database password.</li> <li><strong>XA Info:</strong> Refer to OpenLink's extensive Distributed Transaction Processing documentation for use of this field.</li> </ul> </li> <li>Click <strong>Next</strong>.</li> <li>The third tab contains settings that are not required for a basic connection: <ul> <li><strong>Read Only connection:</strong> Specifies whether the connection is "Read-only." Make sure the checkbox is unchecked to request a "Read/Write" connection.</li> <li><strong>Defer fetching of long data:</strong> Defers fetching of LONG (BINARY, BLOB, etc.) data unless explicitly requested in a query. This provides significant performance increases when fields in the query do not include LONG data fields.</li> <li><strong>Disable interactive login:</strong> Suppresses the ODBC "Username" and "Password" login dialog boxes when interacting with your ODBC DSN from within an ODBC-compliant application.</li> <li><strong>Multiple Active Statements Emulation:</strong> Enables the use of Multiple Active statements in an ODBC application even if the underlying database does not allow this, as it is emulated in the driver.</li> <li><strong>Row Buffer Size:</strong> Specifies the number of records to be transported over the network in a single network hop. Values can range from 1 to 99.</li> <li><strong>SQL_DBMS_NAME:</strong> Manually overrides the SQLGetInfo(SQL_DBMS_NAME) response returned by the driver. This is required for products like Microsoft InfoPath (for which the return value should be "SQL Server").</li> </ul> </li> <li>Click <strong>Next</strong>.</li> <li>Click on the 'Test Data Source' button to make a connection to the database to verify connectivity. A successful connection to the database has been made.</li> </ol>
rdf:type
schema:HowTo
schema:step
n4:this n5:this n8:this n9:this n18:this n19:this n21:this n22:this n23:this n24:this