Skip to Content

What is the best way to transport a Fiori Mobile App between environments?

Aug 02, 2017 at 02:08 AM


avatar image

Does anyone have suggestions as to best practice for transport Fiori Mobile apps (from development to test to production)?

I plan to start by deploying the html5 application and portal site content to test. Then I will need to trigger a Fiori Mobile build, perhaps from Web IDE on the test sub account. Is there anyway to transport the app configuration (from Mobile Secure Cloud) from the dev sub account, or do I need to do that again from scratch, possible leading to discrepancies between the apps for the different environments?

I notice that the sub account ID/GUID is listed in files like .project.json. Another approach would be to move the whole app at file level using GIT, then just change the entries which refer to the dev sub account. Then this app could be deployed to the Fiori Launchpad site in test. Would this be a better approach?

The customer does not have a Continuous Integration (CI) set up

What has everyone else been doing? What would you recommend?

Thanks in advance for your assistance

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

3 Answers

Prithviraj Rajpurohit Aug 03, 2017 at 08:27 AM


Please go through below thread if that helps.



Show 2 Share
10 |10000 characters needed characters left characters exceeded

Thanks Prithviraj, but I think that thread is about on-prem regular Fiori apps. I'm talking about Kapsel hybrid apps which are built using the Mobile Service for SAP Fiori, which is a Cloud Platform service.

Britt Womelsdorf
Aug 03, 2017 at 12:08 PM

Hey Mike -

I am doing some research on my end, but I think unfortunately there is no automated process. So you're thinking that you'd check the whole project into GIT, then clone it to your Prod (or UAT) instead of Web IDE, update the values in the .project.json file, then trigger a rebuild manually?

Sounds like a great blog post when you are done :-)

I've already got some question out to people on the teams and will let you know what I find out.


Show 2 Share
10 |10000 characters needed characters left characters exceeded

Thanks for your input Britt. I will see how I get on. I'm thinking of creating a dedicated branch for test and one for prod. I think I can merge in later changes in the main files, but exclude the files that differ between environments. If you do get any input from the technical teams please pass it on.

Of course, it would be great to have a download/upload feature like we have with html5 applications so that we get complete consistency between environments.


Hey Mike - As we continue to flesh out this topic we'll make sure that you stay informed! (Thought you might have to remind me :-))

avatar image
Former Member Aug 03, 2017 at 08:32 PM

Hi Mike,

Agree with Britt! There seems to be no automated process here.

My client uses Airwatch to distribute the apps.

Let's say, we have release latest build to QA:

  • In my web-ide, i go into neo-app.json >> ensure the destination points to my QA box (say, GW)

Note: GW is a destination configured in Cockpit that points to QA-box here

  • Export and upload the offline project zip to the Admin team
  • Admin generates & distributes the build to Airwatch
  • Testing team downloads & installs the latest build from Airwatch & starts testing it...

-Cheers, Sai

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Thanks for you input Sai. Unfortunately we don't manage the devices so we need to make the app publicly available, through Mobile Place.