This tutorial requires some resources in the cloud. If you don’t already have an Sap Cloud Platform user/account just open a landscape and one will automatically be created for you:

1. Open the SCP cockpit for an eu landscape and log on with your sap email and i/c/d-user password: https://account.hana.ondemand.com ; TODO: work out account reuse/authentication

Clone the repository, no account in github is required.

This tutorial requires the following command line tools which you already have pre-installed:

• cloud foundry command line tool (cf cli)

• MultiApps cf cli plugin

• mta build tool

cf api https://api.cf.eu10.hana.ondemand.com
cf login -u <user.email>@sap.com -o cafe_mta / cf auth ... in case of technical user
cf create-space <i/c/d/-user> -o cafe_mta
cf target -o cafe_mta -s <i/c/d-user>

The cf client marketplace command lists all available backing services SCP provides in your space. The services command lists all created service instances in the space. The following create an application logs service instance with plan lite named 'fortune-logs' and a postgresql database one with a dev plan and name: 'fortune-service-database' .

*logs traced by apps, bound to an application logs service can be browsed in the platform’s application logging service 'kibana' ui

Now push the front-end application fortune-teller-ui with the following

*a cf push manifest file describes one or many apps with their properties like environment variables, memory configurations, bound services etc.

You can check out how your app looks like at it’s platform generated route. List the app details to see it’s route and open it in a browser. look for route: <>

The app url is constructed as the https protocol on that route: https://<route>; e.g. https://fortune-teller-ui-grumpy-wombat.cfapps.eu10.hana.ondemand.com

The app has no back-end to provide content yet; It’s circuit breaker(hystrix) should fall back to a default message and no new fortunes will come with refreshing. Let’s add a hystrix dashboard app to monitor how it behaves:

Let’s configure the dashboard with the front end app url via an environment variable:

*a restart is required in order for the app to read it’s newly set environment variable.

Let’s continue building the application with it’s back-end app. The previously created db service will automatically bind to the app as described in the manifest

Now let’s tell the front end app where to reach the back end. You already found the ui app’s route. Find the backend app’s route and amend :443 (https port). Set it as FORTUNE_SERVICE_FQDN variable to the ui app:

Go back to the ui app and refresh it a couple times - each time a random fortune should be displayed for your destiny to follow.

Congratulations, you brought your application to life 🎉 !

Now let’s delete everything to free the resources.

Let’s assemble an MTA archive! The mta archive is a (zip)package, containing the application’s full or partial deployable content. It is deployed at once with a single command. It’s versioned and may easily be transported and consistently applied to multiple environments e.g. dev/test/prod.

Assemlbe with the already installed mta build tool mbt:

You’ll find a new directory mta_archives created in the project root. Inside is the new *.mtar archive.

Now simply deploy it to the cloud with the following command ⚡ :

That is it 🎉 !

You may find info of the mta with the following commands

Congratulations on your first mta deployment 👏 !

Instead of cf deploy this time run cf bg-deploy

You now have two versions of the app running in parallel on different routes(idle and live). You may examine the new version of the application and verify it’s working correctly before switching the live version’s traffic to it. You should see minor changes in ui’s style & a cheesy message appended to the fortunes by the backend app.

After making sure it works as expected, run the following command. Find the deploy process id printed in the bg-deploy command output or via the cf mta-ops command.

Enjoy your new app version, deployed without down time 👏 !

cf undeploy fortune-teller --delete-services