HTML Microdata document

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

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

Namespace Prefixes

Prefix	IRI
n17	https://www.openlinksw.com/about/id/entity/urn/howto:
n23	http://data.openlinksw.com/oplweb/uda/howto/WindowsLiteJDBCDataSourceNameConfigurationGuideStep5#
n4	http://data.openlinksw.com/oplweb/
n30	http://data.openlinksw.com/oplweb/uda/howto/WindowsLiteJDBCDataSourceNameConfigurationGuideStep7#
n19	http://www.openlinksw.com/about/id/entity/urn/data:opl:web:seo:mdata:
n25	http://data.openlinksw.com/oplweb/uda/howto/WindowsLiteJDBCDataSourceNameConfigurationGuideStep2#
n7	http://data.openlinksw.com/oplweb/uda/howto/WindowsSampleAppUsageC++DemoUsageGuide#
wdrs	http://www.w3.org/2007/05/powder-s#
n14	https://www.openlinksw.com/about/id/entity/urn/mdata:websites:google:uda:howto:
oplsoft	http://www.openlinksw.com/ontology/software#
n28	http://data.openlinksw.com/oplweb/uda/howto/WindowsLiteJDBCDataSourceNameConfigurationGuideStep9#
schema	http://schema.org/
n13	https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/DAV/data/turtle/general/
n24	http://wikis.openlinksw.com/UdaWikiWeb/
n10	https://www.openlinksw.com/about/id/entity/urn/data:openlink:
n21	http://data.openlinksw.com/oplweb/uda/howto/WindowsLiteJDBCDataSourceNameConfigurationGuideStep4#
n12	https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/data/turtle/general/
n15	http://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/data/turtle/general/
n16	http://data.openlinksw.com/oplweb/product_format/st#
n20	https://www.openlinksw.com/about/id/entity/urn/mdata:websites:google:
n29	http://data.openlinksw.com/oplweb/uda/howto/WindowsLiteJDBCDataSourceNameConfigurationGuideStep6#
n5	http://data.openlinksw.com/oplweb/opsys_family/Windows#
rdf	http://www.w3.org/1999/02/22-rdf-syntax-ns#
n11	http://data.openlinksw.com/oplweb/uda/howto/WindowsLiteJDBCDataSourceNameConfigurationGuideStep1#
n9	https://www.openlinksw.com/about/id/entity/urn/data:opl:web:seo:mdata:
n27	http://data.openlinksw.com/oplweb/uda/howto/WindowsLiteJDBCDataSourceNameConfigurationGuideStep8#
n2	http://data.openlinksw.com/oplweb/uda/howto/WindowsLiteJDBCDataSourceNameConfigurationGuide#
n26	http://data.openlinksw.com/oplweb/uda/howto/WindowsLiteJDBCDataSourceNameConfigurationGuideStep3#
xsdh	http://www.w3.org/2001/XMLSchema#
n18	http://data.openlinksw.com/oplweb/uda/howto/WindowsLiteJDBCDataSourceNameConfigurationGuideStep10#
n22	https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/DAV/uda2.openlinksw.com/data/turtle/general/

Statements

