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.

 

Upgrading to TeamConnect Business Intelligence 7.0 Patch 2

  1. Last updated
  2. Save as PDF
This guide provides detailed instructions on upgrading to TCBI version 7.0 Patch 2

Upgrading to TeamConnect Business Intelligence 7.0 Patch 2

If you have a previous version of TeamConnect Business Intelligence and want to upgrade to TeamConnect Business Intelligence 7.0 Patch 2, follow these specific instructions. 

Prerequisites 

Before you begin:

  • Dashboard owners MUST backup their existing dashboards prior to upgrade. Under normal upgrade processes, dashboard templates will persist and not have to be re-imported. The backup ensures that you do not lose your dashboards in the case that we encounter a unique scenario and the dashboards are deleted.
  • Verify that the TeamConnect installer has been run and the TeamConnect database has been updated to version 7.0 and higher versions.
  • After upgrading TeamConnect to v7.0 and higher versions, update the sisense URL(http://localhost:8081) in the TC properties file and restart the TeamConnect before continuing with TCBI upgrade.
  • Make sure the user has DBA access on the server machine from which they will be running syncs. To check if the user is already a DBA:
    •  type lusrmgr in the Microsoft Windows search field and open lusrmgr.
    • In the lusrmgr window, click Groups in the navigation pane and then ora_dba to see the list of oracle DBAs on the server.
    • If the user is not in the ora_dba group, click the Add button and add the user.
  • Grant the database schema access to create a materialized view by logging into sqlplus as sysdba and typing the command:  
    GRANT CREATE MATERIALIZED VIEW TO <DBUsername>;

    where <DBUsername> is the database username for your database. For example:
    GRANT CREATE MATERIALIZED VIEW TO TCTESTCSM;
  • For SQL Server, the login that you provide for TCBI's use must have the following roles:
    • public role
    • db_owner role
  • During the upgrade process, user can do the schemasync at a time after completion of below one or more activities:
    • Turn ON matter level security
    • Add or Remove objects or custom fields from reporting
    • Turn ON/OFF system fields
  • Copy any customization script from the customization folder of the current version into the new version. User can find this customization script files at the below location:

scripts > mssql > install > Customization (or)

scripts > oracle > install > Customization

Note: Ensure that you install TeamConnect and TCBI on different servers.

Overview

This section contains a quick overview of the upgrade process. Each line links to specific instructions on how to perform the process.

To upgrade the Sisense Web Server:

  • Replace current homepage and plug-in files with version from the installation media.
  •  Configure Mitratech branded email templates on web server.

To upgrade the Sisense Build Server:

  • Replace the Elasticube build files with released version on build server.
  • Perform uninstall followed by schema sync for all Elasticubes using new build files on build server.

To configure TeamConnect for the upgrade:

  • Replace the Sisense files in Documents with the new released version.

Upgrading Sisense

Execute this only if the Sisense version is v8.2.1 or earlier.

Follow the below procedure to upgrade Sisense from v8.2.1 to W2023.3 

Note: Ensure that you have enough disk space to run both the Sisense 8.2.1 and 20.23.3 (W2023.3) installer files.

Steps Screenshot for reference

1. Run the Sisense 20.23.3 (W2023.3) installer.EXE file provided by Mitratech Holdings, Inc. and click Continue. 

 clipboard_edee979608df0ab13faaa4cb0689731aa.png

2. A new window pop-ups, click Upgrade.

Note: 

  • You need to upgrade from v7.2 to v8.2.1 and then upgrade from v8.2.1 to 20.23.3 (W2023.3)
  •  In some environments, the upgrade from 8.2.1 to 20.23.3 may hang or fail to fully complete. If this occurs, restart the installation process in Repair mode.

 Upgrade screen.png

3. On successful Upgrade, login to Sisense and navigate to User Settings to verify the Sisense version.

Note: If SSL was enabled for Sisense v8.2.1 then you need to enable SSL for sisense v20.23.3 (W2023.3) before login to Sisense.

  Version num.png

Note: Stop the Sisense services in Task Manager and replace the dll files (Prism.ElastiCubeManager.ApiExtension.dll and Prism.ETL.Client.dll) in the folder path: C:\Program Files\Sisense\Prism

Updating the Sisense Plugin

To update, you must have Administrative privileges on the machine and the ability to install on the C:\ drive. Make sure you have an active account able to upgrade; this account is provided by Mitratech.

Note: Ensure that you run the uninstall.exe file to uninstall the old plugins before starting the Sisense plugin upgrade.

To Upgrade the Sisense Plugin:

Follow the below procedure to upgrade the Sisense plugin:

Steps Screenshot for Reference

1. Open the Sisense installer .EXE file provided by Mitratech Holdings, Inc. Click on the Installer icon with the Application file type (do not click on the Installer folder). 

Note: If you have plugins installed and are using the installer for the first time, you will see a popup as follows, click Yes.

clipboard_ec78f81ea2ec832b1442c187e0dd4a6d4.png

clipboard_e972da1c509fefd27344487b296f07fee.png

3. The TeamConnect Business Intelligence Setup pop-up will appear. Enter your administrator credentials and the site URL, then click Next.

 

Note: If you're using SSL, use the https://<dns> entry here

ie: https://sisense_dev.client.com

 clipboard_ef889edce54abc84cf9bc94f7523c303e.png
4. The Choose Install location screen will appear. Click Install if you are satisfied with the location. 621_Install_FileLocation.png
5. TeamConnect Business Intelligence will begin installing in the next screen. Once it is finished loading, you will be taken through the Setup screens in order to finish the installation. Click Finish when this screen appears. 621_Install_Finish.png

6. Once the plugin is successfully installed, an Uninstall option will appear in the same folder as the installation icon.

Note: To verify that the plugin was installed navigate through the following folder path: Program files > Sisense > app > plugins > TeamConnect > and verify that the plugin.json file is in the TeamConnect folder.

Click here to know how to verify the Installation of Sisense plugin

 clipboard_edf626f838d00693fddee82d390278d18.png

Updating the Sisense Build Server

Replacing Elasticube Build Files  

  1. Create a backup of the existing TeamConnect_BI directory by moving it to a different location and changing the name (for example, TeamConnect_BI_backup). Make a note of the location of the autoCube.properties file. You will need the property values in this file.
  2. Extract the files from the TCBI_Install_Package-xx.zip to the same the location of the original TeamConnect_BI directory.

Creating a Backup of the Existing ElastiCube  

To backup your ElastiCube:

  1. In Windows Services, stop Sisense.ECMS. 
  2.  Open the PrismServer\ElasticubeData directory, typically located here:
    %ProgramData%\Sisense\PrismServer\ElastiCubeData

    Note: If the directory is not in this location, open the Sisense Server Console and click the https://documentation.sisense.com/Resources/Images/7-2/serverpref.png Server Preferences icon to verify the correct path.
  3.  Copy the data to your backup location.

Upgrading the ElastiCube 

  1. After creating a backup, uninstall the ElastiCube by running the TCBI_Uninstall.bat script from the original installation files.
  2. Check the log for any errors.
  3. Open the new autoCube.properties file with a text editor. Define the property values with the information from the previous installation, being careful not to erase any new properties.

Note: Populate the sisense.pluginLocation property with  the location of the Sisense plugin folder. This parameter allows the autoCube to copy the .json file to the translation folder automatically. If the folder location is changed, this property needs to be updated. If this property is left blank, the autoCube will not copy the json file. When populating this property:

  • If you are using a high-availability (HA) system and have custom .json distribution scripts, skip this step.
  • If you are using an alternate distribution method such as a utility to move the .json files, turn the utility off before setting this new property.
  • Exclude the "metadata\translations" subfolder.
  • In the path, use \\ instead of \, for example, C:\\Program Files\\Sisense\\app\\plugins.
  1. Run the updated TCBI_SchemaSync.bat and check the log for any errors.

Note: Sisense has enhanced the functionality of scatter map widget. On the target server, run the below cmd file (script) with Administrator privileges to configure and upgrade it to the latest version (the older version is deprecated).

geo-maps-api-upgrade.cmd

Verifying Scripts

  1. Verify distribution scripts are copying the JSON file to the translations folder for Metadata Translation plugin.
  2. Verify distribution scripts are copying the services folder and JSON file to the dynamicBuckets folder.

Updating the TeamConnect Instance

Replacing the .class and .property in TeamConnect 
  1. In TeamConnect, click the Documents tab and select Top Level from the left pane.
  2. Click the System folder and then click the Report Integration folder.
  3. Click the Sisense folder.
  4. Check out the SisenseReportAdapter.class file, then check in the file and select the SisenseReportAdapter.class file from the new installation.
  5. Check out the sisense.properties file, then check in the file and select the sisense.properties file from the new installation.
  6. Restart the TeamConnect Instance after updating the above .class file.
  7. Verify that the Report Integration Tool has correct information.
    Note:
    • You  must re-type any secured fields such as Password or SharedSecret when you are updating an integration.
    • You cannot change an existing environment or client ID.
  8. Verify that the cube is shared with the tenant admin.
  9. Run the User/Group sync from the Report Integration Tool to update the User name with the User ID in the security tables in the cube.