Create a new application

MindSphere Cloud Foundry applications are hosted in Cloud Foundry space provided by MindSphere whereas the self hosted application feature is tenant specific. To create self hosted applications in Developer Cockpit, a tenant should have subscriptions for the self hosting attribute.

Prerequisites for creating self hosted applications

The following requirements apply for integrating your self-hosted application into MindSphere:

  • You have the Outbound Traffic Upgrade (Contact Sales for this upgrade).

  • Your self-hosted application is reachable via DNS and a valid SSL certificate (self-signed certificates are not allowed).

  • Your self-hosted application exposes one health endpoint for MindSphere's internal monitoring.

  • Your self-hosted application uses the MindSphere Identity Management.

  • Your self-hosted application is registered in the MindSphere Gateway.

Procedure

The instructions for creating new applications are described below:

  1. Login to Developer Cockpit.

  2. Select "Dashboard" on the start screen. Click on “Create new application”.

    118830703883.png
  3. Enter the field parameters.

    129010237323.png

    For MindSphere Cloud Foundry infrastructure, provide Cloud Foundry URL in the components section.

    For self hosted applications, the "Cloud Foundry Direct URL" will be replaced with "Direct URL" in the "Components" section.

    129010377483.png

    For mobile type of applications, the backend component can be hosted in either of the following infrastructure:

    • MindSphere Cloud Foundry

    • Self hosted

    • The mobile type might not have a backend at all

    129010671243.png

    NOTE

    For all applications, the application has a default mobile icon. You can override your own application logo/ icon.

  4. Add at least one component to your application, if the application is a CF or self hosted based application.

    If your application has no backend component, then select "Not applicable" under "Infrastructure". In this case, the "Components" field will be disabled. Application validation is needed only if the mobile application type has a backend component.

    For more information on adding components, see Components for applications.

  5. For CF and self hosted applications: The configurations, by default, are set with a content-security policy header and cache control. Both the keys are set to a default value. You can change if required, but the content-security policy header supports only up to 1000 characters while the cache control can be defined up to 255 characters.

    For mobile applications: Enter the app link and the universal link configuration information for "Android" and "iOS" respectively as per the specified format. For more information on configurations, refer Configurations for applications.

  6. Save your application.

To make the application available on the Dashboard of Developer Cockpit, refer to Availability of newly created applications in Dashboard.