Use your browser to open the SAP Cloud Platform Mobile Services Cockpit in your Cloud Foundry Trial environment.
Since there is no directly accessible link in the SAP Cloud Platform Cockpit,
it is recommended to store the Mobile Services cockpit URL as a bookmark in
your browser.
URL: https://mobile-service-cockpit-web.cfapps.eu10.hana.ondemand.com/
You
may be asked to provide your organization and space.
If there is more than one option, please choose the trial similar to the
screenshot.
The
Mobile Services Cockpit should open.
On the left-hand side, you see the menu to navigate through the various
options.
Click
on the “Features” menu item to open the available features that can be added to
a mobile app configuration.
Browse through the list and read some descriptions to understand what the
various features provide to you.
In
the next steps we will create a new mobile app configuration.
Select “Mobile Application” > “Native/Hybrid” from the left-hand menu. And
click “New” in the upper right corner.
Please note that there is also an “Import” feature that lets you import app
configurations from other Cloud Foundry spaces.
A dialog
will appear and ask you for certain global app parameters. Provide the values
as seen in the screenshot.
Mobile App configuration on Cloud Foundry will be physical apps on the platform
itself. Similar to a deployed Java application. You need respective quota to
create a mobile app. Also, the mobile app can be configured with individual
timeouts as any other Cloud Foundry based application.
Click “Save” to finish the creation of your mobile app configuration.
While
Mobile Services deploys your mobile app to your space you see a yellow
“Creating” indicator on the upper right-hand side of the screen. After a while,
and by refreshing the page the indicator will change to green and shows
“Started”.
Your app is ready to go, but you can’t do much at the moment with it. We need
to add more features to it.
The “Mobile Settings Exchange”
feature is automatically applied to all of your Cloud Foundry (CF) based mobile
apps. It’s a mandatory feature that is taking care of the app and user
registration process.
We
will now add more features to the application, so that our mobile app can
benefit from it.
Click on the “+” sign right to “Assigned features”. This will open a list of
available features – the same we already know from the “Feature” overview.
Choose “Mobile App Update” and click “OK”.
A
dialog will show up and want you to confirm that this change needs to restart
the app we have deployed into your CF space. Since we are in a development
environment we can simply select “Don’t show me again” and confirm.
After a few seconds the new feature will be added to your mobile app.
After
adding the feature, you will be directly sent to the feature specific settings
page for your mobile app configuration. You can see where you are currently on
the breadcrumb navigation on top of the screen.
Click on “com.sap.open.mobile” to navigate back to your app config overview.
Repeat
these steps to add all the features to our mobile app as seen on the
screenshot.
We need:
·
Mobile
App Update
·
Mobile
Client Log Upload
·
Mobile
Offline Access
·
Mobile
Connectivity
·
Mobile
Settings Exchange
Click
“Logs” under the “Analytics” menu to open the Event Log overview.
You see some information about what happened in the cockpit.
Click on the first row of the list to navigate to the details screen.
The
event details screen shows you more information about what happens in Mobile
Services – not only in the cockpit but also during you operate your mobile
apps. It’s the first thing you should check if the mobile app is not behaving
correctly.
It shows you also a list of related events, that help to identify the root
cause of many problems.
The event message will also contain hints on how to solve an error condition.
In our case, the information does not contain such a hint, since we do not see an
event of level “Error”.
Click
on “Server Data” in the left-hand menu to open the server statistics.
When you have more apps and more usage on the server you will see there the
data, that the server collects during runtime.
This is dummy text. It is not meant to be read. Accordingly, it is difficult to figure out when to end it. But then, this is dummy text. It is not meant to be read. Period.
ConversionConversion EmoticonEmoticon