Introduction

MindSphere enables developers to create and manage applications within MindSphere platform and use various services. The MindAccess Developer Plan includes Cloud Foundry Compute Resources for developing applications using various buildpacks.

Overview of Developer Cockpit

Developer Cockpit helps developers to manage their applications developed on the platform. In MindSphere context, an application may consist of multiple Cloud Foundry, Self Hosted and mobile applications with multiple endpoints.

To make the distinction easier, we are using the term component for Cloud Foundry, Self Hosted and mobile type applications and applications developed (with CF and self hosted) for combining one or more components. The applications need to be registered on the platform in order to be accessible from outside.

The platform service that manages these registrations is called MindSphere Gateway and only the registered applications are allowed to be accessed. The components define the locations and paths of the microservices implementing the web applications or services.

Functions and benefits

The path values need to match at MindSphere Gateway and the corresponding component. See the Developer Documentation for possible mappings of gateway to component paths.

Developer Cockpit provides the following functionalities:

  • Create, configure and upload standard and Fleet Manager plugin applications.

  • Transfer applications to the production environment.

  • Overview of developed applications.

  • Configure applications, e.g. "Application Icon" or "Display Name".

  • Secure applications at the endpoint level.

  • Bring applications to Launchpad of MindAccess Developer Plan.

  • Manage application specific roles.

  • Promote and transfer applications from developer to productive environment.

MindSphere uses a multi-layered security concept that supports developers by securing their applications using application specific roles, referred to as "Scopes" in this document.

Developers need to define at least two application specific roles and an application specific scope in order to protect their application from being accessed by unauthorized users.