Databases in SAP BTP

Introduction

Mendix needs access to a relational database back end and can run using different types of database. For deployment to SAP BTP, you have the choice of PostgreSQL, Hyperscaler Option, or SAP HANA.

Running Mendix on PostgreSQL, Hyperscaler Option

Select the postgresql-db (PostgreSQL, Hyperscaler Option) database service from the Available Services.

Upload a file which contains the configuration for this database. Click Browse to select your configuration file. You can use the SAP Hyperscaler PostgreSQL Configurator to help you create the configuration file. For more information, refer to the Parameters section of PostgreSQL on SAP Business Technology Platform, Hyperscaler Option.

During the creation of the environment, the selected PostgreSQL, Hyperscaler Option service is added to your space. When you deploy your app, the app is bound to it.

This database service should not be unbound from your environment. For more information on required services, see the Services Tab.

SAP Hyperscaler PostgreSQL Configurator

To get help to create the configuration file, click Configurator.

You can set the required values for your SAP Hyperscaler PostgreSQL database. Tooltips describe the values which you need to provide.

Click Upload Configuration To Service to automatically apply the generated configuration to the PostgreSQL, Hyperscaler Option database service. Alternatively, click Download Configuration File to create the file which you can then use on the Services tab to configure your PostgreSQL, Hyperscaler Option database.

Running Mendix on SAP HANA

SAP HANA Configuration for Full Accounts

To run a Mendix application on SAP BTP using SAP HANA as the database, there are two options. Both options need to be set up in the SAP BTP cockpit. You can choose one of the following options:

• Provision the SAP HANA DB Service and make it available in your application space.
• Provision SAP HANA Cloud and make this service available to your application space.

Once one of these services is available, you can use the SAP Cloud deployment functions of the Mendix Portal to deploy your app and use the HANA_SCHEMA service to bind your application to the provisioned service. The HANA_SCHEMA creates a separate schema on the SAP HANA Database which isolates your application's data from other applications. In this way, the SAP HANA DB/Cloud Service is shared across applications.

If you have issues with your app running on SAP HANA, use the SAP BTP cockpit to investigate. The Mendix Portal does not have information on the status or configuration of the SAP HANA service.

SAP HANA Configuration for Trial Accounts

For new trial accounts, you can bind your Mendix app to a trial SAP HANA database. Choose hanatrial-securestore from the drop-down of supported databases.

Some older trial accounts do not include hanatrial-securestore. In this case, you can get an error when you try to deploy your Mendix app saying that provisioning has failed because service hanatrial with plan securestore is not found.

SAP HANA Performance Tuning

If your SAP HANA database has performance issues, you can improve it by performing the following tuning:

1. Obtain the following service binding credentials from the Environment Variables of SAP BTP cockpit, or via the CLI:

   • Host
   • Url
   • Schema
   • Password
   • User

2. Go to the Runtime tab of your app environment.

3. Enter the following unsupported environment variables with the associated values, using the values taken from the service binding credentials:

   Variable	Value
   MXRUNTIME_DatabaseHost	{host}
   MXRUNTIME_DatabaseJdbcUrl	{url} + &nonBlockingIO=false&timeZonePerObject=false&packetSize=130000&closeHandlesByCleaner=false&transactionalLobs=false&maxLazyDroppedStatements=100&statementCacheSize=500&deferredPrepared=true
   MXRUNTIME_DatabaseName	{schema}
   MXRUNTIME_DatabasePassword	{password}
   MXRUNTIME_DatabaseUserName	{user}
   MXRUNTIME_DatabaseType	SAPHANA

4. Go to the General tab and restart your app to apply the changes.

The additional parameters that you added to the URL in the MXRUNTIME_DatabaseJdbcUrl set the following tuning parameters: