Skip to Content
Technical Articles

Common MTA deployment errors for FIORI applications

Hello friends,

I am recently into a Cloud foundry application development and I faced a lot of issues regarding the MTA deployment. It took a while to resolve all of the issues while referring the SAP forums and blogs. This actually made me to post this blog mentioning the common errors to all the developers who are starting with SAP Fiori in cloud foundry.

To start with the deployment at first we should have an application which is ready to be deployed. Hope this will be familiar to many of the Fiori developers, still I am just mentioning the major points involved.

  • Configure the cloud foundry end point in SAP web IDE

CF_Endpoint

  • Create a new MTA project from the template as shown below. Make sure Use HTML5 Application Repository is checked at the final step.

New%20MTA%20project

New MTA project

  • Add the UI5 module in to the project by using the following option.

UI5%20Module

UI5 Module

  • Define all your specific application files in the newly created UI5 module by following the standard Fiori application development guidelines and standards.
  • Build the application, which will generated mta_archives folder
  • Now deploy the application using the deploy option on the generated .mtar file as below.

Deploy%20.mtar%20file

Deploy .mtar file

During the deployment the most common issues are mentioned below :

Quota limit exceeded. Instance creation not allowed. 

Deployment may get failed due to size limitations in the sub account to which we are trying to deploy the application.

Any error specific to the quota limit of the cloud foundry account can be rectified by checking the Entitlement under your sub account.

Entitlement

Entitlement

Make sure that Application Run time and HTML5 Applications are left with enough balance if not update the values by clicking the Configure Entitlements button at the top.

Maximum file length exceeded

Error description for the MTA project- test:

Error executing application “test_ui_deployer”: Deployment of html5 application content failed [Deployment Id: xxxxxxxxxxxxxxxxxxxxxxxxxxxx] Error: Error while uploading resources to Server; Status: 400 Response: “Upload application content failed { CODE: ‘1001’ } validation error: Error while parsing request; Error: maximum file length exceeded”

 

This is the most common error as soon as the Fiori applications become big or the web-content is increasing with more supporting files such as pdf’s, images etc. In order to rectify this issue we would require the Command Line Interface (CLI), as we are not able to update the value from mta.yaml.

To set up the command line interface please refer the following posts

  1. Download and install the CF CLI
  2. Configure the proxy setting

Since the application and the dependent service instances are already deployed in the cloud foundry (as part of the .mtar file deployment during the initial try), the next step is to modify the sizeLimit of the app-host service instance. This particular service instance can be spotted in mta.yaml file and the same instance will be present in the Service Instance section of the Cloud Foundry Cockpit.

app-host

app-host

In order to update the sizelimit of the specified service, create a json file with ‘size-limit.json’ and update the file with the following value.

{
“sizeLimit”:4
}

Then execute the following from Command Line Interface ,

cf update-service {service-name} -c {.json path}

In the specified example it will be cf update-service test_html5_repo_host -c size-limit.jsonas we are executing the command from the same folder where the size-limit.json is present. If not the last argument should be the path of the size-limit json.

After the service instance is successfully updated, change the type definition in mta.yaml as below, as the service instance is already existing.

updated%20app-host

updated app-host

Now rebuild the application and deploy the latest generated .mtar file. If the issue persists, increment the sizeLimit value to 8,12, 16, etc… until the deployment is success. Make sure the value is integer.

Timeout Error:

As the MTA project updated with more UI5 modules, the deployment may fail while triggering the deployment from Web IDE (may be you can check with SAP Business Application Studio, if the issue persists there). There will not be any specific errors as well to identify the root cause. There are certain cases where the error message says deployment failed with 0 conflicting processes. In both cases the deployment will not be succeeded if we rely on Web IDE (This is the known issue with Web IDE, which SAP Web IDE team is currently working). In order to overcome the issue, please follow the below steps.

  • Build the application from Web IDE.
  • Export the .mtar file into the local directory
  • Trigger the deployment from the Command Line Interface by using the following command: cf deploy {name of the .mtar file}  for eg: cf deploy test_0.0.1.mtar

Hope the above steps helps everyone.

Thanks and Regards,

Arun

 

Be the first to leave a comment
You must be Logged on to comment or reply to a post.