Subject Item: n2:this
schema:description: Configuration of ODBC Data Source Names associated with the Lite Edition (Single-Tier) ODBC-to-JDBC Bridge for Windows Configuration of ODBC Data Source Names associated with the Lite Edition (Single-Tier) ODBC Driver for JDBC Data Sources (ODBC-to-JDBC Bridge) for Windows
wdrs:describedby: n9:webs n10:products n12:uda-howtos-qa.ttl n13:uda-howtos.ttl n12:uda-howtos.ttl n10:websites n14:seo n15:uda-howtos-seo.ttl n17:island n19:offers n20:seo n22:UDAHowAndStepByGuides.ttl
schema:name: Configuration of ODBC Data Source Names associated with the Lite Edition (Single-Tier) ODBC-to-JDBC Bridge for Windows Configuration of ODBC Data Source Names associated with the Lite Edition (Single-Tier) ODBC Driver for JDBC Data Sources (ODBC-to-JDBC Bridge) for Windows
oplsoft:hasDatabaseFamily: n4:JDBC oplsoft:JDBCBridge
oplsoft:hasOperatingSystemFamily: n5:this
schema:category: Data Source Name Configuration Guide
schema:relatedLink: n7:this n24:InstallODBCJDBCLiteWin32
schema:genre: n16:this
schema:text: <ol> <li>Determine that you have a working JDBC connection to your target database.</li> <li>Also determine the bitness (32-bit or 64-bit) of the driver used as this MUST match the Java Virtual Machine and ODBC-JDBC Bridge Driver bitness.</li> <li>Launch the ODBC Data Sources Application and click the System DSN tab.</li> <li>Click the Add button.</li> <li>Select the OpenLink "Lite" Driver for JDBC Data Sources from the list of available drivers.</li> <li>Select the Unicode version of the driver if and only if you are working with multi-byte character sets, as unnecessary translations can significantly affect ODBC performance.</li> <li>Click Finish.</li> <li>The first dialog prompts for a Data Source Name and optional description. Click Next.</li> <li>The second dialog prompts for a third-party JDBC driver name, JDBC connection URL, and authentication parameters associated with that JDBC URL. <ul> <li>JDBC driver: This is the class name of the target JDBC driver.</li> <li>URL string: This is the JDBC connection URL for the target JDBC driver.</li> <li>Connect now to verify that all settings are correct: Will attempt to connect to the database, once you click Continue.</li> <li>Login ID: This is a valid username for your JDBC database.</li> <li>Password: This is a valid password for your JDBC database.</li> </ul> </li> <li>Click Next to continue.</li> <li>The third dialog takes a combination of database-specific and optional parameters. <ul> <li>Drop Catalog name from DatabaseMetaData calls: Enable this option to have the catalog name not appear for tables, views, and procedures when requesting database meta-data.</li> <li>Drop Schema name from DatabaseMetaData calls: Enable this option to have the schema name not appear for tables, views, and procedures when requesting database meta-data.</li> <li>Return an empty ResultSet for SQLStatistics: Check this box to have SQLStatistics() return an empty resultset. Use this if the underlying database does not support retrieval of statistics about a table (e.g., what indexes it has).</li> <li>Disable support of quoted identifier: If set, the call SQLGetInfo(SQL_IDENTIFIER_QUOTE_CHAR) will return a space (""). It can be used if the DBMS doesn't support quoted SQL like SELECT * FROM "account".</li> <li>Disable support of search pattern escape: If set, the call SQLGetInfo(SQL_LIKE_ESCAPE_CLAUSE) will return a space (""). It can be used if the DBMS doesn't support SQL escape patterns.</li> <li>Enable logging of JDBC calls to the log file: Check this option to enable logging of JDBC calls to a log file.</li> </ul> </li> <li>Click Next to continue.</li> <li>The fourth dialog enables you to set optional ODBC connection parameters. <ul> <li>Read-only connection: Specifies whether the connection is "Read-only." Must be unchecked to INSERT, UPDATE, or DELETE records and to run some Stored Procedures, including some built-in functions.</li> <li>Defer fetching of long data: Defers fetching of LONG (BINARY, BLOB, etc.) fields in wildcard queries. This provides significant performance increases when fields in the query do not include LONG data fields.</li> <li>Disable interactive login: Suppresses the ODBC "Username" and "Password" login dialog boxes when interacting with your ODBC DSN from within an ODBC-compliant application.</li> <li>Row Buffer Size: This attribute specifies the number of records to be delivered from the driver to the client application in a single batch. Values can range from 1 to 999.</li> <li>Max Rows Override: Allows you to set a limit for the maximum number of rows to be returned from a query. The default value of 0 means no limit.</li> <li>Initial SQL: Lets you specify a file containing SQL statements that will be run automatically against the database upon connection.</li> <li>Dynamic Cursor Sensitivity: Enables or disables the row version cache used with dynamic cursors.</li> <li>Enable logging to the log file: Check the checkbox and use the associated textbox to provide the full path to a file in which to log diagnostic information.</li> </ul> </li> <li>Click Next to continue.</li> <li>The fifth dialog enables you to set additional parameters to enhance compatibility with applications. <ul> <li>Enable Microsoft Jet engine options: Facilitates translation of certain data types for the Microsoft Jet Engine. If you notice that money and other datatypes are mishandled with Microsoft or other applications, test with Jet fix enabled.</li> <li>Disable Autocommit: Changes the commit behavior of the OpenLink driver. The default mode is AutoCommit (box unchecked).</li> <li>Disable rowset size limit: Disables a limitation enforced by the cursor library. This limitation is enforced by default. It prevents the driver from claiming all available memory when a resultset (typically generated by an accidental query) is very large. The limit is not normally reached.</li> <li>Multiple Active Statements Emulation: Enables the use of Multiple Active statements in an ODBC application even if the underlying database does not allow this by emulation within the driver.</li> <li>SQL_DBMS Name: Manually overrides the SQLGetInfo(SQL_DBMS_NAME) response returned by the driver. This is required for products like Microsoft InfoPath for which the value should be "SQL Server".</li> </ul> </li> <li>Click Next to continue.</li> <li>The final dialog enables you to test your Data Source. Click the Test Data Source button.</li> </ol> <ol> <li>Determine that you have a working JDBC connection to your target database.</li> <li>Also determine the bitness (32-bit or 64-bit) of the driver used as this MUST match the Java Virtual Machine and ODBC-JDBC Bridge Driver bitness.</li> <li>Launch the ODBC Data Sources Application and click the System DSN tab.</li> <li>Click the Add button.</li> <li>Select the OpenLink "Lite" Driver for JDBC Data Sources from the list of available drivers.</li> <li>Select the Unicode version of the driver if and only if you are working with multi-byte character sets, as unnecessary translations can significantly affect ODBC performance.</li> <li>Click Finish.</li> <li>The first dialog prompts for a Data Source Name and optional description. Click Next.</li> <li>The second dialog prompts for a third-party JDBC driver name, JDBC connection URL, and authentication parameters associated with that JDBC URL. <ul> <li>JDBC driver: This is the class name of the target JDBC driver.</li> <li>URL string: This is the JDBC connection URL for the target JDBC driver.</li> <li>Connect now to verify that all settings are correct: Will attempt to connect to the database, once you click Continue.</li> <li>Login ID: This is a valid username for your JDBC database.</li> <li>Password: This is a valid password for your JDBC database.</li> </ul> </li> <li>Click Next to continue.</li> <li>The third dialog takes a combination of database-specific and optional parameters. <ul> <li>Drop Catalog name from DatabaseMetaData calls: Enable this option to have the catalog name not appear for tables, views, and procedures when requesting database meta-data.</li> <li>Drop Schema name from DatabaseMetaData calls: Enable this option to have the schema name not appear for tables, views, and procedures when requesting database meta-data.</li> <li>Return an empty ResultSet for SQLStatistics: Check this box to have SQLStatistics() return an empty resultset. Use this if the underlying database does not support retrieval of statistics about a table (e.g., what indexes it has).</li> <li>Disable support of quoted identifier: If set, the call SQLGetInfo(SQL_IDENTIFIER_QUOTE_CHAR) will return a space (""). It can be used if the DBMS doesn't support quoted SQL like SELECT * FROM "account".</li> <li>Disable support of search pattern escape: If set, the call SQLGetInfo(SQL_LIKE_ESCAPE_CLAUSE) will return a space (""). It can be used if the DBMS doesn't support SQL escape patterns.</li> <li>Enable logging of JDBC calls to the log file: Check this option to enable logging of JDBC calls to a log file.</li> </ul> </li> <li>Click Next to continue.</li> <li>The fourth dialog enables you to set optional ODBC connection parameters. <ul> <li>Read-only connection: Specifies whether the connection is "Read-only." Must be unchecked to INSERT, UPDATE, or DELETE records and to run some Stored Procedures, including some built-in functions.</li> <li>Defer fetching of long data: Defers fetching of LONG (BINARY, BLOB, etc.) fields in wildcard queries. This provides significant performance increases when fields in the query do not include LONG data fields.</li> <li>Disable interactive login: Suppresses the ODBC "Username" and "Password" login dialog boxes when interacting with your ODBC DSN from within an ODBC-compliant application.</li> <li>Row Buffer Size: This attribute specifies the number of records to be delivered from the driver to the client application in a single batch. Values can range from 1 to 999.</li> <li>Max Rows Override: Allows you to set a limit for the maximum number of rows to be returned from a query. The default value of 0 means no limit.</li> <li>Initial SQL: Lets you specify a file containing SQL statements that will be run automatically against the database upon connection.</li> <li>Dynamic Cursor Sensitivity: Enables or disables the row version cache used with dynamic cursors.</li> <li>Enable logging to the log file: Check the checkbox and use the associated textbox to provide the full path to a file in which to log diagnostic information.</li> </ul> </li> <li>Click Next to continue.</li> <li>The fifth dialog enables you to set additional parameters to enhance compatibility with applications. <ul> <li>Enable Microsoft Jet engine options: Facilitates translation of certain data types for the Microsoft Jet Engine. If you notice that money and other datatypes are mishandled with Microsoft or other applications, test with Jet fix enabled.</li> <li>Disable Autocommit: Changes the commit behavior of the OpenLink driver. The default mode is AutoCommit (box unchecked).</li> <li>Disable rowset size limit: Disables a limitation enforced by the cursor library. This limitation is enforced by default. It prevents the driver from claiming all available memory when a resultset (typically generated by an accidental query) is very large. The limit is not normally reached.</li> <li>Multiple Active Statements Emulation: Enables the use of Multiple Active statements in an ODBC application even if the underlying database does not allow this by emulation within the driver.</li> <li>SQL_DBMS Name: Manually overrides the SQLGetInfo(SQL_DBMS_NAME) response returned by the driver. This is required for products like Microsoft InfoPath for which the value should be "SQL Server".</li> </ul> </li> <li>Click Next to continue.</li> <li>The final dialog enables you to test your Data Source. Click the Test Data Source button.</li> </ol>
rdf:type: schema:HowTo
schema:step: n11:this n18:this n21:this n23:this n25:this n26:this n27:this n28:this n29:this n30:this