A Multi-Target Application (MTA) project is comprised of one or several modules of different types. You learned about module types in a previous lesson. Here, we focus on the SAP HANA Database (HDB) module type.
However, it is important to understand some key settings of an MTA project. Some of them do not have to do only with HDB modules, but are related to the lifecycle of a project in general.
When you create a new project, you have to define a few parameters. Let’s review these parameters.
Key Settings of an MTA Project
Setting | Description | Example |
---|---|---|
Project name | The name given to the new project in your workspace | proj1 |
Schema version | Version of the MTA specification | _schema-version: "2.1" |
Application ID | The identifier of the multi-target application, used during deployment. It must be unique in the target environment, and uses the reverse-URL dot-notation. | ID: com.sap.mta.sample |
Application version | A three-level application version number (Major.Minor.Patch), used to handle successive deliveries of the same application to runtime environments. | version: 1.0.3 |
Description | A free text describing the purpose of the MTA. |
All these settings are stored in the project descriptor file, which is named mta.yaml. This file can be edited with the code editor. It is also automatically updated based on some configuration you perform on the project, in particular when you add an HDB module or define a connection to an external schema or another HDI container.