Informix Jdbc Driver Windows
Corporate Info News Solutions Products Partners Services Events Download How To Buy | |
e-docsSite MapSearchContactGlossaryWebLogic Server Documentation | |
Installing and Setting Up WebLogic Server 4.5:Previous Topic Next Topic Contents | |
Installing JDBC Drivers
IBM INFORMIX JDBC DRIVERS FOR WINDOWS XP - Web Experience Management Sitefinity Build engaging multi-channel web and digital experiences with intuitive web content management Sitefinity Digital Skip to content. DbVisualizer is tested with the major databases and JDBC drivers. For databases more commonly used in the industry we have added support for database specific features. Runs on Windows, Linux, and macOS. Nothing needs to be installed on the UCCX for setting up ODBC connection. The drivers will only be installed on the server that is hosting the wallboard. Only in case of JDBC, the drivers need to be installed on the UCCX. JDBC/ODBC connection to Informix with Openoffice BASE on Windows 7. Will not show table lists. I don't understand how that would effect the JDBC so greatly. I can however execute SQL queries without a problem. I can't use design views. In the end, all I'm trying to do is have a useful GUI that I can build and debug queries with. If OpenOffice.org is a poor choice, I'm still open to other options. But the opensource prospects are ideal.
Three type-2 jdbcKona drivers are included with WebLogic Server: jdbcKona/Oracle, jdbcKona/Sybase, and jdbcKona/MSSQLServer. For these drivers to function, you must have the appropriate vendor-supplied client libraries installed on your machine.
Before attempting to use one of the JDBC drivers, you should verify that you are able to connect to a database using client software (such as Oracle's SQL*Plus, or Sybase's SQL Advantage).
The WebLogic Server distribution includes WebLogic-supplied native libraries for each DBMS. Installing a WebLogic jdbcKona JDBC driver requires that these native libraries be available to WebLogic Server by including them in your system's PATH (Windows NT) or shared library path (UNIX), as described below.
The Informix drivers are used by off box tools that connect to Unity Connection 2.1(1) or later systems via the database proxy service. The help files for each tool that uses the remote database proxy service to attach to Connection has instructions for how to configure the remote ODBC access from off box.
Check the Release Notes included with your package or the WebLogic Platform Support page in the online documentation for details about which platforms, operating systems, DBMS versions, and Java versions are supported for the various WebLogic jdbcKona drivers.
Apr 01, 2015 Featured Games. Replay Rush Replay some of Phineas, Ferb, and Agent P's greatest adventures in these series of microgames! Phineas and Ferb - Drusselstein Driving Test. Animated adventures of two stepbrothers who build inventions while their pet platypus, Perry. Perry the platypus games disney. Perry the Platypus games are mainly inspired by Perry, the cute pet of the Fletcher family, featured in Phineas and Ferb animated television series. He acts as a secret agent of Organization Without a Cool Acronym (O.W.C.A), which is an espionage and spy enterprise comprising of animals.
For information on using the jdbcKona/Oracle see Using jdbcKona/Oracle.
Installing type-2 jdbcKona/Sybase and jdbcKona/MSSQLServer drivers
The jdbcKona/Sybase and jdbcKona/MSSQLServer type 2 JDBC drivers are deprecated. Deprecated features remain for backwards compatibility only but are slated for removal from the WebLogic Server in the near future. They exist only for WebLogic Server deployments that have not yet migrated to other solutions.
Specifically, these drivers have not been and will not be updated to match the latest DMBS features or platform developments nor have they been updated to run under a JDK 1.2 environment. While these drivers may work in many customer situations, some customers have had problems. If you need to install or use these drivers in an existing application, please see the installation guides in the online documentation:
- Installing jdbcKona/Sybase
- Installing jdbcKona/MSSQLServer
If you wish to acquire a driver to connect to a Sybase installation, you should install the jConnect driver available from Sybase. It is free and available at:
- http://www.sybase.com/products/internet/jconnect/
If you wish to acquire a driver to connect to Microsoft SQLServer, you should use the jdbcKona/MSSQLServer type 4 JDBC driver available from BEA. For more information, see: BEA WebLogic JDBC Drivers.
BEA also has a type 4 driver available for the Informix DBMS. For more information, see BEA WebLogic JDBC Drivers.
Installing jdbcKona/Oracle
Client libraries
The client libraries required for jdbcKona/Oracle vary depending on your platform, operating system, and the version of the JDK you are using. For details on your configuration, see the WebLogic platform support page.
The minimum supported client library is Oracle version 7.3.4
Windows NT
- Add weblogicbin to your PATH, for example:
Where c:weblogic is the home directory of your WebLogic Server installation.
- If you are using Symantec Cafe or other IDEs or debuggers:
- Copy the WebLogic-supplied native library to the cafebin directory, or the appropriate directory for your IDE or debugger.
- Copy the WebLogic-supplied native library to a new file name which ends in _g (before the .). For example, copy libweblogicoci34.so to libweblogicoci34_g.so.
Solaris
For Sun Solaris, BEA provides three versions of the WebLogic native layer for Oracle. Depending on the version of your Oracle client, add one of the following directories to your LD_LIBRARY_PATH:
- weblogic/lib/solaris/libweblogicoci34.so is statically linked with the Oracle 7.3.4 libraries. Use this version if you have the Oracle 7.3.4 client installed.
- weblogic/lib/solaris8/libweblogicoci34.so is statically linked with the Oracle 8.0.5 client libraries. Use this version if you have the Oracle 8.0.5 client installed.
- weblogic/lib/solaris7shr/libweblogicoci34.so is dynamically linked with the Oracle 7.3.4 libraries. You should only use this version if you are using an Oracle extension such as ANO, which is not included in the 7.3.4 client library.
Where weblogic is the home directory of your WebLogic installation.
IBM AIX
Add the directory weblogic/lib/aix to your LIBPATH.
Where weblogic is the home directory of your WebLogic installation.
HP-UX 11
Add the directory weblogic/lib/hpux11 to your SHLIB_PATH.
Where weblogic is the home directory of your WebLogic installation.
SGI Irix
- Irix users must run Java in N32 mode.
- You must have the Oracle 8.0.5 N32 client installed on your computer.
Add the directory weblogic/lib/irixsh to your LD_LIBRARYN32_PATH.
Where weblogic is the home directory of your WebLogic installation.
Notes for Microsoft SDK for Java users
If you are using Microsoft SDK for Java with jdbcKona/Oracle, you will need to install a different .dll for the jdbcKona/Oracle driver and use SDK version 3.1 or greater. You will also need to install a separate .dll to work with your debugger:
- Add the distribution directory weblogicbin to your PATH. (Where weblogic is the home directory of your WebLogic installation), or copy weblogicmsoci34.dll into c:winnt or c:windows.
- If you are using Symantec Cafe or other debuggers, also copy weblogicmsoci34.dll into cafebin and into c:winnt or c:windows or into the appropriate directory for your IDE.
Checking connections to the Oracle database
Once you have installed your jdbcKona driver you should check that you can use it to connect to your database. A utility called dbping is included with WebLogic Server that you can use to test this connection.
To use this helper application, type the following at the command line (on one line):
Where c:weblogic is the directory containing your WebLogic Server installation and c:java is the path to your JDK.
Note: If you are using Java 2 (JDK 1.2), omit 'c:javalibclasses.zip' from the above command.
For more detailed instructions on how to verify your connection to a DBMS, see Testing connections.
If you have problems, check Troubleshooting problems with shared libraries on UNIX.
Using IDEs or debuggers with jdbcKona drivers
If you are using Symantec Cafe, other IDEs, or debuggers, copy the WebLogic-supplied native library to a new file with a name that ends in _g (before the dot).
For example, copy libweblogicoci34.so to libweblogicoci34_g.so.
Next step
See Setting your development environment for information on setting up a development environment for running JDBC clients.
Copyright © 2000 BEA Systems, Inc. All rights reserved. |
This script outputs the google search URL required for search on edocs documentation.
WebLogic Type 4 JDBC Drivers
Note: The BEA WebLogic Type 4 JDBC Informix driver is available in the WebLogic Server 8.1 Service Pack 2 and later releases. It is not available with the WebLogic Server 8.1 GA and Service Pack 1 releases.
The following sections describe how to configure and use the BEA WebLogic Type 4 JDBC Informix driver:
The BEA WebLogic Type 4 JDBC Informix driver (the 'Informix driver') supports Informix Dynamic Server 9.4 and higher.
The driver classes for the BEA WebLogic Type 4 JDBC Informix driver are:
Use these driver classes when configuring a JDBC connection pool in your WebLogic Server domain.
To connect to an Informix database, use the following URL format:
Table 3-1 lists the JDBC connection properties supported by the Informix driver, and describes each property. You can use these connection properties in a JDBC connection pool configuration in your WebLogic Server domain. To specify a property, use the following form in the JDBC connection pool configuration:
Note: All connection property names are case-insensitive. For example, Password is the same as password.Required properties are noted as such. The data type listed for each connection property is the Java data type used for the property value in a JDBC connection pool.
Table 3-1 Informix Connection String Properties
Property | Description |
|---|---|
CodePageOverride OPTIONAL | The code page the driver uses when converting character data. The specified code page overrides the default database code page. All character data retrieved from or written to the database is converted using the specified code page. The value must be a string containing the name of a valid code page supported by your Java Virtual Machine, for example, CodePageOverride=CP950. |
ConnectionRetryCount OPTIONAL | The number of times the driver retries connections to a database servers (primary and alternate) until a successful connection is established. Valid values are 0 and any positive integer. If set to 0, the driver does not retry a connection to the list of database servers if a connection is not established on the driver's first pass through the list. The default is 0. |
ConnectionRetryDelay OPTIONAL | The number of seconds the driver will wait between connection retry attempts when ConnectionRetryCount is set to a positive integer. The default is 3. |
DatabaseName OPTIONAL | The name of the database to which you want to connect. If this property is not specified, a connection is established to the specified server without connecting to a particular database. A connection that is established to the server without connecting to the database allows an application to use CREATE DATABASE and DROP DATABASE SQL statements. These statements require that the driver cannot be connected to a database. An application can connect to the database after the connection is established by executing the DATABASE SQL statement. Refer to your IBM Informix documentation for details on using the CREATE DATABASE, DROP DATABASE, and DATABASE SQL statements. |
InformixServer | The name of the Informix database server to which you want to connect. |
InsensitiveResultSetBufferSize OPTIONAL | {-1 0 x}. Determines the amount of memory used by the driver to cache insensitive result set data. If set to -1, the driver caches all insensitive result set data in memory. If the size of the result set exceeds available memory, an OutOfMemoryException is generated. Because the need to write result set data to disk is eliminated, the driver processes the data more efficiently. If set to 0, the driver caches all insensitive result set data in memory, up to a maximum of 2 GB. If the size of the result set data exceeds available memory, the driver pages the result set data to disk. Because result set data may be written to disk, the driver may have to reformat the data to write it correctly to disk. If set to x, where x is a positive integer, the driver caches all insensitive result set data in memory, using this value to set the size (in KB) of the memory buffer for caching insensitive result set data. If the size of the result set data exceeds the buffer size, the driver pages the result set data to disk. Because the result set data may be written to disk, the driver may have to reformat the data to write it correctly to disk. Specifying a buffer size that is a power of 2 results in more efficient memory use. The default is 2048 (KB) |
LoginTimeout OPTIONAL | The maximum time in seconds that attempts to create a database connection will wait. A value of |
Password | A case-insensitive password used to connect to your Informix database. A password is required only if security is enabled on your database. If so, contact your system administrator to get your password. |
PortNumber | The TCP port on which the database server listens for connections. The default varies depending on operating system. |
ServerName | Specifies either the IP address or the server name (if your network supports named servers) of the primary database server. For example, 122.23.15.12 or InformixServer. |
User | The case-insensitive default user name used to connect to your Informix database. A user name is required only if security is enabled on your database. If so, contact your system administrator to get your user name. |
Table 3-2 lists configuration attributes for a sample WebLogic Server connection pool that uses the non-XA version of the WebLogic Type 4 Informix JDBC driver. Table 3-3 lists configuration attributes for a sample WebLogic Server connection pool that uses the XA version of the driver.
Table 3-2 Connection Pool Attributes Using the Non-XA WebLogic Type 4 Informix JDBC Driver
Attribute Hetman partition recovery 2.7 keygen. Jan 14, 2018 Hetman Partition Recovery 2.7 Crack Keygen + Registration Key Full Free Download. Hetman Partition Recovery Crack Download is a truly universal solution for resolving all types of problems with missing information. The tool can recover data from healthy, corrupted and unreadable devices, restore information from formatted disks and deleted volumes. | Value |
|---|---|
URL |
|
Driver Class Name |
|
Properties | informixServer=dbserver1 |
Password |
|
Statement Cache Size |
|
Target |
|
Table 3-3 Connection Pool Attributes Using the XA WebLogic Type 4 Informix JDBC Driver
Attribute | Value |
|---|---|
URL |
|
Driver Class Name |
|
Properties | informixServer=dbserver1 |
Password |
|
Statement Cache Size |
|
Target |
|
Informix Limitation for Prepared Statements
If anything causes a change to a database table or procedure, such as adding an index, or recompiling the procedure, all existing JDBC PreparedStatements that access it must be re-prepared before they can be used again. This is a limitation of the Informix database management system. WebLogic Server caches, retains, and reuses application PreparedStatements along with pooled connections, so if your application uses prepared statements that access tables or procedures that are dropped and recreated or for which the definition is changed, re-execution of a cached prepared statement will fail once. WebLogic Server will then remove the defunct prepared statement from the cache and replace it when the application asks for the statement again.
To avoid any PreparedStatement failure due to table or procedure changes in the DBMS while WebLogic Server is running, set the Statement Cache Size to 0. WebLogic will make a new PreparedStatement for each request. However, with the statement cache disabled, you will lose the performance benefit of statement caching.
Setting the following connection properties for the Informix driver as described in the following list can improve performance for your applications:
InsensitiveResultSetBufferSize
To improve performance when using scroll-insensitive result sets, the driver can cache the result set data in memory instead of writing it to disk. By default, the driver caches 2 MB of insensitive result set data in memory and writes any remaining result set data to disk. Performance can be improved by increasing the amount of memory used by the driver before writing data to disk or by forcing the driver to never write insensitive result set data to disk. The maximum cache size setting is 2 GB.
MaxPooledStatements
To improve performance, the driver's own internal prepared statement pooling should be enabled when the driver does not run from within an application server or from within another application that does not provide its own prepared statement pooling. When the driver's internal prepared statement pooling is enabled, the driver caches a certain number of prepared statements created by an application. For example, if the MaxPooledStatements property is set to 20, the driver caches the last 20 prepared statements created by the application. If the value set for this property is greater than the number of prepared statements used by the application, all prepared statements are cached.
By default, the Informix driver skips the additional processing required to return the correct table name for each column in the result set when the ResultSetMetaData.getTableName() method is called. Because of this, the getTableName() method may return an empty string for each column in the result set. If you know that your application does not require table name information, this setting provides the best performance.
See ResultSet MetaData Support for more information about returning ResultSet metadata.
Table 3-4 lists the data types supported by the Informix driver and how they are mapped to the JDBC data types.
Table 3-4 Informix Data Types
Informix Data Type | JDBC Data Type |
|---|---|
blob | BLOB |
boolean | BIT |
byte | LONGVARBINARY |
clob | CLOB |
char | CHAR |
date | DATE |
datetime hour to second | TIME |
datetime year to day | DATE |
datetime year to fraction(5) | TIMESTAMP |
datetime year to second | TIMESTAMP |
decimal | DECIMAL |
float | FLOAT |
int8 | BIGINT |
integer | INTEGER |
lvarchar | VARCHAR |
money | DECIMAL |
nchar | CHAR |
nvarchar | VARCHAR |
serial | INTEGER |
serial8 | BIGINT |
smallfloat | REAL |
smallint | SMALLINT |
text | LONGVARCHAR |
varchar | VARCHAR |
See GetTypeInfo for more information about data types.
See SQL Escape Sequences for JDBC for information about the SQL escape sequences supported by the Informix driver.
Informix supports the Read Committed, Read Uncommitted, Repeatable Read, and Serializable isolation levels. The default is Read Committed.
The Informix driver supports scroll-sensitive result sets, scroll-insensitive result sets, and updatable result sets.
Note: When the Informix driver cannot support the requested result set type or concurrency, it automatically downgrades the cursor and generates one or more SQLWarnings with detailed information.
The Informix driver supports returning parameter metadata as described in this section.
Insert and Update Statements
The Informix driver supports returning parameter metadata for Insert and Update statements.
Select Statements
The Informix driver does not support returning parameter metadata for stored procedure arguments.
The Informix driver supports returning parameter metadata for Select statements that contain parameters in ANSI SQL 92 entry-level predicates, for example, such as COMPARISON, BETWEEN, IN, LIKE, and EXISTS predicate constructs. Refer to the ANSI SQL reference for detailed syntax.
Parameter metadata can be returned for a Select statement if one of the following conditions is true:
32 Bit Informix Odbc Driver
- The statement contains a predicate value expression that can be targeted against the source tables in the associated FROM clause. For example:
In this case, the value expression 'bar' can be targeted against the table 'foo' to determine the appropriate metadata for the parameter.
- The statement contains a predicate value expression part that is a nested query. The nested query's metadata must describe a single column. For example:
The following Select statements show further examples for which parameter metadata can be returned:
ANSI SQL 92 entry-level predicates in a WHERE clause containing GROUP BY, HAVING, or ORDER BY statements are supported. For example:
Joins are supported. For example:
Fully qualified names and aliases are supported. For example:
If your application requires table name information, the Informix driver can return table name information in ResultSet metadata for Select statements. By setting the ResultSetMetaDataOptions property to 1, the Informix driver performs additional processing to determine the correct table name for each column in the result set when the ResultSetMetaData.getTableName() method is called. Otherwise, the getTableNames() method may return an empty string for each column in the result set.
The table name information that is returned by the Informix driver depends on whether the column in a result set maps to a column in a table in the database. For each column in a result set that maps to a column in a table in the database, the Informix driver returns the table name associated with that column. For columns in a result set that do not map to a column in a table (for example, aggregates and literals), the Informix driver returns an empty string.
The Select statements for which ResultSet metadata is returned may contain aliases, joins, and fully qualified names. The following queries are examples of Select statements for which the ResultSetMetaData.getTableName() method returns the correct table name for columns in the Select list:
The table name returned by the driver for generated columns is an empty string. The following query is an example of a Select statement that returns a result set that contains a generated column (the column named 'upper').
The Informix driver also can return schema name and catalog name information when the ResultSetMetaData.getSchemaName() and ResultSetMetaData.getCatalogName() methods are called if the driver can determine that information. For example, for the following statement, the Informix driver returns 'test' for the catalog name, 'test1' for the schema name, and 'foo' for the table name:
The additional processing required to return table name, schema name, and catalog name information is only performed if the ResultSetMetaData.getTableName(), ResultSetMetaData.getSchemaName(), or ResultSetMetaData.getCatalogName() methods are called.
The Informix driver supports any JSR 114 implementation of the RowSet interface, including:
- CachedRowSets
- FilteredRowSets
- WebRowSets
- JoinRowSets
- JDBCRowSets
Seehttp://www.jcp.org/en/jsr/detail?id=114 for more information about JSR 114.
When searching a Clob value for a string pattern using the Clob.position method, the search pattern must be less than or equal to a maximum value of 4096 bytes. Similarly, when searching a Blob value for a byte pattern using the Blob.position method, the search pattern must be less than or equal to a maximum value of 4096 bytes.
When converting a file to a Blob using the FILETOBLOB feature with the SERVER keyword and a file that exists on the server, the conversion works properly with a command similar to the following:
Informix Jdbc Driver Download
You cannot use the FILETOBLOB function with the CLIENT keyword because the function relies on the Informix client software to handle the data transfer from the client side to the server side. With the WebLogic JDBC Driver for Informix, there is no underlying client software so there is no current implementation to handle this type of data transfer.
The Informix driver supports retrieving the values of auto-generated keys. An auto-generated key returned by the Informix driver is the value of a SERIAL column or a SERIAL8 column.
- When using an
Insertstatement that contains no parameters, the Informix driver supports the following form of theStatement.executeandStatement.executeUpdatemethods to inform the driver to return the values of auto-generated keys: - When using a
Insertstatement that contains parameters, the Informix driver supports the following form of theConnection.prepareStatementmethod to inform the driver to return the values of auto-generated keys:
Ibm Informix Jdbc Driver
The application fetches the values of generated keys from the driver using the Statement.getGeneratedKeys() method.