Skip to content

Commit a80462a

Browse files
Manuel-StamppManuel-Stampp
committed
Automatic commit: Move 'cp-mobile-backend-tools-cache-db', 'cp-mobile-backend-tools-fullstack-introduction', 'cp-mobile-backend-tools-mdk-onboarding', 'cp-mobile-backend-tools-simple-odata' from QA to Production
1 parent c8e75fa commit a80462a

27 files changed

Lines changed: 271 additions & 198 deletions

‎tutorials/cp-mobile-backend-tools-cache-db/cp-mobile-backend-tools-cache-db.md‎

Lines changed: 127 additions & 83 deletions
Large diffs are not rendered by default.

‎tutorials/cp-mobile-backend-tools-cache-db/img_sapms_new_app.png‎

-515 Bytes
Loading

‎tutorials/cp-mobile-backend-tools-cache-db/img_sapms_new_app_2.png‎

98.9 KB
Loading

‎tutorials/cp-mobile-backend-tools-fullstack-introduction/cp-mobile-backend-tools-fullstack-introduction.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Understand Full-Stack Development with Mobile Back-End Tools
33
description: Understand how SAP Mobile Services Mobile Back-End Tools (MBT) can solve common mobile offline challenges.
44
auto_validation: true
5-
time: 5
5+
time: 10
66
tags: [ tutorial>beginner, topic>mobile, products>sap-business-technology-platform, products>sap-mobile-services, products>sap-business-application-studio]
77
primary_tag: topic>mobile
88

@@ -71,7 +71,7 @@ Therefore, usually MBT's central starting point is the metadata file, respective
7171

