Setting Parameters in a Launchpad Configuration File

1. Create a configuration file containing your parameters.

A launchpad configuration file is a standard JSON file where you enter your parameters as name-value pairs.

For more information, see Creating a Launchpad Configuration File.

2. Upload the configuration file to the front-end server.

A launchpad configuration file must be located in a folder where it can only be edited by authorized users.

For more information, see Security Aspects for Launchpad Configuration Files

You can upload launchpad configuration files to the BSP repository or to the MIME repository. The advantage of the MIME repository is that it allows you to set a client cache expiry time, but it requires a few additional configuration steps: You need to provide access to a folder in the MIME repository by setting up an ICF node and an external alias.

For more information, see Uploading a Launchpad Configuration File to the BSP Repository or Uploading a Launchpad Configuration File to the MIME Repository.

3. Provide access to a folder in the MIME repository.

Since the launchpad configuration file is loaded to the client early in the startup process, it does not participate in the standard cache handling mechanism.

If you want to control how long a launchpad configuration file remains in the browser cache, you can upload it to a folder in the MIME repository, which allows you to set a client cache expiry time, and then set up an ICF node and an external alias to make the folder accessible under an allowed path.

You can skip this step if you store your launchpad configuration files in the BSP repository.

For more information, see Providing Access to a MIME Repository Folder.

4. Reference a launchpad configuration file.

For the settings in a launchpad configuration file to take effect, you must create a reference to this file.

For more information, see Referencing a Launchpad Configuration File.