B2C Commerce Hyperforce Realm Move Preparation and Process

Pre-Realm Move Steps

• 4 weeks prior: Open a B2C Commerce Support case, noting the realm move date, and new Hyperforce destination.
• 4 weeks prior: Provide the Hyperforce Public IP Ranges link in order to obtain the Hyperforce external IP list to be added to the firewall allow list. (Compliance login no longer required).                           

Note: All regions need to be allow listed by your third parties. The region can be adjusted in the event of a fail over. It is also possible some services may be sourced from alternate regions in the future.  

          Customer Responsibilities

• 4 weeks prior: Migrate to HTTPS by your scheduled Hyperforce migration date. HTTP (only) traffic will not be supported on Hyperforce. Hyperforce enforces a strict security model requiring HTTPS for all network traffic. To protect customer data from interception or man-in-the-middle attacks, the platform uses TLS encryption and automatically rejects all unencrypted HTTP connections. HTTPS can be enabled by navigating to the following path in Business Manager. 

• • Administration | Global Preferences | Security | Access Restriction tab | Enable Enforce HTTPS and clicking Save
  • Reference: Enforce HTTPS for B2C Commerce

• 4 weeks prior: Add all of the Hyperforce outgoing IPs to firewall settings of all integrations (including third-party integrations) for back-end connectivity, if needed.

• • The Hyperforce external IP list can be found on https://ip-ranges.salesforce.com/ip-ranges.json                         
  • Reference: Hyperforce IPs to Allow 

• 4 weeks prior: Migrate any existing legacy zone to proxy zone. Legacy storefront zones are being deprecated for the Hyperforce transition. All B2C Commerce users must migrate to the Proxy zone configuration, as legacy zones are unsupported on the new infrastructure. This migration ensures a standardized eCDN, access to the latest security features like auto-renewing certificates, and improved troubleshooting.
  • For detailed migration instructions, see Migrate a Legacy Zone to a Proxy Zone. The process involves enabling the migration feature, creating the proxy zone, manually copying specific settings such as Logpush and Rate Limit Rules, and updating your DNS configuration.
  • To determine if you have a Legacy zone, log into Business Manager, select Administration | Sites | Embedded CDN Settings. Legacy zones are listed in the settings and marked with the Legacy Zone label. Proxy zone details can be found in eCDN Proxy Zone FAQ.
• 4 weeks prior: Verify 2FA client certificates are uploaded to eCDN
  • As part of HF migration, WebDAV Auth is moving to eCDN and you will need to bring your client certs and upload them to eCDN for code upload to staging
  • In order for code uploads to work, you must complete these steps:
  • Generate a self-signed cert bundle. Detailed instructions can be found in B2C Commerce Hyperforce 2FA Secure Upload Customer Instructions
  • Upload self-signed root CA cert (i) using Business Manager user interface or CDN-API.
    • Client cert should use the same self-signed root CA cert (i). For more information, see Generate, Sign, and Use Client Certificates for Secure Code Uploads.

• 4 weeks prior: Ensure that the email domains you use for sending emails are listed and approved within Business Manager, under Administration | Operations | Email Settings | Domains

  • Ensure that you continue to use this screen to add approved new domains as you need before you utilize them to send emails

• 4 weeks prior: Ensure that you add the DNS records in your Business Manager, under Administration | Operations | Email Settings | Domains | See DNS

  • Ensure that you continue to use this screen to update DNS records as new email domains are required

• 3 weeks prior: Verify that the SPF record refers to the Production domain (for example, https://production-realmname.demandware.net/*), and not the current IP address.  This will ensure a more seamless transition for successful sending of confirmation emails after the move. Also see Best Practices for sending email via the B2C Commerce platform regarding the use of dots versus dashes.
• 2 weeks prior: If necessary, update the maintenance page for when Production is offline.
• 3 days prior: Avoid submitting firewall change requests 72 hours prior to realm move.

Realm Move Steps

• PIG Move (Production, Staging, Development): Date communicated via case. Time is always during the 2-7 am maintenance window of the source POD's time zone.  During this time, all PIG instances and the storefront will be down. Jobs will not run, so they should be rescheduled to before the move, or manually run after.
  • ~5 hours prior to PIG move start: Staging & Development instances are taken offline to prevent replications and other data changes from taking place, which helps reduce the overall downtime.
  • Pre PIG Move, SFCC to verify the count of customers and orders from PRD BM (just to have them in case of any ELS issues post PIG move)
    • Check the customer and order records by following the steps :
    • Open BM > Merchant Tools > Customers
    • Note down the count (along with time & time zone)
    • Open BM > Merchant Tools > Orders
    • Note down the count (along with time & time zone)
  • Ticket is flagged as Global Handover/Follow the Sun so the support team on duty will monitor the ticket during the move.
  • ~0200 POD time: PIG move begins.  Maintenance page is displayed.  Salesforce case updated noting maintenance has begun.
  • Salesforce performs core activities of the PIG move:
    • Put up maintenance page and shutdown web/apps on old POD.
  • Kickoff final data replication to new HF POD (from old POD). 
  • Start up all databases on new HF POD.
  • Startup web and apps on new HF POD.
  • Shutdown databases on old POD.
• ~0300-0700 POD Time: PIG move completed.
  • Support confirms Business Manager and storefront functionality
  • Support confirms MongoDB functionality
  • Maintenance page is taken down.  Case is updated noting completion.  

For storefront IPs behind eCDN, Operations will manage any required changes.

Post-Realm Move Steps

        Salesforce Responsibilities

• Verify if the Control Center administrator has the required permission/s to manage instances in Control Center.
• Support confirms Business Manager and storefront functionality.
• Support confirms MongoDB functionality.
• Post PIG Move, SFCC to verify the count of customers and orders from PRD BM (just to have them in case of any ELS issues post PIG move) and compare it with Pre PIG Move count
• Check the customer and order by again following the below steps:
  • Open BM > Merchant Tools > Customers
  • Note down the count (along with time & time zone)
  • Open BM > Merchant Tools > Orders
  • Note down the count (along with time & time zone)
• Analytics no longer lives on the POD, so it is no longer migrated during a POD move. For this reason, it no longer needs time to re-populate after a POD move, and should be available for immediate use.

        Customer Responsibilities

• Verify Business Manager instances and storefronts are up.
• Verify code upload works properly.
• Verify connectivity with third-party integrations, processing payments, completing orders, etc.
• Verify external firewalls are allowing inbound access from new “HF POD”

Verify outgoing mail, and confirm that shoppers are able to receive email after placing an order or signing up as a member on your storefront.

Tips for a seamless move

1. Work with internal QA resources to create a verification and validation process to perform post-realm move.
2. Schedule resources to be available and monitoring the realm move ticket from realm move start.  Update the ticket immediately if an issue is encountered.
3. Reschedule any data or code replications that are scheduled to occur during the realm move window (9 pm ET day prior - 7 am ET day of).  Any replications running while the move is occurring will result in a failed job that will need to be manually cleared after the move.