Deprecation notice: Custom Integrations and Adapter Deprecations
Deprecation date: February 17, 2025
Arc XP is deprecating the hosting of custom integrations and adapters on February 17, 2025.
Arc XP’s former Professional Services team developed custom integrations and content adapters for ingesting content into Arc XP and sending content to external systems. Our team built these integrations as custom solutions that we, Arc XP, controlled and maintained on behalf of you, the customer.
Applications impacted
Ad-hoc and bulk migrations: Several customers have services which receive updates from an external CMS.
Adapter integrations with wires: Adapters running automation scripts to pull data and load into Arc. These integrations run on standard intervals, typically have specific provider entitlements and key/secrets that need to be stored.
Outbound Events not supported by current IFX options: Several customers have outbound integrations that use Kinesis to provide content to downstream services.
Print integrations: In several cases customers are using custom print integrations to provide content to their print CMS.
Libraries used in Custom integrations: Several customers have one-off integrations of utilities used for common integrations.
Custom Video Vendor integrations: Bespoke integrations for synching metadata from a video vendor such as Brightcove into Arc.
Why we're deprecating custom integrations and adapters
The legacy adapters are aging, which increases performance and stability risks to these critical integrations. In order to remediate these risks, Arc XP deprecating these services with an end-of-life date of February 17, 2025.
You must now own and support these integrations, which reduces dependencies on legacy code and strengthens the overall stability of your solution.
Action required
If you're affected by this change, Arc XP will contact you directly with detailed instructions.
How we can support you during this change
Arc XP will answer technical questions about legacy applications.
For clients who need access to the respective repos, Arc XP can provide read only access to the Github repo for review and downloading. These repos will be archived and/or deleted after the deprecation date, so clients should plan to create their own repos in their own orgs.
We will NOT be doing any Github Transfers at this time.
We will need the Github Usernames for the admins who need access in the ACS tickets to move forward and assist in providing access to clients.
Any existing data for these applications may be provided at request if it disrupts historical record keeping.
Out-of-scope support
While Arc XP will continue to support currently running applications until they have reached their formal end-of-life, Arc XP cannot guarantee legacy applications will be in a deploy-able/working state once handed off and we cannot advise on the specifics of modified code after hand off.
While Arc XP can provide access to the current code and can be available to discuss existing integrations, Arc XP cannot formally document how or why current code is working the way it is.
Are there any Arc XP product offerings in place now that can help customers establish new integrations?
If you would like to use the latest product offerings at Arc XP, we can advise on what solutions may align with your goals.
Some example product solutions that may be appropriate depending on the particular integration are:
Migration Center
Draft API
Photo Center
IFX