As part of Campaign Gold Standard initiative, Adobe plans to decommission the legacy Data Center. Campaign Classic instances must be transferred to Public Cloud (AWS). Learn more about this initiative in this article.
You will find below a set of common questions about this project, the impact on your Campaign environments, and other useful resources.
For any other question, you can reach out to Adobe Customer Care.
- Build Upgrade : When the Adobe Campaign Classic software is updated to the latest secure build number, yet stays in the same major/minor build Level. For example: Campaign v6.1.1 8222 to Campaign v6.1.8666. Learn more.
- MID/RT : Messages execution servers hosted on Adobe Cloud (MID for batch campaigns and RT for Real time unitary messages)
- Gold Standard upgrade: this program provides improved security, improved support, enhanced maintenance and stability. It also makes future upgrades easier and gives access to new capabilities in Campaign. Learn more.
- AWS: Amazon Web Services (Amazon Public Cloud)
- SFTP: Secured File Transfer Protocol. Learn more.
Extensive testing would be done before the production systems are migration. However in case of any issues, Customer Care will remain the main point of contact. Adobe has set up a team of experts to provide advanced support, if needed.
Existing subdomains will be moved from legacy Data Center to Public Cloud (AWS). This part will be handled by Adobe Deliverability team as part of the migration process.
Adobe will guide the customer through the required tests to ensure configuration is up and running on new Public Cloud (AWS) servers after the migration.
First of all, Adobe Deliverability will assess the platform’s deliverability status and recommend a plan for the switch to the new IPs
No warm-up is required after the migration. It might be some exception and, in such case, Adobe Customer Care will reach out to customers.
However, the plan is to make this operation transparent for the business, unlike the initial ramp-up that is done during go-live.
When the migration is complete, the Campaign instance will have entirely different sending IPs. As a matter of ensuring a smooth transition, Adobe will implement a ramp-up of the new sending IPs by progressively switching traffic from the old to the new IPs.
The sub-domain(s) used for marketing communication will remain the same. However, depending on the implementation, actions might will be needed on the client side:
- In case of sub-domain delegation to Adobe (default), Adobe will take care of all changes and ensure a seamless transition.
- In case of CNAME setup (exception), the client will be requested to implement changes. Coordination with Adobe will be needed.
Note about IP on the allow list
Migration to public Cloud will come with new IPs for Adobe Campaign application servers so that changing IP may then have impacts on connectivity between Adobe servers and your Information Systems.
Let’s consider the two cases :
- Inbound traffic : All network activity that is initiated from your systems or any other third party to Adobe Campaign servers. Configuration will be handled by Adobe and then copied from legacy to public Cloud during migration. Then connectivity for inbound traffic will be preserved as is after the migration and no action is expected from Customer side
- Outbound traffic : All network activity that is initiated by Adobe Campaign servers to your Information System or any other third party (ex: SMS provider). Depending on security policies in place in your organization, IPs changing may require allow list operation from your Information System or any other third party
Global impacts on configuration, connectivity with other systems and products, APIs and timezone are listed below.
Integrations are a combination of IP/web service on the allow list and External account configuration - This will be accounted for and owned by Adobe Customer Care. There will be IP on the allow list that will be required at other end as Application servers IP will change. This information will be provided. Rest is IMS based and should work as-is.
With this migration to Public Cloud (AWS), customer environments will be kept up to date with all necessary security requirements. This includes :
- Newest OS and security patches on a periodic bases
- Isolation of infrastructure per customer
- Managed security and audit reviews for supporting cloud infrastructure such as load balancers, network security rules and storage encryption.
Customer implementation can use custom scripts (Perl/Shell/Python/Java Script) in workflows to manipulate files and folders for example.
Adobe recommends slowing down and ideally pausing all executions just before the application is shutdown on the legacy Data Center: deliveries and workflows. That will ease the restart on Cloud Server (AWS) as processes will have been given time to pause “gracefully” and save any in-progress execution state.
The migration will come with an unavoidable platform downtime. The aim of this plan is to guide towards minimizing this downtime.
Data transfer between Data Centers is on the critical path of the downtime. The data is stored in two ways:
- By far the most important, the database
- Files on the application server (data imports and exports)
Reducing the size of the database is of highest importance to speed up the data transfer. Suggestions:
- Reduce the retention periods of historical data (delivery logs, tracking logs, etc.)
- Delete useless records on other tables (deliveries, recipients, custom tables)
While the migration is running, only one service will remain functional: email links redirection. All recipients will be able to reach the landing page when they click in an email. These clicks will however not be tracked, so click rates for the deliveries that were started shortly before the migration will be lower than usual.