7272
On the one hand, MBT provides runnable tasks that generate a database persistence or persistence descriptor (SQL), reflecting the whole OData model. On the other hand, MBT can build a transparent OData service [based on existing database tables](https://help.sap.com/doc/f53c64b93e5140918d676b927a3cd65b/Cloud/en-US/docs-en/guides/getting-started/mbt/existing-tables.html).
7373

74-
Different database types are supported depending on the runtime. Following databases may e.g. be used with the tools in certain environments (Derby and H2 only for testing, please refer to documentation and/or Product Availability Matrix for official support statements):
74+
Different database types are supported depending on the runtime. Following databases may e.g. be used with the tools in certain environments (Derby and H2 only for testing, please refer to [documentation](https://help.sap.com/doc/f53c64b93e5140918d676b927a3cd65b/Cloud/en-US/docs-en/guides/getting-started/mbt/service-generator.html#option-bind-db-typedb-name) and/or Product Availability Matrix for official support statements):
7575

7676
- SAP ASE
7777

‎tutorials/cp-mobile-backend-tools-mdk-onboarding/cp-mobile-backend-tools-mdk-onboarding.md‎

Lines changed: 17 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -58,25 +58,22 @@ This step includes creating the mobile development kit project in the editor.
5858

5959
| Field | Value |
6060
|----|----|
61-
| `Service File Name`| `EpmCacheService` |
62-
| `OData Source` | Select `Mobile Services` from the dropdown |
61+
| `Data Source` | Select `Mobile Services` from the dropdown |
6362
| `Mobile Services Landscape` | `standard` |
64-
| `Application Id` | As specified in the previous tutorial, e.g. `com.sap.MbtEpmDemo` |
65-
| `Destination` | As specified in the previous tutorial, e.g. `com.sap.MbtEpmDemo` |
66-
| `Language URL` | Delete field content |
67-
| `Enable Offline` | Leave **Yes** |
63+
| `Application Id` | As specified in the previous tutorial: `com.sap.MbtEpmDemo` |
64+
| `Destination` | As specified in the previous tutorial: `com.sap.MbtEpmDemo` |
65+
| `Enter a path to service` | Blank (leave it empty) |
66+
| `Enable Offline` | **Yes** |
6867

6968
!![MDK](img_template_service.png)
7069

71-
The generated application will be offline enabled in the MDK Mobile client.
72-
73-
8. In **OData Collections** step, select all collections. Click **Next** to complete the project creation.
70+
8. In **OData Collections** step, click **Select all data collections** → **Yes**.
7471

7572
!![MDK](img_template_collections.png)
7673

7774
>In [this tutorial](cp-mobile-backend-tools-cache-db), server-side configuration for this MDK app was already done.
7875
79-
9. After clicking **Next**, the wizard will generate your MDK Application based on your selections. You should now see the `EpmCacheApp` project in the project explorer.
76+
9. After clicking **Finish**, the wizard will generate your MDK Application based on your selections and open it in a new workspace. You should now see the `EpmCacheApp` project in the workspace.
8077

8178
[DONE]
8279
[ACCORDION-END]
@@ -93,7 +90,7 @@ These are the metadata definitions available in the editor and the format in whi
9390

9491
- **`DownloadOffline.action`** and **`UploadOffline.action`**: These actions are applicable to Mobile client only. Using app initialization, data is downloaded to the offline store. If you want to have the application download any updated data from the backend server or upload changed data to the backend server, these actions will be needed.
9592

96-
- **`InitializeOfflineSuccessMessage.action`**, **`IninitializeOfflineFailureMessage.action`** and other *Success* or *Failure* **Message actions**: These are messages showing up in the app on a successful or failure of data initialization, sync etc.
93+
- **`InitializeOfflineSuccessMessage.action`**, **`IninitializeOfflineFailureMessage.action`** and other *Success* or *Failure* *Message actions*: These are messages showing up in the app on a successful or failure of data initialization, sync etc.
9794

9895
- **`Main.page`**: This is the first page of your MDK application that is shown. For this application you will use this as a launching page to get to application functionality.
9996

@@ -175,13 +172,15 @@ The procedure consists of an additional MDK Service for online communication, ad
175172

176173
[ACCORDION-BEGIN [Step 4: ](Create MDK Service for online and map rules)]
177174

178-
1. Duplicate Service `EpmCacheService.service` and `.EpmCacheService.xml` via right-click → **duplicate** and rename them to `EpmCacheServiceOnline` keeping the corresponding endings.
179-
180-
2. Open `EpmCacheServiceOnline.service` and uncheck **Use Offline Store** and save.
175+
1. Duplicate Service `com_sap_MbtEpmDemo.service` and `.com_sap_MbtEpmDemo.xml` via right-click → **duplicate** and rename them to `com_sap_MbtEpmDemoOnline.service` and `.com_sap_MbtEpmDemoOnline.xml` keeping the corresponding endings.
181176

182177
![Duplicate files](gif_duplicate_service.gif)
183178

184-
3. Edit `EpmCacheService` to reflect the created rule for custom header. Therefore open `EpmCacheService.service`, expand **Headers** and enter the following:
179+
2. Open `com_sap_MbtEpmDemoOnline.service` and uncheck **Enable Offline Store** and save.
180+
181+
![Uncheck Enable Offline Store flag](img_service_uncheck_offline.png)
182+
183+
3. Edit `com_sap_MbtEpmDemo` to reflect the created rule for custom header. Therefore open `com_sap_MbtEpmDemo.service`, expand **Headers** and enter the following:
185184

186185
| Name | Value |
187186
| ---- | ----- |
@@ -193,16 +192,14 @@ The procedure consists of an additional MDK Service for online communication, ad
193192

194193
4. Expand folders **Actions** → **Service**, right-click → **duplicate** ``InitializeOffline.action`` and rename the copy to `InitializeOnline.action`.
195194

196-
5. Click it to open and switch **Service** to `EpmCacheServiceOnline.service`. Remove all the **Defining Requests**.
195+
5. Click it to open and switch **Service** through dropdown to `EpmCacheServiceOnline.service`. Remove all the **Defining Requests**.
197196

198197
![Create initialize online action](gif_action_initialize_online.gif)
199198

200199
6. Click `ClientRegistrationSet_CreateEntity.action` from folder `Actions` → `ClientRegistrationSet` to open the file.
201200

202201
7. Switch service to `/EpmCacheApp/Services/EpmCacheServiceOnline.service`
203202

204-
8. Uncheck `AuthorizedUser` and `ClientGUID`. They will be populated by the OData service.
205-
206203
9. Via **Object Browser**, locate and insert rule `RandomInt64.js` as value for `ClientId`. Alternatively you can paste `/EpmCacheApp/Rules/RandomInt64.js`
207204

208205
10. In **Headers** section, add the following entry:
@@ -224,7 +221,7 @@ To allow proper upload of a filter entity, modify `BusinessPartnerFilterSet_Crea
224221

225222
1. Click `BusinessPartnerFilterSet_Create.page` from **Pages** → `BusinessPartnerFilterSet` folder to open it with **MDK page Editor**.
226223

227-
2. Expand **Container Item** on the **Controls** pane and drag a list picker control it into the page.
224+
2. Expand **Container Item** on the **Controls** pane and drag a list picker control it into the existing section.
228225

229226
3. Via right-click, delete the `CountryFilter` and `FilterID` elements.
230227

@@ -234,7 +231,7 @@ To allow proper upload of a filter entity, modify `BusinessPartnerFilterSet_Crea
234231
| - | - |
235232
| Name | `CountryPicker` |
236233
| Caption | `Choose Country for subscription` |
237-
| `IsPickerDismissedOnSelection` | **true** |
234+
| Behavior → `IsPickerDismissedOnSelection` | **true** |
238235

239236
5. In **Data** section add three exemplary values for picker items (for which data exists in the referenced system)
240237

‎tutorials/cp-mobile-backend-tools-mdk-onboarding/gif_action_initialize_online.gif‎

-147 KB
Loading

‎tutorials/cp-mobile-backend-tools-mdk-onboarding/gif_duplicate_service.gif‎

68.3 KB
Loading

‎tutorials/cp-mobile-backend-tools-mdk-onboarding/img_1.10.png‎

-22.6 KB
Binary file not shown.

‎tutorials/cp-mobile-backend-tools-mdk-onboarding/img_1.2.png‎

-82.3 KB
Binary file not shown.

‎tutorials/cp-mobile-backend-tools-mdk-onboarding/img_1.3.png‎

-229 KB
Loading

0 commit comments

Comments
 (0)