Siemens MindSphere

1 Introduction

MindSphere is the cloud-based, open IoT operating system from Siemens that lets you connect your machines and physical infrastructure to the digital world. It lets you harness big data from billions of intelligent devices, enabling you to uncover transformational insights across your entire business.

This documentation is meant for Mendix developers who want to deploy a Mendix app to the MindSphere Platform.

To help you with your first MindSphere apps, there is also an example app which contains modules which call the MindSphere APIs. See How to Use the Siemens MindSphere Pump Asset Example App for more information.

2 Prerequisites

To deploy your app to MindSphere you need the following prerequisites.

• A MindSphere user account on a developer tenant
• Mendix Studio Pro
• The Cloud Foundry Command Line Interface (CF CLI) – this can be downloaded from https://github.com/cloudfoundry/cli
• A Cloud Foundry role which allows you to push applications, such as SpaceDeveloper (help in setting up Cloud Foundry users can be found in the MindSphere Cloud Foundry How Tos)
• A MindSphere developer role: either mdsp:core:Developer or mdsp:core:DeveloperAdmin

3 Including Required MindSphere Modules

You must customize your app to allow it to be deployed to MindSphere, registered via the MindSphere Developer Cockpit, and shown in the launchpad. This is done through MindSphere customization modules. There are two ways to include the customization you need in your app.

3.1 Option A: Using the MindSphere App Template

The MindSphere Starter Application in the Mendix App Store contains all the modules and styling which you need to create an app you want to deploy to MindSphere.

Open Studio Pro (version 7.22.2 or above) and follow these steps:

1. Click the icon in the top-right of the menu bar to open the Mendix App Store.

   

2. Enter MindSphere in the search box, and press Enter.

3. Select MindSphere Starter Application in the search results.

   

4. Click Download to create a new app project using this app.

   

5. To start the new app project, confirm where to store the app, the app name, and the project directory, then click OK.

   

3.2 Option B: Customizing an Existing App

If you have an existing app which was not based on the MindSphere app template, you must import the required customization. The three modules which must be imported are:

• MindSphere SSO from the Mendix App Store here: Siemens MindSphere SSO

This module enables users who are logged in to MindSphere to use your app without having to sign in again. It also enables you to test your app locally. For more information, see the Single Sign-On section of MindSphere Module Details.

• MindSphere OS Bar Connector from the Mendix App Store here: Siemens MindSphere OS Bar Connector

This integrates the mandatory MindSphere OS Bar with your app. For more information, see the MindSphere OS Bar section of MindSphere Module Details.

• MindSphere Theme Pack (MindSphere_UI_Resources) from the Mendix App Store here: Siemens MindSphere Theme Pack

This applies MindSphere styling to your app and includes some additional custom files which are required for the correct operation of your app. For more information, see the MindSphere Theme Pack section of MindSphere Module Details.

4 Configuring the Modules

Now that you have your new app, or have imported the MindSphere modules into an existing app, you need to configure the modules to allow your app to work with MindSphere.

4.1 Configuring Single Sign-On (MindSphereSingleSignOn)

The following items in the MindSphereSingleSignOn module need to be configured.

4.1.1 CockpitApplicationName

Enter the name of your app as registered in the MindSphere developer portal as the value of CockpitApplicationName.

These two values must be identical and must, therefore, fit the constraints listed in the App Name section of MindSphere Development Considerations.

4.1.2 MindSphereGatewayURL

This is the URL of the MindSphere gateway and is of the following format:

https://gateway.{Region}.mindsphere.io

This needs to be changed depending on the {Region} your app is running. The default value is for MindSphere running on AWS:

https://gateway.eu1.mindsphere.io

If your app is running on Mindsphere on Azure change this constant to:

https://gateway.eu2.mindsphere.io

4.1.3 PublicKeyURL

The value of this constant is shown below:

https://core.piam.{Region}.eu1.mindsphere.io/token_keys

This needs to be changed depending on the {Region} your app is running. The default value is for MindSphere running on AWS:

https://core.piam.eu1.mindsphere.io/token_keys

If your app is running on Mindsphere on Azure change this constant to:

https://core.piam.eu2.mindsphere.io/token_keys

4.1.4 RegisterSingleSignOn

Add the RegisterSingleSignOn microflow as the After startup microflow or added as a sub-microflow of an existing after startup microflow.

