TeamConnect Technical Specifications
The following information contains the technical specifications for TeamConnect Enterprise 8.0, including supported application servers, databases, web browsers, and Elasticsearch requirements. For deeper detail, always refer to the Installation Requirements and the TeamConnect – Third Party Software Support matrix for TeamConnect 8.0.
Application and Web Server Requirements
Hardware Requirements
To provide TeamConnect with sufficient Java heap space to operate optimally, the TeamConnect server must have enough memory and CPU capacity available to support the usage pattern and the number of users.
- These requirements are based on an out-of-the-box TeamConnect design.
- Additional customization might change the system requirements needed for the application to run efficiently.
| Number of concurrent users | < 100 | 100–300 | 300–500 | 500–1000 |
|---|---|---|---|---|
| Processor | 64-bit single CPU, 2–4 cores, 2+ GHz | 64-bit, 2× dual core or single quad-core, 2+ GHz | 64-bit, 2× quad-core, 2+ GHz | 64-bit, 4× quad-core, 2+ GHz |
| Java heap size | 2–4 GB | 2–4 GB | 4–8 GB | 8–16 GB |
For additional performance guidance (heap tuning, JVM monitoring, and environment testing), see the Application and Web Servers article.
Supported Application and Web Servers
TeamConnect 8.0 supports and requires Oracle JDK 21 and is certified on the following application servers. For a full compatibility matrix across TeamConnect versions (application servers, JDK, databases, and more), see the TeamConnect – Third Party Software Support matrix for TeamConnect Enterprise 8.0.
Oracle WebLogic 15.1.1 with Oracle JDK 21
- Use WebLogic administration tools to create JDBC data sources.
- For SQL Server databases, use Oracle’s MS SQL Server Driver (Type 4), version 7.0 or later.
- For Oracle databases, use Oracle’s Thin driver, version 9.0.1 or later.
IBM WebSphere Liberty 25.0.0.4 with Oracle JDK 21
- Use the Integrated Solutions Console to create JDBC data sources.
- For SQL Server, use the “WebSphere embedded ConnectJDBC driver for MS SQL Server”.
- For Oracle, use the “Oracle JDBC Driver”.
- Set implementation type to “Connection pool data source”.
- Apply the Liberty configuration changes documented for hosted instances to prevent SOAP API call failures.
Apache Tomcat 10.1.34 with Oracle JDK 21
- For Oracle, use
ojdbc8.jar. - For SQL Server, use a version 4 SQL Server driver.
- If Tomcat 9.0 is used for legacy environments, replace JSTL 1.1.2 with JSTL 1.2.
- Apply the configuration changes documented for hosted instances to prevent SOAP API call failures.
- When multiple TeamConnect instances share a Tomcat server, configure unique log file names per instance.
For more information and detailed configuration deltas when moving to Oracle JDK 21, see the TeamConnect 8.0 – Application Server Configuration with Oracle JDK 21 guide and the Application and Web Servers installation article.
Supported Databases
The following databases are supported and certified for TeamConnect Enterprise 8.0. Earlier database versions are supported only for earlier TeamConnect releases and are documented in the TeamConnect – Third Party Software Support matrix.
| TeamConnect version | Database | Supported version | Certified on |
|---|---|---|---|
| TeamConnect 8.0 | Oracle Database | 19c | 19.3.0 |
| TeamConnect 8.0 | Microsoft SQL Server (Windows only) | SQL Server 2022 | 16.0.1000.6 |
For detailed database configuration, required privileges, localization guidance, and sizing considerations, see the Database Requirements article for TeamConnect Enterprise 8.0.
Web Browsers
The TeamConnect 8.0 application platform supports, and is certified for use with, the following web browsers (current generally available versions):
- Safari (current, Mac only)
- Microsoft Edge Chromium (current)
- Firefox (current)
- Chrome (current)
Additional notes:
- TeamConnect is best viewed with a minimum browser width of 1366 × 768 pixels.
- Browsers must be configured with their default settings; non-default security or scripting settings are not certified.
- It is recommended that client workstations do not use JavaScript debugging when accessing TeamConnect and other Mitratech applications.
For a complete browser support table across releases, see the TC 8.0 Web Browser Support article and the Third Party Software Support matrix.
ElasticSearch
Hardware Requirements
Mitratech recommends using three Elasticsearch nodes, each on a separate server.
| Requirement per server | Specification |
|---|---|
| Processor | 4 cores (when choosing between faster CPUs or more cores, choose more cores) |
| RAM | 16 GB minimum, 64 GB maximum |
| Java heap size | Up to 50% of system memory allocated, ideally 12–16 GB, 26 GB maximum |
Software Requirements
- TeamConnect 8.0 is only certified against Elasticsearch 8.17.4.
TeamConnect offers Global Search as part of an integration with Elasticsearch, enabling robust, global searching across TeamConnect records. The integration is configured in teamconnect.properties and uses the Elasticsearch Java API.
Ensure the TeamConnect Global Search Connector module is installed from Available Updates before testing the connection between TeamConnect and Elasticsearch.
For full installation and configuration steps, including Xpack and SSL, see:
Additional Details
This section summarizes environment-level technical changes in TeamConnect Enterprise 8.0 that are important when planning infrastructure and upgrades.
Java & Framework Updates
- Oracle JDK 21 required – TeamConnect 8.0 supports and requires Oracle JDK 21 across supported application servers. Confirm the certified JDK distribution in the Third Party Software Support matrix before go-live.
- Spring Framework 6.2 – The underlying Spring framework has been upgraded from version 5 to 6.2 to keep the platform current, improve security, and align with Jakarta-based libraries.
- Package Renamer Tool (only for Upgrades) – The Package Renamer Tool assists with migrating
javax.*tojakarta.*for custom Java code when moving to Oracle JDK 21 and Spring 6.x. It is highly recommended to run this tool during the upgrade planning for environments with custom integrations.
SSO / SAML Integration
- TeamConnect Enterprise 8.0 introduces native support for SAML-based Single Sign-On (SSO), integrated directly into the core platform (Setup → System Settings → Authentication).
- Existing standalone SAML server implementations must be retired, and configurations migrated to the integrated SAML SSO in TCE 8.0.
- For first-time SAML configuration, see the Setting up SSO-SAML in TeamConnect 8.0 article; for migration from legacy SAML server, see “How to upgrade from SAML Server to Integrated SAML-SSO in TeamConnect”.
Global Search & Elasticsearch
- TeamConnect 8.0 supports Elasticsearch 8.17.4, as documented in the Installation Requirements and Elasticsearch Setup for TeamConnect 8.0.
- TeamConnect Global Search Connector 2.0 is the compatible module version for TCE 8.0.
New Implementation/Upgrade Planning References
When using this page during an upgrade, cross-check the following resources:
- How to Ensure a Successful TeamConnect Enterprise 8.0 Upgrade? – for pre-upgrade actions, module compatibility, JDK and Spring impacts, SAML migration, and Office/DMS updates.
- TeamConnect – Third Party Software Support – for definitive version-by-version combinations of application servers, databases, browsers, Elasticsearch, Office, and DMS components.
- TeamConnect Enterprise Releases – for 8.0 GA details, known issues, and release notes.