Show TOC

Run Your Own Applications in the SandboxLocate this document in the navigation structure

The local sandbox environment for the SAP Fiori launchpad allows you to run your local SAP Fiori apps inside the SAP Fiori launchpad.

After you have created an SAPUI5 application project, the sandbox is available as part of the com.sap.ushell.ushell-lib library.

Configure the SAPUI5 Component to Be Embedded

You create a root component for the application. For an example, see /test-resources/sap/ushell/demoapp/FioriSandboxDefaultApp/Component.js).

The SAP Fiori launchpad sandbox comes with a default configuration file for the demo apps, which is stored under test-resources/sap/ushell/shells/sandbox/fioriSandboxConfig.js (deployed in jar file).

You can extend the default configuration by providing an additional configuration file under URL /appconfig/fioriSandboxConfig.json. Alternatively, you can provide the additional configuration file at another location on the same base URL (protocol, host and port) and refer to it with the URL parameter sap-ushell-sandbox-config. Your configuration changes override the default configuration.

Therefore, you set up a local Java Web server and deploy the configuration as an additional Web module. Create a local configuration file. For more information, see Creating a Local Configuration File.

Creating a Local Configuration File

Context

To create the configuration file, proceed as follows:

Procedure

  1. Create a new Web project using Start of the navigation path File Next navigation step New Next navigation step Dynamic Web Project End of the navigation path and use the project name appconfig.
  2. Create a file fioriSandboxConfig.json under the WebContent folder of the project.
  3. Edit the file as needed.
  4. Deploy appconfig on the local test server:
    1. Open the Servers view.
    2. Double-click the root node.
    3. Go to the Modules tab.
    4. Choose Add Web Module.
    5. Choose the appconfig project.
      Make sure that the path is called /appconfig.
    6. Restart the test server.