If you are are modifying an existing app, you can do this on the Runtime tab of the Project > Settings dialog, accessed through the Project Explorer.

4.2 Configuring the MindSphere OS Bar (MindSphereOSBarConfig)

Change the OS Bar to show information about the app you are running.

This is configured as a JSON object held as the default value of the string constant Config in the MindSphereOSBarConfig module. The imported module has a correctly formatted set of example values.

Change the JSON to contain appropriate values for the following information:

• displayName – the display name of your app
• appVersion – the version number of your app
• appCopyright – app owner’s name and year of publication
• links – links to additional information about the app

More information on the structure and content of this JSON object, together with sample JSON, can be found in App Information, on the MindSphere developer site.

5 Deploying Your App to MindSphere

5.1 Pushing to Cloud Foundry

Before you continue, ensure you have fulfilled the prerequisites described in the section Prerequisites and configured the MindSphere modules as described in the section Configuring the Modules, above.

5.1.1 Creating a Mendix Deployment Package

To create a Mendix deployment package from your app, do the following:

1. Open your app in Studio Pro.

2. Select Project > Create Deployment Package….

   

3. Select the correct Development line and Revision.

4. Set the New version number and add a Description if required.

5. Change the path and File name if necessary.

Your deployment package will be created, and its location displayed in an information message.

5.1.2 Deploying the Application to Cloud Foundry using CF CLI

To deploy your deployment package, do the following:

1. Sign in to MindSphere CF CLI using a one-time code:

   • Enter cf login -a https://api.cf.{Region}.{mindsphere-domain} --sso
   • Open the URL printed by the CLI and sign in using your WebKey credentials to get a One Time Code
   • Enter the One Time Code in the CLI
   If you need to configure proxies for Cloud Foundry, use the Windows set command. For example, set http_proxy=http://my.proxy.ip:1234.

2. Select your org and space using the command:

   cf target –o {org_name} -s {space_name}
   

   If you cannot target your org or space, you probably need to be added to your org. See Cloud Foundry How Tos in the MindSphere documentation.

3. Create a PostgreSQL instance using the command:

   cf create-service postgresql10 {plan} {service_instance} [-c {parameters_as_JSON}] [-t {tags}]
   

   For example: cf create-service postgresql10 postgresql-xs myapp-db

   For more information see Using the a9s PostgreSQL on the MindSphere developers site.

   Each Mendix app needs its own database. Do not bind more than one app to a database as both apps will not work properly. Create a new database instance instead.

4. Depending on your infrastructure and service broker usage, it may take several minutes to create the service instance. Check if your PostgreSQL service has been created successfully using the following command: cf services Your service should be listed, and the last operation should be ‘create succeeded’.

5. Ensure you are in the same folder as the package you wish to deploy.

6. Create a manifest.yml file with at least the following content:

       applications:
       - name: {app_name}
         disk_quota: {disk_quota_size}
         memory: {memory_size}
       services:
         - {service_instance}
   

   disk_quota_size and memory_size must be at least 512M to enable a Mendix app to run.
   See the Cloud Foundry App Manifest Attribute Reference for more information on valid specifications for memory and disk quota sizes.
   Each Mendix app needs its own database. Do not bind more than one app to a database as both apps will not work properly. Create a new database instance instead.

   For more information on the configuration of manifest files, see Configuring the manifest file on the MindSphere developers site.

7. Push your app to MindSphere using the command:

   cf push -p "{deployment_package_name}"
   

   For example: cf push -p "myapp.mda"

5.1.3 Cloud Foundry Stack

You should always use the latest available Cloud Foundry stack. The latest stack in MindSphere is cflinuxfs3. Apps pushed to MindSphere will use this stack.

You can specify that your app uses a specific stack using the following command line option when you push your app:

cf push -p "{deployment_package_name}" -s {stack_name}

For example: cf push -p "myapp.mda" -s cflinuxfs3

cf app {app_name}

For more information about Cloud Foundry stacks on MindSphere, see How Can I Find the Stack my App is using? in Cloud Foundry How Tos on the MindSphere Developer site.

5.1.4 Troubleshooting

If you have issues with deploying your app to Cloud Foundry, you can find additional information in Running a Cloud Foundry-Hosted Application – for Java Developers. Note that this is not written from the point of view of a Mendix developer, so some information may not be relevant.

Ensure that you have configured your proxy settings if these are required.

5.2 Setting up MindSphere Launchpad

5.2.1 Creating a New Application

