| TTU 7.1 JDBC 3.1 | TTU 8.0 JDBC 3.2 | TTU 8.1 JDBC 3.3 | TTU 8.2 JDBC 3.4 | TTU 12.0 JDBC 12.0 | TTU 13.0 JDBC 13.0 |
| JVM 1.3.x | s | u | u | u | u | u |
| JVM 1.4.x | s | s | s | s | s | s |
| JVM 5.0 | u | s | s | s | s | s |
| JVM 6.0 | u | u | u | s | s | s |
| WebSphere 5.0 with IBM JVM 1.3.1 | s | u | u | u | u | u |
| WebSphere 5.1 with IBM JVM 1.4.1 | u | s | s | s | s | s |
| WebSphere 6.0 with IBM JVM 1.4.2 | u | s | s | s | s | s |
| WebSphere 6.1 with IBM JVM 5.0 | u | s | s | s | s | s |
| WebSphere 7.0 with IBM JVM 6.0 | u | u | u | s | s | s |
| WebLogic 7.0 with Sun JVM 1.3.1 | s | u | u | u | u | u |
| WebLogic 7.0 with JRockit JVM 1.3.1 | u | u | u | u | u | u |
| WebLogic 8.1 with Sun JVM 1.4.1 or 1.4.2 | s | s | s | s | s | s |
| WebLogic 8.1 with JRockit JVM 1.4.1 or 1.4.2 | u | u | s | s | s | s |
| WebLogic 9.0 with Sun JVM 5.0 | u | u | s | s | s | s |
| WebLogic 9.0 with JRockit JVM 5.0 | u | u | s | s | s | s |
| WebLogic 9.1 with Sun JVM 5.0 | u | u | s | s | s | s |
| WebLogic 9.1 with JRockit JVM 5.0 | u | u | s | s | s | s |
| WebLogic 9.2 with Sun JVM 5.0 | u | u | s | s | s | s |
| WebLogic 9.2 with JRockit JVM 5.0 | u | u | s | s | s | s |
| WebLogic 10.0 with Sun JVM 5.0 | u | u | u | s | s | s |
| WebLogic 10.0 with JRockit JVM 5.0 | u | u | u | s | s | s |
| WebLogic 10.3 with Sun JVM 6.0 | u | u | u | s | s | s |
| WebLogic 10.3 with JRockit JVM 6.0 | u | u | u | s | s | s |
| ColdFusion MX 6.1 Server Configuration with Sun JVM 1.4.2 | s | s | s | s | s | s |
| ColdFusion MX 6.1 JRun 4 Configuration with Sun JVM 1.4.2 | s | s | s | s | s | s |
| ColdFusion MX 6.1 J2EE Configuration in third-party application server | u | u | u | u | u | u |
| ColdFusion MX 7 Server Configuration with Sun JVM 1.4.2 | s | s | s | s | s | s |
| ColdFusion MX 7 JRun 4 Configuration with Sun JVM 1.4.2 | s | s | s | s | s | s |
| ColdFusion MX 7 J2EE Configuration in third-party application server | u | u | u | u | u | u |
| ColdFusion 8 Server Configuration with Sun JVM 1.4.2 | u | u | u | s | s | s |
| ColdFusion 8 Server Configuration with Sun JVM 5.0 | u | u | u | s | s | s |
| ColdFusion 8 Server Configuration with Sun JVM 6.0 | u | u | u | s | s | s |
| ColdFusion 8 Multiserver (JRun 4) Configuration with Sun JVM 1.4.2 | u | u | u | s | s | s |
| ColdFusion 8 Multiserver (JRun 4) Configuration with Sun JVM 5.0 | u | u | u | s | s | s |
| ColdFusion 8 Multiserver (JRun 4) Configuration with Sun JVM 6.0 | u | u | u | s | s | s |
| ColdFusion 8 J2EE Configuration in third-party application server | u | u | u | u | u | u |
| JBoss 3.2.3 with Sun JVM 1.4.2 | u | s | s | s | s | s |
| JBoss 4.0 with Sun JVM 1.4.2 | u | u | s | s | s | s |
| JBoss 4.0 with Sun JVM 5.0 | u | u | s | s | s | s |
| SAP Web AS 6.40 with Sun JVM 1.4.2 | u | s | s | s | s | s |
| Tomcat 5.5 with Sun JVM 5.0 | u | u | u | s | s | s |
| Tomcat 6.0 with Sun JVM 5.0 | u | u | u | s | s | s |
| Tomcat 6.0 with Sun JVM 6.0 | u | u | u | s | s | s |
Please refer to the Teradata JDBC Driver User Guide for each Teradata JDBC Driver release, to obtain the list of supported combinations of operating systems, CPUs, and 32/64 bit modes for that Teradata JDBC Driver release.
Please refer to the application server vendor's documentation to obtain the list of supported combinations of operating systems, CPUs, and 32/64 bit modes for each application server version.
The Teradata JDBC Driver is supported for use with all combinations of operating systems, CPUs, and 32/64 bit modes that are supported by both the application server version and the Teradata JDBC Driver release.
For Java software, an operating environment consists of the complete combination of the following items:
Generally, the Teradata JDBC Driver is tested in a particular operating environment before that operating environment is supported for use with the Teradata JDBC Driver. Such testing is needed for the following reasons:
If a problem is encountered while using the Teradata JDBC Driver in an unsupported environment, then the GSC will attempt to reproduce the problem in the closest supported environment. If the problem can be reproduced in a supported environment, and the problem is determined to be due to the Teradata JDBC Driver, then the problem will be corrected and retested using the supported platform.