Cloning instances with Service Exchange
When installing Service Exchange, certain tables must be preserved or excluded to maintain connectivity after a clone.
- If the same company isn’t present on the provider and consumer instances, the Company field is deleted, and the inbound and outbound connections move to an Error state.
- Even if the same company is present on both the instances, the Connection may be in an Error state. In this case, you must reestablish the connection and activate the Capture Definitions.
Service Exchange tables to preserve
The following scenarios describe how clone operations affect table data based on table configuration in the preservers and the exclusions tables list.
| Preservers tables | Exclusions tables | Result on target instance |
|---|---|---|
| Included | Included | Target table retains existing data. The system preserves existing records and copies no records from the source. |
| Included | Not included | Target table retains existing records and receives additional records from the source table. The system does not overwrite existing records. |
| Not included | Included | Target table is empty after the clone. The system discards existing target records and copies no records from the source. |
| Not included | Not included | Target table contains only source table data. The system replaces all pre-existing target records with records from the source. |
Add the following Service Exchange tables to the Clone Profile Preservers list if they’re missing. Remove any Service Exchange tables that aren’t in this list.
| Users | Table names |
|---|---|
| Provider |
|
| Consumer |
|
Service Exchange tables to exclude
Add the following Service Exchange tables to the Clone Profile Exclusions list if they’re missing. Remove any Service Exchange tables that aren’t in this list.
| Users | Table names |
|---|---|
| Provider |
|
| Consumer |
|
The following scenarios describe how clone operations affect table data based on table configuration in the Clone profile preservers list and the Exclude tables list.
The following examples use tables from this page to illustrate each scenario:
sn_sb_service_bridge_settings (included in both lists): The system preserves connection settings you configured on the target instance after the clone. Settings from the source instance do not overwrite them.
sn_sb_con_entitlement (included in Clone profile preservers only): The target instance retains existing entitlement records and receives additional entitlement records from the source instance.
sn_sb_error (included in Exclude tables only): The error records table is empty on the target instance after the clone. The system discards error records that existed on the target and copies none from the source.
sn_fds_offering (not included in either list): The system replaces the target table with source data. Records that existed on the target instance before the clone are replaced by source instance records.