To create a new app in the MindSphere launchpad, do the following:

1. Go to the Developer Cockpit > Dashboard.

2. Click Create new application.

3. Set the Type to Standard.

4. Set the Infrastructure to MindSphere Cloud Foundry.

5. Fill in the Display Name of your app, as you want it shown in the Launchpad.

6. Fill in the Internal Name of your app. This must be identical to the value of CockpitApplicationName which you set in the SSO module of your app.

7. Fill in a Version for your app.

8. Fill in a Description of your app, if required.

9. Click Edit icon to upload an App Icon for your app.

10. Fill in the Component > Name. This must be identical to the {app_name} you set in the manifest.yml file.

11. Click the + next to the component to add Endpoints.

12. Specify /** as the endpoint to allow you to access all endpoints relevant to your application, and click Save.

13. Fill in the Cloud Foundry Direct URL. This can be found using the cloud foundry command cf app {app_name}.

14. Set the Configurations > content-security-policy Value to the following (hover your mouse over the text and you will be able to copy the contents to your clipboard):

    If your app is running on MindSphere on AWS use Region eu1:

      default-src 'self' 'unsafe-inline' 'unsafe-eval' static.eu1.mindsphere.io feedback-static.mendix.com home.mendix.com;
      font-src 'self' static.eu1.mindsphere.io fonts.gstatic.com;
      script-src 'self' 'unsafe-inline' 'unsafe-eval' static.eu1.mindsphere.io feedback-static.mendix.com home.mendix.com;
      style-src 'self' 'unsafe-inline' static.eu1.mindsphere.io feedback-static.mendix.com home.mendix.com fonts.googleapis.com;
      img-src * data:;
      connect-src 'self' 'unsafe-inline'  *;
    

    If your app is running on Mindsphere on Azure use Region eu2:

      default-src 'self' 'unsafe-inline' 'unsafe-eval' static.eu1.mindsphere.io feedback-static.mendix.com home.mendix.com;
      font-src 'self' data: *.eu2.mindsphere.io uistorageaccountprod.blob.core.windows.net static.eu1.mindsphere.io fonts.gstatic.com;
      script-src 'self' 'unsafe-inline' 'unsafe-eval' *.eu2.mindsphere.io uistorageaccountprod.blob.core.windows.net static.eu1.mindsphere.io feedback-static.mendix.com home.mendix.com;
      style-src 'self' 'unsafe-inline' *.eu2.mindsphere.io uistorageaccountprod.blob.core.windows.net static.eu1.mindsphere.io feedback-static.mendix.com home.mendix.com fonts.googleapis.com;
      img-src 'self' static.eu1.mindsphere.io feedback-static.mendix.com home.mendix.com sprintr.home.mendix.com data: uistorageaccountprod.blob.core.windows.net;
      connect-src 'self' 'unsafe-inline' *;
    

    These content security policy (CSP) settings are needed to ensure that the MindSphere OS Bar and the Mendix Feedback widget are loaded correctly. You may need to set additional CSP settings if you make additional calls to other domains (for example, if you use Google maps from maps.googleapi.com).

    

15. Click Save to save these details.

16. Click Register to register your app with the MindSphere launchpad.

    If the app has not been pushed yet, there will be no route set up for the app and you will get an error message. This will be resolved once you have pushed your app to Cloud Foundry.

5.2.2 Setting Application Scopes in Developer Cockpit

To set up the appropriate scopes in MindSphere, do the following:

1. Go to Developer Cockpit > Authorization Management > App Roles from the MindSphere launchpad.
2. Enter the Scope Name.
3. Associate it with the MindSphere default roles USER and/or ADMIN. Or associate it with one of your self created MindSphere roles. MindSphere supports up to five application roles.

4. Click Save.

   

For an explanation of the relationship between Mendix roles and MindSphere roles, see section Roles & Scopes in MindSphere Module Details.

5.2.3 Assigning User Roles

Once you have created the scopes for your app, you will need to assign them to the users who you want to have access to the app.

1. Go to Settings > Roles from the MindSphere launchpad.

   

2. Choose the app role (scope) you want to assign from the list of Roles.

3. Click Edit user assignment.

4. Assign Available users to Assigned users using the assignment symbols (for example > to assign a user).

5. Click Close.

   

6 Development Considerations

See MindSphere Development Considerations for additional help on such things as:

• local testing
• multi-tenancy
• limitations