Show/Hide Toolbars

Before you begin to install TeamConnect 5.2, ensure that your system meets the requirements. For a full list of requirements, refer to the Installation Requirements in the Installation Guide.

 

TeamConnect 5.2 can be upgraded to from the following versions:

TeamConnect 5.0

TeamConnect 5.0.1 and 5.0.2

TeamConnect 5.1

 

TeamConnect 5.2 is designed to pair with the following versions of modules (notes below reflect the available versions as of the TeamConnect 5.2 release date):

AP Link 5.0

CSM 5.0, 5.0.1, 5.0.2

Data Warehouse 5.0, 5.0.1, 5.0.2, 5.1
Note: Users on TCE 5.2 will not be able to connect to Data Warehouse if they are running SQL Server 2016 for their TeamConnect AND Data Warehouse databases as well as WebSphere 8.5.5.

Financial Management 5.0

Legal Matter Management 5.0, 5.0.1

Office Suite 2.1.1 and later 2.1 updates

Screen Designer 5.2

 

 

The following changes to the system requirements should be noted for both new installations and upgraded instances:

 

Users must upgrade to Java 8 (JDK 1.8) for TeamConnect to function. More information on setting the appropriate path and installing JDK 1.8 can be found in the Java documentation here.

In order to leverage Sharepoint Online DMS integrations, users must ensure that the Baltimore CyberTrust Root certificate is installed in their application's truststore. This certificate is key to enabling utility of many Microsoft web services applications.

TeamConnect supports SQL Server 2016 as of TeamConnect 5.1.

WebLogic 11g is no longer supported as of TeamConnect 5.1. WebLogic users should upgrade to WebLogic 12c to maintain compatibility with Java 8.

Users who have implemented custom color profiles will need reupload their custom color profiles after upgrade (LESS files). These files do not need to be recreated; uploading (and thereby rewriting these files) will recompile the CSS and ensure that the color profiles work as designed.

Users looking to take advantage of TeamConnect's Elasticsearch integration for global search must upgrade to Elasticsearch 5.3.0. Upgrading Elasticsearch will require users to re-index their instance. Preliminary testing finds that it takes roughly one hour per 4GB for indexing. This number will vary based on the types of files present in the index. Note: For detail on how to complete this re-indexing, please see "Indexing Objects" on the Identifying Parts of the Index Tool help page in the TeamConnect 5.2 guide.