Issue with Event Management Connector Instance Migration

[Community Alums]

Hi,

When I'm trying to move the connectors that I created in Development instance, the connector instance is not getting captured in update set and While I'm trying to move that as xml I'm getting the url same as development.

Please help me with this issue or confirm me whether we should do this as manual activity?

Thanks in advance 

[Dhanraj Poojari]

As per below knowledge article , custom push or pull itnegration created via Integration Launchpad do not get captured in update sets. This is by design and expected behavior (based on the read - I can only say this is a platform limitation and doesn't appear to have a security shade to it!)

If you attempt to migrate a custom connectors via xml it wont work due to underlying dependencies on the integration script, credentials and runtime environment. I have not come across any relevant documentation on recommended practice for migrating custom integrations.

I faced this issue with a custom Meraki EM integration and our NOC team had to spend 6 hours for configuring all Meraki appliances against each environment. The setup collapsed when the lower environments were cloned and custom webhook/integration were wiped.

We took a decision to use Event forwarding feature which would sync PROD events to Non-PROD and avoid redoing the integration in lower environment , setting up of appliances. Our attempts to capture the integrations in update set via also XML also failed and it only ended up creating unwanted records in the connection instance table. So, we had to manually setup the integration in all the environments.

For now only clean option is avoid capturing any components in update set and plan for a manual migration to higher environments. Remember , the connection instance tables are not preserved so it will be wiped in next clone, so plan to either setup preserver / exclusion rule within the clone configurations. Alternatively, setup Event forwarding once the custom integration is migrated to PROD

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2954519