The following page and subsequent installation guide section is for TeamConnect 5.2. For a copy of the TeamConnect 5.0 guide (applicable to 5.0.x releases), please download this PDF from the online help site.
TeamConnect supports, and is certified on, the following application servers.
TeamConnect 5.2 only supports JDK 1.8.
The first column in the table delineates different TeamConnect versions. Please ensure you are viewing the correct requirements based on your version.
Comprehensive details on Java installation can be found at the Java 1.8 download site here.
Supported Versions |
Certified On |
Drivers |
Oracle Weblogic 12c
|
12.2.1.2
|
•For SQL Server databases, use WebLogic administration tools to create a JDBC data source. Use driver "Oracle's MS SQL Server Driver (Type 4) Versions: 7.0 and later •For Oracle databases, create a JDBC data source that uses driver "Oracle's Driver (Thin) Versions: 9.0.1 or later |
WebSphere 8.5.5 |
8.5.5.10 |
•For SQL Server databases, use Integrated Solutions Console to create a JDBC data source that uses driver "WebSphere embedded ConnectJDBC driver for MS SQL Server". •For Oracle databases, create a JDBC data source that uses driver "Oracle JDBC Driver" •For either database, set implementation type to "Connection pool data source" •WebSphere/IBM users need to download the proprietary Java 8 bundle: IBM SDK, Java Technology Edition, Version 8 Note: The Web Services Feature Pack for WebSphere is not supported. |
Tomcat 8.5 Tomcat 7.0
|
8.5.5 7.0.67 |
•For Oracle use ojdbc6.jar •For SQL Server, use a version 4 driver •For Tomcat 8.5, remove JSTL 1.1.2 and replace with 1.2 |
TeamConnect supports the hardware platforms and operating systems that are certified by your application server software vendor.
To provide TeamConnect with sufficient Java heap space to operate optimally, you must ensure that the server on which you are running TeamConnect has enough memory and CPU capacity available to support the usage pattern and the number of users.
The required Java minimum heap size setting is at least 2 GB for TeamConnect. Depending on your environment and usage, you may need to increase your minimum heap size. It is recommended that you use a 64-bit operating system on the TeamConnect application server. It is important that you monitor JVM heap utilization during the test cycle as well as perform a load test to validate that the settings you are planning to use in production can handle the expected user scenarios and load. There are other environmental and configuration considerations that should be taken into account when setting up TeamConnect for optimal performance. For more information, please refer to the performance tuning documentation provided by your application server vendor and database vendor.
Consult the application server documentation for a list of compatible web servers. For details regarding application and web server installation, see your vendors' documentation at the corresponding URLs:
•Apache Tomcat—tomcat.apache.org
•Oracle WebLogic—www.oracle.com
•IBM WebSphere—pic.dhe.ibm.com/infocenter/wasinfo/v8r5/index.jsp
•Microsoft Internet Information Server (IIS)—www.microsoft.com
It is recommended that you configure your web server to "keep alive" the TeamConnect session. This is particularly recommended if you are using a single sign-on method of authentication. "Keep alive" improves the performance of TeamConnect.
