You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: tutorials/cp-mobile-backend-tools-fullstack-introduction/cp-mobile-backend-tools-fullstack-introduction.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Understand Full-Stack Development with Mobile Back-End Tools
3
3
description: Understand how SAP Mobile Services Mobile Back-End Tools (MBT) can solve common mobile offline challenges.
@@ -71,7 +71,7 @@ Therefore, usually MBT's central starting point is the metadata file, respective
71
71
72
72
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).
73
73
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):
Copy file name to clipboardExpand all lines: tutorials/cp-mobile-backend-tools-mdk-onboarding/cp-mobile-backend-tools-mdk-onboarding.md
+17-20Lines changed: 17 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,25 +58,22 @@ This step includes creating the mobile development kit project in the editor.
58
58
59
59
| Field | Value |
60
60
|----|----|
61
-
|`Service File Name`|`EpmCacheService`|
62
-
|`OData Source`| Select `Mobile Services` from the dropdown |
61
+
|`Data Source`| Select `Mobile Services` from the dropdown |
63
62
|`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**|
68
67
69
68
!
70
69
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**.
74
71
75
72
!
76
73
77
74
>In [this tutorial](cp-mobile-backend-tools-cache-db), server-side configuration for this MDK app was already done.
78
75
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.
80
77
81
78
[DONE]
82
79
[ACCORDION-END]
@@ -93,7 +90,7 @@ These are the metadata definitions available in the editor and the format in whi
93
90
94
91
-**`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.
95
92
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.
97
94
98
95
-**`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.
99
96
@@ -175,13 +172,15 @@ The procedure consists of an additional MDK Service for online communication, ad
175
172
176
173
[ACCORDION-BEGIN [Step 4: ](Create MDK Service for online and map rules)]
177
174
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.
181
176
182
177

183
178
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
+

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:
185
184
186
185
| Name | Value |
187
186
|----|-----|
@@ -193,16 +192,14 @@ The procedure consists of an additional MDK Service for online communication, ad
193
192
194
193
4. Expand folders **Actions**→ **Service**, right-click → **duplicate**``InitializeOffline.action`` and rename the copy to `InitializeOnline.action`.
195
194
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**.
6. Click `ClientRegistrationSet_CreateEntity.action` from folder `Actions` → `ClientRegistrationSet` to open the file.
201
200
202
201
7. Switch service to `/EpmCacheApp/Services/EpmCacheServiceOnline.service`
203
202
204
-
8. Uncheck `AuthorizedUser` and `ClientGUID`. They will be populated by the OData service.
205
-
206
203
9. Via **Object Browser**, locate and insert rule `RandomInt64.js` as value for `ClientId`. Alternatively you can paste `/EpmCacheApp/Rules/RandomInt64.js`
207
204
208
205
10. In **Headers** section, add the following entry:
@@ -224,7 +221,7 @@ To allow proper upload of a filter entity, modify `BusinessPartnerFilterSet_Crea
224
221
225
222
1. Click `BusinessPartnerFilterSet_Create.page` from **Pages** → `BusinessPartnerFilterSet` folder to open it with **MDK page Editor**.
226
223
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.
228
225
229
226
3. Via right-click, delete the `CountryFilter` and `FilterID` elements.
230
227
@@ -234,7 +231,7 @@ To allow proper upload of a filter entity, modify `BusinessPartnerFilterSet_Crea
0 commit comments