Once the MTAR is file is generated, then export the MTAR file to personal directory folder. mtar and it can have multiple modules to deploy at one time.Īlternatively you can use MTAR builder(command line tool) to package the MTAR file based on yaml configuration. When the DB module is ready for deployment, Select the Project header and build it, with that an MTA Archive file is generated at the top of the project, this file has an extension of. All of this happening in Dev space of Web IDE. So version control and dependencies are managed very effectively GitHub. Upon the completion of build of Developer_2, a different HDI container is created for Developer_2 in the database, it is independent of Developer_1 container objects, thereafter developer_2 can commit the code back to GitHub with the latest changes.

In Web IDE for HANA, MTA project source code is checked into/Committed GitHub by Developer_1, if the other developer also making changes to the same project, he/she can pull that project code from GitHub and make the necessary changes and build it. In the above example scenario, Developer_1 created an MTA project in Web IDE for HANA, with a DB module which has hdbtable and Calculation views as the development artifacts, upon the build, HDI container is created in the database as run time objects. The below picture describes the very high level process of development and deployment, explained in 3 major steps. However, the deployment process is going to be same for Node module or html module deployments as well. In this document, I am going to take an example of MTA project’s db module which creates HDI-container objects in the database and then deploy them in QA and Production systems. Basically XSA is an On-Premise offering of Cloud foundry run times and deployments process in general. With the XS advanced server, the development and deployment process has been changed a bit from XS classic, on tooling prospective now we got Web IDE for HANA, GitHub and XS Command line tools for the purpose of object development, Source control and deployment respectively. Also, I will explain different options available for deployment of XSA objects. In this blog, I am going to describe the process of HANA XSA application deployment in a Dev - > QA - > Prod system landscape at a very high level.

Mta sa as bind