Components for applications

Components for Cloud Foundry applications

A component represents a single micro service but is not limited to this. It is recommended to have one component for each Cloud Foundry application and each component can have multiple endpoints. However, it is mandatory to have a minimum of one component with one endpoint for an application.

Depending on the complexity of your application, you can add multiple components. You can add one for the frontend and one for the backend as shown in the following figure:

138245082507.png

Component name

Cloud foundry direct URL

Add component

Move component

Delete component

Edit endpoint

Add new endpoint

The URL of a Cloud Foundry application must always end with "mindsphere.io".

NOTE

  • The "Name" field of the application supports only lower-case letters.

  • The component name should be same as the application name in the .yml file.

Accordingly, the name your application in the manifest file, or during the push operation. Otherwise, the automatic registration on an Operator tenant will fail.

Components for self hosted applications

For self hosted applications, it is mandatory to have at least one component for the application and each component can have multiple endpoints. If required, an application can have multiple components.

138245555211.png

Component name

Direct URL

Add component

Move component

Delete component

Edit endpoint

Add new endpoint

NOTE

The URL of a self hosted application must not end with "mindsphere.io".

Adding, editing and deleting of components

For adding endpoints, click the134919114507.png button.

134919728011.png

You can manage the endpoints by using "Edit" or "Delete" buttons.

134918012427.png

You can add arbitrary paths including wildcards here except /api, as this is reserved for calling MindSphere APIs from the browser client of your application.

The mapping matches URLs using the following rules:

  • ?matches one character

  • **matches zero or more directories in a path

  • a specific path, e.g./machines

  • a path with wildcard/machines/*

  • a patch with general wildcard/**that matches also zero or more sub paths

Examples

/machines/drill-? matches machines/drill-1 but also machines/drill-2 or machines/drill-a

/monitoring/machines/drill-* - matches all drill-* endpoints in the /monitoring/machines endpoint

/machines/**/list matches all list endpoints underneath the /machines path

Matching Order

The MindSphere Gateway selects the first matching endpoint based on the request URL. Currently, there is no proximity matching available.