Skip to main content
Mitratech Success Center

Client Support Center

Need help? Click a product group below to select your application and get access to knowledge articles, webinars, training content, and release notes or to contact our support team.

Authorized users - log in to create a ticket, view tickets status and check your success plan details.


TeamConnect 6.3 Technical Specifications

The following information contains the Technical specifications for TeamConnect Enterprise 6.3.

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 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
2x Dual Core or Single Quad Core
2+ GHz
2x Quad Core
2+ GHz
4x Quad Core 
2+ GHz
Java Heap Size 2-4 GB 2-4 GB 4-8 GB 8-16 GB

For more information, see Application and Web Servers.

Supported Application and Web Servers

TeamConnect supports and is certified on the following application servers:

Supported Versions Certified On Drivers
Oracle Weblogic 12c
  • 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
  • Use Java 8 build 261.
WebSphere Liberty
  • For SQL Server databases, use Integrated Solutions Console to create a JDBC data source that uses the 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 Liberty is certified with openJDK 11.
  • Note: The Web Services Feature Pack for WebSphere is not supported.
Tomcat 9.0.22
  • Tomcat is certified with openJDK 11.
  • For Oracle use ojdbc8.jar
  • For SQL Server, use a version 4 driver

For more information, see Application and Web Servers.

Supported Databases

TeamConnect Version Supported Versions Certified On
TeamConnect 6.3 Oracle 19c 19.3.0
SQL Server 2019 15.0.2000.5

For more information, see Database Requirements.

Web Browsers

The TeamConnect 6.3 application platform supports, and is certified for use with, the following web browsers:

  • Safari (current, Mac only)
  • Microsoft Edge Chromium (current)
  • Firefox (current)
  • Chrome (current)

Note: Safari has an issue when running on 32-bit Mac 10.6.4. Other Mac operating systems, including 64-bit Mac OS, do not have this issue.
Important: The browser options must be set to their default settings. TeamConnect is not certified for use with non-default browser settings.

It is recommended that client workstations do not use JavaScript debugging when accessing TeamConnect or other Mitratech applications.

For more information, see Web Browsers


Hardware Requirements

Mitratech recommends the use of three Elasticsearch nodes with each node on a separate server.

Requirements Per Server
Processor 4 Cores (If you need to choose between faster CPUs or more cores, choose more cores.)
RAM 16 GB minimum, 64 GB maximum
Cores 4
Java Heap Size Up to 50% system memory allocated, ideally 12-16 GB, 26 GB maximum 
JVM 50% system memory allocated

Software Requirements

  • TCE 6.3+ (till 6.3.5) are certified only against Elasticsearch 7.10.
  • TCE 6.3.6 and TCE 6.3.7 are certified only against Elasticsearch 7.16.

TeamConnect offers Global Search as part of an integration with Elasticsearch, enabling robust, global searching of TeamConnect. The integration is configured in the file and uses the Elasticsearch Java API.

Additional Details

For more information, refer to TeamConnect 6.3.

  • Was this article helpful?