Tenant ID migration guide

This section contains vital documentation for executing the tenantId migration. Important: This migration guide is only valid for IAS 2025.01.00. Ensure you have the correct version before proceeding.

If you run any Nexeed IAS installation on Tenant ID 7311ea8c-5d48-43fe-acf9-980eedf24b6c or any other non-unique Tenant Id do not skip the installation of InformationRouter version 1.14.0 contained in IAS 2025.01.00.

The Tenant ID is conceptually the unique identifier for all data contained in Nexeed IAS in relation to other installations. This will lead to problems if dataflows meet on shared infrastructure (like e.g. RabbitMQ or Solace) or existing systems are to be merged on a shared installation with multiple tenants.

Therefore, the Tenant ID has to be unique - for systems that have been erroneously installed with either Tenant ID 7311ea8c-5d48-43fe-acf9-980eedf24b6c or any other ID shared by another production system, BCI provides limited migration support with documentation and database scripts.

The Migration instructions and scripts available from BCI are specific to that version and cannot be executed on prior or later versions.

Prerequisites

Ensure that the system is shut down before executing the migration script to avoid any data inconsistencies.

Follow the Information Router tenant id migration documentation in the bci-tenant-id-migration docs for detailed instructions.

Migration steps

Run the following pre-check scripts from the bci-tenant-id-migration repository:
- 010-Pre-check-Connectivity-MDM.sql
- 010-Pre-check-Connectivity.sql
Run the following migration scripts from the bci-tenant-id-migration repository:
- 050-Migration-Connectivity-MDM.sql
- 050-Migration-Connectivity.sql
Follow the steps in 070-Post-Migration-Documentation to ensure a proper and clean setup.
Follow the steps in 075-Post-Migration-Consistency-Check to ensure that the migration was successful.