Performing a Manual Deployment

Set Up SAP HANA Cloud Instance.

First, you need to set up the SAP HANA Cloud instance in your BTP account.

Note

Note that screens in the cloud may change. So, the screenshots in this solution may differ slightly from the screens in your training system.

1. Enter the subaccount that you are using for this course.

   

2. Enter the space that you are using for this course (for example, the dev space).

   

3. In the navigation on the left, choose SAP HANA Cloud.

   

4. Select Create and choose SAP HANA database.

   

   You will be redirected into SAP HANA Cloud Central for the instance creation. When being asked to authenticate, use your SAP Account user credentials that you used to create your SAP BTP account. You should then see the following dialog. Select SAP HANA Cloud and click on Next Step.

   

5. The Location settings should point to your Cloud Foundry org and space.

   Use the following settings for the remaining fields:

   Key	Value
   Instance Name	hana-cloud
   Description	HANA Cloud used for exercises
   Administrator Password	create a password according to the password policy

   

6. Click on the Next Step button.

7. The default parameters for your SAP HANA Cloud database display. Select the Next Step button.

   

8. You have to select an availability zone for the SAP HANA Cloud Database. Confirm the default settings by clicking on Next Step.

   

9. You will see the SAP HANA Database Advanced Settings dialog. Here, you can allow or deny certain IP addresses for connection to your database instance.

   You also find a setting to connect the database to remote sources via the Cloud Connector. This is especially useful in replication use cases, where you need to replicate data from on-premise sources to your SAP HANA Cloud instance. In our use case, this setting is not required.

10. Select the Allow all IP addresses option, then select the Review and Create button.

    

11. The Review page displays. Review the values and choose theCreate Instance button.

    

12. The overview of your database instances appears. There should be a new entry for your hana-cloud instance with StatusCREATING.

    

    The process will take several minutes to complete. Once done, the Status should switch to RUNNING. Use the Refresh button to update the status. Your SAP HANA Cloud instance is now ready to be used.

    

13. Return to your BTP subaccount and to your cloud foundry space and select SAP HANA Cloud.

14. Your hana-cloud instance displays in the SAP HANA Database Instances overview.

    

Prepare the Project for Production.

1. Configure SAP HANA Cloud in the project.

   While we used SQLite as a low-cost stand-in during development, we’re going to use a managed SAP HANA database for production:

   Code snippet

   Copy code

   cds add hana --for production

   Copy code

   Use the displayed code.

2. Enable XSUAA-based Authentication.

   Code snippet

   Copy code

   cds add xsuaa --for production

   Copy code

   This will also generate a xs-security.jsonfile, which has to be configured. This file stores the configuration for the xsuaa-service on SAP BTP.

3. Generate the xs-security.jsonfile content.

   Code snippet

   Copy code

   cds compile srv/ --to xsuaa > xs-security.json

   Copy code

4. Create the MTA descriptor file for MTA-Based deployment.

   This will generate the mta.yaml file, which contains all the services for the multi target application (MTA) deployment.

   Code snippet

   Copy code

   cds add mta

   Copy code

5. Open the mta.yaml file and specify the custom domain in the redirect-uris parameter for the xsuaa resource:

   Code snippet

   Copy code

   
   oauth2-configuration: # <-- add this
    redirect-uris:
    # example: - https://risk-management-approuter.cfapps.eu10-004.hana.ondemand.com/login/callback
    - https:///login/callback
   

   Copy code

   It should be added to the config of the resource definition. At the end it schould look like:

   Code snippet

   Copy code

   resources:
   
   
   - name: risk-management-auth
     type: org.cloudfoundry.managed-service
     parameters:
       service: xsuaa
       service-plan: application
       path: ./xs-security.json
       config:
         # [...]
         oauth2-configuration: # <-- add this
           redirect-uris:
           # example: - https://risk-management-approuter.cfapps.eu10-004.hana.ondemand.com/login/callback
           - https:///login/callback
   

   Copy code

6. Add the managed approuter as gateway to the project.

   This will set up the app router, which acts as a single point-of-entry gateway to route requests to our app. In particular, it ensures user login and authentication in combination with XSUAA. This command will also add the approuter module to the mta.yamlfile.

   Code snippet

   Copy code

   cds add approuter --for production

   Copy code

7. Configure the approuter by opening the xs-app.jsonfile in the app/directory of your project.

   Code snippet

   Copy code

   
   {
     "welcomeFile": "/app/risks/webapp/index.html",
     "routes": [
       {
         "source": "^/app/(.*)$",
         "localDir": "./",
         "target": "$1"
       },
       {
         "source": "^/service/(.*)$",
         "destination": "srv-api"
       }
     ]
   }
   

   Copy code

   This will set up the routing to the SAP Fiori Elements file and to the backend service.

   Note

   The previous steps are required only once in a project’s lifetime. With that done, you can repeatedly deploy the application.

8. Freeze Dependencies

   Deployed applications should freeze all their dependencies, including transient ones.

   Code snippet

   Copy code

   npm update --package-lock-only

   Copy code

   Note

   Note: You should regularly update your:package-lock.jsonto consume latest versions and bug fixes. Do so by running this command again, for example, each time you deploy a new version of your application.

9. Build MTA-project.

   The following command will build the project based on the mta.yamlfile. The output will be stored in the gen/folder.

   Code snippet

   Copy code

   mbt build -t gen --mtar mta.tar

   Copy code

10. Deploy the generated MTA-project.

    Odds are, that you have to log in to your Cloud Foundry org and space first. For this run cf loginfirst and provide the necessary information.

    Code snippet

    Copy code

    cf deploy gen/mta.tar

    Copy code

    This process can take some minutes and finally creates a log output like this:

    Code snippet

    Copy code

    [...] 
    Application "risk-management" started and available at "[org]-[space]-risk-management.landscape-domain.com"
     [...]
    

    Copy code

Inspect Deployed Apps in SAP BTP Cockpit.

1. Visit the "Applications" section in your SAP BTP cockpit to see the deployed apps.

   

2. Click on the risk-management application and then on the application route.

   

3. You will notice that the external data can't be retrieved, since the API key was not set yet. For this, go back one step and select the risk-management-srv application. Click on User Provided Variables in the navigation bar on the left side and set the API key.

   

4. Now, click on Overview on the left side and then restart the application to ensure that this variable change take effect.

   

5. Now review the app again, by opening up the risk-managementapplication.

Platform Simulation

Click on the Start button below to open a simulation of the platform. Then follow the step-by-step instructions to deploy a CAP Application.

ExerciseStart Exercise