|
2 | 2 |
|
3 | 3 | _Running into problems or found a bug? Create an issue [**here**](https://github.com/abap2UI5/abap2UI5/issues)_ |
4 | 4 |
|
5 | | -Compatibility: R/3 NetWeaver AS ABAP, S/4 Private Cloud |
6 | | - |
7 | 5 | #### Key Features |
8 | | -* enables the integration of abap2UI5 Apps into SAP Fiori Launchpads (On-Premise) |
| 6 | +* integrate your abap2UI5 Apps into SAP Fiori Launchpads (On-Premise) |
| 7 | +* compatible with SAP Netweaver (v.7.30 or higher) or S/4 Private (Standard ABAP) |
9 | 8 | * the repository contains an UI5 App (BSP) and a HTTP Service for the communication with abap2UI5 |
10 | 9 | * the abap2UI5 apps and the framework's functionality remain unaltered |
11 | | -* the integration is compatible with SAP Netweaver (v.7.50 or higher) or S/4 Private (Standard ABAP) |
12 | 10 | * installation can be performed using [**abapGit**](https://abapgit.org)  |
13 | 11 |
|
14 | 12 | #### Functionality |
| 13 | +An UI5 app (BSP Application) is installed with abapGit which can be added multiple time as a tile to your launchpad. Each tile can start a different abap2UI5 app: <br> |
15 | 14 | <img width="800" alt="Bildschirmfoto 2023-12-26 um 11 31 11" src="https://github.com/abap2UI5/abap2UI5-launchpad_on_premise/assets/102328295/6c4b5977-61ec-40e9-a246-b223387666d5"> |
16 | 15 | <img width="700" alt="image" src="https://github.com/abap2UI5/ext-fiori_launchpad_on_premise/assets/102328295/17c375e8-10cd-471e-83f8-d62ed27224e3"> |
17 | 16 |
|
18 | 17 | #### Installation |
19 | | -After the installation with abapGit, three ICF nodes are created (1) HTTP Service and (2)(3) for the UI5 App. Check in transaction SICF if they are available and activated. Launch the UI5 app from this provided node:<br> |
20 | | -<img width="500" alt="image" src="https://github.com/abap2UI5/abap2UI5-proxy_app_launchpad/assets/102328295/93567dbe-dcd3-4487-b78a-1d4dd21a0c8d"><br> |
21 | | -<img width="800" alt="Bildschirmfoto 2024-03-28 um 10 30 46" src="https://github.com/abap2UI5/abap2UI5-proxy_app_launchpad/assets/102328295/dfcf0ca3-c2e5-4feb-a01c-f818a8e108e3"> |
22 | | - |
23 | | -For more installation guidelines, check out this [**link.**](https://github.com/abap2UI5/abap2UI5-documentation/blob/main/docs/ext-fiori_launchpad_integration/installation.md) Use this app for the launchpad integration as described [**here.**](https://github.com/abap2UI5/abap2UI5-documentation/blob/main/docs/ext-fiori_launchpad_integration/configuration.md) |
24 | | - |
25 | | -#### Parameters |
26 | | -Maintain the following start parameters: |
27 | | -| Name | Explanation | |
28 | | -| ------------- | ------------- | |
29 | | -| APP_START | classname of the app for the initial call | |
30 | | -| APP_TITLE | title which is set via frontend (optional) | |
| 18 | +Check out the following guidelines: <br> |
| 19 | +[**(1) Installation with abapGit**](https://github.com/abap2UI5/abap2UI5-documentation/blob/main/docs/ext-fiori_launchpad_integration/installation.md) <br> |
| 20 | +[**(2) Configuration of the Launchpad**](https://github.com/abap2UI5/abap2UI5-documentation/blob/main/docs/ext-fiori_launchpad_integration/configuration.md) <br> |
| 21 | +[**(3) Setup Startup Parameters & Title**](https://github.com/abap2UI5/abap2UI5-documentation/blob/main/docs/ext-fiori_launchpad_integration/startup_params.md) <br> |
31 | 22 |
|
32 | | -_If your classname is developed in a custom namespace, use -NS-CL_MY_CLASS instead of /NS/CL_MY_CLASS, "-" is mapped to "/" automatically_ |
33 | 23 | #### FAQ |
34 | 24 | * check out the [**documentation**](https://github.com/abap2UI5/abap2UI5-documentation) for installation & configuration guidelines |
35 | 25 | * your comments, questions, wishes and bugs are welcome, please create an [**issue**](https://github.com/abap2UI5/integration-fiori_launchpad_on_premise/issues) |
0 commit comments