Cloning instances with Service Exchange
When installing Service Exchange, certain tables must be preserved or excluded to maintain connectivity after a clone.
If the default system profile is used, some of the Service Exchange table data isn’t preserved. To address this issue, you must create a custom clone profile with specific settings required for Service Exchange. Navigate to and select New to create a custom profile. For more details on clone profiles, see Clone profiles for clone requests. In this profile, you must validate if the following Service Exchange tables are included in the custom profile:
Note:
- 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
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 |
|