Today I am going to discuss about the Transport and Deployment of Artifacts in WEB IDE : HANA XSA. In the below diagram I am going to discuss about the different deployment option for MTA  Application.

Now describe each and every Application Artifact’s deployment process in Details :

1. Artifact Deployment using SAP ChaRM:

A. First Configure CTS+ for SAP HANA in SAP Solution manager.

Related SAP Link –

https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=447468169#ConfiguringCTS+inSAPSolutionManager7.1and7.2-1.1.CTS+forSAPHANA

B. Configure an HTTP Destination .

C. Configure the Transport Organizer  UI.

D. Configure the XSA Transport Landscape .

Reference SAP link –

https://www.sap.com/documents/2015/07/6ac162e3-527c-0010-82c7-eda71af511fa.html

E. Configure HANA systems to CHARM as Non SAP system(TMS System Landscape Configuration).
F. Configure source and Target systems.

G. Create a CTS Transport using STMS and attach the .MTAR archive to the transport and moved to the configured target.

The overall dataflow will look like below for the SAP ChaRM with CTS+ :

https://assets.cdn.sap.com/sapcom/docs/2016/12/98ccd65a-9c7c-0010-82c7-eda71af511fa.pdf

2. Deployment Using GitHub and CI/CD implementation : 

How to integrate GitHub in web IDE and do push and pop operation to put and fetch data from Git and available in the below link –

https://blogs.sap.com/2022/12/15/mta-project-integration-with-git-in-business-application-studio-hana-xsa/

Now we will discuss about the Git interaction with CI/CD to automate the code integration –

The configuration steps is given in the GitHub with the below reference link –

https://github.blog/2022-02-02-build-ci-cd-pipeline-github-actions-four-steps/

A CI/CD pipeline for SAP HANA extended application services, advanced model comprises the following steps:

• Push your code changes to a source code management (SCM) tool of your choice. The push event to the SCM system triggers the CI process.

• In the CI build, the Cloud MTA Build Tool (MBT) triggers the technology-specific compilers for the respective modules contained in the MTA. For more information, see 

• The Cloud MTA Build Tool packages the artifacts from each module into one archive file with the extension .mtar.

• The build result is automatically deployed into an environment for automated testing during the CI build. The CI build may contain different tests, such as static code checks for the JavaScript sources  and automated user interface tests .

• The MTA archive is deployed to the production environment.

Reference URL :

https://help.sap.com/docs/CICD_OVERVIEW/3324745951b44b578bd65221d2ff8f9a/55242ddaa08d4f3190fd06171b5f85f5.html

3. Deploy with  XS Deploy using command line or Using Web IDE Interface : 

XS advanced run time is installed in HANA XSA server. But if you want to deploy using command line  from your local machine you follow the below steps :

1. Install XS CLI client tools locally.
2. Configure command-line tools to use the NPM Registry to resolve package dependencies if required.
3.  Execute below command to deploy your .mtar file –

A. xs deploy  student.mtar

4.  to check the application use this two command –

A. xs services and xs app.

Reference URL –

https://help.sap.com/docs/SAP_HANA_PLATFORM/400066065a1b46cf91df0ab436404ddc/0919e1cbd20646aead930a5743cfa7e1.html

You can also deploy the mtar file from Web IDE graphical interfaces  after building the MTAR files-

4. Deployment by ABAP Transport using SCTS_HTA_TOOLS :

To use this deployment ABAP stack should be setup on the SAM SID on top of HANA server.

ABAP transport user to transport the attached MTAR files to the corresponding system and import them to the equivalent XSA space.

The configuration is available in the below link –

https://launchpad.support.sap.com/#/notes/2569651

This is all about HANA XSA deployment. Hop it will help.