Deployment

Objectives
After completing this lesson, you will be able to:

After completing this lesson, you will be able to:

  • Explain how to deploy using SAP HANA XSA

Deployment

Manual Deployment Using SAP HANA XSA

Without the DevOps-style development approach, projects must be deployed manually. Before the deployment can be started, a build of the latest project version must be created. In the process of this build, SAP Web IDE creates a multi-target application (MTA) archive. This .mtar file can be found in the mtar_archives folder which is automatically created after the project build was finished. Afterward, this .mtar archive can then be deployed to the SAP HANA database via XSA.

DevOps-style Deployment Using SAP HANA XSA

In contrast to the manual deployment process shown previously, utilizing the DevOps-style development process enables a much more automated and thus agile deployment. After the latest version of the project is released to the Git release branch, the CI/CD tool pulls the changes and executes a deployment via XSA. In this scenario the CI/CD tool basically replaces the developer and undertakes the necessary steps to deploy the project via XSA. Depending on the settings of the CI/CD tool, this can happen on a time schedule (e.g. every day) or based on a trigger (e.g. as soon as a new release is published).

Jenkins

Log in to track your progress & complete quizzes