Synchronize your applications in both data centers to maintain their functionality in case of a downtime.
Make sure that you transfer changes on one of your applications to the one in the other data center, as well, so that its functionality is not interrupted in case of a failover.
Keeping your two applications in sync does not necessarily mean that both applications need to be identical. If you want to offer only a reduced set of functions in your secondary application, we recommend to visually mark it as your backup. In this way, your users are constantly reminded that they are using the backup version and should switch back to the primary one once it is available again.
There are three different ways to synchronize your applications in the primary and the secondary data center:
-
Orchestrate your applications manually. See Synchronize Your Applications Manually.
-
Orchestrate your applications with the help of a continuous integration and delivery pipeline. See Use a Continuous Integration and Delivery Pipeline.
-
Orchestrate your applications through a combination of the Solution Export Wizard and the SAP Cloud Transport Management service. See Use the Solution Export Wizard and SAP Cloud Transport Management.
You can orchestrate your applications through a combination of the solution export wizard and the SAP Cloud Transport Management service.
-
You have deployed the applications you want to synchronize in two different subaccounts in the Neo environment. See Create Subaccounts Using the Cockpit.
-
You have a subaccount in the Cloud Foundry environment. See Create Subaccounts Using the Cockpit.
-
You are subscribed and have access to the SAP Cloud Transport Management service. See SAP Cloud Transport Management and Initial Setup.
-
In SAP Cloud Transport Management, you have defined a transport route from your development system to your failover system. See Configuring the Landscape.
In your subaccount in the Neo environment hosted in your primary data center, use the solution export wizard to export the changes you have made to your application to the SAP Cloud Transport Management service. From the Transport Management service, which is hosted in your subaccount in the Cloud Foundry environment, transport your changes to the backup application in your subaccount in the Neo environment in the secondary data center.
The following figure illustrates this procedure:
Synchronization Through Solution Export Wizard and Transport Management
You can also use the solution export wizard independently from SAP Cloud Transport Management by manually uploading your exported changes to the target account.
-
In the cockpit, navigate to your subaccount in the Neo environment, in which your HTML5 application is deployed. See Navigate to Global Accounts and Subaccounts in the Cockpit.
-
From the navigation pane, choose Solutions.
-
To access the solution export wizard, choose Export. For more information, see Exporting Solutions.
-
In the Select Components section of the Solution Export Wizard dialog, select the components of your HTML5 application you have changed.
The solution export wizard can automatically resolve dependencies, for example, by selecting corresponding roles.
-
In the Export options section, select Transport Management Service to hand over your MTA archive to SAP Cloud Transport Management. For more information about MTA archives, see Multitarget Applications.
-
In the cockpit, navigate to your subaccount in the Cloud Foundry environment. See Navigate to Global Accounts and Subaccounts in the Cockpit.
-
From the navigation pane, choose Subscriptions.
-
On the Transport Management Service tile, choose Go to Application.
-
From the navigation pane, choose Transport Nodes and select the target node.
-
In the IMPORT QUEUE tab, select the MTA archive you have exported with the help of the solution export wizard.
-
Choose Import.
Related Information
Blog - Solution Export Wizard – ease modeling and export of solutions as MTA
Blog - The new cloud-based Transport Management Service
Blog - SAP Cloud Transport Management service generally available
You can synchronize the deployment of your applications in two different data centers by using a continuous integration and delivery (CI/CD) pipeline. Configure it for multi-deployment so that in the final stage of your CI/CD pipeline, your changes are automatically deployed to two subaccounts in parallel. In our case, these subaccounts are hosted in different data centers. For more information about subaccounts, see Managing Subaccounts.
The following figure illustrates this procedure:
Synchronized Deployment Through a CI/CD Pipeline
Use a pre-configured pipeline of project "Piper" and adapt it for multi-deployment to your two subaccounts in different data centers. For more information, see project "Piper".
Related Information
Continuous Integration (CI) and Delivery (CD) Overview
Overview of SAP Offerings for CI and CD
Blog - Continuous Delivery with Jenkins Pipelines
You can orchestrate your applications manually by duplicating your modifications in both data centers, for example, by mirroring from Git repositories.
The following figure illustrates this process:
Manual Synchronization
With this approach, you can decide yourself which of your changes to transport from one data center to the other. Therefore, synchronizing your applications manually allows you to maintain two non-identical applications, for example, if you want to visually differentiate between the UIs in your primary and the backup version.
With regard to the relatively high effort needed for this approach, we recommend it only if you do not plan regular updates or changes to your application.