A launchpad configuration file is a JSON file. The format of this file is described in this section.
The file name of a launchpad configuration file must contain at least one character and have the extension .json.
The following characters are allowed in the file name:
The content of a launchpad configuration file must comply with the JSON format.
The following example shows the content of a launchpad configuration file:
{ "documentation" : { "description" : "This launchpad configuration file disables personalization", "configURL" : "https://<host>:<port>/sap/bc/ui5_ui5/ui2/ushell/shells/abap/cfg/sap/<myconfig>.json", "startupURL" : "https://<server>:<port>/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html?sap-client=<client>&sap-ushell-config-url=cfg/sap/<myconfig>.json", "localStartupURL" : "http://localhost:8080/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html?sap-ushell-config-url=cfg/sap/<myconfig>.json" }, "renderers": { "fiori2" : { "componentData": { "config": { "enablePersonalization": false, "enableSetTheme": false } } } } }
Parameters can be nested. In the example above, the parameter enablePersonalization is nested in the path .
In the example above, the documentation parameter as well as the parameters nested within it are used for documentation purposes only. These parameters are not evaluated by the system. You can delete this section if you do not need it.
After creating a launchpad configuration file, you can upload it to the front-end server. For more information, see Uploading a Launchpad Configuration File to the BSP Repository or Uploading a Launchpad Configuration File to the MIME Repository.