Preface – This post is part of the SAP Multi-Target Application (MTA)  series.

Introduction

A Multi-Target Application (SAP MTA) is a package comprised of multiple libraries, application and resource modules. These have been created using different technologies and deployed to different runtimes but have a common life-cycle. You can bundle different modules together, describe them along with their inter-dependencies to other modules, services, and interfaces, and package them in an Multi-Target Application(MTA) . Please read MTA Documentation by SAP for more info.

A Multi-Target Application can have both UI5 and other open source app implementation. We can deploy Java, Node.js and all other SAP cloud platform services.

SAP MTA Architecture

MTA Architecture

It is clear from the architecture flow diagram above that using our UI5 App, we will be calling a Node.js API which in return will be calling a Blockchain Application Enablement Service. This Enablement Service will help us to communicate with the Multichain environment. Both this UI5 App and Node.js files will co-exist under MTA Application that we will discuss in upcoming sections.

Prerequisites and Restrictions

We need to consider the following limits for the SAP MTA deployment on SAP Cloud Foundry deploy service:

• Maximum size of the MTA archive: 4 GB
• Maximum size of MTA module content: 4 GB
• Maximum size of MTA resource content: 1 GB
• Maximum size of MTA descriptors (mtad.yaml and MANIFEST.MF): 1 MB

References

To learn more about SAP MTA, we recommend to go through following SAP official documentations: