Skip to main content
Mitratech Success Center

Upgrading to TeamConnect Business Intelligence 6.2.2

This guide provides detailed instructions on upgrading to TCBI version 6.2.2.

Upgrading to TeamConnect Business Intelligence 6.2.2

If you have a previous version of TeamConnect Business Intelligence and want to upgrade to TeamConnect Business Intelligence 6.2.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 6.2.2.
  • 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

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:

To upgrade the Sisense Build Server:

To configure TeamConnect for the upgrade:

Updating the Sisense Web Server

This step will update the Sisense Server Console, Sisense Web Application, ElastiCube Manager, and ElastiCube Server. To update Sisense, 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 Sisense; this account is provided by Mitratech.

To Upgrade the Sisense Plugin:

1. Open the Sisense installer .EXE file provided by Mitratech Holding, Inc.

2. 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_e972da1c509fefd27344487b296f07fee.png

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

621_Install1.png

4. The Choose file 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.

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

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.
  4. Note:
    • 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.
       
    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:
    • Exclude the "metadata\translations" subfolder.
    • In the path, use \\ instead of \, for example, C:\\Program Files\\Sisense\\PrismWeb\\plugins.
       
  5. Run the updated TCBI_SchemaSync.bat and check the log for any errors.

Verifying Scripts

  1. Verify distribution scripts are copying cubes to the correct locations for all nodes.
    Note: For a high-availability environment, add the ElastiCube to an ElastiCube set, share both the individual ElastiCubes and the ElastiCube set with the appropriate Sisense administrator account, and then use the name of the ElastiCube set in the report integration.
  2. Verify distribution scripts are copying the JSON file to the translations folder for Metadata Translation plugin.

Remapping Fields  

In existing TeamConnect Business Intelligence reports and dashboards built with TeamConnect Business Intelligence 6.1.2 or earlier, all fields must be remapped once. After this one-time remapping and implementation of this plugin, renamed fields will not need to be remapped anymore. Note: This step only applies to instances that are upgrading from TeamConnect Business Intelligence 6.1.2 or earlier and have existing reports created on those older versions.

Note: These steps must be performed by the owner of the dashboard.

You have two options.

  • If you only have a few reports with few fields, remap the fields manually using the steps below.
  • If you have multiple reports or reports with many fields, use the Metadata Remapping Tool

To remap a field in a report manually:

  1. Open the TeamConnect Business Intelligence dashboard in TeamConnect. Reports that need to be remapped display an error stating that an item cannot be found.
  2. Click the Edit Widget icon in the upper right corner of the report. 
  3. Delete each field in the report by clicking the clipboard_e02902816f6e2b3dddee4a9bafc8ed0a0.png Remove the item icon for the individual field. 
  4. Re-add each field to the report.
  5. Click Apply.

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 SisenseReportPortlet.class file, then check in the file and select the SisenseReportPortlet.class file from the new installation.
  6. Check out the sisense.properties file, then check in the file and select the sisense.properties file from the new installation.
  7. Open the sisense.properties file ad verify that it is pointed at the correct Sisense URL.
  8. If using Sisense in a high-availability (HA) environment, set the new property sisense.highAvailability=true in teamconnect.properties and use cube sets when configuring Sisense.
  9. 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.
  10. Verify that the cube is shared with the tenant admin.
  11. 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.

Turning On Matter Level Security 

Out of the box, Matter level security defaults to OFF upon upgrade to 6.2.2. This means that anyone viewing a Dashboard will be able to see any Matter listed regardless of their TeamConnect security limitations. It is turned OFF because removing the security results in up to a 2x performance improvement. Best practice is to turn off matter security for analytical reports because it could cause perceived inaccuracies if security restrictions limit a user from seeing all the data and therefore, the complete picture. It is possible for a Report Designer to manage some security concerns when building reports. If your organization requires Matter level security, execute the following script to turn it back ON. This change can only be made by someone with SQL access to the TeamConnect database.

If Matter Security is turned ON, it will stay ON after future upgrades. There is no need to manually reset it every time.

Please Note: enabling matter security on the ecube may significantly impact performance of the schema and data syncs.  It will also impact the aggregated values displayed in the dashboards.  For example, a chart that sums financial information will be limited to summing values for only matters that the user can access and may result in an inaccurate financial picture.  Mitratech recommends leaving security disabled and instead using dashboard design to mitigate security concerns.  If enabling security is desired, please consult with your Services or Support representative to discuss these impacts.

The following script should be run against the database where 'YES' is changed to 'NO'. This will cause the necessary security table to be built which will restrict Matters to be displayed only if the user has rights. 

UPDATE Y_SYSTEM_SETTING SET SETTING_VALUE = 'YES' WHERE SETTING_KEY = 'disableTcbiSecurity';

After the script is executed, TCBI schemaSync has to be performed. Once the schemaSync completed, user/group sync for the Report Integration has to be run from TeamConnect. Instructions on how to trigger a schemaSync and a user/group sync follow. 

Adding or Removing Objects and Fields from Reporting

In TCBI 6.2.2, there is now a new column in Setup to make a field reportable for TCBI and a separate column to make a field reportable in the Data Warehouse. For all existing TCBI users, when the upgrade script is run, all fields checked in "Include in Reporting" will be copied to the new column "Include in Tcbi Reporting." Note: any field selected for TCBI should also be included in Reporting BUT fields can be marked YES for "Include in Reporting" but NO in TCBI. You will not see the option to "Include in Tcbi Reporting" until a field is marked YES for "Include in Reporting".

