Deploy and operate applications on Operator plan tenant

Two minor versions of the same application cannot be registered at the same time in MindSphere Gateway.
It is the recommended to use same appname and Space name.
You cannot update the application, with a version that has not been uploaded from the Developer Cockpit.
For detection, once the application is in "Deployed" state in Operator Cockpit, it is not possible to change the cf application name.
Create backing service before pushing the application.
Be aware, that deleting and redeploying the application might result in a different DNS-name by using random route.
Download the binaries the whole zip in an empty folder. Do not add new files to it. CF push uploads all files in the given path. That will be a problem with HTML applications, if you add or changes files i.e. pictures.
Extract also the folder structure of the Zip. This might be part of the CF path variable.
- “Appbinary.zip” includes the components of your CF application, which you target later using “cf push”.
- Ensure that AppBinary is extracted as a separate folder containing only the service components and does not include the icon or metadata file.
Operator needs to access the application in Operator Cockpit to check the deployment status.
Every application needs an own space.
After adding the roles to a user, this user needs to logoff and logon.
Prepare your business model as soon as possible before you publish it to the store.

Receiving an application from a developer is a three step process:

The Developer assigns the application to an Operator in the "Developer Cockpit".
The Operator confirms the receipt in the application catalog in the "Operator Cockpit".
The Developer grants the handover of the application in the "Developer Cockpit".

Navigate to the application details in your "Operator Cockpit" and select "Provisioning" tab.
Click "Add to customer".
Enter the tenant name and an e-mail address of your customer.

Note, that provisioning the application can take up to 5 minutes.