Legacy inbound wires deprecation

These integrations are aging, which increases performance and stability risks to this critical functionality. In order to remediate these risks, Arc XP is announcing the deprecation of these services with an end-of-life date of April 21, 2025. 

In order to effectively hand over this responsibility, and minimize the amount of development required to re-create these integrations, Arc is providing you with the code for the current integration so that it can be deployed as is in your AWS instance.

The code and configurations that we are sharing is currently in a deployable state. But in order to work, you must use AWS.

If you want to simply deploy the integration as it is provided, you must set up an AWS account.

However, if you want to use another Cloud provider, then the code that we are sharing serves only as a reference and you must implement your own integration for the desired provider.

Yes, a development team is required to perform the task of setting up and maintaining the integration.

If you do not have a development team, or if your team cannot take on this work in the timeline indicated, Arc XP works with reliable System Integration partners that can assist you in setting up this integrations.

These partners have broad experience integrating with Arc XP and will have also tested setting up the wires integration themselves. Contact Arc XP Customer Support to learn more. 

Arc XP has tested the code bundles we are handing off thoroughly to ensure that it successfully runs in your own account without relying on any Arc XP-owned resources.  The bundles also contain Read Me files that detail the process for deploying the code in your own AWS account.

All “wires” tasks that were implemented outside of the partner-wires project will NOT be in the scope of this handover.

This means that all wire tasks that are part of a any custom adapter code (deprecation of these services already announced) will not be included in this deliverable.

Arc XP will notify you the week of October 21 with specific details about your impacted integrations.  

Because you have a copy of the code you can modify, ideally, any changes or edits to the feeds can be made by your team.  Making any updates/changes in your copy of the code and getting it deployed ensures that you have the most up to date integration in place and that you control the changes. The Arc team is available until January 21, 2025 to make small changes to the ANS configurations and scheduling behavior of currently running integrations but any request for new workflows or additional wire integrations will not be considered.  Between January 21, 2025 and April 21, 2025 no updates or changes will be made to Arc-hosted integrations. 

Before enabling your deployed integration, you should request that we disable the integration that we have running on our side in order to avoid duplication of content ingestion.

After you have fully verified that your integration is working as expected, create a support ticket requesting that we disable the legacy wire tasks. The ticket must contain the following items:

You should request your legacy integration be disabled at least two business days in advance to guarantee that it can be disabled at the requested date and time. Failing to do so may put your desired disable date and time at risk.

If you need to revise the anticipated deactivation date or time of a wire task, notify our support team as soon as possible and preferably with time in advance, and Arc XP Customer Support will notify the appropriate team, coordinate the rescheduling with the customer, and notify us about the new date and time. The Content Import team may decline the new date and time if it is in too short notice and the deactivation cannot be guaranteed.

If the Content Import team does not receive any type of communication to cancel the deactivation, we will proceed as scheduled.

The deactivation window should be no longer than one hour. Once completed, the Content Import team will notify support.

Once the customer has confirmation that their integration is running as expected, we will proceed to decommission the customers legacy resources.

When we disable the integration on our side, and you enable yours, there is a chance that some content will be lost. While the close timing of disabling/enabling of the feeds should minimize the impact, there is no way to guarantee that no content will be lost during this severed communication.

Once the new implementation is in place, if content ingested from the old, Arc-hosted feed is updated, you could end up with duplicated articles. To mitigate duplicate content, you will have to use Arc XPs editorial tools to either delete the newly loaded story or remove the older story, depending on which choice best fits your editorial needs.