TeamConnect Business Intelligence (Linux) Migration Process Guide

Create the Admin group in New Sisense (Linux)

1. Log in to the Sisense server using an admin account. Navigate to the Admin page, click on Groups in the left pane, and then click on + Add Group button.

2. Enter a group name that matches the existing group name. Add the admin user to the group.

3. After the eCube build is complete and the group is created, share the eCube with the group.
4. Go to the Data tab. Locate the eCube, click the three dots (⋯) next to it, and select Share.
5. In the Share pop-up, select the group. Grant access permissions for the selected group (allow the group to use/access the eCube).

Install/Update the Report Integration package (Linux)

1. Identify the available updates for Report Integration. Use the available updates to update the report integration files.
2. For Linux, install TCBI Report Integration Version 7.0.2.

How to get a Shared Secret?

1. Log in to the Sisense server and navigate to the SSO Settings page.
2. Locate the Shared Secret field and copy its value.
3. Use this value when configuring the Report Integration Settings in TeamConnect.

How to Get the Admin Group Id?

Log in to the Sisense server.

1. Navigate to the Admin tab.
2. In the left navigation pane, select REST API, then choose API version 0.9.
3. Locate the GET /groups/{group} endpoint and click Try it out.

4. Enter the group name and click Execute. In the response body, identify the GroupId value.

Update the AdminGroupId in the Database

To update the AdminGroupId value in the database, perform the following steps:

1. Log in to the database using an account with appropriate privileges.
2. Execute the following query to retrieve the existing properties:

SELECT *
FROM U_REPORT_INTEGRATION_PROPERTY;

3. In the result set, locate the record where:
   • FIELD_NAME = 'AdminGroupId'
     or
   • Identify the corresponding PRIMARY_KEY value for the AdminGroupId property.
4. Update the AdminGroupId using the PRIMARY_KEY and FIELD_NAME by executing the following statements and examples:

update U_REPORT_INTEGRATION_PROPERTY set FIELD_VALUE = <GroupID>
WHERE PRIMARY_KEY = <PRIMARY_KEY>;

Eg. update U_REPORT_INTEGRATION_PROPERTY set FIELD_VALUE = '3321315131' WHERE PRIMARY_KEY = 15005;
OR
update using the field_name:
update U_REPORT_INTEGRATION_PROPERTY set FIELD_VALUE = <GroupID>
WHERE FIELD_NAME = 'AdminGroupId';

Eg. update U_REPORT_INTEGRATION_PROPERTY set FIELD_VALUE = '3321315131'
WHERE FIELD_NAME = 'AdminGroupId';

COMMIT;

Update the Sisense URL in teamconnect.properties

To redirect TeamConnect to the Linux-based Sisense server, complete the following steps:

1. Stop the TeamConnect application or service.
2. Open the teamconnect.properties file and locate the Sisense base URL configuration entry.
3. Update the value to the new Linux-based Sisense server URL. Save the file.
4. Restart the TeamConnect application or service to apply the changes.
5. If the deployment is managed through Jenkins:
   • Update the SISENSE_SERVER parameter with the new Sisense URL.
   • Execute the Jenkins job using the build type WAR_ONLY.

Once the deployment is up and running, update the Shared Secret as follows:

1. Navigate to the integration settings in TeamConnect.
2. Enter the Shared Secret value (from Sisense) and the corresponding password.
3. Click Update Integration to save the changes.

Sync users to the new Sisense server

User synchronization sends TeamConnect user data to Sisense, enabling users to access Sisense dashboards.

1. Log in to TeamConnect.
2. Navigate to Report Integration. Select the User Sync icon/button.
3. Wait for the synchronization process to complete.
4. Once synchronization finishes, TeamConnect users will be available in Sisense and will be able to access the configured dashboards.

Moving Dashboards Between Sisense Environments

Follow the steps below to replicate dashboards from a source Sisense environment to a destination Sisense environment, generate folder mappings, apply the database remap, and then re-sync dashboards.

1. Note: If Dashboard Co-Authoring was left enabled during migration, Pivot Table widgets on the migrated dashboard will lose their Edit Script, breaking any hyperlinks configured on them. To resolve: delete the affected dashboard on the destination instance, disable Co-Authoring on the source dashboard, and re-run this replication step with conflict_resolution_strategy set to "overwrite". Verify the Edit Script and hyperlinks are intact on the Pivot Table before proceeding

2. Navigate to the endpoint: /api/v1/replicate-folder-dashboards
3. Select Try it out.
4. Enter the request body with the source and destination environment details:

{
  "source_domain": "<source_base_url>",
  "source_username": "<source_admin_user>",
  "source_password": "<source_password>",
  "destination_domain": "<destination_base_url>",
  "destination_username": "<destination_admin_user>",
  "destination_password": "<destination_password>",
  "verify_cert": false,
  "folder_name_filter": [],
  "dashboard_title_filter": [],
  "conflict_resolution_strategy": "skip"
}

5. Select Execute to begin the dashboard replication process.
6. After the process completes, copy or download the response output, as it will be required for the next step.

Note: If Dashboard Co-Authoring was left enabled during migration, Pivot Table widgets on the migrated dashboard will lose their Edit Script, breaking any hyperlinks configured on them. To resolve: delete the affected dashboard on the destination instance, disable Co-Authoring on the source dashboard, and re-run this replication step with conflict_resolution_strategy set to "overwrite". Verify the Edit Script and hyperlinks are intact on the Pivot Table before proceeding.

6. Navigate to the endpoint: /api/extract-folder-mapping
7. Select Try it out.
8. Paste the response output from the previous step into the request body. Select Execute button.

9. Once the request completes, download the generated CSV from the link in the response. This CSV provides the mapping between the old folder IDs (source) and the new folder IDs (destination).

10. Open the downloaded CSV file and copy the data rows only (exclude the header row).

11. Open the spreadsheet file GenerateUpdateStatement.xlsx and navigate to the CSV Entries tab. Paste the copied CSV data into the sheet.
12. Use the clipboard paste options and select Split Text to Columns to populate each value into the correct column.

13. Go to the Process Update Statement tab and copy the generated update statements, which will be used to update folder mappings so dashboards reference the correct folders in the destination environment.

14. Update the folder remapping script with the generated update statements (or paste the statements into the script as required by your process).
15. Execute the updated remapping script against the target database.

16. Restart the deployment/application services. After restart, re-run the dashboard synchronization (as applicable to your workflow) and confirm dashboards appear under the correct folders in the destination environment.