These selections have been separated to optimize cube performance. The TCBI cube should be kept as lean as possible for analytics reporting and should not be required to have all the same fields as the data warehouse. Although the selected fields will be copied over, you may optimize performance of your system by removing any fields you do not need for TCBI-based reports. This is particularly true for larger fields like Comments (CLOB type).

Before:

clipboard_e2fa67553ca4f8112c65e02feafac8d96.png

Now:

clipboard_ee99156a31953bac80250dfa1181aaffb.png

Administrators can include or remove entire custom and system objects from TeamConnect Business Intelligence reporting so that reports display the most relevant information and data syncs are faster.

  • If an object is reportable, all fields associated to the object are reportable, except fields explicitly designated as removed from reporting.
  • If the parent object is included in reporting, the setting does not automatically cascade down; the child/embedded object is not included and needs to be set manually.
  • If a child/embedded object is included in reporting, the parent object also needs to be manually included.
  • If a parent object is removed from reporting, then all of its child objects or fields are removed from reporting, regardless of the reporting designation for the child or field. If you want to report on a specific child object, the parent object must be included in reporting.

Custom objects are removed from reporting by default except the objects in the following table. Admins can change this setting in the Setup tool. By default, the following objects are reportable:

Code Type Object
ACCT System Account
CONT System Contact
INVC System Invoice
LNI$ System Line Item
ACPT OOTB Custom Advice and Counsel Involved Party (Legal)
ADCO OOTB Custom Advice and Counsel (Legal)
ALLE OOTB Custom Allegation (Legal)
ASSE OOTB Custom Liability Asset (Legal)
AWAR OOTB Custom Award (Legal)
COAC OOTB Custom Corrective Action (Legal)
COCE OOTB Custom Dispute Cost Center (Legal)
DAMA OOTB Custom Damage (Legal)
DISP OOTB Custom Matter (Legal)
INPA OOTB Custom Matter Involved Party (Legal)
NEGO OOTB Custom Negotiation (Legal)
PART OOTB Custom Coverage Involved Party (Legal)
PROV OOTB Custom Matter Provision (Legal)
RADC OOTB Custom Related Advice and Counsel Matter (Legal)
RTAC OOTB Custom Related Advice Matter (Legal)
SANC OOTB Custom Sanction (Legal)
TCOC OOTB Custom Transaction Cost Center (Legal)
TENA OOTB Custom Lessee (Legal)
TERM OOTB Custom Matter Term (Legal)
TRAN OOTB Custom Coverage (Legal)
VIOL OOTB Custom Violation (Legal)
MTR$ OOTB Custom Matter (Essentials)
INP$ OOTB Custom Matter Involved Party (Essentials)

(Objects that are provided with TeamConnect and its modules are considered “out-of-the-box” (OOTB) custom objects.)

Note:

  • On average, adding an additional custom object to be reportable will add ~3 minutes to the schema sync and ~1 minute for each category that the custom object has. The time it takes to loading the data into the ecube depends on the size of the table in the database.
  • If you have removed an object from reporting and that object is used in a report widget, the widget will return an error stating that the field no longer exists. Remove the non-reportable field manually by editing the widget.
  • If you are upgrading TeamConnect, before any modules are installed, the admin needs to manually make the module’s “out-of-the-box” (OOTB) custom objects reportable or run a specifically provided script in order for the items to be reportable.
  • When an object has the Remove from Reporting (Business Intelligence) checkbox selected, the object is only removed from TeamConnect Business Intelligence reports; Legacy reports with Data Warehouse are not changed.

To add or remove an object from reporting:

  1. Click Setup and select Object Definitions from the Go to… menu.
  2. Select the object and click the General tab.
  3. To exclude the object from reporting, select the Remove from Reporting (Business Intelligence) checkbox. To include the object in reporting, clear the Remove from Reporting (Business Intelligence) checkbox.
  4. Click OK. After the next schema sync, the object will be included or removed from TeamConnect Business Intelligence reporting but will still be included in Legacy reports using Data Warehouse.

To add or remove a custom field from reporting:

  1. Click Setup and select Object Definitions from the Go to… menu.
  2. Select the object.
  3. On the Custom Fields tab, select the appropriate fields and click Edit Selected. In the Include in Data Warehouse column, select No to remove the field from reporting, or select Yes to have the field included.
  4. Click OK. After the next schema sync, the field will be included or removed from both TeamConnect Business Intelligence reporting and Legacy reports using Data Warehouse.

Updating Existing Reports  

If you are upgrading from a TeamConnect Business Intelligence 6.0.x version, you will need to update the existing reports.

To update your existing reports: 

  1. The following objects have been removed from reporting, so remove these objects from any reports: 
    • Task 
    • Appointment
    • Document
    • Expense
    • History
  2. The following tables that contain "List" values have been removed from the ElastiCube to increase performance. Remove any of these "List" fields in existing reports.

    • Category
    • Involved Party
    • Skill
    • Territory
    • Attendee
    • Assignee
    • Resource
    • NonUSTax
    • NonUSTaxCode
    • Matter Cost Center
    • Invoice Cost Center
  3. The following Default fields from the tables listed in the previous step have been moved into the main object. If you used these fields in  any of your reports, remap the fields to the new location.
    • Default Category (both leaf and full name; see note below)
    • Default Address
    • Default Phone
    • Default Fax
    • Default Inet Address
    • Default Email
    • Main Assignee

Note: The Default Category fields are divided into Category and Category Full. For example, if a matter has a bankruptcy, Category shows Bankruptcy only; Category Full displays Dispute|Bankruptcy.

The Categories field is still available and doesn’t change. This field displays each category entry on a separate line. If you have one matter with many categories, you can still see all categories, it’s just listed in separate lines. No data is removed.