Object Transporter Migration of a Core Connector Fails: ISU User Name Required
What it means
Migrating a Core Connector integration between tenants with Object Transporter carries over the integration definition but not its Integration System User assignment, since ISUs are tenant-specific security objects that Object Transporter does not migrate. When the target tenant tries to activate or update the integration without an ISU attached, the underlying call to create or update that user fails because the required user name is empty.
Troubleshooting
- Confirm the failure happens specifically after an Object Transporter migration, not on an integration built directly in the target tenant, since that isolates the cause to the migration step rather than the connector's own configuration.
- Open the migrated Core Connector integration in the target tenant and check whether an ISU is assigned under the Integration System's launch and security settings.
- If no ISU is assigned, that confirms the root cause: Object Transporter migrates the connector's field mappings and settings but never carries over ISU assignment, since ISUs are tenant-specific.
- If a dependent integration is chained to this connector's business process definition through a Fire Integration step, check that link is also correctly configured in the target tenant, a broken link there can surface as an unrelated page error before this ISU issue is even reached.
Assign an existing or newly created ISU to the migrated integration system in the target tenant, then retry activating or updating it.
Treat ISU assignment as a required checklist item after every Object Transporter migration of a Core Connector, since ISUs never travel with the migration package. Document which ISU should back each connector per tenant so migrations don't leave a gap that only surfaces the next time someone tries to update the integration.